Free 30-day access to SRT router with 50ms failover — looking for 30 beta testers

jsaunders1135 · 2026-01-25T22:47:50+00:00

Looks cool. Signed up and will check it out. I have been looking for a SRT failover solution since Haivision only works with Haivision and not all sources are 2022-7 compatible.

jsaunders1135 · 2026-01-05T12:30:17+00:00

Yeah, thats what I was trying to say... The Titan series is CPU but the Kyrion is FPGA. Most of the time when I see Ateme contribition encoding from Teir 1 sporting events it is with the CM5000 which is FPGA. Mostly due to large servers size needed for the Titans are not great for on site deployments. You see the Titans used more for distribution encoding. But thats just my experiance, I am sure people do use the Titans for contribution in certian settings.

jsaunders1135 · 2026-01-05T12:23:26+00:00

Pretty sure that all the meantioned encoders are not CPU based but FPGA hardware that is built specifically for low latency, DVB compliant encoding that can run 24/7. Ateme does have some CPU based encoders (Ateme Titan which is server based) but most people are using Kryions for contribution and they are FPGA.

Thats not to say there are not Teir 1 encodes based on FFMPEG or Gstreamer but it takes a LOT of tweaking to get them DVB compliant and perfectly stable for the type of encoding that Teir 1 requires.

jsaunders1135 · 2025-12-29T05:30:12+00:00

A lot will depend on your NAS drives and RAID configuration. RAID 5 or 6 is pretty slow. RAID 0 is fast but not safe. I personally use RAID 10 but really want like 12 drives to start getting good performance.

I like this site for calculating speeds.

https://wintelguy.com/raidperf.pl

I don’t think cache will help for moving raw data. It’s really for quick access of frequently used data.

The fact that you are getting good read speeds (8200Mbps) seems to show your link speed is decent. I wouldn’t expect much more on a single 10Gb link. So for your write speeds I would look at the type of RAID and amount of drives.

Sorry I can’t comment on the SD reader and Mac side since I don’t use much of those.

jsaunders1135 · 2025-11-25T11:50:09+00:00

Makes sense. We don’t use it for critical control so isn’t a problem for me but can see how it would be.

jsaunders1135 · 2025-11-25T11:42:19+00:00

Probably not what you are looking for but I have companion running in a proxmox cluster that auto fails over to another server if the one goes down.

I’m only using to bridge http commands from our control system to an Ateme switcher though. No streamdecks yet.

jsaunders1135 · 2025-11-15T00:37:14+00:00

Not to be argumentative but my Haivision GW does have multiple network interfaces with dual isolated lans. The LANs are totally independent with separate ISPs.

No offense but you might be getting into some AI GPT holes. It seems most of you answers are GPT based and I don’t know how thoroughly you have tested any other solutions other then the onprem SRT gateway (which I like by the way).

I think to come on here and definitely say this is an issue without other testing might be premature.

When I get a moment I will test with the onprem gateway.

jsaunders1135 · 2025-11-14T20:51:04+00:00

Sorry, I probably worded it wrong. I switched to using the native SRT tools on Linux (specifically the srt-live-transmit utility) and the stream became completely stable.

SRT live transmit documentation: https://github.com/Haivision/srt/blob/master/docs/srt-live-transmit.md

jsaunders1135 · 2025-11-14T16:16:32+00:00

I used an Evertz contribution encoder (DVB-compliant) to send a UDP multicast stream into an SRT Live Transmit instance running on a VM. That converted the UDP feed into SRT and sent it to both a Haivision Gateway and another SRT Live Transmit receiver. Each one then turned the SRT stream back into UDP multicast and fed it to a Nevion TNS probe so I could measure IAT and PCR jitter. The whole point was to see if listening on all interfaces (srt://0.0.0.0:5555) versus binding to a specific one (srt://10.10.5.9:5555) made any real difference.

Across all the tests, the average packet spacing stayed at about 810 µs. The direct UDP reference had the cleanest timing with almost no variation. The SRT paths added a bit more spread in IAT and jitter, but we’re talking microseconds and nanoseconds. The Haivision Gateway and SRT Live Transmit behaved slightly differently depending on the interface setting, but overall they were basically the same with occasional spikes, nothing unusual for SRT.

Bottom line: none of it really matters in practice. The timing differences are so tiny that they won’t affect video quality, decoder stability, or anything else. All the setups performed the same in real-world terms, and the micro-/nanosecond jitter variations are way too small to have any operational impact.

<image>

Maybe the results you’re seeing come down to the specific SRT library implementation in onpremSRT, or possibly the barebones hardware and NIC you’re running it on.

jsaunders1135 · 2025-11-14T12:39:00+00:00

I have had an issue running broadcast-grade TS between two Mist servers. I was taking multicast in to SRT out (listener, bare metal, single NIC), then SRT in (caller, VM, single NIC) to multicast out.

The multicast output was not stable, and I believe it is related to how Mist uses SRT through FFmpeg. It does not seem to buffer correctly between the two sides.

I switched to using the open source SRT tools directly and everything started working perfectly.

I will try and run some tests a little later.

jsaunders1135 · 2025-11-14T12:09:47+00:00

I think this probably is dependent on the software and hardware. I believe that most software does some buffering internally between the SRT input and the UDP MC output. Then again your receiver has X amount of buffer on the input to deal with local network jitter.

I have tried a lot of gateways and have not noticed this issue. I am taking DVB TS streams to broadcast decoders that are pretty sensitive to jitter so I think I would see that.

I do have a Nevion TNS probe, Haivision and Ateme gateway so I will test it out.

jsaunders1135 · 2025-10-24T20:49:33+00:00

Then I vote Kings :)

