I've just tried out the 2.0 Beta on OSX, and I'm sort of puzzled by the choice to revert to an individual frame saving method and not use QT.
I'm trying to figure out what the advantage is, considering the slowness that saveFrame() causes in the execution of instructions. For whatever reason the old movieMaker in 1.5 has no slowness issues whatsoever, as opposed to saveFrame() which slows things nearly to a stop after 100 frames or so.