05-18-2020, 08:17 PM
as mabalot said earlier "Mac users can change their frame size in JK. Go to Manage (at the top left corner in the app) - Audio Setting - Audio Booster then change your frame size to 1ms experimental."
The "Manage" tool is in the very top left corner of the JK app - it is there in both Mac and Windows versions
The Audio Frame Size is similar to setting the audio buffer size.
We have been using this with our quartet - me on Mac and the others on Windows.
I can lower the Frame Size to the 1 ms experimental setting and get a 6.8ms audio latency using a Behringer UMC404HD on my 2012 MacBookPro running OSX 10.11.6 (the default Frame Size was 2.5ms and gave an audio latency of 9.8)
The problem with the lower Frame (buffer) size is that it can increase the jitter to unacceptable levels - the audio is garbled and has pops and clicks - I am the only one who can use the 1ms experimental frame size successfully.
One of our members uses a new Scarlet 2i2 - JK shows him as zero audio latency - he found a reference that the Scarlet interface somehow interferes with JK measurement of audio latency and thus it returns a zero value - so the zero might not be true.
That has been our experience - hope it might help
The "Manage" tool is in the very top left corner of the JK app - it is there in both Mac and Windows versions
The Audio Frame Size is similar to setting the audio buffer size.
We have been using this with our quartet - me on Mac and the others on Windows.
I can lower the Frame Size to the 1 ms experimental setting and get a 6.8ms audio latency using a Behringer UMC404HD on my 2012 MacBookPro running OSX 10.11.6 (the default Frame Size was 2.5ms and gave an audio latency of 9.8)
The problem with the lower Frame (buffer) size is that it can increase the jitter to unacceptable levels - the audio is garbled and has pops and clicks - I am the only one who can use the 1ms experimental frame size successfully.
One of our members uses a new Scarlet 2i2 - JK shows him as zero audio latency - he found a reference that the Scarlet interface somehow interferes with JK measurement of audio latency and thus it returns a zero value - so the zero might not be true.
That has been our experience - hope it might help