[Eric St-martin]

Agreed!

FCP is so full of these discrepancies it’s a total embarrassment for Apple.

That’s not to talk about the outrageous multiple crashes per day this application is doing that people are so prone to justify on forums.. you shouldn’t use xdcam or HDV codec to edit, you should not display the thumbnails it’s sucking-up to much resources, you installed from scratch or upgraded type of silly answers. Come on! We spent many thousand dollars on acquiring these systems which were supposed to be professional, we’re having gigs of ram installed, dual multiple core processor, huge raids and yet, they are playing the system resource depravation song! Might be true that lessening the stress on the application will prevent problems but I only have one answer to that : Lame application programming, testing and fixing. Take the Mac Ad with the accountant… replace the bean counter script with saying : new FCS upgrade, fix the current one and you’ve got yourself how I feel about Apple…. why not trying it with the latest.. it’s not going to have any of the problem my previous system had!

If only apple was as serious with it’s pro applications as much as we are in the way we use’m! I think they are too busy acquiring new market share with tablets, phones and other trendy stuff.

Cheers,
Eric

[Eric St-martin]

The reason for that is the finder is sorting numericaly and FCP’s browser sorts alphabethicaly.   

In order to get it to behave the way you want it to, you need to use leading zeros in your item names. For instance, clip names should be 001,002,003 and so on.
Then, clip 02 will alphabethicaly preceed clip 10.

Regards,
Eric 
 

[Eric St-martin]

Your best choice would be either a Mackie or Euphonix.

I’d rahter go with Euphonix since they are modular, using Ethernet and are made for FCS. They seem to have a smaller footprint as well.

Regards,
Eric

[Eric St-martin]

This is what I’m referring to https://discussions.apple.com/thread.jspa?threadID=2109359&tstart=0

The problem occurs when ever frame resizing is in play with compressor 3.5.

[Eric St-martin]

Courtney, you are right.  Allthough not that many people seems to complain about it yet, there is a bug in compressor 3.5 which completely screws-up it’s ability to output video with size transformation. This problem occurs regardless of the type of the source file (codec, interlace or pogressive, intraframe only or GOP).

It looks like the frame control setting is ignored which disturbs the result even for convertions from 1080p to 720p but the problem becomes even more obvious (and then I mean event for my dead grand mothers eye) when producing SD DVD. The result is basicaly single field output that is line doubled in a progressive mpeg2  which leaves us with a fantastic resolution of 720×240.  Btw any output codec will display the problem. Even h.264 mov. 

On compressor forums, people are starting to complain about the problem and reinstall from scratch (even Osx) didn’t solve the problem. 

The only solution I found which would have offered a temporary workflow while we are waiting for the fix from apple didn’t work completelly, is much longer and anihilate any chance of automation but I will still share it with you:

1- export from fcp with “export using QuickTime conversion”. Make sure you resize the video to 720×480 right then using the anamorphic pixel setting for 16:9 content. Use the same codec as your origin or a flavor of apple prores of your choice. 
2 – use compressor to produce the DVD files. Compressor still does a great job when it doesn’t resize. 

Now the main drawback is the following:  with QuickTime conversion, the edit markers and compression markers are lost. So when compressor takes the file, it doesn’t have hints as to where to put the key frames. So some transitions and pans look bad. 

But voilà. Hope it helps. 

Eric