Hi, it seems that jammr always sends my audio to the jam session when I first connect to it, even if my “Send” button is unselected.
To avoid sending my audio I have to select and unselect the “Send” button, and from then on, the button works as expected.

I observed this last week, but I thought it was due to frequent crashes of the jammr client (my local ALSA system was not configured properly), and I thought maybe when the client crashes it loses track of the Send state.

Yesterday I fixed my system, so jammr doesn't crash anymore, but I experienced the same bug (confirmed by other people in the chat), so it seems there's something wrong.

Steps to reproduce:
* Unselect the “Send” button, and quit jammr nicely (BTW I can see that in ~/.config/jammr/jammr.conf the state of “enableXmit” is set properly)
* Start jammr and connect to a session
* The “Send” button is always off (and so it's enableXmit), but people in the chat say they hear me
* Select the “Send” button: people still hear me
* Unselect the “Send” button: people won't hear me anymore
* From now on, the button works OK

Anyone experienced this? I'm running the jammr 1.2.4 .deb package downloaded from the website.

Thanks for reporting the bug. A fix will be released in jammr 1.2.5 over the next few days.

By the way, the code change is here:
https://github.com/wahjam/wahjam/pull/131

A jammr update will be released in a few days after testing and considering other bug fixes/improvements.

Thanks for fixing it! I forgot to suggest a small visual improvement to the send/metronome buttons: the color shade used when the buttons are active is a bit too light, making difficult to see if the button is on or off when you are playing and you are not close to the computer screen (especially if the screen is tilted). I would use a darker tone/color for the “on” state.

Thanks for the suggestion!

I think this change will have to wait for the new user interface, because they are currently “native” buttons. Their look depends on the operating system and user's settings. A color that looks good on a default Windows machine might look very strange on Mac, for example. The new UI will be 100% custom widgets so it will be possible to make these changes consistently across all platforms.

Ah I see. Thanks for explaining. As a workaround, I found I can pass the qt “-style” option to jammr, so running gives a slightly better view on my system.