Mark Maness
Forum Replies Created
-
And they still do in FCP7!
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
No.
I can tell you that if you add a Motion project to your timeline, such as a simple lower third, it will crash about 90% of the time. I use Motion projects on the timeline because this was on the the big selling point of FCP6 if you remember. Besides, its keeps the drives cleaner and makes edit easier, except for the crashing.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
[Jeremy Garchow] “So when do your crashes happen? If you edit off of a local drive, do the crashes still happen (I know that’s a lot to ask, why edit local when you have a TerraBlock?)”
Well, I will admit that most of the time, our crashes have something to do with graphics. It could be a Photoshop file or JPEG on the timeline. It could be a Motion project. But sometimes, I’ll just hit the space bar to play my timeline and FCP just stops and crashes.
We edit completely from the TerraBlock. Very very rarely do we edit from a local drive. The last time was when the upgraded the TerraBlock from 6TB to 12TB.
Either way, every time there is a crash, you can reset the permissions and a long list will show what has been fixed.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
[Jeremy Garchow] “That’s a lot of different applcations to crash, and the common thread does seem to be all video type appications which might point to the extrnal hard drive. I’d plug in another drive and see if it works better. If it works better, you can probably assume your drive has too much information, if you are still crashing, I’d suspect something more at the system level. “
All very true, Jeremy. But we are seeing these issues too on our systems. Ours do have 500 gig OS drives that are about 60% free space, and our video goes on the TerraBlock (shared fibre channel array).
The only thing I can say… when these crashes do come, I usually reset my permissions and I almost always have a long list of corrected permissions every time.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
Hey, it could have been one of the Microtime switchers. Do you remember them?
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
What kind of Macs are you using, Walter?
I have found this to be an unstable version in our post house. I crash about 15 – 20 a day. Mostly graphics card issues – ATI X1900 512m. The computers are Mac Pro systems, first generation Quad and Octocore, each with 8 gig of RAM, both running 10.6.3.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
I’m sorry… I should have clarified myself before posting. I was in a hurry whiel editing and rendering.
My sequences are a combination of XDCAM HD and HDV converted to ProRes422 (1440×1080). The HDV footage is the predominate footage, so I chose to edit in ProRes422. That makes my XDCAM HD footage the secondary. XDCAM and ProRes work well together in it full raster format (1920×1080). But as you know, XDCAM HD and HDV are both in the 1440×1080 non-square aspect.
One would expect that converting HDV to ProRes422 would make the footage full raster. This is not so. Thus, the added renderings and lengthier render times.
Apple needs to address this issue. Its only been two years like this.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
BUT…
There is a SERIOUS issue here. Yes, FCP can edit XDCAM HD and EX natively (after the Quicktime wrapper) but at 1440×1080. ProRes422 is a full raster codec at 1920×1080. Therefore, you’re forcing a non-square 1440×1080 into a full raster 1920×1080 timeline.
Here’s the issue. EVERYTHING has to be rendered. Yes, it looks good but at a rather lengthy render time and if you change anything, re-render.
This is a very very slow workflow and had caused lots of crashes when using any plugins on the clips. All of my software is up to date and active. My system works perfectly with DVCProHD but has extreme difficulty with XDCAM HD and ProRes422.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
I try to edit on one codec only. But those codecs are the ones we use primarily. Its not codec specific problem because it happens in any codec that we work with, like DVCProHD ( our codec of choice because of speed ).
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com -
To add to Jerry’s suggestions…
Don’t export to H.264 straight from FCP. Export a master program in the codec you edited, then compress your video in Compressor. The final output will look much better than inside of FCP.
_______________________________
Wayne Carey
Schazam Productions
https://web.mac.com/schazamproductions
schazamproductions@mac.com