David Burch
Forum Replies Created
-
In my experience hardware works much better, especially when downscaling ineterlaced footage. I get beautiful results from my Kona LHe. However, I use software downscaling when working with 24p, so that I can create a progressive 24p DVD.
-
Here’s something you might try:
First, copy your project to a different drive, without copying the event files (project only). Next, select your newly copied project, go to the file menu and select “consolidate media”. This will give you the option to create a new event with only the media used.
Hope that helps.
-
I would highly recommend editing in a standard video size, and then re-sizing your final product when you’re done to your client’s specifications. You could shoot 720p and upscale slightly, or shoot in 1080 and downscale (probably the better option).
The reason FCPX only edits in standard sizes is because those are really the only sizes cameras shoot in. The only time video should ever be in a non-standard size is for content delivery, either for web distribution or for mobile devices. Delivery formats should be avoided like the plague when editing; always edit from source material if at all possible. This goes for DVD, web video, and even Blu Ray. If you have no choice (if you don’t have the source material to work with, for instance), then your best option is to first convert the video to a standard, edit-ready format like ProRes 422 before editing. Hope that helps.
-
I found the problem. Apparently, a single .psd file was causing the hang. Here’s my theory: because FCP now is capable of working with Photoshop layers, it has to rasterize each layer separately instead of using the pre-rasterized, flattened image that Photoshop creates. My hunch is that it was getting hung up on a smart filter my .psd was using, causing a recursive loop and thus the memory dump. This would explain why the latest version is the first time this issue has shown up, and also why certain projects seemed to work fine while others didn’t.
So the take-away is, beware of importing Photoshop files, especially with smart filters.
-
A bit of an update: it seems that the problem is not limited to simply trying to export. It happens when I try to load a project into the timeline as well. Looking at the Activity Monitor, what starts happening is the program will quickly eat up all physical memory and then start paging out to virtual memory like crazy, with hardly any page-ins. This seems to go on indefinitely, until I force-quit the program. Meanwhile, FCP is non-responsive (spinning beach ball of death).
I have tested some of my other, smaller projects, and they seem to have updated to the new version just fine. I’m beginning to think that the problem lies with the process of updating my rather large event to the new version. I have tried hiding all but one project file, and that doesn’t fix the problem. This never showed up before the update, so I know it’s not that my computers simply can’t handle the media. I think something is broken and causing a recursive loop when FCP tries accessing media files. That’s my theory, anyway. At any rate, it’s infuriating. At this point I’m going to have to go back to a backup drive on my one computer that hasn’t updated yet and export full-resolution versions of each project, so I can continue working from those in a new event.
-
I’ll add my $.02. I would love to see a return of batch exporting and in-timeline chapter marks. These seem like simple features to add back in.
-
I’m on Lion. I tried moving the codecs out of the QT folder as well…no dice. I think I’m just going to try a full system restore.
-
I’m not seeing a “receipts” folder in my user library. In the Mac HD root library, the only items are BSD.pkg, InstallHistory.plist, and a folder with nothing in it called db.
-
Good suggestion, but when I tried it said “cannot install; a newer version is already installed”.
I tried re-installing XDCAM Transfer…that didn’t work either.
-
That seemed to do it! Thanks!