Hi,
we are experimenting with doing remote voice tracking for Rivendell.
I have a test setup that is as close to my planned deployment setup as I
can get right now:
A Rivendell box running centos 7 and rivendell 3.2.1
A Raspberry Pi4 running Raspbian GNU/Linux 10
They are on the same switch very near each other and are connected together
audio wise like this:
Riv box onboard sound card
Pi4 usb UCA 222 wired up inputs to outputs
The Riv box is configured to use the alsa driver as the input and output
for rdlogedit.
The Pi is running jack using the dummy driver and zita bridges for the uca
222. (IIRC, I tried direct use of the USB codec and had more issues)
Jack Mixer is running to do routing and amplification as needed.
I could not find a voip phone that would work with jack so I am using
linphone with the pulseaudio-module-jack.
Using ssh tunnels with port forwarding to get toe the desktops of the Pi
and the Riv box.
After making all of the needed connections in the jack graph on the pi 4
and setting the linphone on the pi 4 to auto answer, we have a working
"system"
vnc to the Riv box (and the Pi if you like or want to tune volumes) and
bring up rdlogedit. Choose a lof that needs voice tracking and click the
button.
Dial the number/account for the liniphone on the pi4.
Start voice tracking. it works. (Mostly good enough. Latency wise. You can
slide things around to adjust. It is not bad.) it is the quality of the
vocal that out "ears" guy is not fully satisfied with. It will do in a
pinch but we would like to achieve better if we can get close to the same
latency with openob.
Moved on to try and replace the linphone link with a 2 way openob link over
openvpn. Latency was much worse and sound was "breaking up"...
I may have had problems with how I brought up the links.
The Pi4 may have been causing issues.
My network may have been less than perfect... ~;-)
Decided to move the testing location to the real location which is on
business fiber and not a home cable modem. Nook takes the place of the PI4.
Riv server is there but the nook and hte riv box are not wired up to allow
for the full test. I think I can fake enough on the nook to get a decent
test though.
On the far end, (same location) instead of a linphone call from a mac, we
have jack and openob on another nook running openvpn.
First the nook next to the Riv Box:
obuser@obstl01:~$ ps ax | grep openob
10773 pts/15 SLl+ 23:09 /usr/bin/python3 /usr/local/bin/openob 10.8.0.1
ntest-rx-node rem2shk-link rx -a jack -jn openobshackrx -aj -jp
jack_mixer:frmShk
10784 pts/7 SLl+ 35:25 /usr/bin/python3 /usr/local/bin/openob 10.8.0.1
stest-tx-node shk2rem-link tx -a jack -jn openobshacktx -aj -aj -jp
jack_mixer: 10.8.0.4 --framesize 2 -j 10 --fec -b128
Now the nook at the "remote" site:
obuser@obstl02:~$ ps ax | grep openob
8769 pts/2 SLl+ 62:32 /usr/bin/python3 /usr/local/bin/openob 10.8.0.1
ntest-rx-node shk2rem-link rx -a jack -jn openobnookrx -aj -jp
jack_mixer:frmShk
10740 pts/6 SLl+ 43:10 /usr/bin/python3 /usr/local/bin/openob 10.8.0.1
ntest-tx-node rem2shk-link tx -a jack -jn openobnooktx -aj -jp
jack_mixer:toShk 10.8.0.1 -e opus -b128 --framesize 2 -j 10 --fec
Could not get good latency. Help. I have reduced my frames per period on
both sides to see if that helps but have not been able to retest yet. Does
anyone see any glaring problems in my openob invocations at each end?
Should I reduce the quality of the Music link as that does not matter so
much for this application and leave the quality of the vocal link higher as
that is the point of trying this versus linphone?
Any other thoughts?
Does openob keep statistics on itself and its links in the redis server and
if so, can we get reports of the situation?
all the best,
drew
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
G'day all,
We seem to get the pops and clicks which I presume could be fixed by
buffering but I am unsure is I can increase the buffer size/time.
Thoughts?
--
Mike Phillips
Coast FM.
Mike,
Several of the Jack2 packages are compiled with dbus enabled. This
shouldn't be a problem, but on some systems dbus doesn't get started
unless you are running X. I've run into this on Ubuntu/Debian systems
quite a bit. Jack doesn't actually need X to run, it is possible to
compile it without dbus.
Sometimes work around this and run jackd2 by doing a dbus-launch to get
the dbus daemon started. An alternate is to try Jack1 as you've
indicated.
Admittedly for a few reasons I often prefer Jack2, but for what you're
doing it really doesn't matter which you use.
Lorne Tyndale
>
> G'day along,
>
> I have installed jackd, but I am getting...
>
> root@tantive:~# jackd -d alsa -d hw:0
> jackdmp 1.9.11
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2014 Grame.
> jackdmp comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> no message buffer overruns
> no message buffer overruns
> no message buffer overruns
> JACK server starting in realtime mode with priority 10
> self-connect-mode is "Don't restrict self connect requests"
> Failed to connect to session bus for device reservation Unable to
> autolaunch a dbus-daemon without a $DISPLAY for X11
>
> Audio device hw:0 cannot be acquired...
> Cannot initialize driver
> JackServer::Open failed with -1
> Failed to open server
>
> THere is no X on this box and very little running, I can;t see what or
> why it can't get hw:0.
>
> Any pointers?
>
> --
> Mike Phillips
> Coast FM.
> _______________________________________________
> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
> To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk
G'day all,
Is case you have not heard there is a virus thing going around :-)
We are home basing all our radio presenters where possible.
We have been using openob for obs for some time but only one at a time.
We are now in the situation of having multiple openob trx's at the same
time (only because they are not switched off) and this, I believe, is
causing issues.
questions:
1. I presume multiple tx's to 1 rx does not work.
2. I should be able to to run multiple openobs on different ports using
jack and it will merge everything together? Hopefully.
So so long as only one rx is sending audio we will only hear one feed.
Ideally I would use an audio switch to switch between the various feeds
but we have no real way of setting this up now.
We do have this but only one OB input currently. :-(
--
Mike Phillips
Coast FM.
G'day along,
I have installed jackd, but I am getting...
root@tantive:~# jackd -d alsa -d hw:0
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Failed to connect to session bus for device reservation Unable to
autolaunch a dbus-daemon without a $DISPLAY for X11
Audio device hw:0 cannot be acquired...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
THere is no X on this box and very little running, I can;t see what or
why it can't get hw:0.
Any pointers?
--
Mike Phillips
Coast FM.
Mike,
You can run multiple ob connections on different ports, I've done this
before. I'd have to double check my notes, but years ago I had a
machine at a station which had a multiple in-out sound card (with 8 in's
and 8 out's an M-Audio Delta 1010lt) and I'd set it up to be able to -
from one computer at the station - have 4 different stereo incoming /
outgoing connections at the same time, each one with different audio.
OpenOB was on the back end making it all work.
Essentially I ran several different instances of OpenOB at the studio
each on different ports. I'd establish both send/receive channels
(again on different ports) to each location. On the Studio end I'd
routed it all through Jack. Of course this means with some jack
disconnect/connect commands it is easy to change where audio goes. The
studio end all ran on a single computer, just with multiple instances of
OpenOB.
The biggest trick to keeping it all working was to be very specific
about documenting it all. Without solid documentation it would become
easy to incorrectly route audio to the wrong location.
So as an example:
Remote location 1 talks to Studio computer - OpenOB 1, on a particular
set of ports
Remote location 2 talks to Studio computer - OpenOB 2, on a particular
set of ports
Remote location 3 talks to Studio computer - OpenOB 3, on a particular
set of ports
etc
Studio OpenOB 1, 2, and 3 all ran on the same computer, just as
different processes and using different Jack connections.
Route it all in Jack at the studio. If you want location 1, 2, and 3
all going to the same audio output at the studio then Jack can do that
for you - just route the audio from all 3 OpenOB's to the same audio
card output.
For extra security you might want to consider having the remote
computers establish a VPN connection into your studio. OpenOB by itself
is not secure, I would not recommend using it on the public internet
without some added security layer.
Hope this helps.
>
>
> G'day all,
>
> Is case you have not heard there is a virus thing going around :-)
>
> We are home basing all our radio presenters where possible.
> We have been using openob for obs for some time but only one at a time.
>
> We are now in the situation of having multiple openob trx's at the same
> time (only because they are not switched off) and this, I believe, is
> causing issues.
>
> questions:
> 1. I presume multiple tx's to 1 rx does not work.
>
> 2. I should be able to to run multiple openobs on different ports using
> jack and it will merge everything together? Hopefully.
>
> So so long as only one rx is sending audio we will only hear one feed.
>
> Ideally I would use an audio switch to switch between the various feeds
> but we have no real way of setting this up now.
> We do have this but only one OB input currently. :-(
>
> --
> Mike Phillips
> Coast FM.
> _______________________________________________
> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
> To unsubscribe send an email to openob-users-leave(a)lists.talkunafraid.co.uk
I just got my hands on 2 Pi 4 kits.
One setup, one just nearing completion of initial setup. The first thing I
want to test is openob on both ends.
Has anyone doe this yet? If so, same procedure as for Pi 3 or are there any
quirks?
all the best,
drew
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Chris,
On Wed, Jan 15, 2020 at 5:24 AM Sojo Gold <sojogold(a)gmail.com> wrote:
> Hi Drew,
> I will try and catch you on IRC ...but not today.
>
WHen you can then.
>
> I have setup jack as you indicated and copied your openOB command line to
> both TX and RX.
> Now I have openOB reporting a stereo transmission..but I have no sound
> from the RX pc.
> Using Audacity to show recording on both TX & RX pc's.
>
So, if you try and record *input* audio on each pc with audacity and no
openob running, do you see stereo in on both? (That is a stereo waveform in
the display, not a mono display?) As an additional check, if you record a
stereo signal that has obvious left right sides, do they show up in the
recording?
> I can record the input audio on the TX pc however not on the RX ie no
> sound out.
>
I don't understand exactly what you mean by this. Is this your audacity
test? Of something you are trying with openob now in the mix? Did you set
jack instead of alsa to the right of the mic as the sound system to record
on each machine when testing?
> The RX pc will play out a local saved audio file okay.
>
> Could you confirm the pulseaudio control (pavucontrol) settings... as when
> comparing TX with RX ...RX I appear to have the same settings in both.
>
Sorry, I don't think I can. I only have access to the one side for about
another week. I will poke around and see if I can find a backup tx machine
if I get some time.
> Audacity devices on TX is simply shows as "default" but on RX for some
> reason "default" cannot be found in the list.
>
Check that you are using jack and not alsa in audacity.
> Hmm...
> pavucontrol - output devices - on RX pc shows..
> PCM2902 Audio Codec Analogue Stereo - port: Analogue Output
> Jack sink (PulseAudio JACK Sink) as fallback.
>
I am showing Built in ... (HDMI)
and
PCM2902 Audio Codec Analogue Stereo - port: Analogue Output
Not seeing anything like Jack sink (PulseAudio JACK Sink) as fallback.
>
> pavucontrol - output devices - on TX pc shows.. exactly the same.
>
> hope this makes sense..I will try and setup a time slot to IRC you in the
> next few days.
>
If you look at qjackctl connections window when openob is up, is openob
connected sensibly on each end? Does it even show up in the jack graph on
both ends?
>
> Thanks and much appreciated.
> Chris P.
>
all the best,
drew
>
>
>
>
> On 14/01/2020 15:21, drew Roberts wrote:
>
> Chris,
>
> This might be easier to do interactively. I am in the IRC channel
> #rivendell on freenode. Look for zotz.
> You could try #openob as well...
>
> I use xchat on linux. If you use a different os, find a client for your os.
>
> Or you could try this web client:
> https://webchat.freenode.net/
>
> Freenode's main page:
> https://freenode.net/
>
> Some hints below in case you miss me there...
>
> On Tue, Jan 14, 2020 at 8:40 AM Sojo Gold <sojogold(a)gmail.com> wrote:
>
>> Hi Drew,
>>
>> I have installed Jack on both TX and RX PC's. Have used pavucontrol to
>> disable the built-in sound card of both PC's.
>>
>
> First things first. We will leave openob out of the equation.
>
> I suggest you use qjackctl to do this.
>
> Start qjackctl. Make sure jack is stopped. Go to setup. On the settings
> tab, choose the alsa driver, choose the correct interface, my uca222/uca202
> (front / back) shows as hw:CODEC, choose you sample rate, I have 48000,
> chose your frames/period, I have 2048, choose your periods/buffer, I have 3.
>
> Save the changes. Click start on the main qjackctl window.
>
> Start something that can record audio from jack. audacity, jack time
> machine, ardour, whatever. Record some audio and make sure you have stereo.
>
> Do this at both ends to ensure you have jack capable of doing stereo at
> each end.
>
> Now try and get openob working correctly at each end.
>
> This may give a clue as to what your receive end might look like:
>
> /usr/local/bin/openob 10.8.0.1 test-rx-node test-link rx -a jack -jn
> openob -aj -jp jack_mixer:ICh2
>
>
> all the best,
>
> drew
>
>
>> Jack Audio Connection Kit - Connections - Audio tab show Out's as
>> PulseAudio JACK Sink, front left/front right, to -----> IN's as PulseAudio
>> JACK Source - System - playback_1/playback_2 receptively.
>>
>> OpenOB still sends audio okay but is till Mono.
>>
>> I'm pretty convinced the TX Opus capability parameters has been
>> misconfigured..
>> i.e.. the log at startup shows sprop-stereo-(string)0 which is Mono.
>>
>> see here:
>>
>> *2020-01-13 19:29:55,538 - openob.link.STUDIO-link.config - DEBUG - Set
>> openob:STUDIO-link:caps to application/x-rtp, media=(string)audio,
>> clock-rate=(int)48000, encoding-name=(string)OPUS,
>> sprop-maxcapturerate=(string)48000, sprop-stereo=(string)0,
>> payload=(int)96, encoding-params=(string)2, ssrc=(uint)1869211510,
>> timestamp-offset=(uint)2778079888, seqnum-offset=(uint)6787*
>>
>> *2020-01-13 19:29:56,452 - openob.node.test-tx-node.link.STUDIO-link.tx -
>> INFO - Started mono audio transmission*
>>
>>
>> *well still getting my head around JACK.. do I need to set parameters in
>> the openOB command line..??*
>>
>> *cheers for you input, much appreciated.*
>>
>>
>> *Chris P. *
>>
>>
>>
>> On 13/01/2020 23:01, drew Roberts wrote:
>>
>> Chris,
>>
>> if you machine is "strong" enough to run jack, it should get you up and
>> running until you figure things out and it may be a final solution as well.
>>
>> If you need any further help, ask me on list and I would be happy to see
>> what help I can provide.
>>
>> drew
>>
>> On Mon, Jan 13, 2020 at 12:12 PM Sojo Gold <sojogold(a)gmail.com> wrote:
>>
>>> Hi Drew,
>>> Thanks for the feedback...hmmm will need to look at JACK then..
>>> Chris.
>>>
>>> On 13/01/2020 13:44, drew Roberts wrote:
>>>
>>> I can't give you a solution but I can tell you what I did as a
>>> workaround when time was running short for me.
>>>
>>> I put jack in the mix on both ends.
>>>
>>> Someone had suggested that I edit an alsa config file. I can't remember
>>> the results of that. My setup was perhaps not exactly parallel to the
>>> suggested fix and I did not have time to dig deeper. You can perhaps search
>>> the list archive for the discussion.
>>>
>>> In any case, once I had jack in the mix, I got stereo where I had mono
>>> before.
>>>
>>> all the best,
>>>
>>> drew
>>>
>>> On Mon, Jan 13, 2020 at 7:38 AM Sojo Gold <sojogold(a)gmail.com> wrote:
>>>
>>>> Hi,
>>>> Thanks to the amazing work and dedication to this wonderful project
>>>> from some awesome engineers, I, as one of the somewhat inexperienced , have
>>>> managed to create a working link using two Linux Mint v19.3 PC's for our
>>>> cash strapped community radio station. Thank you.
>>>> I have a small query and a related question.
>>>>
>>>> Using the default test command line on both PC's, INFO on the TX PC
>>>> reports "Started mono audio transmission"* BEFORE* I had started the
>>>> RX PC link. This was a bit confusing, however, there was no audio until the
>>>> RX link was started.
>>>>
>>>> I tested the link once established, for separation and found it is
>>>> actually Mono!. I'm using default ALSA driver and two Behringer UCA-202's.
>>>> I appreciate this is only the default settings and probably should use
>>>> command line configuration options but in a previous version OpenOB worked
>>>> as stereo "out of the box" using defaults. Has something changed in this
>>>> regard.
>>>>
>>>> So, is there any sort of tutorial on using the CL parameters. I am
>>>> aware of the "Further Usage" paragraph referring to '*openob -h*' etc
>>>> but wondered if there was something more in depth to help me fix the Mono
>>>> problem.
>>>>
>>>> Anything much appreciated.
>>>>
>>>> Chris Perkins
>>>> Flame Radio
>>>> Wirral
>>>>
>>>>
>>>> _______________________________________________
>>>> openob-users mailing list -- openob-users(a)lists.talkunafraid.co.uk
>>>> To unsubscribe send an email to
>>>> openob-users-leave(a)lists.talkunafraid.co.uk
>>>>
>>>
>>>
>>> --
>>> Enjoy the *Paradise Island Cam* playing
>>> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>>>
>>>
>>>
>>
>> --
>> Enjoy the *Paradise Island Cam* playing
>> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>>
>>
>>
>
> --
> Enjoy the *Paradise Island Cam* playing
> *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
>
>
>
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Hi,
Thanks to the amazing work and dedication to this wonderful project from
some awesome engineers, I, as one of the somewhat inexperienced , have
managed to create a working link using two Linux Mint v19.3 PC's for our
cash strapped community radio station. Thank you.
I have a small query and a related question.
Using the default test command line on both PC's, INFO on the TX PC
reports "Started mono audio transmission"/BEFORE/ I had started the RX
PC link. This was a bit confusing, however, there was no audio until the
RX link was started.
I tested the link once established, for separation and found it is
actually Mono!. I'm using default ALSA driver and two Behringer
UCA-202's. I appreciate this is only the default settings and probably
should use command line configuration options but in a previous version
OpenOB worked as stereo "out of the box" using defaults. Has something
changed in this regard.
So, is there any sort of tutorial on using the CL parameters. I am aware
of the "Further Usage" paragraph referring to '*openob -h*' etc but
wondered if there was something more in depth to help me fix the Mono
problem.
Anything much appreciated.
Chris Perkins
Flame Radio
Wirral
