Encore always transcodes my x264 compressed files

[Eric_Daoust]

Hi everyone. I'm about to go crazy working on my first Blu-Ray disc! I work on a Mac Pro using Encore CS6 on Mac OS X 10.6.8. I am looking to use an AVC/H.264 encoded file by the x264 compression engine, which is supposed to be the best out there. For this, I have tried using FFmpegX and Handbrake with regular settings (1920x1080p, 23,976fps, 16:9, constant quality) starting from an Uncompressed 10-bit output from my Premiere timeline.

I am very satisfied by the compressed H264 outpout file, but no matter which application I use and the different configurations (tried different profiles inside Handbrake), everytime I import the  file, Encore sees it as a file that has to be Transcoded again. And of course you can imagine how the result looks like when an h264 file is encoded twice...

I have tried reading every possible forum on the subject of H264 Blu-Ray compatible files... without any success. I desperately need your help!

I have even tried pointing to the "encoded" file on my hard drive by telling Encore it has been encoded already, but the compilation of my Blu-Ray fails everytime when I does this.

I have succeeded once to create a file with Handbrake that is "sometimes" accepted in Encore (happened twice, I think), but it's bitrate was too risky to my taste for compatibility (38mbps) and therefore was only a test. I have no idea why this one worked...

[carlos_oboe]

Yes i know that you are using only x264 without gui.  Please post your final settings to get a good video in Encore. I know that i can't do 25p but if give me a valid frame rate to get PAL BluRAY with 25p or 50i with 25p sequence. I don't want to transcode to 24p because in Spain is 25p.

I want to transcode Avid DNxHD to x264 and bring back to Encore

ThankYou

[Jeff Bellune]

I'm not using MeGui, so I don't know if you can encode a Blu-Ray compliant file when using MeGui.

You can encode a BD-compliant file that Encore will respect *if* you output from MeGUI as .264 and not .m4v.

Jeff

[carlos_oboe]

Yes i've tried, But i think is more flexible with X264 only. If someone is making BluRay with sequences in 25p for PAL Land please post settings here or send me an email.

[email address deleted for privacy protection]

[Jeff Bellune]

Hi Carlos,

I deleted your email address from the previous post.  I did it to prevent spambots from picking it up.  If you'd like to make it available to the forum, please disguise it.  For example: myemailaddress -at- m y d o m a i n /dot/ c o m

Thanks,

Jeff

[Eric_Daoust]

PMK3 wrote:

What  codec's did you use when you tried the AVI format. AVI isn't the best format to use on a MAC, but uncompressed AVI doesn't use any codec's. If you are also getting the same "buggy output" with uncompressed AVI , then perhap's the easiest solution is to use a PC.

x264 on a PC doesn't need to be installed, just download the x264.exe file and run it in a DOS-promt. Codec problem's are also easy to fix in Windows, just download and install the codec that you need.

I've tried using x264.exe on my girlfriend's old PC (Windows XP SP3 32bit) with my original MOV output and the program crashed everytime just after indexing the input file (when the encoding starts). I got the 8-bit depth 32bit version. PMK3... When you successfully encoded my file with x264.exe, which file were you using? Did you use any conversion beforehand or just used the 422 8-bit MOV input AS-IS? Because it doesn't seem to work for me. I even tried the same file in MeGUI and it made x264 crash exactly the same way.

[Eric_Daoust]

Here is my PC version info:

Microsoft Windows XP [Version 5.1.2600]

(C) Copyright 1985-2001 Microsoft Corp.

C:\>x264 --version

x264 0.125.2208 d9d2288

(libswscale 2.1.0)

(libavformat 54.9.0)

(ffmpegsource 2.17.2.1)

built on Jul 18 2012, gcc: 4.7.1

configuration: --bit-depth=8 --chroma-format=all

x264 license: GPL version 2 or later

libswscale/libavformat/ffmpegsource license: LGPL version 2.1 or later

[Eric_Daoust]

@PMK3:

An export test from my Mac with the Animation codec and then encoded on the PC with x264.exe did not crash and gave me a normal-length .264 video, but with lots of noise over it (see below). So the crashing problem seems to be codec-related (the first problematic file was the usual MOV Uncompressed YUV 4:2:2 8-bit). I am trying at the moment with a Prores file...

In the meantime, when you have a minute, please indicate which of my files you have used to compress sucessfully with x264 on the PC and with what options? At the moment, I'm using these configurations, but should I remove, for example, muxer raw?

x264.exe --bitrate 25000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 30000 --vbv-bufsize 30000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES422HQ.264 --input-res 1920x1080 input_PRORES422HQ.mov

[PMK3]

Eric_Daoust wrote:

When you successfully encoded my file with x264.exe, which file were you using? Did you use any conversion beforehand or just used the 422 8-bit MOV input AS IS?

