Tim Lynch

I too want to facilitate my choir group where some people are running Jamulus but others only have Zoom. The goal is for everyone to join Zoom for video and shared/common audio, but when it is time to sing, have Jamulus-enabled participants be able to sing together on Jamulus and share that Jamulus audio feed into Zoom, which Zoom-only folks can listen to and/or sing along while muted. My first attempt was just to use Zoom screen share from my Mac joined to both Zoom and Jamulus with the Zoom "share...

I too want to facilitate my choir group where some people are running Jamulus but others only have Zoom. The goal is for everyone to join Zoom for video and shared/common audio, but when it is time to sing, have Jamulus-enabled participants be able to sing together on Jamulus and share that Jamulus audio feed into Zoom, which Zoom-only folks can listen to and/or sing along with while muted. My first attempt was just to use Zoom screen share from my Mac joined to both Zoom and Jamulus with the Zoom...

My experience installing Jamulus (version ~3.5.12) on a stock Raspberry Pi 3B Plus h/w rev 1.3 running Raspbian 9.13 was that the lowest I can set the buffer size using qjackctl is 512 frames. If I select 256 frames or lower, qjackctl returns error: "ALSA: Cannot open PCM device alsa_pcm for capture". Jamulus works OK with frame size 512, but I'd like to get the latency lower, if possible. Would an add-on hardware sound module help with that? Would an out-of-the-box Raspberry Pi 4B do any better...

Thanks for this great tool! Does the tool as-is support a way to prepend or append the computed checksum or CRC value to the resultant output file? Current options seem to want to place the checksum somewhere in the same range of the binary data derived from the hex file, thus overwriting some of that data. "Modify it to do that yourself" is a perfectly valid answer; I just wanted to make sure I'm not missing or misunderstanding something.