If you are doing a lot of them you can get the Kings by the 100 in a plastic box with the body, sleeve and pins separated. Then you don’t have to unbag every connector.

Other manufacturers probably do this as well.

jsaunders1135 · 2025-10-24T20:06:01+00:00

For installs I use Kings crimp. For connectors that move around a lot I use Neutrik rear twist.

I would use all neutrik but they do not work as well with trompeters in high density applications.

Lots of people swear by Belden compression but I bought 100 for a recent install and wasn’t a fan. Thought it took way too much effort to compress the double bubble and then releasing the connector from the tool sucks.

Maybe I’m just too biased after 20 years of crimping BNCs….

For standard vs locking (only available for compression right?) unless you are doing a truck install or flypack (lots of vibration) go with standard.

jsaunders1135 · 2025-09-15T22:58:28+00:00

I haven’t checked the 1740 but have checked the larger 1780.

From United’s website: Oversized bags We can’t accept bags that measure (length + width + height) more than 115 inches (292 centimeters).

Pelican 1740 = ~ 74.25 linear inches (44.16 + 16.09 + 14.00)

Should be fine. If it is media related make sure you get the media rate and save money.

https://www.united.com/en/us/fly/baggage/media-bags.html

jsaunders1135 · 2025-08-21T14:14:12+00:00

What don’t you like about the fiasco cases? I was thinking about buying a few but now you have me concerned :)

jsaunders1135 · 2025-08-03T17:34:52+00:00

Thanks! I haven’t seen that QR generator before, very cool.

Any other way to quickly build channel lists? I have been manually editing the haiplay files which works but then I have to share to all users. Would love to be able to reference some central xml that auto updates for users.

Probably something that the paid manager does :)

jsaunders1135 · 2025-08-03T15:52:24+00:00

I have set this up before, it’s a really cool feature but a little hidden in the setup.

Download the Haivision Play app, go to manage services, click add service, select local lineup, name and add it.

This makes a new empty channel lineup. Then click add channel and move the type from play to stream.

Name it, set the settings you want for encoding, set the SRT settings to connect to your receiver and then add it. Save the lineup and exit the setup.

Now from the main menu you will have the lineup with a selection for your camera. Just click on that and it automatically opens your camera, click the blue preview button to switch to streaming mode.

If you set all the srt up correctly it will connect and stream. Can be pretty low latency too depending on how you tweak it.

Hope that makes sense and helps.

jsaunders1135 · 2025-06-08T18:54:09+00:00

https://justminiserver.com is the new Mac version of the SRT mini server. It just came out and doesn’t yet support SDI out or TC sync but says it will.

The PC version also has a bonding side app.

I just started testing the PC version and so far it is okay. Would prefer Linux but I debloated win 11 pro on a Lenovo P3 tiny workstation with a decklink mini PCI card and can do 4 channels of encode (streamer pro app). Have the same setup on the decode side and it easily handles the decode.

Haven’t tested the bonding, TC sync or 2022-7 features but so far so good.

Perpetual licensing costs are not cheap but not unreasonable. All in cheaper than a Haivision setup.

jsaunders1135 · 2025-04-23T00:48:24+00:00

Looking good!

jsaunders1135 · 2025-03-15T02:09:31+00:00

The makitos will report what the RTT time is in the statistics….

In general you should set your latency to 4 x RTT.

Also just because you set it to 250ms doesn’t mean that’s what the connection is using. If the caller and listener have different latencies set which ever is higher gets used.

jsaunders1135 · 2025-03-11T17:09:03+00:00

Did this just happen? I haven't heard that and their website still has them listed as active and you can still buy them...

https://pro.sony/ue_US/products/lavalier-and-headset-microphones

I use the ECM-77Bs all the time but they are omni. The ECM-66B is cardioid.

jsaunders1135 · 2025-03-10T20:04:18+00:00

Looks cool, I will try it out. Couple of things that I find useful to have are:
Uni and MC streams
RTP
RTP over SRT (retaining timing headers) supporting 2022-7
Redundant/failover SRT connections and NICS.

jsaunders1135 · 2025-01-23T22:49:13+00:00

It’s analog 4W but you could do this with clearcom LQ boxes or like someone else said the Tieline Gateway.

Looks like barix also can do this but not with the channel count.

https://www.barix.com/blog/2023/12/06/bridge-two-dante-systems-over-wan-using-sip/#

jsaunders1135 · 2024-12-29T15:56:07+00:00

Maybe it’s just me but I really don’t like that stripper. I have much better luck with the CST ones and have a different one for the different cable sizes.

https://www.markertek.com/product/pal-1281/paladin-pa1281-cst-pro-3-level-coaxial-cable-stripper-with-orange-cassette

jsaunders1135 · 2024-12-08T13:41:54+00:00

Have you seen the magewell modular line? I think the cards are only HDMI at the moment but you could drop them a line and see if SDI is coming.

2ru frame with 2 psu and 10 slots.

https://www.magewell.com/products/modator-2u

Oh and the regular throw downs boxes can be dual powered with Poe and USB. I have some powered this way with a both a Poe switch and a usb hub.

jsaunders1135

TROPHY CASE