Rudolf Cornelissen

So, as I said (hope you saw the modification I did to my msg, as I had the enabled<>disabled texts reversed) that with small buffers enabled the situation is at it was with 3.5.0, and with small buffers disabled the 64 samples sound vol increases to that of the 128 samples volume. I just did a quick test with Audacity, with the amplification effect, based on my hearing for comparison: I expect the volume steps to be around 3dB, which should be audible for most people outthere. so if we take 128 samples...

Hi Volker, With 3.5.1 with small network buffers -enabled- the situation has not changed. 64 samples is lowest volume, 128, mid, and 256 highest volume. With small network buffers -disabled- it's different: 64 and 128 samples are now both 'mid' volume (so same as 128 before), and 256 is still highest volume (same as before). Thanks for the amazing software BTW! PS: I modified this message, had it reversed noted before. Sorry. So: enabled has old situation, disabled small buffers brings 64 samples...

Hi Volker, With 3.5.1 with small network buffers -disabled- the situation has not changed. 64 samples is lowest volume, 128, mid, and 256 highest volume. With small network buffers -enabled- it's different: 64 and 128 samples are now both 'mid' volume (so same as 128 before), and 256 is still highest volume (same as before). Thanks for the amazing software BTW!

Hi all, I'm also using Jamulus since a week or two. My conclusion with this low volume thing is that the audio stream volume from client to server is influenced by the buffer delay setting: the lower the buffer, the lower also the volume. That, of course, should not be. I'd say this is a simple to fix fault in Jamulus..? As a not so nice workaround you can increase this setting but of course your latency will increase as well.. BTW I'm using ASIO4ALL with Realtek HDA (onboard). I guess I should try...

Hi all, I'm also using Jamulus since a week or two. My conclusion with this low volume thing is that the audio stream volume from client to server is influenced by the buffer delay setting: the lower the buffer, the lower also the volume. That, of course, should not be. I'd say this is a simple to fix fault in Jamulus..? As a not so nice workaround you can increase this setting but of course your latency will increase as well.. BTW I'm using ASIO4ALL with Realtek HDA (onboard). I guess I should try...

Hi all, I'm also using Jamulus since a week or two. My conclusion with this low volume thing is that the audio stream volume from client to server is influenced by the buffer delay setting: the lower the buffer, the lower also the volume. That, of course, should not be. I'd say this is a simple to fix fault in Jamulus..? As a not so nice workaround you can increase this setting but of course your latency will increase as well..

Hi all, I'm also using Jamulus since a week or two. My conclusion with this low volume thing is that the audio stream volume from client to server is influenced by the buffer delay setting: the lower the buffer, the lower also the volume. That. of course, should not be. I'd say this is a simple to fix fault in Jamulus..? As a not so nice woraround you can increase this setting but of course your latency will increase as well..

Creative Geforce 2 Titanium problem