James Lackleter
Forum Replies Created
-
Ah perfect! Thank you
-
What is the frame rate of your video? Do not use multiple frame rates in this program.
-
Jeremy are you aware of any other bugs. I’ve cut the whole thing in X and I’m so close to being done, don’t want to recut in Avid… I’m just paranoid about finishing in the program. I think it was you who mentioned clicks popping up (pun intended) with faulty faders. Which I’ve just been fixing with the range tool. Everything is seemingly fine now that I’ve brought all the 24 clips down to 23.98 by rerendering proxies. Thanks for that by the way.
I’ve also had issues with certain clips not panning to left and back speakers, it’s not phase issue. Otherwise surround has been working out fine, I did most of the work outside of X and imported the clips. Logic filters for channel EQ and Limiter work great.
Anyway any other bugs you know of?
P.S. Oliver I know you use resolve, I’m sure some of you other guys do. A bug in new version which screwed me. If you move the directory of your R3D files, they will not be able to link back. Even if you put the directory back in it’s original place. Only happens with R3D files.
-
Nat, Resolve is for color correction not audio mixing
-
The scene was a 5 minute long take with no cuts, starts as a cu and pulls back to wide. It’s impossible to tell, especially since it moves back to wide. It was just the faulty playback of 24 fps pushing it out of sync.
This also explains why it was playing back fine in MC but not in FCPX.
-
Yes the fractional problem is what I was experiencing. I just rerendered 23.98 proxies for all the 24.00 fps footage. When I XML out to Resolve, I simply change frame rate from 24.00 to 23.98 and Tom’s your uncle.
-
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.
-
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.
-
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.
-
I think FCPX has jumbled information and automatic pulldown/up is messing up the sync. FCPX seems to have problems with WAVE files in general, I did convert to AIFF which solved nothing.
Let me make a new test with Avid without using the proxies I made in FCPX with the Redcode, because I suspect FCPX pulled the footage and is not reporting it.
I will use RedCine, export the 24 fps clip and 23.98 and load it into 23.98 Avid Project with unaltered BWAVE and see what happens.