Hey folks. I've noticed a curious volume issue when connecting to my private server running v3.5.2 under Windows 10. In a nutshell, I have Jamulus client settings set at: audio quality High, buffer delay 64, auto jitter buffers, mono audio channels, and 'enable small network buffers' off. Using Focusrite ASIO (latest beta driver). After connecting to the private server, I note that the volume of my guitar is rather low. If I turn on 'enable small network buffers' then immediately turn it off, my guitar volume jumps by several dB. This issue only happens when using a buffer delay of 64, not 128, etc.
I read through the Github issue, 'Audio level changes if Buffer Delay is changed #106' at https://github.com/corrados/jamulus/issues/106, which appears to only fix the issue for buffer delays of 128 to 256 in v3.5.1? It's not clear if a buffer delay of 64 is addressed.
Am wondering if anyone else is experiencing this issue?
-Al
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I spoke a guy yesterday who had the same problem, he was (also) using a Jamulus server under Windows 10 and the Jamulus client on the same pc. The problem was gone if he connected to someone else's (public) server.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Coming back to this issue. I have tried to reproduce this with my setup but I cannot. The audio level stays about the same. Can you please try again if this issue is still there with the newest Jamulus version?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Volker. At the time of initial reporting, I was using a 1st gen Focusrite Scarlett 6i6 USB interface with beta Focusrite USB driver version 4.64.15.598. The beta driver was used to fix an issue with Scarlett interfaces that got stick at 136 buffer - see https://github.com/corrados/jamulus/issues/53.
I noticed that the Focusrite 4.64.15.598 beta driver is no longer available at http://beta.focusrite.com/ and a newer non-beta driver is avaialble in their customer portal - Windows: Scarlett Mix Control 1.10 + USB Driver 4.65.5.
I no longer use a Scarlett interface (sold it to a friend) and have since upgraded to a newer MOTU M2. I don't experience any audio level changes with the MOTU M2 when switching 'Enable Small Network Buffers' on/off. I also have no idea if Scarlett interfaces experience this issue. Perhaps other Scarlett users can pipe in and let us know if they encounter this issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your feedback. If the issue is audio hardware related then I think it is not a problem of the Jamulus software but of the hardware driver. So I will close the Issue on Github then. If you have this Issue again, just let me know and I re-open the Issue on Github.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey folks. I've noticed a curious volume issue when connecting to my private server running v3.5.2 under Windows 10. In a nutshell, I have Jamulus client settings set at: audio quality High, buffer delay 64, auto jitter buffers, mono audio channels, and 'enable small network buffers' off. Using Focusrite ASIO (latest beta driver). After connecting to the private server, I note that the volume of my guitar is rather low. If I turn on 'enable small network buffers' then immediately turn it off, my guitar volume jumps by several dB. This issue only happens when using a buffer delay of 64, not 128, etc.
I read through the Github issue, 'Audio level changes if Buffer Delay is changed #106' at https://github.com/corrados/jamulus/issues/106, which appears to only fix the issue for buffer delays of 128 to 256 in v3.5.1? It's not clear if a buffer delay of 64 is addressed.
Am wondering if anyone else is experiencing this issue?
-Al
Have you tried mono-in/stereo-out - it helped in our band; not a very scientific answer, I know, but worth a try if you did not change that, yet
I spoke a guy yesterday who had the same problem, he was (also) using a Jamulus server under Windows 10 and the Jamulus client on the same pc. The problem was gone if he connected to someone else's (public) server.
I have created a Github Issue: https://github.com/corrados/jamulus/issues/169
Wonderful! Thanks Volker.
-Al
Coming back to this issue. I have tried to reproduce this with my setup but I cannot. The audio level stays about the same. Can you please try again if this issue is still there with the newest Jamulus version?
Hi Volker. At the time of initial reporting, I was using a 1st gen Focusrite Scarlett 6i6 USB interface with beta Focusrite USB driver version 4.64.15.598. The beta driver was used to fix an issue with Scarlett interfaces that got stick at 136 buffer - see https://github.com/corrados/jamulus/issues/53.
I noticed that the Focusrite 4.64.15.598 beta driver is no longer available at http://beta.focusrite.com/ and a newer non-beta driver is avaialble in their customer portal - Windows: Scarlett Mix Control 1.10 + USB Driver 4.65.5.
I no longer use a Scarlett interface (sold it to a friend) and have since upgraded to a newer MOTU M2. I don't experience any audio level changes with the MOTU M2 when switching 'Enable Small Network Buffers' on/off. I also have no idea if Scarlett interfaces experience this issue. Perhaps other Scarlett users can pipe in and let us know if they encounter this issue?
Thanks for your feedback. If the issue is audio hardware related then I think it is not a problem of the Jamulus software but of the hardware driver. So I will close the Issue on Github then. If you have this Issue again, just let me know and I re-open the Issue on Github.