Gronaz

Hi If you are the maintainer of shortypower.org, have a look at this: https://ed2k.shortypower.org/?hash=64CC48379BE1C3125704F96A68F504B8 >> Gaal's flag wrong for Ukraine https://shortypower.org/ >> Gaal's flag OK

Hi If you are the maintainer of shortypower.org, have a look at this: https://ed2k.shortypower.org/?hash=64CC48379BE1C3125704F96A68F504B8 >> Gaal's flag wrong for Ukraine https://shortypower.org/ >> Gaal's flag OK

Or just run the bootable USB Jamulus Linux stick a great guy built for us here

In Mono mode I had the sound only in left ear. After switching to Stereo I saw the slider was set full Left. After setting it to Center then switched back to Mono, I got the sound in both ears (v3.5.9git).

... but the server mix is heard in stereo. Hi Gilgongo, does this mean that 1) the mono upload data also contains flags on network packets to reroute the instrument on one channel and the microphone to the other channel (I wonder when this reroute happens: just before the server sends back or just after the packets reach the clients network input)? Or do you mean that 2) the mixed mono signal will reach identically both L&R channels on all band mates (even the uploader, who, from the POV of any client...

C'est la vie

Hi CONFIG+=nosound is intuitive to me : no sound until recompile w/o the option. So what is the difference of compile/run in the post title? I guess they are related, but I can't know how because the server wiki instructs to compile with "headless" then gives a run example with -n. headless has less dependencies so is running "jamulus -s" implies -n when compiled with headless. Is all this to prevent errors on launch on headless server when running a simple "jamulus -s" and to create a smaller footprint...

Hi CONFIG+=nosound is intuitive to me : no sound until recompile w/o the option. So what is the difference of compile/run in the post title? I guess they are related, but I can't know how because the server wiki instructs to compile with "headless" the gives a run example with -n. headless has less dependencies so is running "jamulus -s" implies -n when compiled with headless. Is all this to prevent errors on launch on headless server when running a simple "jamulus -s" and to create a smaller footprint...