Major problem with time code in 2.0

[Troy Murison]

Hi Tim,

I just created a ‘offline’ file in a new PPro 2.0 project
that was set to be a NDF project and got similar problems.
I created a offline clip with a reel number and tc set to
the following:

Media Start 01:00:00:00
Media End 01:00:30:00
Media Dur 00:00:29:29

These are the immediate resulting clip values in the bin
(still in NDF project):

Media Start 01;00;03;18
Media End 01;00;33;17
Media Dur 00;00;30;00

With a DF project, the same in points were used (; indicated
that it was DF) and the clip’s points tracked fine, even after
I then changed the project’s settings to NDF. However, subsequent
newly created NDF offine files with the project set to NDF
showed the same problem.

Again, I had no media in the project, standard 48k DV 29.97 NTSC
4:3 project setting to start. Don’t know what the results would
be with captured clips from tape that have mixed format TC
as I don’t have anything lying around and it’s late.

Just to be sure I also tried a Adobe SD-SDI project setting on
one machine too with the same results.

I had given up on 1.5 with all it’s messed-up TC problems, and
to be honest the (few) tests I have done to this point in 2.0
have been mostly okay (not perfect though) but these tests have
involved conforming EDLs created in Avid and FCP, which 1.5
would totally hose-up. At least 2.0 gets that mostly right in
my limited experience. But, I must say that this is very
distrubing that these kinds of issues have not been properly
addressed. I thank you for bringing it to my attention before
I counted on it to do a offline project. I’m sure others will
chime in and I am hoping there’s a simple fix or something I’m
overlooking, but…

I guess I don’t have any answers or help for you, but know that
on my machines (I tried the same test on two) exhibit exactly the
same results. I thought(hoped?) maybe I could disprove that 2.0
was the culprit and that starting the project in 1.5 was the
problem, but I guess not…

Sorry to give you this news… Good luck,

-Troy Murison
Seattle, WA

[Timothy Eaton]

Troy,

Thanks very much for giving it a try. Maybe an Adobe connected reader will also take a look at this — it would be great to hear that there is some simple answer!

I’ve been a long-time Premiere user and we’ve had various problems with time code in the past. But with 2.0 I assumed these problems would go away since there are other fine improvements. How hard can it be to write a software module that deals accurately with time code since it’s an absolutely essential component of video editing systems? I’m not going into full rant yet, but I’m thinking about those sixty hours of digitized footage duplicated on three Premiere offline systems with three editors using the same footage, several hours of selects, and fifteen minutes of edited program with hundreds of edits. Ouch.

Thanks again Troy,

Tim

[Ken Adolph]

What is the original source footage? DV? HDV? Other?

Ken Adolph
Media Group
Editor/Post Supervisor
https://www.mg.ca

[Timothy Eaton]

Ken,

The source material is DVCPro HD from a Panasonic AJ HD1200 deck outputing composite SD video for offline editing, digitized with a Matrox RTx.100 card. But 2.0 converts all of that code to drop frame even if I unlink the video files and make them all offline, so they are no longer seen as a Matrox DV file, and in the process of converting them to drop frame, it offsets them dramatically and unpredictably. This is why I decided to see what would happen if I simply created an offline file in the project window. I was willing to re-enter all of our digitized files manually from an old list. (You can try it yourself — it only takes about ten seconds to create one) But the fact that 2.0 alters the simplest user created offline file, essentially making it useless for digitizing rules that plan out. I’m hoping to hear there is a simple solution (not a workaround) for this.

Thanks for any help you can give. Tim