Ron James
Forum Replies Created
-
This happened to me once and I think I simply went into my pref’s and emptied the thumbnail cache. Can’t remember at the moment if there’s an option to empty it, or if you have to workaround by choosing a new location. You could always shutdown FCP and go to your thumbnail cache at the finder level and trash it.
Either way, that should restore the proper thumbnails.
HTH
-
That’s weird.
I’m not a big fan of the slug, though. It’s always caused problems for me. What I’d do is export some black as a self-contained clip, import it and use that as your slug.
One of the problems I was having with the generated slugs was when using the TC reader for TC burn. At first, it just dropped the timeline timecode whenever it would hit a slug, but then it started messing with the TC values (in the reader) throughout the rest of the show. More trouble than they’re worth, IMO.
-
Ahh, this must be why I lost sync when following your instructions for v.1.1 in FCP 5?
-
” Well, actually rather than applying the wiggler to a layer it’s more like applying a randomizer to keyframes. In AE it’s great because you can apply the wiggler to any parameter.”
Ah, yes. That’s exactly what I thought it was. I seem to remember you could apply it to any kind of keyframes. A tool like that for FCP would be amazing.
-
” Newest version of FCP allows you to update PS files (and other linked files) on the fly and reconnect automatically. There’s a new check box in prefs “automatically reconnect”.”
Ah, thanks for that! Never even noticed this setting.
-
https://www.macworld.com/2006/02/secrets/marchcreate/index.php
This is a good little guide to using Compressor for the conversion. My guess is most users haven’t tried it, or don’t even know these settings exist.
-
What’s wrong with Compressor? The trick is to go in and change some frame settings. It’s going to take a lot longer the better you want it, though.
I actually just used the Nattress 1.1 filter (yes, I know there’s a newer one) on a feature-length NTSC conversion to PAL and ended up with video that was about 15 minutes or so shorter than the audio. That was after following the instructions very carefully and then waiting 12 or 13 hours for it to render.
I was on a workstation in a prod. company, though (not my own workstation) so maybe there was something else fouled up in the FCP settings that I wasn’t aware of, but I doubt it.
In the end, I had to get out Compressor to do the job.
Has anyone else had this problem with the Nattress conversion? And is there any noticeable difference from Compressor when you actually set the frame controls to better and/or best?
-
Or just use the flicker filter in FCP. It’s worked pretty well for me in the past.
-
Couldn’t you just use a photoshop file and update just the photoshop file before opening the project? The file would update in every instance, wouldn’t it, especially if you keep it as a master file and make sure you don’t break the affiliate relationships (so you could simply force it offline, then reconnect it to make sure it updates every instance)?
-
I’ve gotta add, though, from my experience of working on many different systems since v.1, FCP plays a lot nicer when *clips* are captured, as opposed to whole tapes, especially when you’re working on a large and complicated project. For example, I’ve never personally had to deal with the dreaded ‘preparing video for display’ problem that so many have.
Further, I personally can’t stand having to shuttle through hour-long clips in the Viewer. I find it very clunky. It wouldn’t be so bad if you could zoom into the playhead area. If I’m searching for something through an full-tape clip, I dump it into a timeline first.