[PLUG-AV] Another experiment in updating our AV workflow

[Harry McNally]

Hi James

I wasn't able to stay on Sunday to hear what steps are needed next for the RPi4.

Now that the talks have an interim one-crate system, is your work on RTSP 
services RPi-ready so the next meetup can try the architecture out ?

I could research those USB-powered mixers to see if an "audio" RPi with an 
attached mixer is feasible. That would replace the USB audio device I proposed.

If there is a list of what packages are needed on top of the latest Raspbian 
(lite or desktop ?) I'd prefer to bring a prepared RPi ready for integration 
testing.

I understand now that Nick's network design needs to be the Swiss-Army-Router 
for all networking situations. That is a project in its own right. Just 
wondering, Nick, if PLUG needs to buy a specific wireless router so you have 
the flexibility for all the expected network situations; and so network is a 
single box solution.

It would be wonderful if RPis could mean a single crate (or several backpacks) 
becomes the Aladdin's Cave for a multi-camera event :-)

All the best
Harry

On 12/3/21 11:33 am, James Henstridge wrote:
> On Tue, 9 Mar 2021 at 10:23, James Henstridge <james at jamesh.id.au> wrote:
>> The eventual goal is to allow the different parts to self configure.
>> If you turn the camera nodes on first, then the OBS machine should
>> connect to them when it starts.  If the OBS machine starts first, it
>> will wait until the cameras come online, and plug them into the scenes
>> you've set up previously.  If everything works correctly, then the
>> RTSP sender machines could easily be headless: the RTSP server would
>> start on boot, and Avahi would advertise the camera once it gets a
>> DHCP address.
> I think I've got this part of the plugin working now.  The source is
> now gets you to choose a service name for the stream (e.g. "Camera-A"
> in the sample rtsp-sender.conf), providing an option list of all
> available cameras on the local network.  When the camera drops from
> the network, the underlying ffmpeg_source is reconfigured with an
> empty URL, and when it appears again we configure it with the new URL.
> This means that OBS reconnects to the camera almost instantly when it
> becomes available.
>
> So that pretty much covers what I wanted from an auto-configuration
> stand-point.  If you set up all the OBS scenes you want for a
> broadcast in advance, it would pretty much be a case of plugging
> everything in and having it self organise.  There is no need for a
> display on the sender machines, so it could easily be a Raspberry Pi
> like I demoed this week.  We could even store the Pi and capture card
> wired together, so setup would only involve connecting power,
> ethernet, and HDMI.
>
> James.
> _______________________________________________
> AV mailing list
> AV at plug.org.au
> http://lists.plug.org.au/mailman/listinfo/av