free run is lost when running off-speed and swapping battery
#Timecode lockit code#
We set the Sensor FPS to match the Project FPS rate, and things worked fine from then on.Īs far as the issue of a time code reset following a power cycle, here's a short section from one of the Alexa supplements: I tried a couple of quick runs at doing a proper time code jam, but I only had about five-to-ten seconds (literally, I'm not exaggerating), and each time neither camera would accept the jam.įinally, when we (the ACs and I) had a five minute chance to go into the menus, I discovered that the "Project FPS" and the "Sensor FPS" did not match. I asked about frame rate and both ACs assured me that the cameras were set correctly, which was 23.976. I first discovered this on a shoot that galloped into action without proper time for setup of either of the two Alexas. However, having a mis-matched Project FPS and Sensor FPS does affect us, and it affects time code jamming. Those, of course, are not sound department areas. (Try it here on the Alexa Simulator and you'll see what information this displays: ).įor most projects we do these days, you'd want to see the Project FPS and Sensor FPS both showing "23.976."Īs far as the REC OUT and MON OUT frame rates, it depends upon what subsequent devices the camera is feeding. Both affect several things.Īt the Arri's HOME screen, click on INFO, then press the FPS INFO button. There is a " Project FPS" setting, and there is a " Sensor FPS" setting. Don't feel bad, even a lot of camera people are clueless to this. Here's the thing, with an Arri Alexa there is more than one area that needs attention in respect to frame rate.
0 kommentar(er)
