In my case - the volume produced by Jamulus is very low (quiet).
Other programs running on the same PC produce reasonable/high volume... no problem.
This is true for both Internal Speakers output and when working with earphones.
This is on Windows 10, jamulus 3.4.5, and using the PC native sound system (no external soundcard),
and after joining (for testing) a number of "rooms"/servers in the central-server list.
Any idea what can be done about it?
Is there a way to make jamulus to up the volume produced?
Thanks!
Ari
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having this issue too. I am using Mac and using a Soundcraft UI24r as my interface with Jamulus 3.4.5. I have a private server setup and people can connect. There volume is very queit and they say I sound muffled. just very quiet.
I am not sure where I am going wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you please check the following:
- What is the position of the Pan fader in the Jamulus main window? It should be in the middle.
- Have you selected the correct input channel in the Jamulus settings dialog below the Device setting?
- Is your mixer fader on the right side in the Jamulus main windows at maximum?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys. I just joined and was having this same problem and this resovled it for me. Go into Settings and change the 'Audio Channels' from Mono to Stereo. Volume is now super loud! I guess it was splitting the two signals coming in across a mono channel.
Yes and yes, thanks....The problem is intermittent, I suspect that it has to do with delay time...if too much laggging time, then no sound, but this doesn't seem to be consistent either...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 another soundcard as a double check the fault is not -there-.. Oh, though a friend of mine uses an USB Behringer interface, and from his description, I think he also suffers from the above noted effect.
Last edit: Rudolf Cornelissen 2020-04-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I also found that 64 is quieter than 128, and 256 is louder that 128. This was using 3.5.0 client on a Macbook with a UMC404HD, and talking via my own 3.5.0 server on AWS. Not sure why the change in volume, but maybe needs investigating. I assume it's something to do with the codec.
Last edit: Tony Mountifield 2020-04-18
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will soon release a new version of Jamulus which includes an updated OPUS package. Let's see if the issue is still present with that new OPUS version.
BTW: I could not reproduce this issue on my PC.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 volume up to 128.
Rudolf.
Last edit: Rudolf Cornelissen 2020-04-19
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you tell approx. how many dB the signal is louder? If you just say it is louder it may 0.1 dB which can only be heard by experts or it may be 10 dB which would be very noticable, e.g.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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 to be the 'normalized' volume: 256 samples increases the volume with 3dB, and 64 samples, when on small buffers, lowers the volume with 3dB.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BTW I'm using ASIO4ALL with Realtek HDA (onboard). I guess I should try another soundcard as a double check the fault is not -there-.. Oh, though a friend of mine uses an USB Behringer interface, and from his description, I think he also suffers from the above noted effect.
Ok, I can reproduce the issue with my Lexicon Omega audio card as well. I just did not notice this issue before. I created an Iusse at Github: https://github.com/corrados/jamulus/issues/106
We should follow up our discusson there now instead of posting it here in this thread.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We started using Jamulus in our choir some days ago. Most of our members are using Windows 7 or 10 with onboard soundcards, basic 3.5mm-jack earplug+mic, and Asio4All (I'm using Linux, so my chances to test are somehow limited).
Some of these people can barely be heard. We tried increasing the mic volume (gain) in the Windows' settings (we tried both with Jamulus turned on and connected, and with Jamulus closed), and this worked for some, but not for others. In those cases, turning the mic on or off in Windows did not have any effect in Jamulus either.
Strangely, in some cases this didn't work one day, but it did another with exactly the same computer and setup! It is driving us crazy.
Does anyone know what could be going on and what steps to follow to make sure they will always be able to change the mic volume from Windows settings?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
In my case - the volume produced by Jamulus is very low (quiet).
Other programs running on the same PC produce reasonable/high volume... no problem.
This is true for both Internal Speakers output and when working with earphones.
This is on Windows 10, jamulus 3.4.5, and using the PC native sound system (no external soundcard),
and after joining (for testing) a number of "rooms"/servers in the central-server list.
Any idea what can be done about it?
Is there a way to make jamulus to up the volume produced?
Thanks!
Ari
I have the same problem. If I use the speaker or headphone normally is all fine with very high volume, but when I open Jamulus the max volume is low.
For now I use an external amp with my headphone...
I am having this issue too. I am using Mac and using a Soundcraft UI24r as my interface with Jamulus 3.4.5. I have a private server setup and people can connect. There volume is very queit and they say I sound muffled. just very quiet.
I am not sure where I am going wrong?
Can you please check the following:
- What is the position of the Pan fader in the Jamulus main window? It should be in the middle.
- Have you selected the correct input channel in the Jamulus settings dialog below the Device setting?
- Is your mixer fader on the right side in the Jamulus main windows at maximum?
It was the connection to my interface and understanding the patching. I did not have the volume up on the correct channel of my mixer.
Hello Volker,
Thanks for offering these options as help!
Maybe just becuase you offered your help, the volume situation is MUCH BETTER today...
I do not have any explanation... But as in other cases in life, when the "expert gets in", the problem disappears... or, is diminishing.... ;-)
Two of your suggestsion did not have any effect.
- The Pan fader was already in the middle
and
- All mixer faders were in the up-most position.
-Playing with the ASIO Setup did have a slight positive effect.
(But, as I wrote, the main change was already felt without this modification....)
In case others have this problem - this is my setup:
HP EliteBook laptop, Windows 10.
Using ASIO4ALL.
In the" Setup Asio" window I have:
-> Conexant ISST Audio
-> Conexant ISST Audio capture
-> Conexant ISST Audio output
-> Out: 2x 48KHz, 24Bits (This one produces a slightly higher volume)
Out: 6x8-192KHz, 24Bits (This one produces a loweer volume)
Thanks!
Ari
Hi guys. I just joined and was having this same problem and this resovled it for me. Go into Settings and change the 'Audio Channels' from Mono to Stereo. Volume is now super loud! I guess it was splitting the two signals coming in across a mono channel.
I'm using a Focusrite 2i2 for guitar and mic.
Hope that helps.
Previously I was able to hear on Jamulus but today I get no sound. Pleaae help.
I am on Windows 10 with ASIO4 all
Did you try changing the settings to Stereo like I mentioned above?
And make sure you try Volker's suggestions above as well (if you have no sound at all)
https://sourceforge.net/p/llcon/discussion/software/thread/01618b0c5c/#bb9b
Yes and yes, thanks....The problem is intermittent, I suspect that it has to do with delay time...if too much laggging time, then no sound, but this doesn't seem to be consistent either...
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 another soundcard as a double check the fault is not -there-.. Oh, though a friend of mine uses an USB Behringer interface, and from his description, I think he also suffers from the above noted effect.
Last edit: Rudolf Cornelissen 2020-04-17
Yes, I also found that 64 is quieter than 128, and 256 is louder that 128. This was using 3.5.0 client on a Macbook with a UMC404HD, and talking via my own 3.5.0 server on AWS. Not sure why the change in volume, but maybe needs investigating. I assume it's something to do with the codec.
Last edit: Tony Mountifield 2020-04-18
I will soon release a new version of Jamulus which includes an updated OPUS package. Let's see if the issue is still present with that new OPUS version.
BTW: I could not reproduce this issue on my PC.
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 volume up to 128.
Rudolf.
Last edit: Rudolf Cornelissen 2020-04-19
Can you tell approx. how many dB the signal is louder? If you just say it is louder it may 0.1 dB which can only be heard by experts or it may be 10 dB which would be very noticable, e.g.
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 to be the 'normalized' volume: 256 samples increases the volume with 3dB, and 64 samples, when on small buffers, lowers the volume with 3dB.
Thanks for your tests.
This proves that it is not the OPUS library which causes this. I'll look in the code if I find something which could cause the issue.
Ok, I can reproduce the issue with my Lexicon Omega audio card as well. I just did not notice this issue before. I created an Iusse at Github: https://github.com/corrados/jamulus/issues/106
We should follow up our discusson there now instead of posting it here in this thread.
Hi Volcher,
Do you know if Jamulus can be installed in a Chrome Book (when I try it defaults to a mac installation)
Thanks,
Frank
Unfortunately not. I have no idea...
Ok---Thank you...
Kevin, changing to stereo in your setup sends your mic to the listener's one ear and the guitar to the other!
We started using Jamulus in our choir some days ago. Most of our members are using Windows 7 or 10 with onboard soundcards, basic 3.5mm-jack earplug+mic, and Asio4All (I'm using Linux, so my chances to test are somehow limited).
Some of these people can barely be heard. We tried increasing the mic volume (gain) in the Windows' settings (we tried both with Jamulus turned on and connected, and with Jamulus closed), and this worked for some, but not for others. In those cases, turning the mic on or off in Windows did not have any effect in Jamulus either.
Strangely, in some cases this didn't work one day, but it did another with exactly the same computer and setup! It is driving us crazy.
Does anyone know what could be going on and what steps to follow to make sure they will always be able to change the mic volume from Windows settings?