AF100 internal codec vs Samurai

Mike@AF said:
Well that's a bummer. I like to use free rolling timecode so I can shoot with time of day timecode. So Samurai basically becomes unusable for someone like me.
Click to expand...

No, you roll it from the unit not the camera. I would set time of day on both camera and Samurai.
 
But then they won't match, which is not good if recording audio externally and jam syncing timecode. Again, bummer...
 
Mike@AF said:
But then they won't match, which is not good if recording audio externally and jam syncing timecode. Again, bummer...
Click to expand...
Which is why I continually harp that the idea of using timecode to trigger external recording is an inadequate idea. The proper way to do it is to use the SDI recording flags. Detecting changing timecode is a cheapo workaround, not a proper solution. It can work in rec run situations, but won't ever allow true free run operation, whereas if they'd just take the effort to recognize the SDI recording flag, they'd have no problems and all would be happy and hunky dory.
 
Bloody drive got stuck again and on top of that Atomos FW 261 doesn't work because they forgot to spell it right. Renamed to ATOMSAM.FW and it worked.
 
Last edited:
Thanks for the heads-up. The "ATOMSAM.2.61.FW" file must be renamed to get it to work. And the SDI record bit
detection is implemented. Haven't tried it yet, but if it works as stated .. this is very good
news for us free-runners :-)
jeff
ps: Atomos could learn a little from Apple on UI feedback during firmware
installation. The spaztic flashing makes the device appear as though
it's malfunctioning. A progress bar and/or some textual feedback
as to how the install is going would calm one's nerves.
 
Last edited:
Hasn't happened to me. Usually, you slidethe release and pull the drive out via the caddy.I wish the caddy was made from a more durableplastic or thin aluminum. It deforms easily and I can understand how it might get stuck.But, i would go SDI for the AF100. Samurai isfairly compact.
 
I warned about the possibilty of the drive getting stuck some time ago. (It happened to me twice)

Do not over tighten the screws when mounting the drive into the caddy. Allow it to have some "play" (movement to accomodate the caddy fit and the connection).

Do not push the drive and caddy in ...too forcefully.
 
editman said:
Bloody drive got stuck again and on top of that Atomos FW 261 doesn't work because they forgot to spell it right. Renamed to ATOMSAM.FW and it worked.
Click to expand...

Thank you!!!!!!! I've tried several times to install it without success: I've renamed it and now it works!!!!

Thank you again and Happy New Year

Gary
 
Could you verify that it uses the SDI start/stop record bit/flag and not the timecode run with the new firmware?
 
I have two drives and the SSD drive doesn't get stuck but my spinning drive does. I already have another SSD on order so I'll stay away from spinning discs. If it get stuck you have to remove one side of the recorder and realign the unlocking mechanism. A bummer indeed.
 
editman said:
I think this function is available in the 2.6.1 firmware.
Click to expand...
Just looked, and it looks like they have implemented it exactly as it should be done. Well done Atomos!

Here's the quote from the Atomos site:
Cameras can output the camera record state on HD-SDI in an ancillary data packet. The Samurai will start/stop the recorder if this packet is detected.

This means when you hit record on the camera and the camera starts recording, so will the Samurai. When you hit record on the camera and the camera stops recording, so will the Samurai. Supported cameras are Sony, Panansonic, Red, Canon and Arri. I can provide a list of actual cameras tested. Not all cameras output the ancillary data packet so naturally the Samurai will not respond.
Click to expand...
 
You must log in or register to reply here.
Back
Top