Gates Bradley
Forum Replies Created
-
I’ve filed 31, haha.
Is that to say turning off the stopwatch by default is not an option? I figured it was a long shot…
-
Nevermind. A helpful friend from the good people at Arts & Labor in Austin, TX brought to my attention the scroll bar on the side of the video tab in the export menu. Ignorance it is on this one.
-
Again, you are correct sir. I reset the keyboard shortcuts to the default and it works intuitively, with the exact functionality I was hoping for. Sweet relief!
Gonna dig around and see why when set to Final Cut shortcuts this function changes.
Thanks again Kevin! You are one patient dude.
-
Thanks.
I have to say, this sort of willingness to listen to and help out customers – I never saw anything like that from apple. It’s really appreciated, and impressive.
-
Yeah, apologies, I should have gone into more detail. My footage was actual all shot 720p (native) on an HPX170, so it actual only records the 24 frames it uses (as opposed to pulling it out of 60), which makes my issue all the more bizarre.
-
Why would it need to be pulled down if it was shot, transcoded as 24p and being edited in a 23.98p timeline?
That is to say, I don’t know when or why Final Cut decided to do this. Is there a way to check pull-down settings for clips?
Ah! I found it. In the Modify>Timecode menu (a menu i heretofore in 7 years with final cut have never had reason to open) for some reason each clip was set to 30fps. Changing each one (one by one. awesome) to 24 solved the problem.
I wish I knew why it happened in the first place, but thanks for steering me in the right direction.
-
I’m currently in the process of making the switch to premiere, but am not really sold, and here’s why:
They get the big issues down. It’s amazing. I rarely need to render my timeline, it processes things so fast. The metadata options are amazing for organizing footage. Being able to edit most things natively (I cut a lot of 5D & P2 footage) saves a lot of time.
But the devil is in the details, and here’s where Adobe gets it wrong quite frequently. I’ve spent half my time on this project I’m working on trying to figure out what Final Cut makes intuitive. Now part of this you can chalk up to breaking in a new program, but part of this is just that the act of editing in a timeline was not as thoroughly thought out as in FCP (minus X, of course). I feel like I’m stuck between AVID circa 2002 and FCP.
My list of feature requests currently stands at 14, and it’s all basic, little stuff that makes workflows run more smoothly, but that added together is really slowing me down (and making me grumpy). My biggest gripes are…
1) No equivalent of shift+option drag to duplicate a clip (one has to copy, manipulate track activations, and then paste- see below)
2) There is no GUI for mapping keyboard shortcuts (taking me FOREVER to get it how I like)
3) only support for 4 camera multiclips (kind of odd given all that extra processing power)
4) the way it manages insert/overwrite edits vis-a-vis track activations requires too many unnecessary step
5) no quick fit-to-fill edit command (one has to go through a menu)The list goes on, but you get the idea. The bright side of things is apparently Adobe really cares about customer feedback.
-
…further update: in the source window, every frame that ends with a 3 or an 8 is skipped. so the frame counts run [00:01; 00:02; 00:04; 00:05; 00:06; 00:07; 00:09] with the same for the frame counts in the teens and twenties. So although it’s running at 24fps (23.98), it displays base-30 time code.
The problem is, this is really screwing up an XML export, as I have to migrate a sequence from final cut to premiere (long story), and it’s throwing the in-points of a lot of my edits off.
Would greatly appreciate some light being shed on this conundrum. I’m having to match up my frames in the two projects by eye (no fun).
-
I still don’t know why, but the issue seems to come from things I export out of After Effects.
So I export out of my AE comp and export settings are 23.98, and Final Cut recognizes it as such, except something happens in the source window everything gets screwed up. So it seems like it is, indeed, a Final Cut issue, but thought this was relevant info.
These are all either ProRes 4444 or ProRes Proxy files, for what it’s worth.
-
Also, I should clarify, that while this clip is a part of a multiclip (which had been collapsed), the same issue still holds true when I view the original media in the source window.
Running FCP 7.03.