Matt Lyon
Forum Replies Created
-
Ahh, cool… I haven’t had any fcp 7 gigs yet. I was looking at an fcp 6 UI. I should have mentioned that in my first post.
Matt Lyon
Editor
Toronto -
That\’s too bad it is not working consistently. All I can say is that I\’ve used the reel renaming functionality for many years and have found it to be very reliable. Maybe you need to re-install fcp? Drastic, I know…
For good measure, I would turn on \”ignore permissions on this volume\” in the property window for your external HD… If it isn\’t already.
Matt Lyon
Editor
Toronto -
//There is 4:3 title safe markers in a 16×9 sequence. They\’re small but they\’re there.//
I should have been more specific, I actually meant in anamorphic timelines. What I really want is a way to show the 4×3 area within a 16×9 frame so I can protect for center crop transfers… Or is there a way to do this and I\’m just missing it?
Matt Lyon
Editor
Toronto -
The keyframe editor is my big pet peeve too! At least give us indpendent x/y controls and a crosshair tool for moving the anchor point.
4:3 safe area overlay in 16:9 timelines.
Better caching for sequences with lots of stills. I edit lots of animation leicas (aka \\\”animatics\\\”) and the endless re-caching can be agonizing!
command-deselecting a clip also deselects incoming and/or outgoing transitions.
Realtime drop shadows for text (or is every machine I\’ve ever used just too slow??)
Happy new year everyone!
Matt Lyon
Editor
Toronto -
Hi Marrian, sorry if I wasn\\\’t clear… I wasn\\\’t using the word \\\”bad\\\” in the literal sense. The files are probably fine but in cases like these I like to eliminate all the variables one at a time to narrow down what is wrong… Hence the new project, copying the files to a different drive, etc.
When FCP changes the reel name of a clip it modifies the file itself on the hard drive. In your case it sounds like something is preventing this from happening properly. This could be a number of things. Now that you\\\’ve trashed your prefs, can you modify the reel name and get it to stick properly? The surest way to check is to close all open fcp projects, quit, relaunch and bring the files into a new project.
Matt Lyon
Editor
Toronto -
Yikes! Sounds like bigger issues then just some rogue files. Have you tried starting a fresh, empty project. Copy one of the bad files to a different drive, bring it into the empty project and see if you can replicate the problems.
Matt Lyon
Editor
Toronto -
What file system is your your hard drive formatted as? Changing the reel names in FCP should stick with the files, regardless of what system you bring them too. So I suspect the issue is with the drive. But in any case, you should be able to do everything you want directly within FCP, so I don\’t think an external tool is neccessarily the answer.
Matt Lyon
Editor
Toronto -
Hi John, you need to familiarize yourself with how sequence settings work. There is lots of info on the Cow and other places on the web (and of course, the FCP manual). But before you do too much work, you have to decide what you want your final product’s tech specs to be. HD, Standard def? WIdescreen? 4×3? etc… What’s your framerate? 23.98 (aka 23.976) is the most common for animation.
It’s not clear from your post if you are doing frame by frame “cel” style animation, and you just need to assemble the drawings in FCP, or are you importing lots of elements and using FCP to add movement? (or maybe a bit of both)
Matt Lyon
Editor
Toronto -
That’s awesome Andrei, glad you sorted it out!
Rike’s tip is a good one to keep in your back pocket. There are many cases where Final Cut will change the way it interprets media based on the default sequence setting you have selected at the time you import the files. Even though audio files don’t really have frame rates per se, Final Cut seems to pseudo-assign them one at time of import.
If you really want to geek out, export an xml of the timeline. Each audio clip has two attributes, “NTSC” and “TIMEBASE” that can get set improperly:
<ntsc>"TRUE"</ntsc>—- can be set to TRUE or FALSE
<timebase>"24"</timebase>—— I’m not sure what all the permutations of this one areSo my hunch is your clips initially had either or both of these attributes set improperly when you first imported. Following the steps in Rike’s post is the surest (and maybe only) way to flush FCP’s memory and re-import the files with the right attributes.
This is also true of still frames, which can lead to headaches if the frame rate of the still image doesn’t match the frame rate of your timeline.
So sorry for the information overload 🙂 I’m hoping this post might help someone in the future, because I see this issue come up a lot!
best,Matt Lyon
Editor
Toronto -
no problem Andrei, happy to help. I actually think that more can go wrong when dealing with just “pure” audio files. Select your clip and hit command-nine to open the “item properties” window. Check the audio format, sample rate and bit depth and compare them to your sequence settings. As a test, you might want to re-convert a file quickly in Quicktime player to AIFF and see if the new file has the same problems. Use whatever bit depth and sample rate settings match your timeline.
Matt Lyon
Editor
Toronto