-
X mismatched Frame Rate projects/ wave bug fix/ Logic Import still broken
Just a couple notes here I think some may find helpful.
If you import using REDCODE for your R3D files, and create proxies inside of X, it will not create proxies based off the frame rate of the current project setting, but will base it off of the original camera frame rate. Also some frame durations were wrong. So I recommend you use Redcine X or resolve for your proxies, not REDCODE.
Also I complained on a weekly basis and they finally fixed the issue with wave files and multiple imports some of you may remember I was complaining about that.
One more note, there are so many threads stating X will pull down footage for you based on your project frame rate. This is absolutely false.
Logic import is still broken, I find it hilarious that it’s still not fixed, (probably because I’m using protools) But this is a disgrace, and a slap in the face and quite a surprise for anyone who upgrades to Logic X. So yes Logic Pro X import is broken, please make people aware of this so they aren’t screwed when they try to transfer.
-
18 Replies
-
[james Lackleter] “but will base it off of the original camera frame rate”
But isn’t that what you want? In order for X’s original/proxy workflow to function, frame rates need to match, otherwise you can’t successfully flip between them. If you change the frame rate, then it’s not really a valid proxy of the original.
[james Lackleter] “Also some frame durations were wrong.”
Can you clarify?
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[james Lackleter] “Logic import is still broken, I find it hilarious that it’s still not fixed, (probably because I’m using protools) But this is a disgrace, and a slap in the face and quite a surprise for anyone who upgrades to Logic X. So yes Logic Pro X import is broken, please make people aware of this so they aren’t screwed when they try to transfer.
“I don’t know what you mean by this James. We pulled in an AAF from FCPX into Logic Thursday. Are you talking about importing the XML? That resulted in a ton of layers so our AAF was the better import option into Logic. Or are you talking about sending a project from logic into FCPX? Because I’ve done that too. That actually worked really well.
John Davidson | President / Creative Director | Magic Feather Inc.
-
24 to 25 is a standards conversion, which typically does not involve adding a pulldown cadence. Very rarely you’d see 24+1, and you’d more likely see the speed change (footage speed changed to play 24@25), but most professional standards conversion done today is motion compensated through hardware.
Fcpx does allow real time speed change conforms, but you have to hold it’s hand.
Red Proxies, of course, are going to be created at the frame rate shot. RCX does this too. Resolve might allow a different output frame rate, but that’s not going to match back very well, and by the nature of math will introduce either artifacting or speed change.
I wish you would explain exactly what it is you are trying to do as many of us have asked because we just may be able to help.
-
X does add pull down. That is completely true. Just drop a 24p file in a 1080i sequence and step through frame by frame and check it.
Regarding proxies- it creates proxies at the frame rate of the source footage which is the only way I can think of to make proxies. Certainly wouldn’t make it the frame rate of some unknown or possibly non-existent sequence. For that matter you could be using the footage in all sorts of different sequences.
-
[Bret Williams] “X does add pull down. That is completely true. Just drop a 24p file in a 1080i sequence and step through frame by frame and check it.”
As well as 720p23.98 to 59.94 and 720p25 to 50.
I think James is confusing pulldown with standards conversion.
-
It will attempt to, but not successfully. Take the same clip, make a 23.98 project, put in a 24 fps, and 23.98 version of the same clip, and note the difference in clip duration. Logic does not carry over surround, it converts to stereo and removes all add plugs. Also produces way to many tracks, probably because it has no reference since X has none. Cine X should have FPS option, I don’t use it but I’d be shocked if it didn’t.
I didn’t say X doesn’t attempt to do this, what I should have said is it doesn’t do these things properly to clear confusion.
-
This all depends on your source material.
A 23.98 and 24.0 version ‘of the same clip’ are going to have different durations unless you have motion compensated the change in speed.
I also pointed out in the other thread how fcpx is misinterpreting some of these speed changes and you have to drag them back out manually if you need to match original audio timing as audio has no frame rate (or resample the audio to match time).
One second of recorded audio is going to match the same second of recorded video at whatever frame rate the video was recorded. Once you change the video frame rate by altering speed, you have changed the reference timing and the video will no longer match the audio.
Do you need everything to be the same duration, or do you need to match a particular timing according to frame rate? Or both?
-
I don’t really need anything, just sharing some findings so maybe it’ll help someone. Thanks though, much appreciated. And everything is indeed synced so no need to recut the project. It was just the issue I stated above, X not correctly playing back. Thank God.
Also just to clarify prior post, my point is if I take the same clip in 23.98 project, one at 23.98, and one 24.00 fps, if X is was accurately converting the 24.00 fps in playback to 23.98, then these two clips should have the same length duration.
As much as I hate this program I do like some things. A friend gave me a DV tape from his sister’s wedding, asked me to cut it together. One hour for transcode, thirty minutes to cut, recorded at 29.97, brought down to 23.98, automatically resampled audio. Two hours including export.
-
[james Lackleter] “Also just to clarify prior post, my point is if I take the same clip in 23.98 project, one at 23.98, and one 24.00 fps, if X is was accurately converting the 24.00 fps in playback to 23.98, then these two clips should have the same length duration.”
What exactly is converting the clip? Are you applying some conforming in X (now called “automatic speed” – WTH?) because otherwise a 24fps clip containing the same set of frames should definitely be longer than a 23.98 clip.
-
Not if it’s suppose to be pulling down the footage based on the project frate, which is why I said it does not automatically pull down footage.
Reply to this Discussion! Login or Sign Up