I have downloaded the following sample's from you:

EricDaoust_UN_23976fps_1920x1080.mov

EricDaoust_x264_23976fps_1920x1080p.mp4

EricDaoust_x264_CONSTANT_23976fps_1920x1080p.mp4

input_mpeg2_100b.mov

input_mpeg2_100b.mpg

And the only sample that didn't work with x264 was EricDaoust_UN_23976fps_1920x1080.mov.

All other samples worked with x264 AS-IS.

Eric_Daoust wrote:

C:\>x264 --version

x264 0.125.2208 d9d2288

(libswscale 2.1.0)

(libavformat 54.9.0)

(ffmpegsource 2.17.2.1)

built on Jul 18 2012, gcc: 4.7.1

configuration: --bit-depth=8 --chroma-format=all

x264 license: GPL version 2 or later

libswscale/libavformat/ffmpegsource license: LGPL version 2.1 or later

This is also the version I'm using.

Eric_Daoust wrote:

In the meantime, when you have a minute, please indicate which of my files you have used to compress sucessfully with x264 on the PC and with what options? At the moment, I'm using these configurations, but should I remove, for example, muxer raw?

x264.exe --bitrate 25000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 30000 --vbv-bufsize 30000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES422HQ.264 --input-res 1920x1080 input_PRORES422HQ.mov

The only option's i didn't use when I encoded my H.264 sample was --muxer raw and --input-res.

--muxer raw forces x264 to encode a raw H.264 video stream and --input-res is only needed when x264 can't detect the proper resolution of the source file.

[Eric_Daoust]

My friend I believe we are close to a solution! Apple Prores HQ 4:2:2 worked when encoded on PC! What codec do you think would be preferable to get the highest quality output while being compatible with x264 on Windows? Should I try the Avid codecs instead of Prores from Apple?

[PMK3]

Eric_Daoust wrote:

What codec do you think would be preferable to get the highest quality output while being compatible with x264 on Windows? Should I try the Avid codecs instead of Prores from Apple?

There are only 3 codec's that I'm using when working with video, And these codec's are: Mjpeg, CanopusHQ and Cineform Neoscene. Mjpeg is used for Proxy Editing (aka Offline Editing), CanopusHQ is used with Vegas Pro and Cineform Neoscene is used with Premiere Pro.

None of these codec's are freeware, so I would prefer Avid DNxHD over Prores because DNxHD is freware and is also avaible on both MAc and PC. Prores can also only be decoded on window's, you can't encode to Prores in Window's (I haven't yet managed to export a Quicktime with Prores on window's).

[Eric_Daoust]

Avid DNxHD and Apple PRORES 4:4:4:4 seems to both be high-quality codecs. While making my tests, I've had great success with very high quality Apple PRORES 4:4:4:4. Although my source is only 4:2:0, the result is better in noisy areas than with ProresHQ 4:2:2 for example.

Then, the encoding with x264 is just something else. I almost can't even tell its h264 encoded. I can't wait to try the whole project which should take about a whole day to render on this old PC computer at "-- very slow".

I'll report back if everything goes as planned. I'm using a hard drive with partition exFAT which allows to go from a mac to pc with ease with files higher than 4gb (which was the limitation of MS-DOS).

Again thank you for your help PMK3!

[Eric_Daoust]

The encoding seems to work really well, finally!

I had one last question concerning the bitrate. If my project is to end up on a BD-R (25GB) disc, what would be my max allowed bitrate? I have made a compression with the bitrate setting at 32500. My 5.1 soundtrack is compressed in Dolby at about 450 kb/s and since the whole content is only 15 minutes, I have plenty of room on the 25GB disc.

I have read many versions of the Blu-Ray disc specs including max birate at 25000 and 40000... Not sure what to think. But I'm guessing that the BD-R's birates are a bit lower than a true BD disc...

What do you guys think?

Also, considering the program's length, wouldn't I be better using constant bitrate? Or two pass encoding? Anyone?

[Eric_Daoust]

I've read on this forum (http://forums.adobe.com/thread/722465) and in a Samsung Blu-Ray player manual that any BD-R exceeding 25mbps bitrate could not be read by most set top players. PMK3, in your opinion, would this be safer then?

x264.exe --bitrate 22000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 25000 --vbv-bufsize 25000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES4444.264 --input-res 1920x1080 input_PRORES4444.mov

Also, should I use constant framerate since my material is only 15 minutes long? Or maybe two-pass encoding? Could anyone please guide me with the command line? Thanks.

[Eric_Daoust]

« PMK3, why have you forsaken me? » 

[PMK3]

Eric_Daoust wrote:

