I don't know exactly how iMovie works, but I suspect
it's basically an edit decision list (a relatively
simple file listing the start and end times of each
clip, and where transitions, titles etc. come in),
plus a QuickTime version of the movie for easy
viewing in iMovie.
That's correct. The list of clips stored in the project file shows the name of the Media file for each clip, plus the frame number of where the clip starts in the Media file and the length of the clip. With some historical data too for Undo-ing.
The QuickTime movie inside the project has a very different data structure, but a similar function. It's a reference movie with no video or audio data of its own, just pointers to the Media files. It knows which frames to play from each Media file, and when.
But when the final movie is
commited for recording to another media (tape, DVD
disk) the source material is taken from the original
clips according to the 'rules' of the edit decision
list. Am I correct?
__ ...even close?!
___ Just
guessing.
True.
(doesn't QT work with lesser resolution and
fewer frames/sec?
__)
Not quite true. iMovie uses QuickTime for everything it does (except control the iMovie user interface, of course.) All the Media files for video clips are DV Streams, a type of QuickTime movie. There's no separating iMovie video/audio from QuickTime. iMovie is just a front end for invoking QuickTime commands.
(I'm using the word QuickTime here to refer to the underlying system commands and functions that the Mac uses to play and edit video and audio. I'm not referring to QuickTime Player, which, like iMovie, relies on the underlying QuickTime software to do its thing.)
You can, of course, export an iMovie project to any kind of QuickTime movie you want — there are thousands of possibilities. If you want, the exported movie can show a smaller frame size and contain fewer frames per second. (There is no such thing as "resolution" in QuickTime, just frame size, in pixels.)
Which brings me back to the stuttering problem. If
the culprit lies in the handling of audio, then I
wonder if a solution can be far off. Since the
problem didn't exist in earlier versions, shouldn't
it be fairly easy to resolve the problem now?
____
Another wild guess!
It shouldn't be terribly hard to fix, but the problem that's been with us for some time and it's not been fixed. Since not everyone has the problem, the exact cause may be difficult to nail down.
The most anyone has been able to do is say "My guess is it's an audio problem of some kind." which this thread is helping to prove.
Your efforts to hang in there are very helpful. It's providing the most detailed information I've seen. When your work is done, I hope you send feedback to Apple with these details. If someone has their lights on at Apple, they should send you a hard disk and ask for a copy of the original project so they can analyze it properly.
Go here to send your feedback:
http://www.apple.com/feedback/imovie.html
Karl