going backwards with julian
I think some definative documentation of how Logic is syncing and how it effects frame accurate playback of QuickTime would be very welcome.
i agree.
You mentioned that Logic stays time constant but changes the movie playback speed. Surely that means the QuickTime exact frame rate is now no longer the same as the source video in the online suite so how can true sync be guaranteed?
no. this isn't right. depending on the codec, the video is seen in terms of "packets" of data which correspond to frame rate. but QT won't necessarily playback each frame at exactly 1/25th of a second, it might vary slightly. logic forces it to playback exactly 1/25th of its seconds. this is because the data rate might vary in the video i guess.
but audio is handled differently because it IS a stream. i am not exactly sure how QTs sync its video to its audio other than measuring the number of frames against the number of samples.
Also is there always a frame base as some quicktime files (MPEG 2 for example) cannot be edited until they are transferred into an editable frame accurate format.
muxed video and audio are a different issue altogether because they are bitrate dependant. in this scenario the video and audio are sort of "entwined" - again i'm no expert, but the info is out there on this one. not only that mpeg encoded video and audio is also dependant on the codec of the original material. for example and mpeg-1 will not play if it was created with sorensen 3 if the sorensen 3 codec is not installed on the system. mpeg is a muxing format not a codec - if i understand this correctly and i am pretty confident that i do.
And isn't a QuickTime file just a stream of data - it is the codec that interprets that data (as a constant stream?) and reconstructs the frame content as encoded.
it is entirely dependant on the codec. consequently there ARE all sorts of syncing issues which relate to audio and video with certain kinds of codecs. incidentally, it is generally considered a good move to use a low compression codec like DV when using logic unless you have a capture/playback card, because it is less work for the computer to decode. they greater the encoding generally the greater the strain on the computer. that said, it again dependant on the codec. some are really efficient at the decoding end such as h.264 which can give you really good quality video for relatively little cpu strain and very small file sizes.
Even on the capture side if you happen to be capturing in a quicktime format I would have thought the relationship with QuickTime would be generated by the host software not the card.
sort of - it is generated by the codec (in this case coder) which comes with QT and the capture device. i use miromotion jpega, which gives me extremely good results at a data rate of about 1.5 Mb/s. i play this back (i have to use this codec for the card to do the decoding - or else the computer will do the decoding) through the card and out on to a normal TV.
You keep mentioning video cards but I don't see how there would be any relationship between video cards and quicktime.
well, the video cards use QT as the format for the digitized video. they have to talk to each other regarding the unpacking of the compressed video data. therefore their relationship is critical. i remember absolutely not being able to use certain combinations of OS, QT, capture card driver.
if you are getting the QT from such a high end source, then depending on the codec i am sure that they should work solidly with logic.
to be certain of your aif file being exactly right with the film, you have to go by the BITC. if the file is being played back on a system synced to the video then the video will be set to chase the audio system and the event that you had at 567464 samples into your cue corresponding to 10:23:44:67 will match.
i have delivered this way for years with nary an issue.