Clip name over SDI not working

[Josh Stafield]

Hi,

I have an Atomos Shogun Connect which I use with my Alexa 35. Some clients like to be able to record proxies on the Shogun or use the Camera to Cloud, Frame I/O feature. The Shogun has the ability to accept clip names over the SDI connection and I have successfully tested this with an Alexa Mini LF and AMIRA. Unfortunately I can't get this working with Alexa 35. The timecode and R/S triggers are coming through fine but no clip name. Is this a bug or did the SDI data change between Mini LF and Alexa 35 (which presumably would mean Atomos need to add a new option at their end)? Or perhaps I have some deep menu setting wrong.

Cheers,

Josh

[Andreas Berkl]

Dear Josh,

as per my information there was an issue with clip name over SDI up tp SUP 1.0.3, but it is claimed to be fixed for SUP 1.0.4 (released May 6 this year).

Which SUP version are you running? Are you getting wrong clip names on your Shogun or nothing at all?

Thanks, Andreas

[Josh Stafield]

Thanks for your reply Andreas. I originally tried this a while ago with an older SUP and the Shogun got a series of underscores and then a box symbol as the clip name. It would not change as I recorded more clips so the second clip would crash the Shogun.

I upgraded SUP 1.1.0 today prior to testing. It looks like the Shogun is registering a signal from the camera but clip name section is now blank (no weird square symbol anymore). Same crash happens if you record more than one clip.

[containhowl]

Andreas, I appreciate your response. When I first tried this with an earlier SUP, the Shogun's clip name ended up being a string of underscores followed by a box symbol. I tried recording multiple clips, but it never changed, eventually causing the Shogun to crash after the second clip.
slope

[charlesgrenier]

Hi ! I have the same problem here…. I have a Shogun Connect with OS 11.0.8 and It won’t record Arri 35 clips over SDI. Did you find a solution since the last post ? Than you !

[Josh Stafield]

My problem was solved once Atomos updated their OS to version 11. I have successfully used A35 and the Connect a few times since then.

[Fletcher_AC]

I'm having a similar issue except I am also not getting the R/S trigger to work over SDI.
We are using a Shogun Inferno and have tried with a Blackmagic Video Assist as well with no luck.

Is there anything we need to do differently with the Alexa 35 to get this to trigger recording?

[Fletcher_AC]

Update: Still not working. We have now been able to try to trigger the SDI record with 2 different A35's and a Mini LF.
It's working with the Mini LF, but not with either of the A35's - Any Ideas?

[Fletcher_AC]

For future reference we have found a solution.
The Tally Light setting needed to be set to Tally Light (recording) not Tally Light (CAP) - System > Buttons & Display.

[Jan Heugel]

Hi Mr. Fletcher,

this wrong behavior is a bug and has been fixed with SUP 2.0.
Firmware 2.0 is right out of the oven, released on Wednesday this week.

Download SUP 2.0 here.

Cheers,
Jan