[Raven Plenty]

The answer explained clearly by Andy (and apple.com). Thanks!

[Raven Plenty]

Actually to further get back to my original post, my hope was to be able to apply filters (whether video or audio) to entire sequences. As far as I know, the only way to do this right now is to make a nested sequence, but I still wish I could simply apply filters to regular sequences.

[Raven Plenty]

In this case it’s actually because the computer in question is suffering from the dreaded Compressor “unable to submit to queue” problem and I was hoping to just use Quicktime as a quick solution before trying to fix Compressor.

I think my question is still valid though, even if it’s only an acedemic one. Note: Quicktime can’t even play an mpeg2 file, let alone encode one. I still would have thought the mpeg2 encoder/decoder would automatically be added to Quicktime after installing FCP…it automatically adds Quicktime Pro functionality after all, why stop there?

[Raven Plenty]

Michael, thanks for the suggestion but it has the same effect as dragging a filter from the filter palette onto clips…it still just adds another copy of the filter in addition to the existing clip filters. (i.e. If I already have a Compressor/Limiter filter in a target clip, it just adds second Compressor/Limiter to that clip.) I was hoping for a way to update the filter settings on multiple clips. Thanks though.

[Raven Plenty]

In summary, in order to globally change the Compressor/Limiter settings to all clips in the timeline, I must make the change to one clip, copy (attributes) from that clip, remove all audio filters from the remaining clips, then paste the audio filter attributes to those clips. Sheesh! Room for improvement sez me.

Thanks very much for your help though. Cheers.

[Raven Plenty]

Next question… Is there a way to remove one type of filter (eg. Compressor/Limiter) but preserve other filters (eg. EQ) from multiple clips in the timeline? I see that I can right click the selected clips, choose “Remove Attributes…” and then select “Audio > Filters”, but that removes ALL audio filters.

Over to you David (et al)…

[Raven Plenty]

Thanks for your lightning quick response. The downside to that method is that if I decide to change the filter setting, I have to copy and paste all over again, and that actually adds a second copy of the filter rather than updating the existing filter attributes. Any further insights? Thanks again!

P.S. Please let me know if you think this is more appropriate for the FCP Basics forum.

[Raven Plenty]

No, sadly it’s all on one hard drive right now. This will be changing soon. What won’t be changing soon enough for me is the move to a non-tape camera in our office. Real-time capturing sucks, dropped frames or not.

You know that bungee thing looks pretty fun, even if it is going nowhere fast!

Thanks again.

[Raven Plenty]

re: “wouldn’t be accurate…” but it’s already captured X minutes of good footage, why wouldn’t it just keep everything that’s good up to the dropped frame, and let me recommence from where it stopped? Instead of dumping megs or gigs of perfectly good footage, making me start over from the beginning? I realize I’m just venting and not contributing to a solution, but still. Seriously, this isn’t a major annoyance to more than a few people?

Regarding the firewire setup, it’s being captured to the internal hard drive. That’s the only setup we have now, we’re moving towards setting up a dedicated editing station that’s a bit more robust. (Although the computer is a month-old Mac Pro with plenty of RAM.)

Thanks for your help.

[Raven Plenty]

Jeremy, the problem is with dropped frames, not time code breaks. And yes, we’re trying to capture a full tape – not full, about 30 minutes. Again, I don’t see why it has to lose the footage that’s already been captured just because 1 frame is dropped. Why not treat it the same way it treats time code breaks? I say: “arrgh.”

Thanks for your input Rafael, I guess we’ll give it a shot and keep a keen eye open for any jumps where a frame might be missing.

(Just a note, I only had this problem when I vainly attempted to do other work on my computer while capturing. My colleague was having the problem, maybe he was doing the same.)