1 of 1 people found this helpful
Debian 8 at one point switched to libav from ffmpeg which eliminated gstreamer0.10-ffmpeg. They did go back to ffmpeg but don't think gstreamer0.10-ffmpeg is there yet. You can try to install unsupported packages. Here is a link https://launchpad.net/~mc3man/+archive/ubuntu/gstffmpeg-keep
How are you going with OpenOB on your RPi3 with cirrus logic audio?
I'm on the same project and finally got my cirrus working on the RPi3.
encounterd the same problem with installing the ffmpeg
And also installing the redis-server
up and running yet?
just wondering of you did, maybe giving me some pionters :-)
I am having the same difficulties. Has anyone had any luck?
I'm jumping on the ¨trying to do this too¨ bandwagon.
I would be happy to get OpenOB working with the simple USB audio adapters ($50) or the Behringer UCA202.
I have the Cirrus, but have given up for now.
Tried installing on RPI3 from instructions on OpenOB´s homepage - but it became a chaotic hunt for dependencies.
I´ve been installing OpenOB using this guide and thus far have had no dependency problems.
Will report back as I learn more.
Everything installed smoothly using the link above, but when I try to make the connection listed on james harrison´s tutorial page - where it says
openob 192.168.0.10 test-rx-node test-link rx
I get the following error
Traceback (most recent call last):
File "/usr/local/bin/openob", line 9, in <module>
from openob.node import Node
File "/usr/local/lib/python2.7/dist-packages/openob/node.py", line 4, in <module>
from openob.rtp.tx import RTPTransmitter
File "/usr/local/lib/python2.7/dist-packages/openob/rtp/tx.py", line 2, in <module>
ImportError: No module named pygst
Any ideas whatś gone wrong?
1 of 1 people found this helpful
Tells me the code is Python based and needs to install PyGST Tutorial/Getting Started - Pitivi wiki . Good luck, hoping this works.
That link appears to be very broken in 2017.
Did this -
sudo apt-get install python-gst0.10
I did find the Pitivi page, but then I needed to install flatpak, then it appeared they didn't have a specific version for Raspbian Jessie......and on and on.
Thanks for the link.
Progress has been made...kinda. I have OpenOB installed on 2 RPI3-s.
10.0.0.114 is the transmitter and config server.
10.0.0.110 is the receiver.
I can start the receiver with ¨openob 10.0.0.114 test-rex-node test-link rx¨ and eventually get ¨Waiting for transmitter capabilites...¨
but when I fire up the transmitter with the line below, this is what I get.
openob 10.0.0.114 test-tx-node test-link tx 10.0.0.110
2017-03-19 00:22:05,042 - openob.link.test-link.config - INFO - Connecting to configuration host 10.0.0.114
2017-03-19 00:22:05,051 - openob.node.test-tx-node - INFO - Link test-link initial setup start on test-tx-node
2017-03-19 00:22:05,052 - openob.node.test-tx-node.link.test-link - INFO - Starting up transmitter
2017-03-19 00:22:05,059 - openob.node.test-tx-node.link.test-link.tx - INFO - Creating RTP transmission pipeline
(128000, False, True)
2017-03-19 00:22:05,121 - openob.node.test-tx-node.link.test-link.tx - INFO - Set receiver to 10.0.0.110:3000
(python:1117): GStreamer-CRITICAL **: range start is not smaller than end for `GstIntRange'
Additionally if I don´t have the jack server running, I just get errors.
If I don´t start Jack I get the following
2017-03-19 00:45:17,982 - openob.node.test-tx-node.link.test-link.tx - INFO - Set receiver to 10.0.0.110:3000
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
AL lib: (EE) alsa_open_capture: Could not open capture device 'default': No such file or directory
might this offer a clue?
This problem seems to go away if I have jack running.
Unfortunately, I was under the impression that Jack was not necessary to run OpenOB.
Previous versions of OpenOB, as shown on this page (Broadcast-quality OBs with Raspberry Pis – Talk Unafraid ) indicate that you can specify hardware rather than rely on an audio server.
OK. Installed everything on both transmitter and receiver RPI3's.
But the units seem to not be seeing each other.
Here is the transmitter side:
pi@Transmitter-Pi:~ $ openob 10.0.0.114 test-tx-node test-link tx 10.0.0.110
2017-03-24 22:07:23,930 - openob.link.test-link.config - INFO - Connecting to configuration host 10.0.0.114
2017-03-24 22:07:23,938 - openob.node.test-tx-node - INFO - Link test-link initial setup start on test-tx-node
2017-03-24 22:07:23,940 - openob.node.test-tx-node.link.test-link - INFO - Starting up transmitter
2017-03-24 22:07:23,941 - openob.node.test-tx-node.link.test-link.tx - INFO - Creating RTP transmission pipeline
(128000, False, True)
2017-03-24 22:07:24,002 - openob.node.test-tx-node.link.test-link.tx - INFO - Set receiver to 10.0.0.110:3000
and the transmitter just sits there.
Here is the receiver side:
pi@KZZM-Rec-Pi:~ $ openob 10.0.0.114 test-rx-node test-link rx
2017-03-24 17:07:15,253 - openob.link.test-link.config - INFO - Connecting to configuration host 10.0.0.114
2017-03-24 17:07:15,272 - openob.node.test-rx-node - INFO - Link test-link initial setup start on test-rx-node
2017-03-24 17:07:15,275 - openob.node.test-rx-node.link.test-link - INFO - Waiting for transmitter capabilities...
and the receiver just sits there.
Am I missing some config info?
I'm wanting to install OpenOB on a Pi 3 with Wolfson/Cirrus audio card.
I've got the card drivers running and it's detected by ALSA.
I was following the installation tutorial here -> https://jamesharrison.github.io/openob/tutorial.html
but I'm baulked at installing gstreamer0.10-ffmpeg which seems to be obseleted in Debian 8, and presumably therefore Raspbian Jessie. I just wondered if anybody had done this and overcome this issue?
I could build it from sources I guess if necessary, but I know nothing of the gstreamer architecture.