G'day all,
What is the best way to install now?
I have done in the past:
1. apt-get install python-pip
2. apt-get install git
3. apt-get install git python-gst-1.0 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base gstreamer1.0-plugins-bad
gstreamer1.0-plugins-ugly gstreamer1.0-plugins-good
gstreamer1.0-tools gstreamer1.0-alsa python-redis
4. (or) apt-get install git python-gst-1.0 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base gstreamer1.0-plugins-bad
gstreamer1.0-plugins-ugly gstreamer1.0-plugins-good
gstreamer1.0-tools python-gobject python-gobject-2 gstreamer1.0-alsa
python-redis
5. pip install git+https://github.com/jonty-comp/openob.git@gst1.0
6. easy_install OpenOB
Or some incarnation of the above, I seem to remember having to look at
chicken guts to make it work :-)
--
Mike Phillips
Coast FM.
Until now, we only planned to use our remote setup to send vocal audio over
the link from the "road" end (tx). The music part of the final signal was
to be created at the "transmitter" end (rx).
Now we have a situation where we think we want to send the complete audio
mix from the "road" end (tx).
We are noticing pauses / glitches in the audio.
What is a good approach to try and "fix" this situation?
Some info. Openob link is running on an openvpn tunnel.
"transmitter" end (rx):
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.1 netmask 255.255.255.255 destination 10.8.0.2
/usr/local/bin/openob 10.8.0.1 test-rx-node test-link rx -a jack -jn openob
-aj -jp jack_mixer:ICh2
"road" end (tx):
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.6 netmask 255.255.255.255 destination 10.8.0.5
/usr/local/bin/openob 10.8.0.1 test-tx-node test-link tx -a alsa -d hw:0
10.8.0.1 -e opus -b128 --framesize 60 -j 80 --fec -l 5
The above line is my latest effort. Started with this:
/usr/local/bin/openob 10.8.0.1 test-tx-node test-link tx -a alsa -d hw:0
10.8.0.1
The loss on the link just observed with mtr was under 1%. Does it hurt to
set it higher than observed? (I am not concerned with delay / latency on
the link if I can get a better sound out the far end. (Within reason. I
don't want to burn CDs and drive to the far end... ~;-)
all the best,
drew
Is there any other info I should supply?
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Well,
for testing purposes, I have set up 2 Pis on a local lan.
Transmitting PI has usb sound card and openob uses alsa invoked like this:
/usr/local/bin/openob 192.168.86.149 test-tx-node test-link tx -a alsa -d
hw:1 192.168.86.149
aplay -l gives:
card 1: CODEC [USB AUDIO CODEC], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
Receiving Pi uses onboard sound card and openob uses jack invoked like this:
/usr/local/bin/openob 192.168.86.149 test-rx-node test-link rx -a jack -jn
openob -aj -jp jack_mixer:ICh2
It is also running jack-mixer and a few other toys.
After hooking things up as desired in qjackctl, I see the mono audio in
jack-mixer and hear it in my headphones plugged into the Pi's soundcard.
Any thoughts on how to track down the mono issue?
all the best,
drew
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Just as an FYI, I've run into a quite a few stereo USB sound cards that
- even though they are stereo - only get recognized as mono on the input
/ record side by ALSA.
Sometimes they can be forced to stereo mode by tweaking .asoundrc, and
sometimes that doesn't even work.
In my experience USB sound cards are a hit and miss to whether they
actually get seen as stereo inputs.
Lorne Tyndale
> James,
>
> I decided to brink up jack on the tx end and had stereo passing over the
> lan.
>
> Now to put openvpn in the mix and see if the PIs are strong enough to do
> the whole show without undue strain causing audio issues.
>
> Thanks again for your help.
>
> all the best,
>
> drew
>
> On Thu, Nov 21, 2019 at 7:11 PM James Harris <james(a)digital-light.co.uk>
> wrote:
>
> > Hi Drew,
> >
> > I had the same issue when I got 4.0.3 running, I can't remember if I found
> > a workaround to the issue or it simply went away when I used openob-gui. I
> > will try and get my development units out on Sunday to look back. For
> > reference, I am using the Cirrus/Wolfson sound cards on the Pi at each end,
> > I also have an x86 box set up that I configure as one end or other of the
> > link when I want to work on new ideas.
> >
> > I have some vague recollection of comparing the all of the stored redis
> > keys when openob was started on its own to when it was started from
> > openob-gui, but there was a lot of faffing involved and it was too long ago
> > for it to be clear in my mind.
> >
> > On a completely different point, during the summer I used the system for a
> > week over a point to point WiFi link and one of the days, during a short
> > period of packet loss, one end of the link couldn't read keys from redis
> > (can't remember if it was local or remote) and the link fell over. I made
> > copious notes at the time and have the intention of adding some error
> > handling for that condition. I believe the behaviour at the moment to
> > simply quit openob is incorrect and that an error handling routine should
> > pick up the condition and retry the connection either a given number of
> > times or for a given amount of time before returning to the same state as
> > when it is waiting to establish first connection. So probably time for me
> > to get the whole lot back out on the bench anyway.
> >
> > Regards,
> >
> > James
> >
> >
> > On 21/11/2019 23:15, drew Roberts wrote:
> >
> > Well,
> >
> > for testing purposes, I have set up 2 Pis on a local lan.
> >
> > Transmitting PI has usb sound card and openob uses alsa invoked like this:
> >
> > /usr/local/bin/openob 192.168.86.149 test-tx-node test-link tx -a alsa -d
> > hw:1 192.168.86.149
> >
> > aplay -l gives:
> > card 1: CODEC [USB AUDIO CODEC], device 0: USB Audio [USB Audio]
> > Subdevices: 1/1
> > Subdevice #0: subdevice #0
> >
> > Receiving Pi uses onboard sound card and openob uses jack invoked like
> > this:
> >
> > /usr/local/bin/openob 192.168.86.149 test-rx-node test-link rx -a jack -jn
> > openob -aj -jp jack_mixer:ICh2
> >
> > It is also running jack-mixer and a few other toys.
> >
> > After hooking things up as desired in qjackctl, I see the mono audio in
> > jack-mixer and hear it in my headphones plugged into the Pi's soundcard.
> >
> > Any thoughts on how to track down the mono issue?
> >
> > all the best,
> >
> > drew
> >
> >
> > --
> > Enjoy the *Paradise Island Cam* playing
> > *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
> >
> > _______________________________________________
> > 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
> >
> > _______________________________________________
> > 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/<hr>_______________________________________________
> 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
James...
Doing the actual machine with the hat this morning. Found an error in the
docs you sent which I overrode without noting.
On Wed, Nov 20, 2019 at 3:12 PM james(a)digital-light.co.uk <
james(a)digital-light.co.uk> wrote:
> Hi Drew,
>
> There are a few dependencies that have moved on in terms of version
> numbers, but it does work.
>
> I managed to get it all working on stretch and documented the process some
> time back when I was tinkering with openob-gui, looking at my notes:
>
> sudo apt-get install python-gst-1.0 gstreamer1.0-alsa libgstreamer1.0-0 gstreamer1.0-libav gstreamer1.0-doc gstreamer1.0-tools
>
> sudo apt-get install gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly
>
> sudo apt-get install python3-pip
>
> pip3 install openob
>
>
pip3 install openob
needs to be
sudo pip3 install openob
all the best,
drew
> Should get you through it. If you get stuck anywhere, I would appreciate
> the feedback and I will update my notes.
>
> Regards,
> James
>
> Sent from my Huawei phone
>
>
> -------- Original Message --------
> Subject: [openob-users] Raspbian Stretch?
> From: drew Roberts <zotzbro(a)gmail.com>
> To: For users of the OpenOB project <openob-users(a)lists.talkunafraid.co.uk
> >
> CC:
>
> OK,
>
> does anyone have openob running on raspbian stretch?
>
> Any gotchas? I am having issues.
>
> I would be quite happy setting up 2 Pis with openob on a lan as a first
> cut.
>
> Do I need to ditch stretch and go back to jessie on these machines or can
> we get openob running fine on stretch?
>
> I don't really want to be doing this. We had a nice setup all tested out.
>
> A Nook next to a rivendell server. The Nook running ubuntu and openob.
>
> The remote and had a pi running openob and a "hat?" soundcard. (Can't put
> my hands on the link to it now.) A little mixer, a mic, a laptop.
>
> The remote person could connect to the "studio", control the nook and
> rdairplay and run a whole remote show from the field without a boardop in
> studio.
>
> openvpn between the pi and the nook with openob over the vpn link.
>
> We haven't used it in forever. Now have a need again and openvpn and
> openob seem to be missing from the remote pi. (Plus the Nook seems to be
> rebooting about every 10 minutes for some reason we have not been able to
> track down yet.
>
> Ouch.
>
> So, I am trying to get the pi end working again (with a new pi at first)
> and then work on the nook (or a replacement) end...
>
> I know this is a bit long winded, but the actual setup was quite sweet and
> I thought it might inspire someone.
>
> --
> 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/
James,
thanks so much for you help.
I now have audio flowing.
Newly installed openob and openvpn on the send side (raspberry pi).... Old
openob and openvpn on the receive side (server/nook side)... USB sound card
on pi for now. I see audio passing through the meters on the nook. (Some
messages make me think it may be mono and not stereo at this point, but I
am too burned out right now to troubleshoot...
Thanks again.
all the best,
drew
On Wed, Nov 20, 2019 at 3:12 PM james(a)digital-light.co.uk <
james(a)digital-light.co.uk> wrote:
> Hi Drew,
>
> There are a few dependencies that have moved on in terms of version
> numbers, but it does work.
>
> I managed to get it all working on stretch and documented the process some
> time back when I was tinkering with openob-gui, looking at my notes:
>
> sudo apt-get install python-gst-1.0 gstreamer1.0-alsa libgstreamer1.0-0 gstreamer1.0-libav gstreamer1.0-doc gstreamer1.0-tools
>
> sudo apt-get install gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-bad gstreamer1.0-plugins-ugly
>
> sudo apt-get install python3-pip
>
> pip3 install openob
>
> Should get you through it. If you get stuck anywhere, I would appreciate
> the feedback and I will update my notes.
>
> Regards,
> James
>
> Sent from my Huawei phone
>
>
> -------- Original Message --------
> Subject: [openob-users] Raspbian Stretch?
> From: drew Roberts <zotzbro(a)gmail.com>
> To: For users of the OpenOB project <openob-users(a)lists.talkunafraid.co.uk
> >
> CC:
>
> OK,
>
> does anyone have openob running on raspbian stretch?
>
> Any gotchas? I am having issues.
>
> I would be quite happy setting up 2 Pis with openob on a lan as a first
> cut.
>
> Do I need to ditch stretch and go back to jessie on these machines or can
> we get openob running fine on stretch?
>
> I don't really want to be doing this. We had a nice setup all tested out.
>
> A Nook next to a rivendell server. The Nook running ubuntu and openob.
>
> The remote and had a pi running openob and a "hat?" soundcard. (Can't put
> my hands on the link to it now.) A little mixer, a mic, a laptop.
>
> The remote person could connect to the "studio", control the nook and
> rdairplay and run a whole remote show from the field without a boardop in
> studio.
>
> openvpn between the pi and the nook with openob over the vpn link.
>
> We haven't used it in forever. Now have a need again and openvpn and
> openob seem to be missing from the remote pi. (Plus the Nook seems to be
> rebooting about every 10 minutes for some reason we have not been able to
> track down yet.
>
> Ouch.
>
> So, I am trying to get the pi end working again (with a new pi at first)
> and then work on the nook (or a replacement) end...
>
> I know this is a bit long winded, but the actual setup was quite sweet and
> I thought it might inspire someone.
>
> --
> 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/
OK,
does anyone have openob running on raspbian stretch?
Any gotchas? I am having issues.
I would be quite happy setting up 2 Pis with openob on a lan as a first cut.
Do I need to ditch stretch and go back to jessie on these machines or can
we get openob running fine on stretch?
I don't really want to be doing this. We had a nice setup all tested out.
A Nook next to a rivendell server. The Nook running ubuntu and openob.
The remote and had a pi running openob and a "hat?" soundcard. (Can't put
my hands on the link to it now.) A little mixer, a mic, a laptop.
The remote person could connect to the "studio", control the nook and
rdairplay and run a whole remote show from the field without a boardop in
studio.
openvpn between the pi and the nook with openob over the vpn link.
We haven't used it in forever. Now have a need again and openvpn and openob
seem to be missing from the remote pi. (Plus the Nook seems to be rebooting
about every 10 minutes for some reason we have not been able to track down
yet.
Ouch.
So, I am trying to get the pi end working again (with a new pi at first)
and then work on the nook (or a replacement) end...
I know this is a bit long winded, but the actual setup was quite sweet and
I thought it might inspire someone.
--
Enjoy the *Paradise Island Cam* playing
*Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
Hi Guys
I have recently built a new Open OB link using 2 x Raspberry Pi 2s on Rasbian Strech release.
The transmitter is using an Audio Injector sound card and the receiver is using a PiFi DAC+ v2.0. I have had this hardware configuration working previously but I note that there may have been an update to the OpenOB package (OpenOB 4.0)
Has anyone had success getting the latest version of Open OB working on Raspberry Pi or is there a means that I can install OpenOB v3.0 instead of v4.0
Regards
Terry O'COnnor
Seems to work, at least I received your email.
>
> Just testing the list as I've migrated it to a new box on mailman3 -
> hopefully all is well.
> --
> Cheers,
> James Harrison<hr>_______________________________________________
> 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
