|
|
|
08-13-2022, 07:53 AM
|
#1
|
Human being with feelings
Join Date: Jun 2009
Location: Germany, Slovenia, Croatia
Posts: 53
|
[6.xx macOS-arm64] 55/20 ms latency readout with built in IO MBP 16" M1Max
Applies to all arm64-Versions since I installed on the machine in April 2022 up to 6.65.
I am getting a confusing latency readout in an empty Reaper session compared to e. g. LPX or Live on a Macbook Pro 16" M1Max with built in standard IO. This has been on macOS 12.4.x and is on macOS 12.5 alike.
• Create an aggregate device with Mic as input and Speaker as output
• Choose the device as audio device
Reaper:
48 kHz 24 bit WAV: 1/2ch 128spls ~55/20ms
LPX:
48 kHz 24 bit BWF: 11,0 ms Roundtrip (5,7 ms Output)
Live 11.1.6:
48 kHz 24 bit AIFF: Input 2,67 ms, Output 5,67 ms, Global 8,33 ms
I have no idea what Reaper measures here. Is it just reporting wrong values ? I have the feeling it makes me look stupid…
Justin, Shwa, any hint in this department ?
|
|
|
08-13-2022, 09:21 PM
|
#2
|
Human being with feelings
Join Date: Oct 2006
Location: Michigan
Posts: 184
|
so in this case, I believe REAPER is actually reading correctly. the apple DSP used for the speaker playback actually adds significant latency. if you switch to headphones you'll notice the latency drop by alot
|
|
|
08-14-2022, 01:56 AM
|
#3
|
Human being with feelings
Join Date: Jun 2009
Location: Germany, Slovenia, Croatia
Posts: 53
|
Quote:
Originally Posted by Magoostus
…the apple DSP used for the speaker playback actually adds significant latency.…
|
This reasoning does not make sense. If three Apps use the exact same I/O-CoreAudio-Device then all properties of that device should reflect in the DAW latency readings.
Or why should the macOS loudspeaker DSP only be present in Reaper and not the others ?
|
|
|
08-14-2022, 06:23 AM
|
#4
|
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
I think it (core audio on macos 12+) might be doing echo cancellation or something. Maybe there’s some way for us to open the core audio devices with that bypassed, but I haven’t found it yet :/
|
|
|
08-15-2022, 02:42 AM
|
#5
|
Human being with feelings
Join Date: Jan 2009
Location: Montreal, Canada
Posts: 170
|
With a 14" MacBook Pro (M1 Pro), macOS 13 (22A5321d) and Reaper 6.65, I'm getting "~35/20ms" at 128 samples.
|
|
|
08-15-2022, 01:53 PM
|
#6
|
Human being with feelings
Join Date: Oct 2006
Location: Michigan
Posts: 184
|
ya i just checked and logic is reading the latency incorrectly on my m1 macbook air speakers, reaper is correct, I can't get less than 23msec of latency with a buffer size of 15 samples, and it definitely feels like 23msec on both logic and reaper
Last edited by Magoostus; 08-15-2022 at 02:01 PM.
|
|
|
08-16-2022, 08:15 AM
|
#7
|
Human being with feelings
Join Date: Jun 2009
Location: Germany, Slovenia, Croatia
Posts: 53
|
Adding Bitwig Studio:
2,67 ms
So three DAWs - Logic, Live and Bitwig - report consistent latency - whereas Reaper has different results. Either Reaper is wrong, because three Apps are consistent, or the other DAWs are miscalculating. Ok, I could try to do a measurement, but am lacking time to evaluate an appropriate test environment.
Wouldn't it make sense, Justin, to reach out about that to the other developers ? I mean that could be enlighting, couldn't it ? Shouldn't there be info on the DSP for the loudspeakers in the Apple developer department ? It is clear that there must be DSP just to provide means to decode Dolby Atmos audio streams on the speaker system.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:31 AM.
|