[Ron James]

As mentioned in the other posts, you need to post your actual FCP sequence settings. It doesn’t matter how great your titles are when you bring them in, it matters how FCP is treating them once they get there.

I’m guessing you’re in DV-NTSC (aka DV25) and what you’re seeing is good old DV compression.

G5 Dual 2.7 GHz
2 GB RAM
OS 10.4.6
FCP 5.0.4
QT 7.1.1

[Ron James]

Big thanks to everyone for the great help. I’ve got a new appreciation for Activity Monitor, that’s for sure.

It must’ve been one of two things:

1) I reinstalled the FCS2 upgrade

2) We’d been jumping around from DVNTSC to HDV, because the interviews were shot both formats over time, so I opened my problem sequences and put them into new sequences after choosing Easy Setup to match the format. However, instead of just copying and pasting in, to be safe, I matched back to the source, then cut them back into the new sequences. Now the exports seem to make progress again.

Thanks again, everyone. Much appreciated,

James

[Ron James]

Ah, thanks! So I can probably rule QT out, then. Next step, I’ll try reinstalling FCS2

[Ron James]

Hey Jeremy, no that isn’t checked. I’ve been using since v.1, so I’ll never ever forget that ‘recompress’ checkbox. Remember it used to be selected by default?

I’m wondering now if the problem could be QT 7.3, although if I remember correctly, I had to install 7.3 to upgrade to FCP 6.0.2.

The exports are definitely bogging right down to a halt, though. And I did a full render with “full” selected. It’s almost as if it’s recompressing anyway. Weird. Whatever it is, it’s affecting Compressor exports, too, so I can’t get anything out of Final Cut. This is officially a pain in my backside now.

Thanks for your continued help!

[Ron James]

Jim, there’s most definitely something screwy in this Mac. Can you tell me what version of QuickTime you’re running? I’m wondering now if it’s 7.3 that’s wreaking havoc.

Thanks!

James

[Ron James]

Hi, rafalaos…

Okay, I’m back on this machine and it’s definitely bogging down. I’ve got a sequence that’s fully rendered (with “full” checked) that is just DVTSC w/ a timecode read. Right now, I’m just trying to export a reference movie.

The data read (in Activity Monitor) is averaging about 3.5 MB.

Final Cut Pro CPU is about 145%.

This only started happening after upgrading to FCS2 from FCS1.

James

[Ron James]

Hi, Rafael…

Excellent suggestion. I’ll be on this system again on Wed and will report back. I very much appreciate everyone’s help!

James

[Ron James]

Jim,

What OS version are you using, Tiger or Leopard? I can’t remember if I said so in my original post, but I’m using the latest of Tiger (just ran software update on Friday).

I’m really hoping it’s just a snafu. Maybe I should try reinstalling Final Cut Suite when I’m back in there.

Thanks for the response!

James

[Ron James]

I tried a similar sequence on an intel iMac and it worked normally. I wonder if it’s PowerPC-related or if there’s some gremlin hiding in that machine. I’ll try repairing the permissions a couple times and definitely try your suggestion, also, related to the rendering. I’ll try that first, actually.

Thanks for the help, Jeremy!

James

[Ron James]

Hey Jeremy,

Isn’t that the same as doing option-r? I’ve been very confused about rendering since they changed it way back in v.3 or whatever, but doesn’t option-r render all?

Great suggestions, though. I should’ve tried taking the filter off, too, but I was in time-crunch mode. I won’t be at that machine again until next week, but I’m making a list of your suggestions.

Thanks again,

James