[Dan Shott]

Yes, you can media manage a sequence without the media online. For shows that we send to online where the media is going to be redigitized we actually media managed it with the media offline. Here is the settings we use.

In media manager have it Create Offline clips then click Deleted unused media from duplicated sequence and click Use Handles (then select how long you want the handles to be). We usually uncheck everything else except Duplicated selected sequence and place in a new project.

This will created a new project with your sequence in it and a batch capture of this will bring in just the media in the sequence plus handles.

[Dan Shott]

Yes, you can media manage a sequence without the media online. For shows that we send to online where the media is going to be redigitized we actually media managed it with the media offline. Here is the settings we use.

In media manager have it Create Offline clips then click Deleted unused media from duplicated sequence and click Use Handles (then select how long you want the handles to be). We usually uncheck everything else except Duplicated selected sequence and place in a new project.

This will created a new project with your sequence in it and a batch capture of this will bring in just the media in the sequence plus handles.

[Dan Shott]

That is exactly the problem we have run into. We export these stills so we can work with them in Photoshop (where they do come in at 640×480) and then bring the psd files back into Final Cut. If you use Photoshop to stretch them out to 720×480 they look pretty close to what they should be but that doesn’t seem to be the ideal solution, plus its a pain to have that extra step.

To earlier posts, it happens when exported from both the viewer and the canvas, and unfortunately a screen capture wouldn’t work as we need these to be accurate pretty much to the pixel.

It seems like Apple tried to fix something that wasn’t broken for people who use these stills in video.

[Dan Shott]

As a post house that has been plagued by the lost render files in FCP6 (that the update claims to fix), I would also love to hear if anyone has run into any problems with the update/knows of any reasons to hold off on updating.

[Dan Shott]

Here is the article that was mentioned. So far apple has admitted FCP 6 has a render issue, but not real fix yet.

https://docs.info.apple.com/article.html?artnum=306068

[Dan Shott]

We just started seeing this same problem with DVCPRO HD since we upgrade to FCP 6 (now running FCP 6.0.1 QT 7.2)

I’ve been running a lot of tests on it and find that some exports come back in fine and others come back in needing to be rendered. The only thing I’ve been able to find consistent is the clips that are brought back into the same sequence that need to be rendered, if you turn on Toggle Clip Keyframes they all have a blue bar showing FCP thinks they’ve had a speed change applied to them.

I’ve also seen other weird things with it. For example, there are two clips next to each other in a sequence. If I export them individually the exported clips come back into the sequence fine fine, but if I export them together it comes back in needing to be rendered.

One more thing I’m just now noticing. If I export a couple clips in a sequence the new clip comes back in fine. If I put a transition between two of the clips it comes back in saying it needs to be rendered, thinking it has had a speed change applied.

Not sure what any of it means, but thought I’d throw in what I’ve been seeing in hopes of finding a solution to the problem.

[Dan Shott]

Looks like on the reimage some of the machines had their energy savers set back to put the hard disks to sleep whenever possible.

Thanks to everyone for your help!

[Dan Shott]

We wiped the drives, did a fresh install of the OS and software and then ran all of the software updates.

The editors have been reporting that they are noticing their machines gets slow if they let it sit for a bit, then when they go back to edit, the machine seems to take a while to ‘wake up’

[Dan Shott]

We wiped the drives, did a fresh install of the OS and software and then ran all of the software updates.

The editors have been reporting that they are noticing their machines gets slow if they let it sit for a bit, then when they go back to edit, the machine seems to take a while to ‘wake up’

[Dan Shott]

Thanks for the suggestions David. Unfortunately we’ve tried both of these without any success in speeding up Final Cut Pro.