Andrew Young
Well-known member
- Joined
- Jul 4, 2007
- Messages
- 179
- Reaction score
- 0
- Points
- 16
- Location
- New York
- Website
- www.archipelagofilms.com
I could not find any reference to this issue in a search. Very curious to know if anyone else is experienceing it. I just finished up a two week shoot and got some very strange timecode behavior that is going to really complicate the conform.
I’m shooting an upgraded R1 w/ build 17 v3.4.1 and TOD has always been selected as the displayed and primary timecode in the camera ( I verified this many times as the problem began to occur). Dailies were rendered out using REDrushes and the timecode drop down menu was always set to External/TOD (also triple checked this). However, when I bring either the proxies or the rendered Quicktimes into FCP and look at the Media Start Timecode column, the results I’m getting fluctuate seemingly randomly between TOD and Edgecode.
In some cases, the proxies show the TOD TC, while the REDrushes renders of the very same clips show Edgecode and in some cases it’s the proxies that show Edgecode while the renders have TOD. In some cases the timecode switch happens after the camera had been rebooted and/or a setting was changed such as resolution or shutter speed. But in many cases, the primary TC switches from TOD to Edgecode (or vise versa) in the middle of a set-up when I know that no settings changes were made on the camera. Sometimes, it switches for one shot, then switches back, and other times it just continues with the new primary timecode. In addition, when I render out a batch of dailies using REDrushes, sometimes the TC changes from TOD to Edgecode exactly where the proxies change and sometimes the change occurs on different clips. For example, in the middle of a bunch of clips that came out with Edgecode, clip #17 of the renders might have TOD instead, but on the proxies, it’s #16 that has the TOD code. And all of this TC flipping occurs even though TOD was the setting used for the entire batch.
When I bring the clips into Clipfinder it is easy to verify that all clips have both types or TC and that each type appears to be correct. What is wrong is that I only randomly seem to get TOD as my primary TC, in spite of the fact that both camera and REDrushes were set to TOD. Very strange and a real nightmare for post.
In all cases, TOD was also chosen as the burn-in TC and in all cases this is correct, but because of the random switching behavior, the burn-in matches the Quicktime TC only about half the time.
Unfortunately, I do not have access to many clips from earlier in my camera’s life, but I do have one clip from about 10 months ago where this same thing appears to be happening.
This is a pretty serious issue, given that I am handing off dailies to productions that will need to conform later to the R3Ds. Now the EDL that they will be generating will be a mish mash of EC & TOD. I know I can slog my way through it manually, but it is not going to be fun. I would greatly appreciate any insights other users may have about this problem.
I’m shooting an upgraded R1 w/ build 17 v3.4.1 and TOD has always been selected as the displayed and primary timecode in the camera ( I verified this many times as the problem began to occur). Dailies were rendered out using REDrushes and the timecode drop down menu was always set to External/TOD (also triple checked this). However, when I bring either the proxies or the rendered Quicktimes into FCP and look at the Media Start Timecode column, the results I’m getting fluctuate seemingly randomly between TOD and Edgecode.
In some cases, the proxies show the TOD TC, while the REDrushes renders of the very same clips show Edgecode and in some cases it’s the proxies that show Edgecode while the renders have TOD. In some cases the timecode switch happens after the camera had been rebooted and/or a setting was changed such as resolution or shutter speed. But in many cases, the primary TC switches from TOD to Edgecode (or vise versa) in the middle of a set-up when I know that no settings changes were made on the camera. Sometimes, it switches for one shot, then switches back, and other times it just continues with the new primary timecode. In addition, when I render out a batch of dailies using REDrushes, sometimes the TC changes from TOD to Edgecode exactly where the proxies change and sometimes the change occurs on different clips. For example, in the middle of a bunch of clips that came out with Edgecode, clip #17 of the renders might have TOD instead, but on the proxies, it’s #16 that has the TOD code. And all of this TC flipping occurs even though TOD was the setting used for the entire batch.
When I bring the clips into Clipfinder it is easy to verify that all clips have both types or TC and that each type appears to be correct. What is wrong is that I only randomly seem to get TOD as my primary TC, in spite of the fact that both camera and REDrushes were set to TOD. Very strange and a real nightmare for post.
In all cases, TOD was also chosen as the burn-in TC and in all cases this is correct, but because of the random switching behavior, the burn-in matches the Quicktime TC only about half the time.
Unfortunately, I do not have access to many clips from earlier in my camera’s life, but I do have one clip from about 10 months ago where this same thing appears to be happening.
This is a pretty serious issue, given that I am handing off dailies to productions that will need to conform later to the R3Ds. Now the EDL that they will be generating will be a mish mash of EC & TOD. I know I can slog my way through it manually, but it is not going to be fun. I would greatly appreciate any insights other users may have about this problem.
