sonosaurus / sonobus

Source code for SonoBus, a real-time network audio streaming collaboration tool.
https://sonobus.net
GNU General Public License v3.0
1.53k stars 110 forks source link

Sonobus GUI causes netjack to disconnect #86

Open VennStone opened 3 years ago

VennStone commented 3 years ago

This is an odd one I have been able to replicate on everything from a RasPi 4 to a Threadripper. After about 5 minutes of running with someone connected to the Sonobus session netjack1 (or 2) will disconnect from the server. This is with Jack2 1.9.17 running on all ends. The problem is alleviated somewhat if Jack is run in asynchronous mode. It will still happen, just takes longer.

I can run the same Sonobus session headless for hours without so much as a hiccup.

Here is the output for what it's worth. aoo_client: not connected aoo_client: not connected aoo_client: already connected! aoo_source: sink not found! JackFreewheelDriver::ProcessSync: SuspendRefNum error JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!! JackAudioDriver::ProcessGraphSync: SuspendRefNum error, engine may now behave abnormally!! netxruns... duration: 2ms JackFreewheelDriver::ProcessSync: SuspendRefNum error JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!! JackFreewheelDriver::ProcessSync: SuspendRefNum error JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!! JackAudioDriver::ProcessGraphSync: SuspendRefNum error, engine may now behave abnormally!! JackFreewheelDriver::ProcessSync: SuspendRefNum error JackAudioDriver::ProcessGraphSync: ProcessWriteSlaves error, engine may now behave abnormally!! JackEngine::XRun: client = SonoBus was not finished, state = Triggered JackAudioDriver::ProcessGraphSync: Process error master seems gone... entering freerun mode JackAudioDriver::ProcessGraphSync: Process error JackAudioDriver::ProcessGraphSync: Process error resync after freerun... 642703 netxruns... duration: 1359ms JackAudioDriver::ProcessGraphSync: Process error netxruns... duration: 2ms netxruns... duration: 90ms aoo_client: not connected aoo_client: not connected

Outside of initial setup I'm testing Sonobus headless so it's more of a huh vs a show stopping bug. Thought I would at least give it a mention.

For anyone wanting to play the home game:

Start Jack2 in sync mode with something along the lines of jackd -R -S -P 70 -d alsa -d hw:DSP -r 48000 -p 128 -n 2

Start netjack1 on the host jack_netsource -H 192.168.remote.IP -n 5 -i 2 -o 2 -I 0 -O 0

On the remote (Sonobus) PC jackd -R -S -P 90 -d netone

essej commented 3 years ago

I'm not sure I understand what you are reporting....

Can you give more details of how/why you are using netjack in this setup in conjunction with SonoBus?

VennStone commented 3 years ago

Right on.

My setup is for live streaming and podcasting. I've been experimenting with sonobus in place of jacktrip. It's three PCs for hosts, one PC for the DAW, and one that handles live streaming & video. Ardour handles the mix minus and audio processing, records a dry copy, and sends the wet to the streaming box where OBS handles the mixdown for streaming and saves the multitrack audio with the video coming in over NDI from the other PCs and capture devices. There is an additional mixdown for the closed captioning as well.

The host PCs run an instance of jacktip/sonobus. I could have everyone in a single room or jacktrip hub server but I've been on the receiving end of that crashing and it's no fun.

Five ethernet cables and a switch. That's why I use netjack.

1DSCF0602