Tips, Tricks & More

Home > Tips, Tricks & More

Using Jamulus audio in Zoom (or other) meeting apps

Several users have reported success allowing a "virtual audience" for a Jamulus session by using Jack audio to route the Jamulus signal through the JackRouter to the target application.

You can also use Voicemeeter (Banana) to route Jamulus output to multiple destinations, for example to your headphones and the meeting application at the same time.

Making a server status page

With the -m and -a command line arguments a server statistic information can be generated to be put on a web page.

Here is an example php script using the server status file to display the current server status on a html page (assuming the following command line arguments to be used: -m /var/www/stat1.dat -a myServername.com):

<?php
function loadserverstat ( $statfilename )
{
   $datei = fopen ( $statfilename, "r" );
   while ( !feof ( $datei ) )
   {
	  $buffer = fgets ( $datei, 4096 );
	  echo $buffer;
   }
   fclose($datei);
}
?>
<?php loadserverstat ( "stat1.dat" ); ?>

Jamulus client Linux start script

Here's a Linux start script for Jamulus using an old Audigy4 sound card, the large number of available audio faders for which makes it hard to get the correct settings.

This script therefore includes the most important audio fader settings. The second part of the script deals with the jack connections. I use Guitarix as my guitar effect processor which I plug in in the jack audio path.

Finally I start Jamulus automatically connecting to the central server.

Here is the script:

amixer sset 'Mic' capture 30% cap
amixer sset 'Mic' playback 0%
amixer sset 'Line' playback 60% unmute
amixer sset 'Audigy Analog/Digital Output Jack' unmute
amixer sset 'Analog Mix' capture 100%
amixer sset 'Analog Mix' playback 0%
amixer sset 'Wave' 100%
amixer sset 'Master' capture 100% cap
amixer sset 'Master' playback 100%
amixer sset 'Master' playback 100%
amixer sset 'PCM' playback 100%
amixer sset 'PCM' capture 0%
guitarix &
/home/corrados/llcon/Jamulus -c myJamulusServer.domain.com &
sleep 3
jack_disconnect system:capture_1 Jamulus:'input left'
jack_disconnect system:capture_2 Jamulus:'input right'
jack_connect system:capture_1 gx_head_amp:in_0
jack_connect gx_head_amp:out_0 gx_head_fx:in_0
jack_connect gx_head_fx:out_0 Jamulus:'input left'
jack_connect gx_head_fx:out_1 Jamulus:'input right'
jack_connect Jamulus:'output left' system:playback_1
jack_connect Jamulus:'output right' system:playback_2

Using the --ctrlmidich MIDI controller channel option

Jamulus user Ignotus writes - If you want to use a generic MIDI controller:

In the file src/soundbase.cpp, go to line 290 and remove the - 70 at the end (not the semicolon). Save and compile.

MIDI CC messages consist of a Control Number, Controller Value, and Channel.

The mixer faders in Jamulus are zero-indexed and linked to the Control Number, so Control Number 0 operates the first fader, 1 the next, etc. Channels start at 1 and this is the parameter you set at launch, but you can make the Jamulus client listen to all 16 channels by setting this parameter to 0. The Controller Value is the MIDI value (0 - 127) that your controller sends to operate the fader.

If you can't (or don't want to) change the Control Numbers in your MIDI controller, add an offset to line 290 so that your Control Numbers - offset = 0, 1, ... etc.