I am having problems similar to the others posting here so I am including it. Here is my hardware:
win10 pro 18363 1909
focusrite Scarlet i2i 3rd gen - 1605 4.65.5
jamkazam 1.0.3794 after update
Using only the focusrite driver software I change the buffersize to 128 and it works fine with other audacity and other products.
I stop the other products, start jamkazam and connect to focusrite usb asio-asio.
When I "add gear" the buffersize shows 240, samp rate=48000
latency 20.92ms (always exactly)
I select the ASIO setup and change to buffsize 128. The Focusrite driver shows 128
Moving ahead Jamkazam returns the buffsize to 240 and the high latency (20.92) persists.
pu$ng resync does not help
It appears that Jamkazam (and not the driver) insists on returning the buffsize to 240.
I don't have this problem with jamulus or other software.
Thanks
Fritz
I am posting the Focusrite response to the above issues with the 2i2 so that others can use it. Apparently these are the gyrations required to get the Focusrite to reset the buffersize. It worked for me.
----Fritz
==============================================================================
here's an additional buffer size setting in JamKazam that it's worth trying.
- Click "Manage" in the top left corner of the screen
- Audio Settings > Audio Booster
- Reduce the "Frame Size" down to either 1ms or 2ms
This will in turn reduce the buffer size in the Focusrite Notifier Settings panel.
============================================
win10 pro 18363 1909
focusrite Scarlet i2i 3rd gen - 1605 4.65.5
jamkazam 1.0.3794 after update
Using only the focusrite driver software I change the buffersize to 128 and it works fine with other audacity and other products.
I stop the other products, start jamkazam and connect to focusrite usb asio-asio.
When I "add gear" the buffersize shows 240, samp rate=48000
latency 20.92ms (always exactly)
I select the ASIO setup and change to buffsize 128. The Focusrite driver shows 128
Moving ahead Jamkazam returns the buffsize to 240 and the high latency (20.92) persists.
pu$ng resync does not help
It appears that Jamkazam (and not the driver) insists on returning the buffsize to 240.
I don't have this problem with jamulus or other software.
Thanks
Fritz
I am posting the Focusrite response to the above issues with the 2i2 so that others can use it. Apparently these are the gyrations required to get the Focusrite to reset the buffersize. It worked for me.
----Fritz
==============================================================================
here's an additional buffer size setting in JamKazam that it's worth trying.
- Click "Manage" in the top left corner of the screen
- Audio Settings > Audio Booster
- Reduce the "Frame Size" down to either 1ms or 2ms
This will in turn reduce the buffer size in the Focusrite Notifier Settings panel.
============================================