Sean Oneil
Forum Replies Created
-
Dan,
To do the things you want, you have to understand the fundamentals of how Quicktime and all the Apple pro apps work.
For example, an important tool you are overlooking is Cinema Tools. Quicktime movies have a header which includes, among other things, timecode and playback framerate.
Final Cut cannot re-interpret the framerate of any piece of media for whatever reason. But it doesn’t stop you from changing it. Open up Cinema Tools and import your clip. You can conform it to whatever speed you want. So if you want 59.94 video to be interpreted as 29.97 and thus playback at half speed, Cinema Tools is the way to do that.
Sean
-
[Dan Powers] “Second. Final cut takes clips that are 23.98. After Effects will render at 23.98 and FCP chokes on it. You have to render out of AE at 23.976 not 23.98.”
It’s ALWAYS 23.976. Look at the math. 23.98/24 = 29.97/30.
Final Cut and all Apple products refer to it as 23.98 for purposes of simplicity even though it really means 23.976. Based on your experience, AE outputs 23.980 literally, which is never something you want.
In other words, if 23.976 is the preset option that’s the one you always want to use. If 23.98 is the preset option it really is 23.976 – they’re just rounding up the number for simplicity.
Sean
-
[walter biscardi] “The problem was identified by the Adobe Encore team to be a problem with either Quicktime or the Mac OS. The other problem was the Encore team neglected to tell us this nifty little tip until yesterday when they told us all is well in CS4.”
I’ve seen a lot of your posts showing disapproval for Adobe’s way of handling these problem. I don’t blame you one bit, and I share your opinion. I just spend over $1000 simply because there was no other reasonable way to create a BD. I don’t use Photoshop and AE intensely enough to merit the upgrade to CS3 – I just did it for Encore. All software has bugs at first, but I would expect something that’s been out this long (CS4 was just announced after all) to have been fixed by now.
Sean
-
[Shane Ross] “But then it won’t match with your digibeta timecode for when you re-capture…so that is a pickle.”
You can still have the original 29.97 Non-Drop frame timecode embedded in 23.98 video.
Sean
-
The Quicktime Player does this all the time. Some flag telling it that it’s anamorphic was not present.
If Final Cut says it’s 1440×1080, then that’s what it is.
Sean
-
[walter biscardi] “Are you working on a Mac?”
Yes, I am.
Sean
-
[Jeremy Garchow] “But have you done this conversion in Compressor before? You might be surprised, especially in this case where the audio can’t take the pitch up.”
I use Compressor every day. It’s awesome and does an excellent job no matter what kind of conversion you do. That wasn’t my point. One should never convert 24 to 25 except in rare circumstances. They should instead conform it, which is standard practice.
Sean
-
[Jeremy Garchow] “Sean, have you acutally looked at this in Compressor and then tried it for yourself?
There is a ‘fast’ and a better and a best.”
I said there’s no “fast conversion” in Cinema Tools, not Compressor.
Sean
-
[Paul Del Vecchio] “I couldn’t agree with you more, Eric. Premiere is a great editor. At this point, I believe Avid, FCP, and Premiere are all great editors. But yeah, Adobe has to somehow get people to look at Premiere again. I remember talking to a FCP editor and him saying, “I hate Premiere, everything you do, you have to render, render, render.” Not the case anymore. Premiere just got a bad rep from before it was Premiere Pro.”
The thing is, Premiere Pro has been comparable to FCP ever since it became Premiere PRO – back in 2004 or whatever. Four years later it’s rep doesn’t seem to have changed. They should have dumped the word “Premiere” from the name and called it something completely different.
Sean
-
[David Chabashvili] “Did the same conversion in FCP – same results. Also tried fast convert with Cinema Tools, but the result is same – subtle pauses every second.”
Dave, it’s a big mistake to use Compressor for this conversion. 99 times out of a hundred, you don’t convert it. You “conform” it using Cinema Tools. I don’t know what settings you used (there’s no such thing as “fast convert”).
Conforming (not converting) simply tells QT to play it back at 25fps instead of 23.98. It doesn’t alter the video or add extra frames. It just speeds it up ever so slightly. This is really the only proper method for turning film into PAL, unless this is a music video or something where the audio speed absolutely cannot be altered.
In a way you are ruining the video by adding redundant fields. A reverse 12:1 pulldown is very difficult (no Pro Apps tools support it) for any editor who wants to cut TV spots, trailers, author a DVD etc. You’re making a big mistake IMO.
Sean