James Brown
Forum Replies Created
-
From looking everywhere I found that there’s a chance the hanging I was experiencing was to do with the new way that Mountain Lion redirects graphics processing. On an older model Macbook Pro on FCP7 it may cause problems.
I am now running fine on Lion (I had to clean install Snow Leopard from the disks then upgrade to Lion), but I also had my 2 drives on FW800 daisy chained, this continued to create slightly different problems. I changed the configuration to running one of my drives on the FW800 and the other on USB 2.0 which works fine editing 1080p video in FCP7.
So the solution was both operating system and drive configuration, which made it difficult to diagnose. But this solution has been working for a good few months now.
Cheers,
James -
With the ripple edit tool selected Shift-Opt-click (Mac) enables you to individually choose multiple ripple trimmers.
You can either
1. Drag these ripple trimmers to your desired edit point.
2. Press E (extend edit to make the edit)
3. Press T (to go into trim mode) and then use J,K,L to dynamically trim.Once you get used to it they’re actually more versatile than Avid’s trim tools. One thing I would suggest to Adobe though is for an asymmetrical trimming mode, which goes into trim mode with video and audio asymmetrically selected, that would save a lot of time.
Cheers,
James -
In addition rendering in 8bit YUV (also in sequence settings). you’ll notice many of your preview bars go away if you use this because it’s not requiring as much processing power. I haven’t run into a problem since I changed both to Prores LT and 8 bit YUV in Sequence settings. Still early days yet though.
-
I’ve just been having a similar issue and have found many “solutions” in forums and none have worked.
It may be premature, but I have been working happily on my prores HQ 1080p footage on a FW800 drive for the last while (previously FCP was hanging nearly every 2 minutes) since I changed my sequence settings to Prores LT.
Obviously you’ll want to reset your settings when it comes to exporting, but in terms of a fix for the instability, it seems to be working for me so far.
-
The only work around I’ve managed for this is to mark the frame in the source window which rolls out markers on to all other instances of the clip. Then you manually find the marker in your resource/sync sequence. Obviously this stops being practical after about 20 markers.
To quickly find the clip itself choose “reveal in project” then at the top of the project window there is a drop-down menu of all the instances of that clip.
If anyone has a real answer to this question though I would love to hear it.