21 Jul
2020
21 Jul
'20
6:49 a.m.
On 21/07/2020 13:47, stinga wrote:
On 21/07/2020 07:32, Evan wrote:
I tried to send some images but it looks like we can't do that on this
list :-(
--
'ooroo
Stinga...(:)-)
---------------------------------------------------
Email: stinga(a)wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ `\ /) ~
doesn't move and it should use > (O) X< ~ Fish!!
the hammer. If it moves and `\___/' \) ~
shouldn't, use the tape. \\\
---------------------------------------------------
I'm working with a community radio station
and looking for
suggestions on how best to receive the OpenOB streams from (4)
remote studios to the hub studio (single fixed IP).
The remote studios have RasPi4 OpenOB senders, the hub end will be
(4) RasPi4 OpenOB receivers, audio from each receiver will be
selectable, as required, for re-broadcast on the main FM Station. The
audio switching at the hub end all figured out and tested.
All remote studios have broadband service (Satellite and no fixed
IP), I have a single test site that has been streaming for the past
couple of months and works fine.
However I have not resolved how best to now get the (4) OpenOB remote
studios, sending to the single fixed IP at the hub end and received
on their respective RasPi OpenOB receivers.
After experiencing one hack on the test stream's exposed redis server
(not surprised), It is now obvious I will now need to secure all the
streams on a working system. I have looked at a couple of options,
such as a local OpenVPN server, OpenVPN with IPvanish server, spiped
or Zerotier (as suggested by Klaus),.
With many options, I am looking for guidance at this point on best
way to go. Any help, comments or suggestions would be most welcome.
G'day,
Each openob tx has its own name.
4 rx running on 1 node
Use jack to dis/connect streams.
We use systemd to stop and start the rx streams, just to reduce bandwidth
/etc/systemd/system/openob_obdave.service:ExecStart=/usr/local/bin/openob
redis obdave_rx obdave rx -ajack --jack_name openob_obdave
--jack_port_pattern system:playback
/etc/systemd/system/openob_obglenn.service:ExecStart=/usr/local/bin/openob
redis obglenn_rx obglenn rx -ajack --jack_name openob_obglenn
--jack_port_pattern system:playback
/etc/systemd/system/openob_objames.service:ExecStart=/usr/local/bin/openob
redis obCB obCB rx -ajack --jack_name openob_objames
--jack_port_pattern system:playback
/etc/systemd/system/openob_obnik.service:ExecStart=/usr/local/bin/openob
redis obnik_rx obnik rx -ajack --jack_name openob_obnik
--jack_port_pattern system:playback
We have a lot of streams flying around so stop/starting them just
helps a bit.
We then have a webpage to control who is active
We always switch at TOH when IRN news is playing, so it sounds seemless.
I have been looking at trying to control volume with jack so we can
fade from one to the other, rather than a hard chop.
Here is what njconnect currently looks like:
*
*Some of this is for historical reasons, we started with 2 physical
studios and a Sustaining service when not live, we then added a single
OB and we needed a way to switch between audio sources remotely, due
to the OB part.
C19 happened and then there was a requirement to home base some of our
presenters and the OB part seemed to be the way to do this. So OB got
expanded by 4 more units.
AT TOH we need to switch back for the news, so we sent the IRN news
back out of another openob stream and it seemed like a good idea to be
able to have presenters talk to each other on show hand over. IE
current presenter may have a chat with next presenter about what they
are doing in their show so yet another couple of OB feeds to shove
around. And then there is a final openob that we use for STL to FM
transmitter.
**