[Timothy Eaton]

Thanks Tim, How do I clock it down in post? Tim

[Timothy Eaton]

Excellent Dezmond. Thanks for your help. I’ll try the CF 24FPS mode for HDV capture.

Tim

[Timothy Eaton]

Thanks Dezmond,

If we cross convert to 720p 59.94 would the clip play on a 24p timeline? Also, what happens if we shoot in Sony’s Cineframe 24 mode? Would that cross convert to 24p?

Tim

[Timothy Eaton]

Stefan,

Thanks for the help. I got it working today. Tim

[Timothy Eaton]

Hi Tim and all,

Adobe tech support was kind enough to call back this morning with some good news, a setting which had slipped his mind the day before. Under Edit / Preferences / Media…, there is a checkbox for Display Media Timecode In Source Frame Rate, which when checked eliminates at least the problems with creating an offline file in non drop code. Many thanks to Adobe tech Chris for chasing this down. He was very helpful.

On our end, we still have some work to do, but this gives us additional confidence that Adobe programmers are giving some attention to time code. Thanks to all who posted on this issue.

Tim Eaton

[Timothy Eaton]

As I tried to say Ken, my point applies only to the conversion of code, either with material that has already been captured, or with time code that is entered as non drop and converted to drop. I think the example I gave in the previous post was fairly succinct. If the time code for a given file is not converted from one tc format to the other then it makes no difference.

Tim

[Timothy Eaton]

Dave,

I don’t fully understand all the ins and outs of how PPro assigns these values or decides drop or non drop either. I do know that because 2.0 handles code differently from 1.5, and because I made an error in Display Format when I captured some of the footage in 1.5, we’re in big trouble. I also know that I should be able to enter non drop code in the project window and not have it converted to drop frame. Ken may have come up with a solution to that by suggesting we enter code, using capture instead. I know we’re probably looking at a lot of work to reconstitute our project. Maybe in the future we’ll simply do everything drop frame!

Thanks for your input — if you have any additional thoughts, I would love to hear them.

Tim

[Timothy Eaton]

Tim,

Change your project settings (Display Format) to non drop frame and try it again.

Tim

[Timothy Eaton]

Okay, for the purposes of sorting this out, imagine that I set my camera for hour 0 non drop frame code and record an hour of material. Suppose I then capture that material with my project settings (Display Format) set to drop frame in 1.5. 1.5 does not care about this error and treats it as non drop. But if I then import this material into 2.0, it now converts it to drop frame time code. Since the camera was set on hour 0, the offset in Premiere will be about 3.5 seconds at the end of the tape.

Suppose I now set my camera for hour 23 non drop frame code and record an hour of material. I then capture that material with my project settings (Display Format) set to drop frame in 1.5. 1.5 does not care about this error and treats it as non drop. But if I then import this material into 2.0, it now converts it to drop frame time code. Since the camera was set on hour 23, the offset will be almost 83 seconds at the end of the tape.

Two tapes, both of which have one hour of material, both captured exactly the same and imported exactly the same. But the offset is dramatically different, and the only procedural difference is assigning hour 0 or hour 23 in the camera. None of this makes a bit of difference if we’re simply going to finish with the captured material. But as soon as we make the decision to recapture and online (say in HD) it makes a huge difference whether we stayed in 1.5 in the first place since it doesn’t care whether we correctly set the Display Format, and secondly whether Premiere Pro understands that every tape effectively begins at hour zero.

Tim

[Timothy Eaton]

Hey Ken,

This just in. I tried using capture for manual entry and despite that fact that non drop frame code appears in the project window as drop frame under Video In Point and Video Out Point, it captures perfectly. This could be very helpful for us.

Many thanks,

Tim