I've read on this forum (http://forums.adobe.com/thread/722465) and in a Samsung Blu-Ray player manual that any BD-R exceeding 25mbps bitrate could not be read by most set top players. PMK3, in your opinion, would this be safer then?

x264.exe --bitrate 22000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 25000 --vbv-bufsize 25000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES4444.264 --input-res 1920x1080 input_PRORES4444.mov

Yes, these setting's should be safe to use if set top player's has problem's playing anything higher than 25 Mbit.

Eric_Daoust wrote:

Also, should I use constant framerate since my material is only 15 minutes long? Or maybe two-pass encoding? Could anyone please guide me with the command line? Thanks.

If you are only going to put 15 minutes of material on a BD-R then use constant bitrate. x264 will use constant bitrate if you remove the option --vbv-maxrate 25000.

x264.exe --bitrate 22000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-bufsize 25000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES4444.264 --input-res 1920x1080 input_PRORES4444.mov

And this is for a 2-pass encoding

.

x264.exe --bitrate 22000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 25000 --vbv-bufsize 25000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 1 -o out_PRORES4444.264 --input-res 1920x1080 input_PRORES4444.mov

x264.exe --bitrate 22000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 25000 --vbv-bufsize 25000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 --pass 2 -o out_PRORES4444.264 --input-res 1920x1080 input_PRORES4444.mov

[Eric_Daoust]

Amazing. I can't thank you enough! I'm happy we could figure out a way to solve this issue and I really appreciate your help.

[carlos_oboe]

Hello, again.

I have another problem with a 23,976 sequence. I have 1920x816 sequence in premiere. 2:35 ratio. Is there any form to get transcoded file in premiere. I have used the settings that i've written below. Please is there any form to do in x264, or i have to export with black bars in premiere. With this settings i get the black bars but i get untrascoded in Encore.

x264.exe --bitrate 25000 --preset veryslow --tune film --bluray-compat --fps 24000/1001 --force-cfr --bframes 3 --ref 4 --muxer raw --no-weightb --weightp 0 --b-pyramid none --vbv-maxrate 30000 --vbv-bufsize 30000 --level 4.1 --profile high --keyint 24 --min-keyint 1 --open-gop --slices 4 --colorprim "bt709" --transfer "bt709" --colormatrix "bt709" --sar 1:1 -o out_PRORES422HQ.264 --input-res 1920x1080 input_PRORES422HQ.mov

Thank you

[Eric_Daoust]

@tjh65: I understand, but I did not find a way to convert to 4:2:0 on the mac, neither am I qualified enough to compile swscale into x264. I'm at the point where I maybe should wait for my girlfriend's new PC to come in and write back in a few weeks

But I know I have installed and compiled ffmpeg. Any idea what kind of command would allow me to convert to 4:2:0 with this program?

Thanks again for your support.

[excited_Genie16B8]

Anybody had ANY success using an x264 encoded file with Encore?

I finally got mine to work.  I use the XviD4PSP front end, adjust my settings as I want them, encode...and it works fine in Encore CS6.  No transcoding.

[carlos_oboe]

Has anyone solved how to compile -swscale in OSX? I have compiled today x264 for OSX in Mountain Lion and i have the same problem as Eric Doust. Strange green bars, in windows doesn't occurs. I think it's the change between 422 to 420 but i need to compile with this.

[Guest]

What settings did you use?

EDIT: Ok, i've just discovered something interesting. None of the videos i had encoded using Megui and x264 would be accepted into Encore without it displaying that they were untranscoded. So i decided to try out the trial of x264Pro tried encoding a couple fo short videos to see if they woudl be accepted, which they were.  Now, all of a sudden, all of my previous files are now being eccepted into Encore and displaying "Don't Transcode". Why would that be? Nothing has changed apart from installing X264Pro

[excited_Genie16B8]

Eric_Daoust wrote:

Here is the file.

Well, one thing I notice right away is that it's an MP4 file.  Encore will be expecting an .m4v file.

[PMK3]

Eric_Daoust wrote:

I have tried reading every possible forum on the subject of H264 Blu-Ray compatible files... without any success. I desperately need your help!

Hi Eric,

Can you download and try the sample pmk3.264 in encore. The sample can be downloaded from here: http://hem.bredband.net/b131706/

This sample is blu-ray compliant and works perfectly with Sony DVD Architect Pro 5. but I need to know if it also work with encore.

[Eric_Daoust]

Hi PMK3! Your file works perfectly fine. When imported, it says "Do not transcode" in Encore. Now please allow me to ask a way to encode a file like this with x264 on mac?

I've also tried compiling x264 yesterday on my mac, but I'm such a newbie I couldn't add mp4 support to it. I've installed Xcode, then Mac Ports, then the basic tools. But I would probably require more guidance on install it properly.