-
Major audio video sync problem in CS5
Ok, we’ve got two brand new Mac Pro systems (8 core/12GB RAM/RAID 5/AJA KONA LHi). Both machines have the same issue:
Several 35 to 40 minute clips were captured from miniDV tape via Firewire with Premiere to DV .mov files. When put on the timeline, the audio plays in sync for about 25 minutes and then repeats from the beginning of the clip while the video continues. If the files are played directly in Quicktime or brought into FCP, they’re fine with no issues. The audio only repeats in Premiere. It’s incredibly weird.
ALL of the latest updates have been installed for all hardware and software. Reinstalled Premiere on one of the systems, didn’t change anything. Does anyone have an idea of what to do? Thus far, we’ve had nothing but trouble with these machines, and CS5 is often the culprit. Not happy.
-
5 Replies
-
[Micah McDowell] “When put on the timeline, the audio plays in sync for about 25 minutes and then repeats from the beginning of the clip while the video continues.”
Does this happen only on a timeline, or in a source monitor too?
If you create an instance of a clip with an in-point trimmed right to where the problem occurs (e.g. at 24 minutes), does the problem occur at the same place?
Alex
DV411 -
i have never found a project where i had to (as in HAD TO) save 25+ minute video files. even in long takes, it usually makes more sense to split and splice. big files are clumsy and, especially if you are going to edit them later, very very VERY bad for your workflow.
take the time to decouper (as in french for cut up) your material and name it properly. the time you invest in this initial stage will be paid back 20-fold: you will get to know your material better, you will force yourself to work in an orderly fashion, you will examine and precut all your footage in that beautiful organ you have placed above your mouth and beneath your baseball cap (aka The Brain), so on and so forth.
when you look at the timeline, the clipnames will help you understand the cut. when you look at your bin, you will know how many times (if at all) you used that specific scene. as opposed to 38 references to clip 000001.mov
and, in 10 years time, when you go back, you will love yourself (or whomsoever took the time to properly precut and name all the footage) for having all of the names meaning something (jack falls from tree is much clearer than 45 minutes of clip 000001.mov).
this isnt a workaround, it\s just a safe method for editing and organization which will avoid that uou (and your software) run into this type of problem.
why are you losing your time with minidv footage for anyway? i hope that it is historical material and that you are not shooting minidv in this day and age, otherwise i guess you deserve to have this type of problem. LOL
oh yeah, and, if you arent going to use FCP, and have opted for the CS5 suite, why not just save lots of money and use a PC? you really shouldnt be happy with your machines. or should i say with YOUR CHOICE of hardware – software combo?
-
@Alex… the problem occurs in both the source monitor and in the timeline window. Will check soon to see if it loops at the same point every time; not at that machine at the moment. I’m guessing it might.
@tonygil… thank you for your time in replying. It’s a live switched show recorded to miniDV master (our local station doesn’t take anything else… sorry we’re behind the times unlike you fancy folks). Capturing the show to add lower thirds and graphic opens/credits in post, trim and tweak a bit, and print to tape. I’ve captured files that length via Firewire for years on Avid, FCP, and Premiere alike, on Mac and PC both, with never an issue, hence my frustration. And the files work in other apps, just not in Premiere… I do think Premiere has a bug. I don’t think we deserve any problems, thank you.
-
Can you “trim” the clip in QT Pro and save it in two pieces and see if the repeated audio is still there?
The QuickTime format is interesting…it starts out by allocating room for an index file…then, when the clip gets long enough so that the index file is full, but it’s “land-locked”, QT makes a slot for a new index file further into the clip and first migrates the whole index file it created initially into it (filling it halfway immediately), then adds the data to it as necessary, and this process repeats as necessary as the continuous clip gets longer…
(For very long QT captures, those successive index file “migrations” get pretty large…)
I wonder if there is a new index file there that somehow doesn’t bother FCP or QT, but throws PPro off because it has a slight variation…or defect?
Do you have other long DV clips that behave the same way? Is it possible to do a test? Also…are you using the Kona card in this process at all?
Keep in mind that QuickTime is still principally 32 bit and the fact that CS5 being a 64 bit app can even deal with it is a feat of adaptation. On the Windows side, Adobe had to write its own QT frame server to act as a go between so that 32 bit QT codecs can be used by the 64 bit applications. I wonder if whatever special accommodation Adobe had to make on the Mac side is suddenly facing some pointer in the index file that it doesn’t fully understand?
I’d be curious what you find.
TimK,
Director, Consultant
Kolb Productions, -
Are you using multiple video monitors?
Reply to this Discussion! Login or Sign Up