Lost broadcast signals from Linux Flame

Hello,

I suddenly lost my broadcast displays from my Linux, both on my Eizo and my Panasonic 70". I’ve checked all the physical connections, made sure the 4k HDMI splitter is on, rebooted the Linux twice, checked and toggled all the Flame setup related options, and nada. I had been working on it yesterday just fine, then today there’s no signal on either. I didn’t change any hardware connections or software settings – this just came out of nowhere.

I have two 20’ HDMI cables arriving this evening. Before I start running cables and messing things up though, I wanted to see if there are any other ideas to try? Thanks in advance.

Not sure what verion you’re on, but there’s two places in your prefs where it can go awry. One is in the user prefs and the other is in project. I don’t remember when that changed. I’ve never had the video shut itself of spontaneously, but I have had audio do it several times.

For the future, get this optical HDMI cables. They are much thinner than traditional long run copper cables, and still cheap.

Maybe try sending the monitors something different than a black frame?

Have you tried in the setup app switching from ADA/BMD to the opposite then back again?

Is it on single link or dual link? Have you tried swapping that to the other and back again?

I tried switching ADA/BMD in the Flame setup, no dice. I’ve pretty much toggled everything relevant that I can find. I’ve switched the Broadcast Timing between Quad Link and Dual Link.

@ytf I see all the Broadcase Monitor prefs in Flame prefs. Where are the user prefs for broadcast that you mention?

Thanks, gents.

Well now you tell me! Thanks man.

It depends on what version you’re running. I forget when it changed, but these are the two places I look.


Thanks Tim. I’m on 2025.2.2 and tried all of these…

Flip the framerate in Flame to 1920x1080 50i, then flip it back. I do this very frequently to resolve bcast monitor issues.

gross.

Also Alt+B is hotkey to toggle bcast monitor. I would think a reboot would clear that, but worth checking.

I had a similar issue not long ago and it was because I accidentally selected Full range, when it should be Legal. Also check if your get the same problem when you create a new project .

@GPM can you send screen shots of your setups. Is it an internal card or an external BOB?

Is the Broadcast working from other apps?

Do you have another app open at the same time that might be reserving/holding onto the monitor output (such as Resolve or a Creative Cloud app)?

Hey Adam,

Thanks for reaching out. I’m receiving a new mini-hdmi to hdmi cable and a 4k hdmi splitter today – one of those seems to be the likely culprit. I’ll def update here when I get them and test…

When debugging AJA issues, it helps to take the Flame out of the loop. Exit Flame, then from a root shell:

# cd /lib/modules/$(uname -r)/aja/current/bin
# ./ntv2outputtestpattern

This should output some color bars, regardless of what Flame is trying to do. If you see color bars, then the issue is likely with Flame preferences. If not, you could have a hardware fault you’ll need to diagnose.

And if you have to diagnose video issues, those small portable BMD monitors are great:

Sorry, I forgot to update. Replacing the 4k HDMI splitter solved the problem. Thanks for all the input here.

Curious: What kind of splitter did you have, how old was it and did it just fail without warning? I ask because I’d like to know if mine are in their golden years as well.

It was a Kanex 4-port HDMI splitter. There were no warnings of decay, it just crapped out. I now have a new one that works fine, and a backup in the closet.

*It alarmingly took Amazon 4 days more than promised to deliver the Kanex. So I’d advise just getting one to have on hand. Trying to Flame without a broadcast monitor is basically living like a refugee.

It makes one appreciate the luxury of having B&H just a short subway ride away.