Q: Blu-Ray burning error after Final Cut Pro 10.1.2 update.

Ok, this is my workflow. I hope it works also for you...
PS : It also solve my other problem : FCPX --> ProRessHQ --> Compressor 4 --> Blu-ray .264 of 1.69GB

Step 1 : Export to ProRes422HQ
Export your project to a ProRes422HQ .mov file. You can do this also via Compressor. This still works.

Step 2 : Download x264

Download the x264 program via this link : http://download.videolan.org/pub/videolan/x264/binaries/macosx-x86-64/

This program is free but not that easy to use. Took me some time to find (via 'The Internet') the correct syntax so that Adobe Encore CS5.5 and Toast 11 accepted the file without transcoding or re-encoding the generated .264 file.

Step 3 : Encoding the .mov file to a.264 file using x264

Use these commands to generate the .264 file. This is for a 25p file. But you can also use x264 for 24p/30p/... movies. You only have to change the --fps and --keyint options. You can also play with the bitrates.

Pass 1 :

x264-r2453-ea0ca51 --bitrate 22000 --fake-interlaced --tune film --bluray-compat --fps 25 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 22000 --vbv-bufsize 22000 --level 4.1 --profile high --keyint 25 --min-keyint 1 --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o OutPutFile.264 --input-res 1920x1080 InputFile_ProRes422HQ.mov

Pass 2 :

x264-r2453-ea0ca51 --bitrate 22000 --fake-interlaced --tune film --bluray-compat --fps 25 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 22000 --vbv-bufsize 22000 --level 4.1 --profile high --keyint 25 --min-keyint 1 --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o OutPutFile.264 --input-res 1920x1080 InputFile_ProRes422HQ.mov

PS: There is also another option, for beter results, I'm testing for the moment and that is this one : --preset very slow.

Step 4 : Create the .ac3 audio file via Compressor

Import the ProRes422HQ file into Compressor and create only the ac3 audio file.

Step 5 : Import the .264 and .ac3 file into Toast or Adobe Encore.

If al goes well, Adobe Encore doesn't need to transcode the .264 file.

And in Toast you set via the custom option that no re-encoding is needed.

Step 6 : Burn and enjoy...

I hope this workflow works for all of you...

If not, we need to find out what's wrong...

A simple way if you have Time Machine:

Delete FCPX 10.1.1 und Compressor 4.1.2

only restore 10.1.1 an 4.1.1 and everything works fine

but you will not be able to open .fcpbundle you have saved with 10.1.2

How to work with 10.1.2 - .fcpbundles in 10.1.1?

Before you restore 10.1.1 and 4.1.1 you have to make a final prores422.

Then restore to 10.1.1 and 4.1.1 and import this prosres in a new (10.1.1-) project.

Quote:

    A simple way if you have Time Machine:

    Delete FCPX 10.1.1 und Compressor 4.1.2

    only restore 10.1.1 an 4.1.1 and everything works fine

    but you will not be able to open .fcpbundle you have saved with 10.1.2

Yes I know that's also a solution, but not for me.

My project was created and saved with 10.1.2. I also had some Motion project include in the FCPX project. And Motion was also updated. So restoring Motion was also not an option.

So I had to find another solution.

But thanks for sharing your solution. Perhaps other people can benefit from that one.

That's also a way of working but that easy if you need to change some things.
The project is a dance show (more than 2 hours) and things need to be changed up until the end.

Update to this post...

Step 1 : Export to ProRes422HQ

Step 2 : Download x264

Step 3 : Encoding the .mov file to a.264 file using x264

The --preset veryslow option works also. So this gives you beter results.

Pass 1 :

x264-r2453-ea0ca51 --bitrate 22000 --fake-interlaced --preset veryslow --tune film --bluray-compat --fps 25 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 22000 --vbv-bufsize 22000 --level 4.1 --profile high --keyint 25 --min-keyint 1 --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o OutPutFile.264 --input-res 1920x1080 InputFile_ProRes422HQ.mov

Pass 2 :

x264-r2453-ea0ca51 --bitrate 22000 --fake-interlaced --preset veryslow --tune film --bluray-compat --fps 25 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 22000 --vbv-bufsize 22000 --level 4.1 --profile high --keyint 25 --min-keyint 1 --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o OutPutFile.264 --input-res 1920x1080 InputFile_ProRes422HQ.mov

Step 4 : Create the .ac3 audio file via Compressor

Step 5 : Import the .264 and .ac3 file into Toast or Adobe Encore.

Step 6 : Burn and enjoy...

I tried this also but it didn't work for me.

I still get a very small .264 file. (A two hours project will result in a 20GB file, not a 1.69GB file)

See my other discussion : FCPX --> ProRessHQ --> Compressor 4 --> Blu-ray .264 of 1.69GB
I even tried Compressor 3.5.3 but still the same small file : FCPX --> ProRessHQ --> Compressor 4 --> Blu-ray .264 of 1.69GB
So the only solution that works for me is using x264 as described in this post.

Hi, this post won't be of help to anybody but I'm just curious as a fan of Apple and Final cut pro.  By looking at the views of this thread (nearly 10,000 so far) it must be painfully obvious that there is a blu ray burning issue with 10.1.2.  (as I have the same problem)  Since this is a pretty important function for many users, especially those in business, is there some thought as to why the patch or version 10.1.3 is taking so long?  Seems like the only ones addressing this are the people in this discussion that have taken huge amounts of their time to figure out these extravagant  work arounds. 

It's pretty clear from the thread that the FCP team is aware of the problem and have reproduced it. When you have to rewrite code for an application that is more than a million lines it takes a bit of time, especially when rewriting it will probably effect multiple components of two applications, both of which access OS core components. It's a shitload of work and throwing more people at it usually does not make the problem any better, usually makes it worse.

A very logical answer!  It's true, walk a mile in somebody elses shoes.  (or in this case, the person doing the rewriting)  Thanks!

@Tom

You are right! But what if i will say to my customers:

"Problem? There is no problem, but i will help you. Only pay 99 € and you may have a solution

from me - no: we will search for a solution"

This was the answer from the apple support guy 5 weeks ago. Nothing happened until now.

The new answer of this guy - 3  days ago - was, that he is now not in this support-team, did not

know anything about a problem and i have to open a new support case with a new team member - and of course

this will cost 99 €!!!

Thank you apple!

AppleCare pro video, audio, and XSAN have closed.

But wait…

For $6,000, the support remains available.

Russ

That's unlimited support. That's been there separate from pro apps support.

Yup,

But the options narrow.

Russ