The playback frame rate can vary as sometimes
QuickTime cannot process all the data so drops
frames. That is wht there is an option in the "view
menu" play all frames - this will play every frame
but at the expense of time accuracy. However a recent
mac should be able to play all the frames of most
codecs in time.
I have had the random variable sync problem in Logic
for a while now - including Logic 6.4.3 Not sure of
the cause but it's definately a problem - I'm just
surprised more people aren't noticing it.
Julian
Yeah, but what's it doing at a rate like, say 25.19 ??
Does it try to bring it's own artistic approach out in the free world trying to show me some of *it's own* suggestions of what's a good movie ?
🙂
And "more people"... - well, there IS definitely a difference in people's ability to notice these things, and most of Logic's users will never ever use movies at all. Even if they do, they mostly do MUSIC, film scoring. And try to notice frame accuracy with strings...you'd be happy if every audio/midi is in sync to the scene, but not to frames. I mean, for music there's no problem at all.
I have to start/stop 20 times at 2-3 second bits repeatedly to exactly lip sync hundreds of regions. That's different.
Not that I don't agree with you, that there truly is bunch of jerks out there, even in the business, who don't care at all 😉, but for a lot of users there's simply little chance to ever get into it that close.
To Norway now, and to all the others of course:
I'm using the original Capture Scratch files now and it seems to works fine - so far.
Again, unfortunately this is a change of more than one state at a time.
1. It is the original imported movies, not the "export" of a FCP edit where I edited all 3 of them into one. The Import was done directly by logging out of FinalCut Studio 5.0.4 using a Formac TVR as firewire input device.
2. Therefore it is significantly smaller in its filesizes (10, 12 and 6 GB compared to the exported 28 gig file.
3. Video is now located on the same drive as the audio I'm using.
So what does that tell you techies out there ?
As I found this other thread about sync problems with FCP exported files in Logic, I tend to go on this one for now. For comparison these guys edited directly in QT and did the export from there and the resulting file played back ok in Logic then. So it's not the filesize, provided they are doing exactly the same edits. They assumed it a FCP bug.
And what about you guys here in this thread - are you using FCP exported files as well ?
What does it tell that it obviously works in ProTools ? (At least in Norway ?Maybe better processor cooling because of the climate up there ?)
Could it be a kind of bug of Logic and FCP together ?
Is FCP producing strange files ?
Or is Logic just too picky about it ?
Any help still appreciated...
spocintosh