Milliseconds Measured in Counter
Moderator: James Steele
Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
-
- Posts: 746
- Joined: Wed Sep 19, 2007 1:48 pm
- Primary DAW OS: Unspecified
Milliseconds Measured in Counter
This may be a dumb question, but...
I'm trying to measure latency at different buffers and plug-ins with my setup.
I zoom way-in on peaks in the waveform editor and compare the input and output tracks.
I have the counter set to real-time.
The last part of the counter's four measurements (hours, minutes, seconds, ???).
The ??? part is; am I measuring milliseconds there, or, milliseconds x 10 ????
Thanks!
I'm trying to measure latency at different buffers and plug-ins with my setup.
I zoom way-in on peaks in the waveform editor and compare the input and output tracks.
I have the counter set to real-time.
The last part of the counter's four measurements (hours, minutes, seconds, ???).
The ??? part is; am I measuring milliseconds there, or, milliseconds x 10 ????
Thanks!
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.03, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro
Re: Milliseconds Measured in Counter
Hello,
If your counter is showing 00:00:00.00 then yes the least significant readout is seconds. As in 00.00 seconds (two decimal places or in hundredths of a second.
For more accurate reading use samples. 44.1 samples = 1 millisecond @ 44.1K or .00002267 seconds / sample.
At 96k = .000010416667 seconds or 96 samples / 1 millisecond.
I always use samples when testing latency.
If your counter is showing 00:00:00.00 then yes the least significant readout is seconds. As in 00.00 seconds (two decimal places or in hundredths of a second.
For more accurate reading use samples. 44.1 samples = 1 millisecond @ 44.1K or .00002267 seconds / sample.
At 96k = .000010416667 seconds or 96 samples / 1 millisecond.
I always use samples when testing latency.
It's the ear, not the gear!
MacPro 2.66 gHz 12 core (dp 10.01) - Lynx Aurora16 - OS 10.12.6/WaveArts/TruePianos - Legend 32ch console - G16 Fostex
(2) MacPro 2.66 gHz 12 core (DP 9.5) OS 10.12 - 24 I/O - 2408 mk2 - Da7- (PT 12) - 8 trk MCI
MacPro 2.66 gHz 12 core - OSX 10.12 - Genesys Black - Lynx Aurora16 - waves - Oxford - McDSP - 16 trk Otari - analog sweetness
MacPro 2.66 gHz 12 core (dp 10.01) - Lynx Aurora16 - OS 10.12.6/WaveArts/TruePianos - Legend 32ch console - G16 Fostex
(2) MacPro 2.66 gHz 12 core (DP 9.5) OS 10.12 - 24 I/O - 2408 mk2 - Da7- (PT 12) - 8 trk MCI
MacPro 2.66 gHz 12 core - OSX 10.12 - Genesys Black - Lynx Aurora16 - waves - Oxford - McDSP - 16 trk Otari - analog sweetness
-
- Posts: 746
- Joined: Wed Sep 19, 2007 1:48 pm
- Primary DAW OS: Unspecified
Re: Milliseconds Measured in Counter
Hey thanks you for that!
I'll do it your way!
I'll do it your way!
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.03, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro
-
- Posts: 746
- Joined: Wed Sep 19, 2007 1:48 pm
- Primary DAW OS: Unspecified
Re: Milliseconds Measured in Counter
I'm still a little confused.
If the difference between two events is 1,890 samples, and I'm at 48k, how many milliseconds latency is there?
That is, a peak in track 1 was at 6778766 samples, and the the same peak in track 2 was at 6780656 samples, according to DP's counter set to "samples"?
If the difference between two events is 1,890 samples, and I'm at 48k, how many milliseconds latency is there?
That is, a peak in track 1 was at 6778766 samples, and the the same peak in track 2 was at 6780656 samples, according to DP's counter set to "samples"?
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.03, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro
Re: Milliseconds Measured in Counter
25.4JSmith1234567 wrote: how many milliseconds latency is there?
2018 Mini i7 32G 10.14.6, DP 11.3, Mixbus 9, Logic 10.5, Scarlett 18i8
-
- Posts: 746
- Joined: Wed Sep 19, 2007 1:48 pm
- Primary DAW OS: Unspecified
Re: Milliseconds Measured in Counter
YOUCH !!!!!!!!!!!!!!!!!!!!bayswater wrote:25.4JSmith1234567 wrote: how many milliseconds latency is there?
OSX Big Sur (latest). Mac Pro Late 2013 ("trash-can"), 3.5 Ghz 6-Core Intel XeonE5, 64GB RAM. Motu DP 11.03, Vienna Pro Server, Presonus Notion, Osculator, Keyboard Maestro