evdh

Q: FCPX --> ProRessHQ --> Compressor 4 --> Blu-ray .264 of 1.69GB

Hi,

When I export a 2 hour and 16min movie from FCPX to Compressor 4 and convert it to a Blu-ray .264 file I'll end up with a file of 1.69GB. This is not normal. I used the default settings to create a Blu-ray file.

When I export a 2 hour and 16min movie from FCPX to Compressor 4 and convert it to a ProRess HQ file I'll end up with a file of 191GB. This is normal.

But when I convert this ProRess HQ file to a Blu-ray file .264 I'll end up again with a file of 1.69GB. This is not normal.

What am I doing wrong?

Is the movie to long for a Blu-ray and is Compressor confused because it's more than 2 hours?

When I convert the same ProRess HQ file to m2v (dvd) I'll end up with a file of 3,79GB. Tat's ok. No problem with that one.

 

For the Blu-ray file .264 I use the default setting from Compressor 4.

 

Thanks for helping me out...

Posted on Jul 17, 2014 1:12 PM

Close

Q: FCPX --> ProRessHQ --> Compressor 4 --> Blu-ray .264 of 1.69GB

  • All replies
  • Helpful answers

  • by Russ H,

    Russ H Russ H Jul 17, 2014 2:59 PM in response to evdh
    Level 7 (21,840 points)
    Quicktime
    Jul 17, 2014 2:59 PM in response to evdh

    evdh wrote:

     

     

    Is the movie to long for a Blu-ray and is Compressor confused because it's more than 2 hours?

    If you do the math, you'll find that you need to reduce the bit rate to about 26 Mbps. I'm assuming you're having Compressor create the disk. If you want additional material on the disk, you'll have to lower it further and use either Toast or Adobe Encore to author it.

     

    Russ

  • by evdh,

    evdh evdh Jul 17, 2014 9:48 PM in response to Russ H
    Level 1 (15 points)
    Jul 17, 2014 9:48 PM in response to Russ H

    Thanks for the tip. I'll try it...

    But it was in Auto mode and the file size indicate it was going to generate a file of 22GB. But I get a file of 1.69GB.

  • by Russ H,

    Russ H Russ H Jul 18, 2014 5:33 AM in response to evdh
    Level 7 (21,840 points)
    Quicktime
    Jul 18, 2014 5:33 AM in response to evdh

    Try it with a bit rate of 25.

     

    It sounds like the application tried to compensate for the length and the adjustment went awry. Unfortunately, I can't test that kind of project to see what happens at those lengths – at the moment anyway.

     

    Russ

  • by evdh,

    evdh evdh Jul 18, 2014 12:56 PM in response to evdh
    Level 1 (15 points)
    Jul 18, 2014 12:56 PM in response to evdh

    No good...

    I tried Average Bit Rate 15 and Max Bit Rate 20. File is 1,34GB.

    I tried Average Bit Rate 20 and Max Bit Rate 25. File is 1,69GB.

  • by Russ H,

    Russ H Russ H Jul 18, 2014 2:18 PM in response to evdh
    Level 7 (21,840 points)
    Quicktime
    Jul 18, 2014 2:18 PM in response to evdh

    Please post screenshots of the general pane and the video pane in the Inspector with the setting selected.

     

    Russ

  • by evdh,

    evdh evdh Jul 18, 2014 10:53 PM in response to Russ H
    Level 1 (15 points)
    Jul 18, 2014 10:53 PM in response to Russ H

    I'll post them later this evening.

    And thanks for helping me with this problem.

  • by evdh,

    evdh evdh Jul 20, 2014 3:03 AM in response to Russ H
    Level 1 (15 points)
    Jul 20, 2014 3:03 AM in response to Russ H

    This is the info about the inserted mov file.

    Screen Shot 2014-07-20 at 11.57.40.png

    This is the info screen when the file is inserted.

    Screen Shot 2014-07-20 at 11.53.56.png

    These are the default settings for creating the .264 file.

    Default the Average and Max are set to Auto (21,31 and 35)

    But like you wrote, set them to 25, did not solve the problem.

    I also tried 20-25 and 15-20.

    Screen Shot 2014-07-20 at 11.54.28.png

    These are the files that are generated.

    Screen Shot 2014-07-20 at 12.01.35.png

    Estimated size is 21GB, not 1,6GB.

    Thanks for your time...

  • by Russ H,

    Russ H Russ H Jul 20, 2014 7:00 AM in response to evdh
    Level 7 (21,840 points)
    Quicktime
    Jul 20, 2014 7:00 AM in response to evdh

    So what's on these small files in the way of content? What part of the video gets encoded?

     

    Have you tried a job action – forcing the layers to single layer?

     

    There are quite a number of posts on the FCP X forum from people having trouble with long length (> 1 hour) Blu Ray recordings. Unfortunately, no one has pin pointed a cause or a cure. Possibly your issue is related to theirs.

     

    Russ

  • by evdh,

    evdh evdh Jul 20, 2014 10:12 AM in response to Russ H
    Level 1 (15 points)
    Jul 20, 2014 10:12 AM in response to Russ H

    Everything is encoded.

    this is a screenshot...it should be FullHD 1080p. It's not even SD quality.

    Screen Shot 2014-07-20 at 19.09.05.png

  • by evdh,

    evdh evdh Jul 20, 2014 10:14 AM in response to Russ H
    Level 1 (15 points)
    Jul 20, 2014 10:14 AM in response to Russ H

    I just tried the same thing with Compressor 3.5.3 and the result was beter. A file of 3.6GB.

    I redo the same file but with Average/Max of 20/25.

    And I also have a look at the FCPX forum.

  • by evdh,

    evdh evdh Jul 21, 2014 7:29 AM in response to evdh
    Level 1 (15 points)
    Jul 21, 2014 7:29 AM in response to evdh

    My solution for the moment...

    For the moment I export from FCXP 10.1.2 via Compressor 4 to ProResHQ (the full length 02:10:00) and bring it in Adobe Encore. That still works.

  • by evdh,Solvedanswer

    evdh evdh Aug 7, 2014 3:28 AM in response to evdh
    Level 1 (15 points)
    Aug 7, 2014 3:28 AM in response to evdh

    SOLVED

     

    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 -oOutPutFile.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 -oOutPutFile.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...