|
|
All the news now and in your digital future
Show all posts by user
This forum is now READ ONLY. You cannot post questions here.
Re: Crashes - 12 years ago
Ben King Wrote: ------------------------------------------------------- > Hey Jon didn't Rami have a similar to the issue on > a large project that turned out to be a one > corrupt audio file? Not sure... I didn't hear about that one. But while FCP uses QuickTime for a lot of things, it would appear that Apple has written their own code for certain functions (perhaps because iby Jon Chappell - Café LA
Re: Crashes - 12 years ago
Just to clarify - it's ok to install an earlier version than the one it shipped with, as long as it is not earlier than the OS it was designed for. For example, the 2009 Mac Pros were originally designed for Leopard and then Snow Leopard came out afterwards. So even though they started shipping with Snow Leopard, it was ok to install Leopard on them because the hardware support existed in the preby Jon Chappell - Café LA
Re: Crashes - 12 years ago
I just remembered a problem I ran into a few months ago. The company had a similar issue where the project would beachball for a good hour or so before opening successfully. After much head-scratching, we eventually managed to narrow it down to a particular clip that opened just fine in QuickTime (hence why Corrupt Clip Finder didn't find it) but Final Cut Pro had difficulty because it was readinby Jon Chappell - Café LA
Re: Power outage in the middle of Import from camera - 12 years ago
We have software that can restore media but it doesn't support HDV yet. The only other software I know of that can do this is:by Jon Chappell - Café LA
Re: Recombining FCP projects in to one project - 12 years ago
I agree with Strypes. You should also tread carefully when using media that isn't fully optimized for FCP.by Jon Chappell - Café LA
Re: Devil's Advocate asks: Why bother with Color? - 12 years ago
Shane Ross Wrote: ------------------------------------------------------- > Sorry, but the 3 way does NOT have the > functionality of Secondaries. You can't vignette > to isolate areas (known as POWER WINDOWS)...Color > allows up to 16. I use this a lot. Technically you could duplicate the clip, garbage matte it and apply the color correction. It won't look great and thoseby Jon Chappell - Color
Re: Crashes - 12 years ago
How big is your project file? The malloc error indicates that Final Cut Pro may be running out of memory. Remember that even though you have 16 GB of RAM, only 4 GB can be addressed by Final Cut Pro. 1.5 GB is reserved for frameworks so a maximum of 2.5 GB can be used for your project.by Jon Chappell - Café LA
Re: WARNING - Just did Prokit update. - 12 years ago
Here is a solution, providing you can get hold of a copy of the older ProKit framework:by Jon Chappell - Café LA
Re: "FCP quit unexpectedly" - 12 years ago
Sorry, I should have said "upgrade", not "update". It is a paid upgrade ($299) and I inadvertently implied it was free.by Jon Chappell - Café LA
Re: "FCP quit unexpectedly" - 12 years ago
Final Cut Pro 5.0.4 is not compatible with Intel computers or Snow Leopard. You need to update to FCP 6 or higher for Snow Leopard and Intel compatibility.by Jon Chappell - Café LA
Re: WARNING - Just did Prokit update. - 12 years ago
Ben King Wrote: ------------------------------------------------------- > Link to the 2010-02 Pro Application Update > 2010-02 > > > > Going to try backdating to this. > Unfortunately this won't work because ProKit is a separate update. I will be on Skype later - maybe I can send you my ProKit.framework (I haven't updated yet) and we'll see if that works.by Jon Chappell - Café LA
Re: "FCP quit unexpectedly" - 12 years ago
Can you post one of the crash logs here?by Jon Chappell - Café LA
Re: WARNING - Just did Prokit update. - 12 years ago
Ben, you should report all of this here: (requires free developer registration)by Jon Chappell - Café LA
Re: WARNING - Just did Prokit update. - 12 years ago
strypes Wrote: ------------------------------------------------------- > Sounds like an update to avoid. Yep, especially as it offers nothing new for Final Cut Studio.by Jon Chappell - Café LA
Re: Flash files - 12 years ago
The easiest way is to create an H.264 and change the file extension to FLV. This will be fully accepted by Flash. If you don't want to go down this route you will need to get a Flash encoder, which should ship with the Adobe Flash authoring software.by Jon Chappell - Compressor - Media Compression and Conversion
Re: How can i add the Apple ProRes Codec(encoder) in my project? - 12 years ago
Duplicate of this thread: Please don't cross-post in future.by Jon Chappell - Compressor - Media Compression and Conversion
Re: 4:3 anamorphic PAL 720x540 to SD-DV Conversion - 12 years ago
Have you tried selecting the Geometry tab in Compressor, going to the "Output Image Inset (Padding)" section and setting Padding to "Preserve source aspect ratio"?by Jon Chappell - Compressor - Media Compression and Conversion
Re: WARNING - Just did Prokit update. - 12 years ago
Some people have managed to get it working by copying the old ProKit.framework from another computer or restoring it from a Time Machine backup.by Jon Chappell - Café LA
Re: About ProRes Encoder,Need Help! - 12 years ago
To compress a movie using the ProRes codec, you can use , specifying the new codec information in the attributes dictionary. There is a lot of documentation on this. But your user will need to have Final Cut Studio installed. There is no legal way to do this without FCS unless you approach Apple about licensing the ProRes encoder. P.S. Please don't cross-post.by Jon Chappell - Café LA
Re: interlacing issue - 12 years ago
It's happened to me more times than I can count, although I can't recall whether or not it occurred with embedded Motion projects.by Jon Chappell - Motion
Re: FCP in Applications folder at 136gb - 12 years ago
If you forget to backup your preferences, a better solution might be locking them. Locking preferences prevents modification, which in turn prevents them from getting corrupted. Instead of having to remember to back them up, simply unlock them on the rare occasions you change them and then lock them again.by Jon Chappell - Café LA
Re: FCP in Applications folder at 136gb - 12 years ago
I wonder if it's something to do with file permissions. Perhaps it defaults to the application bundle if it doesn't have write permissions for the scratch folder.by Jon Chappell - Café LA
Re: FCP in Applications folder at 136gb - 12 years ago
It's best not to leave them in there. Either move them elsewhere and reconnect or delete them and re-render.by Jon Chappell - Café LA
Re: no color? - 12 years ago
For some reason you can't send to Color by right-clicking. You have to go to File > Send To > Color.by Jon Chappell - Color
Re: interlacing issue - 12 years ago
Final Cut Pro sometimes incorrectly detects the field dominance of a clip and erroneously places a Shift Fields filter onto it. Make sure FCP is not adding a Shift Fields filter to your Motion project.by Jon Chappell - Motion
Re: woes with 10.6.4..... - 12 years ago
I'm not sure if it's wise to install new ProKit updates for old versions of Final Cut Pro. Might cause more issues than it solves.by Jon Chappell - Café LA
Re: woes with 10.6.4..... - 12 years ago
The new Mac Pros boot into 64-bit mode by default. If you boot into 32-bit mode by holding down the 3 and 2 keys together while booting, does Final Cut Pro work properly?by Jon Chappell - Café LA
Re: i have studio 3 but i still have QT 10 - 12 years ago
There is a very important reason why there are two QuickTime Players. QuickTime X introduced hardware acceleration for certain formats, but you can only take advantage of this if you open the movie for playback only. So in order to get hardware acceleration, you have to sacrifice the ability to edit the movie. So QuickTime X is for playback, QuickTime 7 is for editing. P.S. There is already aby Jon Chappell - Café LA
Re: i have studio 3 but i still have QT 10 - 12 years ago
You can't not install the QuickTime Pro license. I know my reply above implied this was possible, but that's only because I ignored what the OP had said as I thought they had made a mistake and probably meant to say "QuickTime Player 7". Apologies for the confusion. But it makes absolutely no difference to the operation of Final Cut Pro as the recording and exporting functions are prby Jon Chappell - Café LA
Re: i have studio 3 but i still have QT 10 - 12 years ago
I think there's some confusion here. "QuickTime Pro" refers to the Pro version of QuickTime Player. It has no effect on Final Cut Pro or any app that uses QuickTime. There is no "Pro" version of QuickTime Player X, only QuickTime Player 7. So if you want to take advantage of the pro features within QuickTime Player 7 (again, this is only applies to the player) then you needby Jon Chappell - Café LA
