Portsdown stream receiver input

[KA5BBC]

How does one build, configure, and implement the Portsdown stream receiver input for the repeater controller?

I'm assuming that I would need to build a Portsdown for each stream input (hopefully headless rather than needing more screens etc.) but where do I go from there?

[G8GKQ]

Andy

The recommended solution is not to use a Portsdown, but to use a Ryde for the stream input. This is of course headless and does not need an IR remote control. It is all configured in the config.yaml file.

Dave

[KA5BBC]

Thank you again Dave..

There is a bit of a learning curve but I will get there.

I have no doubt that there will be many many more questions before I am done

[KA5BBC]

OK.. Ryde is built enough to operate a stream receiver.
(I am waiting for components to populate the GPIO breakout and control boards I have)

How do I configure it so that those given a suitable IP and log in can access the repeater?

[KA5BBC]

After a couple of days of research and experimentation I have realised that I had misunderstood "Stream Receiver" within the Portsdown/Ryde infrastructure and that what I want to do is not possible with these builds.
Building a way to have a fellow ham who can not access a repeater directly, for any one of many possible reasons, access through an IP stream from OBS, ATEM Mini, or Portsdown is a larger challenge than I expected.
On RPi I have looked at about a dozen options including appliance style builds and individual application installs. This includes RTMP, SRT, and other streaming modes. SRT was my primary choice as it uses less bandwidth for higher quality, is more reliable, is more secure, and is an available option in most if not all options for the remote accesser.
OnPremises SRT Player for RPi looked like a great option as it is an appliance style application, is simple to operate, and outputs directly to HDMI. However, I could not get my ATEM, OBS, or any other application to stream to it with the SRT Player in listener mode, necessary for remote initiated connections. The lack of clear and useful documentation could be part of the problem, they link to a 3:45 video, with no speech, with the first 1:50 taken up with downloading and writing to the SD Card.
NGinX can perform the task, however, the delay and latency so bad that it could be unusable and I have not been able to find a way to implement hardware decoding or optimisation.
The majority of other applications, despite hints/suggestions/statements on websites, could not output to HDMI but rather acted as transcoders or restreamers.
BlackMagic Designs’ Streaming Bridge looks like a excellent option, unfortunately I don’t have one to confirm this, and all demonstrations and reviews on Youtube etc show significantly lower delay and latency than any of the RPi options.
I know that some groups are using commercial solutions, free and paid versions, such as the Amateur Television Network here in the US which is using Whereby and Zoom which, while somewhat secure, could leave a repeater open to abuse and misuse.

I would like to know what solutions others have found that work for them and how they are implemented.

[g0mjw]

But the Ryde already does this? https://wiki.batc.org.uk/Stream_Receiver

[G3GJA]

...and does it very well. Our local repeater, using a Ryde stream receiver based on a Raspberry Pi4, regularly gets IP connections from all over the UK and once from Las Vegas.

1920 x 1080 @ 25fps out via HDMI to the repeater's video switching.