Hi Craig
Thanks for the reply, I haven’t tweaked anything. Simply exported as quicktime file self contained from FCP time line. Once completed I dragged the 8gb .mov file into compressor, dragged the h.264 codec in and let rip. I wanted its best preset setting so left it at its default and as mentioned it became 11GB. It should in my experience come right down through compression for it to be suitable for uploading.
This is the first time I’ve worked this way. I would normally complete my edit and then send to compressor and from there drag my codec in. Usually no problem except the wait!
The reason I changed was that sending to compressor and adding in this case the h.264 codec was taking up to 13++ hours and kept failing before finishing. For a project of this length and not being as heavy as past projects I looked at trying to utilise all my cores and understand the problem with this scenario.
I haven’t utilised qmaster and all my cores to date as in the past it would just fail by sending to compressor directy from FCP. I only recently learned of the problem qmaster has with projects being sent directly from FCP and that you are best exporting as quicktime file self contained, switching on qmaster and then dragging your file in to compressor rather than sending.
Apologies for the long post I just want to give you as much info as I have experienced to date. I have a sneaky feeling that the .motn files that are brought to FCP are causing the hassle… I would have always created my project in motion then exported uncompressed and then imported it back into FCP.
Thanks again
Dave
Dave Davin
Creative Director
RAIC Productions
http://www.raicproductions.com