Frage von Vanguart:
Hello,
I have the following problem.
We have a short film a few sequences in 720/60p or 720/50p filmed later in order to make clean slow motion to ...
in average yields now the following problem when I import the clips into a 720/60p or 720/50p timeline and the speed to 50% drossle everything works smoothly and cleanly, I do it but in 720/25p timeline, the format in which the film is to be played later, I have violent jerking, as if it were only about 25p material, where the software calculates the slow motion ... in the correct speed to play the clips in 25p timeline no problems ... bildüberblendung I've drawn ...
where is the mistake ... have the same approach already used in a previous project in Premiere and have no problems, so why shrugs Final Cut at the history around it ... it is s.einer System Preferences, I have to convert the clips or specially can be interpreted, is a hidden button somewhere for oscar lupen time ... what do I do wrong ...
Thank you very much
Vanguart
Antwort von MarcBallhaus:
Is known, but no problem. Put the sequence as the 50p sequence s.and then build your Slomos quite normal - but without setting intermediate (Häcken at not fading!).
The finished cut do you play then later with Exporieren -> Using Compressor, and then choose where you just 25p. What is not funktioniett Export -> Using QuickTime Conversion. Experiment itself, the quality is completely different with Compressor, although actually be sorted out only the Zwischenbidler.
Another workflow is about Cinema Tools, but you need to first convert everything to ProRes. Will hot, all the clips in Cinema Tools for 25p conformal reinziehen and then to the Project. Go synonymous, but I find cumbersome.
MB
Antwort von Vanguart:
okey, I once tried habs, the compressor seems to me synonymous with wokflow nich results lead to the right, similar to jerky for me like it came straight out of final cut in the 25p timeline ...
and the variant with cinema tools is a bit complicated, but seems to have a better result to ...
And besides, I already find that the problem is nen, da gibts because no other possibility ... more
gibts infos about whether everything in Final Cut Pro 7 has been improved because ne send zeitlupe not get directly from the timeline is a bit too annoying to find a cut of the quality program should be able to handle selbstverständlicherweise sone function smoothly ...
regards
