Daniel Frome
1
COW Coin
Forum Replies Created
-
Oh, we definitely don’t know for sure. Only a combination of a factors:
– We need some of these features NOW – waiting until June would be annoying
– The $995 special from AVID and the FCP X $299 price make it affordable to own both if FCP X ends up having said featuresWin/Win situation in my opinion.
-
We’ve started a migration back to AVID too (well…our studio was never AVID based in the first place actually). The problem is not the “new” way of editing in FCP X. The problem is that we were hoping that FCP would introduce a few items that AVID already had…and instead we saw no new features to compete with AVID, just a better way of doing the stuff FCP already does.
-
You’re a life saver. This worked, so long as I put a clip on every track that I needed to display.
-
You’re correct. Just place the 720 60p (which you’ve now conformed to 29.97) into your 1920×1080 timeline and scale it up. That’s the correct move.
-
I’ll also chime in here:
It’s not just long GOP. It’s a project size issue. Whether you’re editing dvcproHD, XDCAM, whatever, we found that the bigger the .fcp file the more frequent your crashes will be. Having lots of RAM won’t solve the issue, since FCP is a 32bit application and will only use/see about 3.5GB of RAM.
We found while editing dvcproHD footage we could get to about 50MB projects before crashes started to occur. Projects that were 100MB in size crashed so often that they were not usable. In between the 50-100 size there was generally a linear correlation of stability/size.
The tollerance for long GOP projects is worse, but I can’t say for certain how much worse. Either way, any project less than 50MB shouldn’t be of any huge concern.
How will Apple fix this? A 64bit re-write will not completely solve, but should help increase the threashold. The issue is somewhat unavoidable due to the nature of how fcp stores its information. Looking at the new Premiere CS5 (which shares much of the same project architecture) we can see that the 64bit code does indeed allow bigger projects that don’t crash. We should hope that the same will apply to FCP.
-
No, an OMF will not do the trick.
The key is to create a quicktime with multiple stereo tracks. This enables us to create 1 quicktime file with separated audio elements, and distribute the file to various departments of our studio who all have different sound requirements. There’s lots of other cases where we use this feature (which is possible with FCP).
-
Already submitted this feature request — so your extra nagging definitely can’t hurt 🙂 Thanks for your help.
-
Submitted. Thanks again for your help.
daniel
-
Thanks Todd. I actually saw this post in my search before asking the question. I’m sure it works, but it seems a little cumbersome.
On a similar note, my initial google search showed that all editors across multiple software (final cut pro, vegas, premiere) are all asking for this feature. In the emerging tapeless world the filename display is just as important as the timecode. At least it is for us (an animation studio). I’ve submitted a feature request to make a video filter that does this. I hope someone listens — it would be great to have.
As a side note: We use FCP at work, but several key people here (including myself) have been quite giddy about PproCS5. It’s a great product and we are actively looking at making the switch at our studio. It’s small hurdles like this that we’re looking at overcoming before diving in.
-
Do this —
1) Make a duplicate of your sequence
2) right-click that new sequence “make sequence clips independent”
3) right-click sequence and “make offline”The sequence now becomes a giant batch of “OFFLINE [filename]” visuals. Take this sequence, and drag it back over-top of the original sequence (which has the media still connected). Then crop off everything except the filename.
It’s going to take a while to render out the new sequence – but it works.
Apple should really just include a filter to do this… it’s really stupid.