Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Atomos' Samurai now allows file naming to match R3D file names for Epic and Red One

I just update to the 4.1 firmware .I am getting some problem here.My samurai showing no clip.my setting is TIMECODE---CAMERA TRIGGER RED EPIC,SOURCE----HD-SDI,FILE NAMING -----SOURCE RED ONE/EPIC. Do I need to change any other settings in samuarai or in camera.please help me out.thanks
Sunil Prem
 
Make sure your SDI output is turned on in the camera.

SUNILPREM said:
I just update to the 4.1 firmware .I am getting some problem here.My samurai showing no clip.my setting is TIMECODE---CAMERA TRIGGER RED EPIC,SOURCE----HD-SDI,FILE NAMING -----SOURCE RED ONE/EPIC. Do I need to change any other settings in samuarai or in camera.please help me out.thanks
Sunil Prem
Click to expand...
 
Might be possible with the Ninja too, if Atomos manages to move the data via their Connect Converter S2H. But for someone buying new, the Samurai is the better option.
 
Bob Gundu said:
Make sure your SDI output is turned on in the camera.
Click to expand...
Thank you Bob.yes my SDI out put have turn on the Camera.but some time record and some time not record in Samurai.in previous build don't have any other issue . only the problem coming out with in file naming source Red One/Epic.
Thanks
Sunil Prem
 
Not to be a jerk, but the Pix240 has done this for a while, with no problems. Now with the new firmware, it records to PrRes 4444 330mbit 12bit as well. A boon for me when I'm keying green screen on a tight deadline!

Glad to see they are moving forward, though. Saw them at NAB a couple years ago, had a great booth, but very little product available. Nice to see they are growing!
 
Thomas Koch said:
Must update. If no one else does, I'll be able to confirm or deny, Shoot - Edit with ProRes - Conform to R3d in Resolve - grade r3d. If anyone beats me to it, way better. I'm on a huge shoot this week, so I won't have a ton of time.
Click to expand...

how did you go with this? I want to the same but don't have all the pieces available for a couple of weeks to test
 
I am having the T001,T002... issue as well. How do you conform in resolve in this situation?
 
So what is the purpose of the firmware update if you have to rename the clips?
 
Ryan Emanuel said:
So what is the purpose of the firmware update if you have to rename the clips?
Click to expand...

My feeling exactly. Seems ATOMOS brings us 90% there with these updates, but fails in the last 10% making the whole thing moot.

To satisfy my curiosity, I did do a small shoot, and did go thought the process of renaming the files, and everything worked great using the ATOMOS clips as offline files then conforming in Davinci. My only request is to fix this addition of T001, T002, etc, then there is a very efficient way of using these files.

I did get a response on the ATOMOS forum, and their advice was to rename the files. A bit weak in my opinion.

Anyway good try ATOMOS, but a minute late and a dollar short on this one.

Colin
 
Given their track of updates, I suppose they'll fix this. Renaming is pretty painless with an automatic renamer application, there are quite a few for PC or Mac.

And then there's always the Soundpix 240 …
 
Has anyone experienced that magnifying in triggers recording of clips? I have like 5 clips on the samurai for one clip on the redmag. This is probably the reason for the extra file extensions.
 
Ryan Emanuel said:
Has anyone experienced that magnifying in triggers recording of clips? I have like 5 clips on the samurai for one clip on the redmag. This is probably the reason for the extra file extensions.
Click to expand...


Turn off rolling Timecode on the samurai at it works fine.
 
Has anyone had an issue with Scarlet Beta 4.0.6 where the Samurai doesn't read the time code or start/stop triggers over SDI, during preview/record? If I put the Scarlet into playback mode, the Samurai reads the timecode, so I'm assuming it's either a buried setting on the Scarlet or another glitch in 4.0.6...
 
Bug in the RED firmware.

Paul Rondeau said:
Has anyone had an issue with Scarlet Beta 4.0.6 where the Samurai doesn't read the time code or start/stop triggers over SDI, during preview/record? If I put the Scarlet into playback mode, the Samurai reads the timecode, so I'm assuming it's either a buried setting on the Scarlet or another glitch in 4.0.6...
Click to expand...
 
Thanks, Bob. That's frustrating. I never saw that mentioned anywhere.
 
You must log in or register to reply here.
Back
Top