MeGUI: bug reports and feature requests

[hello_hello]

I did not say that MeGUI should not mux...

I just said that MeGUI should not use x264 for muxing.

MeGUI comes with GPAC (MP4) and with mkvmerge (MKV), so it can use those for muxing, instead of x264.

I didn't say it shouldn't mux either, just that I've not come across a valid argument for it not outputting directly to MKV.
No matter what the output, 99.99% of the time the encoded video will need to be remuxed anyway to add the audio etc, and that doesn't change if the output is .264 or .mkv. You're saying the second method shouldn't be used despite the fact it allows you to open/preview the encoded video before it's remuxed, but you haven't explained why. For example:

x264 is an encoder first and foremost, and not a muxer, so x264 should only be used for encoding IMHO (i.e. using --output "output.264" "input" only).

Can you point me to where that rule is written? Or at least provide a justification for it?

[sneaker_ger]

hello_hello does understand very well. He prefers x264's mkv output so he can preview the intermediate files in his player. If his player does not allow H.264 ES playback he will not "still be able to do what you can do now".

I think he posed a very valid question: what downsides does direct mkv output have that justify a switch to ES output?

[hello_hello]

jq963152,
I fully understand. Maybe it's your own lack of understanding which is the reason for you ignoring the questions I've asked.

There's a huge difference between outputting directly to MKV and outputting .264 and then remuxing it as MKV. When you output directly to MKV there's no intermediate .264 file. The MKV file is created as the video is encoded. There's no re-muxing as such. As soon as the encoding has finished the MKV can be opened by a media player. In fact you can open the MKV while the video is still being encoded. No remuxing required. You probably can't do any of that when the output is .264.

So no, when the output is .264, I can't do what I can when the output is MKV.

Maybe you could try answering my question. Where is it written the x264 encoder shouldn't output directly to MKV and what are your justifications for saying it shouldn't be used that way? By all means output to a .264 file yourself, but I don't understand why you keep claiming the x264 encoder shouldn't be used to output directly to MKV without offering a single reason why.

[sneaker_ger]

Here are two:

The first problem is only relevant for Blu-Ray - it does not matter when I final format (after adding audio/subtitles) is mkv anyways.

H.264 ES does also not have an index, so that's no plus of ES output.

[hello_hello]

Here are two:

some SEI messages and/or header are lost

You left off the rest of that quote:
"and muxing software refuses to mux h.264 stream"

Doesn't that relate specifically to encoding for Bluray (http://forum.doom9.org/showthread.php?p=1399419#post1399419) anyway? I don't understand exactly what it means myself, but I'd wager neither do you, which kind of negates you offering it as a reason.

Edit: Well it seems sneaker_ger confirmed above that it's only relevant for Bluray encoding, so when encoding for Bluray you'd probably not choose MKV as the output, but otherwise, I'm still not seeing a good reason for removing MKV output as an option.

x264's direct mkv output does indeed not create an index for seeking

There's no index for seeking when the output is RAWAVC either!!!
Which part of the process am I not explaining well??
It doesn't matter if the output is RAWAVC or MKV, either way in order to add the audio it needs to be muxed along with the video into a new MKV. Therefore whether the video output is RAWAVC or MKV, the final output file will have an index created for seeking. So what difference does it make??

[detmek]

Some of recent changes in MeGUI are more.... philosophicaly inspired or just cosmetical. Those do not have any practical value. Reason is probably: "I think it is the right way to do that so, lets do it that way. Is it pracitcal and usefull? Who cares.".
I mean, removing MP4 support so we could use official build (though we have funcional Komisar's build with MP4 support). Or "2373 [MP4 Muxer] default GPAC string will be erased".
I was hoping for 10-bit support, not this.
Anyway, for me it is an easy decision: I reverted back to 2356 and replaced official x264 with Komisar's.
As I already explained (in this thread or some other), MP4 support is handy for more MediaInfo information and I use it for small test clips. Direct MKV suppot is good as we can preview large files during encoding process.
On the other hand, direct .h264 output prevents preview, doubles the space requirement (intermediate file + muxed file) and takes more time. Really usefull.
I would like to continue to use MeGUI, but...

Oh, yes. About missing SEI messages. It is only related to streams meant to be used for authoring Blu-Ray disks. Those streams muxed in MKV or MP4 container can be prefectlly played on Blu-Ray players if those players support MP4 or MKV format. And, MeGUI already offers direct .h264 output. So, that is not reason to remove direct MP4 or MKV output.

[hello_hello]

Oh, yes. About missing SEI messages. It is only related to streams meant to be used for authoring Blu-Ray disks. Those streams muxed in MKV or MP4 container can be prefectlly played on Blu-Ray players if those players support MP4 or MKV format. And, MeGUI already offers direct .h264 output. So, that is not reason to remove direct MP4 or MKV output.

Out of curiosity, do you know specifically which SEI messages are "lost"? Or for that matter, if it's still true? The thread which was originally referenced is the one on Bluray encoding (http://forum.doom9.org/showthread.php?p=1399419#post1399419) but it's over three years old now and things change.
I'm having trouble finding any definitive info as to which SEI messages are effected. Are they something other than the encoder settings etc which MediaInfo displays (they seem to be identical regardless of the original output format)?

[detmek]

Sorry, I don't. I just remember reading this when I followed news about x264 Blu-Ray compatibility. You should ask shon3i (http://forum.doom9.org/member.php?u=89473) for more information. He might know more. I usually don't encode for Blu-Ray.

[hello_hello]

RAWAVC output is necessary while megui developers not implement automuxing using mkvmerge, not with x264.

Other solution, could be remuxing mkv files generated with mkvmerge, again.

If I'm understanding you correctly, isn't that effectively how it works? At least when using AutoEncode or (probably) OneClick.

If you use AutoEncode to add an encoding job (no audio included) to the job queue and select MKV as the output, by default MeGUI adds two jobs, the first encodes to RAWAVC, while the second remuxes that as an MKV with mkvmerge.

MeGUI could probably output directly to MKV when using AutoEncode and still remux it, but either way, using AutoEncode gets MeGUI to do the "automuxing" you refer to.

If you add the same encoding job directly from the video encoding section while specifying MKV, you get the encoder outputting directly to MKV. There's no "automuxing" or "automatic remuxing" with mkvmerge, but if you want that, you'd use AutoEncode instead.

Are we on the same page there?

Edit: You can get AutoEncode to output directly to MKV (no intermediate .264 file) when MKV is the selected output container. The option is under Settings: "Always mux mkv encoding with mkvmerge". If you uncheck that option, AutoEncode doesn't output an intermediate .264 file.

From my quick testing:
With the option checked, AutoEncode always outputs an intermediate .264 file which it then muxes into an MKV with mkvmerge.
With the option unchecked (MKV as the output container) the encoder output is MKV, which is only remuxed with mkvmerge if additional streams (ie audio) are being added to the final output file.
It appears there's no way to get AutoEncode to output directly to MKV AND remux that with mkvmerge unless the job includes adding additional streams to the encoded video.

[detmek]

You realy shouldn't say anything about AutoEncode muxing option. Now they can change thet, too as "x264 should always output raw stream".:-(

[Overdrive80]

hello_hello does understand very well. He prefers x264's mkv output so he can preview the intermediate files in his player. If his player does not allow H.264 ES playback he will not "still be able to do what you can do now".

I think he posed a very valid question: what downsides does direct mkv output have that justify a switch to ES output?

I think that each of us have your prefered election, with respect to you needs... but for one user within high knowledge is best option is use .264 output and auto-muxing with mkvmerge. The goal of a program is normally oriented to users with a basic knowledge level ... if it were not so then have to remove the profiles codecs, etc...

The option of Kurtnoise, I think is most successful.

[hello_hello]

On the subject of AutoEncode and MKV output:

In my opinion, if "Always mux mkv encoding with mkvmerge" is checked in MeGUI's options, it'd be nice to also have an option to choose whether the encoder output is MKV or RAWAVC (assuming MKV as the chosen output container). Then, regardless of the type of encoder output, it'd always be remuxed with mkvmerge even if no additional streams are being added. And when "Always mux mkv encoding with mkvmerge" is checked, AutoEncode would always produce a final, seekable MKV, regardless of the intermediate file type.

With "Always mux mkv encoding with mkvmerge" unchecked, mkvmerge would only be used to mux rawavc as an MKV, or when AutoEncode is adding additional streams to the output file.

In fact the "Always mux mkv encoding with mkvmerge" option could then be relabelled as something like "AutoEncode always produces seekable MKVs" or something similar.

[mini-moose]

Edit: You can get AutoEncode to output directly to MKV (no intermediate .264 file) when MKV is the selected output container. The option is under Settings: "Always mux mkv encoding with mkvmerge". If you uncheck that option, AutoEncode doesn't output an intermediate .264 file.


Nice, thanks for pointing that out! It works for both auto and one-click.

[AMED]

Have you tried MKVCleaver (http://www.videohelp.com/tools/MKVcleaver)? Unlike extracting with MeGUI though, any audio delay which might be used in the original MKV won't be added to the name of the extracted file, so you'd need to check for any audio delay with MediaInfo manually.Since MKVCleaver uses mkvextract it also fails like MeGUI.

Or try this method (http://www.avsforum.com/t/1407589/makemkv-and-lpcm-audio) to see if MeGUI/MKVExtract will then extract it.According to the MakeMKV author, by doing this change to the mkv header you will lose all channel layout information.

Another option..... you can add video files (MKV, MP4, AVI etc) directly into MeGUI's audio section and convert the audio within. No need to extract it first. It works most of the time. I think for MKVs (if the usual methods for decoding the audio fail) MeGUI will index the MKV and open the audio with AVISynth and FFAudioSource().

Thats basically what i'm doing, but i'm using EAC3to to convert the Audio in to AC3.

I have no problems doing these steps but new users might be confused to why OCE errors when it tries to extract the audio. Maybe this is not a big issue since it hasn't really been reported in the MeGUI threads.

Would it be much effort to warn the user when using OCE how to deal with the audio format?

[tebasuna51]

...
According to the MakeMKV author, by doing this change to the mkv header you will lose all channel layout information.

Yes, with this method mkvextract make a wav file with a wrong simple header (fields BlockAlign and BitsPerSample are wrong) instead with the WAVE_FORMAT_EXTENSIBLE header stored in the mkv.
Also lose the field MaskChannel with the channel layout info.

Thats basically what i'm doing, but i'm using EAC3to to convert the Audio in to AC3.

Yes, MeGUI -> Tools -> HD Streams Extractor (eac3to) can be used to extract this wav from this mkv or encode directly to AC3.

[mini-moose]

When I use one-click encoder the import avs that's created sometimes has global MeGUI_darx/dary added and sometimes not.

Recent set I did of all the same source (different clips but same crop/resize/filtering on all) had first 2 with simple import and others with global MeGUI_darx/dary.

I'm not sure how it's supposed to be and why it changed. Not completely sure why darx/dary is even needed when the initial avs has all the resizing info needed.

[LigH]

These variables usually belong to the "Clever™ Anamorphic Encoding" feature, when no deskewing is desired. I never use the One-Click feature, so I don't know if both are related.

[mini-moose]

These variables usually belong to the "Clever™ Anamorphic Encoding" feature

I think I figured it out. On One-click, I've set advanced config to "keep resolution (disable crop & Resize)" and the "Auto Crop/Anamorph Output" are uncheked and greyed out.

However, when I launch the OCE dialog for the first time the "Anamorph Output" is checked (even though greyed out), and megui produces import avs files with dary/x.
To get back to my setting (i.e with anamorph checked off) I need to change profile and then simple import avs files are created.

I'm not too sure how important dary/x are, I tend to believe not so much as my resize values are already in the initial avs. Perheps it's useful to other users with a different routine.
Previous megui build had a bug in the dary/x settings so I rather it won't be used at all if it's not needed.

[LigH]

The existence of these variables apparently prevents MeGUI from resizing. But it will probably make MeGUI set up aspect ratio flags in the container in the final multiplexing job.

[mini-moose]

The existence of these variables apparently prevents MeGUI from resizing. But it will probably make MeGUI set up aspect ratio flags in the container in the final multiplexing job.

The "Output Resolution/auto crop/Anamorph Output" part in AVS settings is obviously aimed at one-click users who don't want to mess around too much. But, I don't see why the greyed out sections would still effect when I have those options disabled. I use OCE cause of the ease of queuing a number of encodes at once, and the ease of adding all components for the final muxed mkv (vid/audio/subs/chapters/language tagging). AutoEncode is also quite good for that but requires a few more stages.

[AMED]

Yes, MeGUI -> Tools -> HD Streams Extractor (eac3to) can be used to extract this wav from this mkv or encode directly to AC3.

Another way around this is to rip LPCM in to FLAC in makeMKV.

[Zathor]

I was hoping for 10-bit support, not this.
I have no experience at all with 10bit x264. LigH and you already wrote what must be done: http://forum.doom9.org/showthread.php?p=1632640#post1632640
Is it sufficient to add only the binaries, add a new checkbox in the x264 preset (8/10 bit - different command lines for 10bit required? If yes which?) and that's it?

[LigH]

As far as I know...

If you only want to process 8-bit-per-channel video with chroma subsampling 4:2:0 (YV12), as usual for the AviSynth core, and encode it with 10-bit component resolution (which is slightly more efficient as such already, but less hardware decoder compatible), yes, all you need is an alternative x264.exe, and not even any more command line options.

Even finer chroma subsampling (YV16 for 4:2:2 or YV24 for 4:4:4, instead of YV12 for 4:2:0) may not be too hard with some additional command line options; it is just even less hardware decoder compatible.

But to support "deepcolor support (http://avisynth.nl/index.php/High_bit-depth_Support_with_Avisynth)" (8 bit LSB + 8 bit MSB interleaved in the video), it will be a lot more complex, the whole script creation may hardly be automatizable anymore without a good amount of thoughts.

[detmek]

As LigH said, for 10-bit x264 encoding you will need:
1. New binary (from VideoLan or Komisars)
2. Checkbox for user to choose between 8-bit and 10-bit binary (like 64-bit version of x264 encoder), but this should probably go to x264 configuration dialog and be per preset option.
3. Disable profile selection as Baseline, Main and High with 10-bit x264 as those can not be used with 10-bit x264.
Command line is the same for 8-bit and 10-bit version, except for 3 profiles.
This will allow as to encode 8-bit video with 10-bit x264 for increased compression and reduced banding. True 10-bit input is a bit harder to implement fast so, maybe latter.

And for those that encode FRAPS captures, updating Avisynth to 2.6 will be great addition:
1. New Avisynth 2.6
2. Drop-down meni for ConvertToYV12/YV16/YV24 in Avisynth Script Creator
3. Drop-down meni for output-csp (i420, i422, i444) in x264 configuration dialog.

[detmek]

Do not just disable them.

Instead, replace them with the appropriate profiles (and appropriate VBV restrictions), as i already suggested earlier, see the following quote:



No need for that. Profiles in 10-bit encoder depends on output colorspace. If you use YV12 you can not set Hi422 or Hi444 profile, nor Baseline, Main or High. And, if you use YV24, you can not use any profile but Hi444. x264 10-bit encoder automatically sets correct profile.

[detmek]

Technically, you are right. But, setting VBV for 10-bit encodes is pointless.
There are 3 reasons for using VBV:

1. Blu-Ray authoring
2. Network streaming
3. Compatibility with (hardware) decoders

For 8 bit encodes:

1. BD authoring requires different VBV than H.264 standard specifies so no use for that.
2. Due to network speed limitation, streaming requires much lower VBV values than those H.264 standard specifies. Basically, VBV is network specific.
3. So, the only reason for using VBV with 8 bit encodes is compatibility with some rare hardware decoders. For other hardware players we have device presets. Sofware decoders decode everything.

Now, for 10-bit encodes:

1. BD is out of the question
2. As I already said, network streaming requires much lower VBV settings but maximum VBV settings for 10-bit encodes are even higher than for 8-bit encodes. So, no use for that, too. And, it is network specific.
3. There are no consumer hardware decoders that can decode 10-bit video. And when we get ones, those will probably decode everything, like most hardware players today that can decode every 8-bit video.
And, as I said, VBV restrictions are so high for 10-bit video that no one is going to use so high bitrates that will outpass VBV restrictions.

So, there are two reasons to set VBV for 10-bit encodes:

1. We want to be "by-the-book".
2. For testing purposes.

BTW, Dark Shikari usually says: "Don't use VBV unless you have to" and I agree with that.

Same goes for maximum bitrate of 300000kbs. Rising limit to 960000kbs must be tied to 10-bit checkbox. But also no practical purpose as no one is using so high bitrate because encoded video will be larger than source.

I really don't see the reason why are you insisting so much on such cosmetic features that no one use.

[LigH]

VBV restrictions are so high for 10-bit video that no one is going to use so high bitrates that will outpass VBV restrictions.

You are pulling a Gates here... ;)

[hello_hello]

The official H.264 specifications always require VBV restrictions, so IMHO it is very reasonable to always encode with VBV restrictions ;).

Maybe you should post in the MPEG-4 AVC / H.264 forum and enquire as to why x264 itself doesn't apply VBV restrictions "by the book" because if anything it should be the encoder's responsibility to enforce them.

In my opinion the main problem with x264 not enforcing VBV restrictions is a lack of consistency, given it does enforce others according to the level specified, so it'd probably be reasonable to assume it enforces all of them.
Plus there's been/is a lack of consistency between encoder GUIs and even between different x264 builds.

Mind you having said all that I do think the current system is a pretty good compromise. x264 doesn't automatically enforce VBV restrictions so MeGUI tells it to do so when choosing a profile and level, but there's nothing to stop you using MeGUI's encoder configuration to remove the VBV restrictions from the command line if you prefer not to use them (assuming you've not selected a target playback device).

[SacredCultivator]

Sorry if this was mentioned within the change of not being able to output .mp4 for encodes.

But seems (only tested) with VLC after I produce the rawavc file and then mux it using meGUI's MP4 muxer, I can't seek videos and it just freezes with VLC. But using CCCP/Media Player Classic it's fine.

NO settings were changed within meGUI except for updating the internal files through meGUI. So not sure if it's something that was intentional or not from the change.

I apologize if that's vague and can provide more info if needed.

[Zathor]

Does anyone see a problem changing the default MOD value to 8 in the AVS script creator? I have a request ongoing here:
https://sourceforge.net/p/megui/bugs/727/

x264 has no problems with mod8 but I am not sure about xvid.

[hello_hello]

Does anyone see a problem changing the default MOD value to 8 in the AVS script creator? I have a request ongoing here:
https://sourceforge.net/p/megui/bugs/727/

x264 has no problems with mod8 but I am not sure about xvid.

I don't think there's too much issue even for Xvid these days, although I don't know for sure.

I leave it set to the default of mod16, even though when resizing I'll generally change it to suit, but that's literally because when using the arrows to specify the width and height, steps of 16 get you close to the desired resolution faster than steps of 8 or 2.

On a similar note, is there really a need to have a setting to enable upsizing? Especially one which is kind of hidden away in the AVS Configuration. Is there a reason for not simple having it enabled and doing away with the option to enable/disable it?

While I'm typing, is it possible for the script creator's resizing to behave the way cropping does? If you crop, disabling and re-enabling it doesn't change the specified copping. Disabling and re-enabling the resize filter resets it to the original resolution (minus cropping), possibly for reasons which allude me.

[Richard1485]

When the Blu-ray compatibility option is checked, the open GOP setting can be selected/deselected, but it appears do to nothing, and while --open-gop is supported by the Blu-ray spec, and it's probably a good idea to use it when encoding for Blu-ray, it's not compulsory so there's probably no reason why MeGUI should force it's use.

Yes. That's true as long as the target playback device is not set to Blu-ray. Can one add a command to the custom command line under the miscellaneous tab that will force MeGUI to close GOPs?

[detmek]

About MOD8, AFAIK players do not have problem with mod8 Xvid. I am not sure about compression efficiency with mod8.
But, considering that x264 is more often used and the problem described in bug tracker, I think it is probably good idea to change default mod to mod8. For those who need mod16, they can change that manually.
The hole point of choosing default values for some parameter is that it fits needs for most people and mod8 probably does that.
About Handbrakes mod2: Handbrake only outputs H.264 video and x264 works just fine with mod2 so that is why they changed that to mod2.

[hello_hello]

Zathor, do you recall me previously posting regarding MeGUI occasionally pulling an aspect ratio out of thin air? I seem to be able to duplicate the problem reliably now. Although maybe it's less MeGUI bug and more user error.
I've been reproducing the problem by manually changing the resizing in a script after it's been loaded into the video section, but before it's been added to the job queue.
Going back through the log file, this is how changing the resizing effected the SAR.
656x356 SAR 1:1
658x356 SAR 328:329
658x358 SAR 29356:29281
656x358 SAR 179:178

If I reload the script after manually changing the resizing, the SAR is always 1:1.

It appears as though MeGUI decides on the aspect ratio of the video when the script is loaded into the video section. Then when the encoding job is queued and run, if the resizing in the script and the predetermined aspect ratio don't "match", MeGUI decides it needs to get a little anamorphic to fix it.
Whether the above behaviour is by design I don't know, but at least I think I've found out why it's happing. To be honest though, given (from a user perspective) everything else related to the encoding seems to be set when the encoding job is added to the queue, I didn't expect aspect ratio would be an exception. Over the years I've probably loaded a script for encoded many times, then manually changed something in it such as noise filtering, and as long as I did so before adding the encoding job to the queue I don't think it's ever caused a problem.
In fact a quick test seems to indicate (as an example), I can add noise filtering to a script after it's been added to the queue, and MeGUI uses the script in it's current state when the job is run (ie the noise filtering is included).

I haven't tested any of the above using anamorphic encoding to see if MeGUI changes the SAR the same way, but for the moment I'll make sure I'm fairly OCD when it comes to always re-loading scripts after I change something.

[Kurtnoise]

*Testers needed*

I'm adding few things into MeGUI (external muxers & 10bits for x264 encoder) but I need you to test it heavily before to commit my last patches. Moreover, I'm lazy to upload exec into the server, so :

1/ Grab the build from here (http://kurtnoise.free.fr/megui/) and replace the main executable (might be great to backup the old one before to overwrite it)
2/ Grab x264-10 bits encoder from here (http://download.videolan.org/pub/x264/binaries/win64/) (x64) or there (http://download.videolan.org/pub/x264/binaries/win32/) (x86) - The file to retrieve begins by "x264-10b"
3/ Put it into the MeGui\tools\x264\ folder
4/ Rename it like x264-10b.exe and/or x264-10b_64.exe
5/ Run your tests
6/ 10bits Encoder and/or External muxer can be enabled/disabled through the MeGUI Settings.
7/ Feedback welcome => :logfile: if you have some errors

:thanks:

[invy]

I am having the problem again where my files (in OCE) are being detected as having 2 audio tracks. Here are 2 MediaInfos:

General
Complete name : C:\42551_812_0813_2159-0.mpg
Format : MPEG-PS
File size : 2.20 GiB
Duration : 36mn 55s
Overall bit rate : 8 525 Kbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Duration : 36mn 55s
Maximum bit rate : 9 411 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Compression mode : Lossy

Audio #2
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 36mn 55s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -1s 51ms
Stream size : 50.7 MiB (2%)

Text #1
ID : 224 (0xE0)-CC1
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #2
ID : 224 (0xE0)-CC2
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #3
ID : 224 (0xE0)-1
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #4
ID : 224 (0xE0)-2
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)



General
Complete name : C:\42551_812_0809_2159-0.mpg
Format : MPEG-PS
File size : 2.27 GiB
Duration : 36mn 56s
Overall bit rate : 8 811 Kbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Duration : 36mn 56s
Maximum bit rate : 9 411 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Compression mode : Lossy

Audio #2
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 36mn 56s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -676ms
Stream size : 50.7 MiB (2%)

Text #1
ID : 224 (0xE0)-CC1
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #2
ID : 224 (0xE0)-1
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #3
ID : 224 (0xE0)-2
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

[LigH]

It is correct for AC3 in DVD compatible MPEG-2 Program Stream multiplexing to be in substream 0x80 of MPEG Private Stream 2 (0xBD). But it should not be reported in MPEG stream 0x80. A more technically oriented MPEG analyzer (possibly MPEGanalizzatore (http://www.offeryn.de/dv.htm)?) may reveal if the multiplexer created a nonsensical file.

[invy]

I should have mentioned that when I run the file through VideoReDo's Quickstream Fix, it fixes the problem.

Before fix:

General
Complete name : C:\1.mpg
Format : MPEG-PS
File size : 2.04 GiB
Duration : 29mn 58s
Overall bit rate : 9 763 Kbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Duration : 29mn 58s
Maximum bit rate : 10.4 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Active Format Description : Letterbox 16:9 image
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio #1
ID : 128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Compression mode : Lossy

Audio #2
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 29mn 58s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Delay relative to video : -596ms
Stream size : 41.2 MiB (2%)

Text #1
ID : 224 (0xE0)-CC1
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #2
ID : 224 (0xE0)-1
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #3
ID : 224 (0xE0)-2
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)



After fix:

General
Complete name : C:\1.mpg
Format : MPEG-PS
File size : 2.03 GiB
Duration : 29mn 58s
Overall bit rate : 9 696 Kbps

Video
ID : 224 (0xE0)
Format : MPEG Video
Format version : Version 2
Format profile : Main@High
Format settings, BVOP : Yes
Format settings, Matrix : Custom
Format settings, GOP : Variable
Duration : 29mn 58s
Bit rate : 9 311 Kbps
Maximum bit rate : 10.4 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Active Format Description : Letterbox 16:9 image
Frame rate : 29.970 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.150
Time code of first frame : 00:00:00;00
Time code source : Group of pictures header
Stream size : 1.95 GiB (96%)
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Audio
ID : 189 (0xBD)-128 (0x80)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Muxing mode : DVD-Video
Duration : 29mn 58s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 41.2 MiB (2%)

Text #1
ID : 224 (0xE0)-CC1
Format : EIA-608
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #2
ID : 224 (0xE0)-1
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)

Text #3
ID : 224 (0xE0)-2
Format : EIA-708
Muxing mode : A/53 / DTVCC Transport
Muxing mode, more info : Muxed in Video #1
Bit rate mode : Constant
Stream size : 0.00 Byte (0%)


Also, the 2 audio tracks are always the same size in KB because it is (obviously) the same track encoding twice.

If I could just tell OCE to just ignore the 2nd track, it would be fine. Note: the "use only first track" option in the audio config has no effect on this.

[detmek]

Testing 10-bit encoder and external muxer.
[Error] Log
-[Information] Versions
--[Information] [18:23:39] MeGUI: 2383
--[Information] [18:23:39] Operating System: Windows 7 Premium Edition x86 SP1 (6.1.65536.7601)
--[Information] [18:23:39] .Net Framework: 4.5 (4.5.50709)
--[Information] [18:23:40] AviSynth: 2.6.0.3 (09-03-2013) - portable
--[Information] [18:23:40] DevIL: 1.6.6 (26-05-2004)
--[Information] [18:23:40] AvisynthWrapper: (02-01-2009)
--[Information] [18:23:40] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [18:23:40] Haali DSS2: (14-04-2013)
--[Information] [18:23:40] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [18:23:40] LinqBridge: 1.0.0.0 (28-05-2009)
--[Information] [18:23:40] MediaInfo: 0.7.64.0 (05-07-2013)
--[Information] [18:23:40] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [18:23:40] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [18:23:40] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [18:23:40] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [18:23:40] Automatic update is disabled
-[Error] Log for job3 (video, GIJ.mkv.avs -> GIJ.mkv.h264)
--[Information] [18:24:07] Started handling job - 14-08-2013
--[Information] [18:24:07] Preprocessing
--[Information] [18:24:07] Avisynth input script
---[NoImage] LoadPlugin("D:\PROGRAMI\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("G:\x264\TF\GIJ.mkv", cachefile="G:\x264\GIJ.mkv.ffindex", threads=1)
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] Spline36Resize(640,256) # Spline36 (Neutral)
---[NoImage] #denoise
--[Information] [18:24:08] resolution: 640x256
--[Information] [18:24:08] frame rate: 24000/1001
--[Information] [18:24:08] aspect ratio: 5:2 (2.500)
--[Information] [18:24:08] Job commandline: "D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe" -L "D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe" --crf 21 --keyint 240 --sar 1:1 --output "G:\x264\GIJ.mkv.h264" "G:\x264\GIJ.mkv.avs"
--[Information] [18:24:08] Process started
--[Information] [18:24:08] Standard output stream
--[Information] [18:24:08] Standard error stream
---[Information] [18:24:08] D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe: unknown option -- L
--[Error] [18:24:08] Process exits with error: 0xFFFFFFFF (-1)
--[Information] [18:24:08] Job completed - 14-08-2013
-[Error] Log for job4 (mux, GIJ.mkv.h264 -> GIJ.mkv.mp4)
--[Information] [18:24:08] Started handling job - 14-08-2013
--[Information] [18:24:08] Preprocessing
--[Error] [18:24:08] Error starting job
---[Error] [18:24:08] Exception message: Calling setup of processor failed with error 'Required file 'G:\x264\GIJ.mkv.h264' is missing.'
---[Error] [18:24:08] Stacktrace: at MeGUI.core.gui.JobWorker.startEncoding(TaggedJob job)
---[Error] [18:24:08] Inner exception: null
10bit enoding generates error.

[detmek]

[Information] Log
-[Information] Versions
--[Information] [18:28:06] MeGUI: 2383
--[Information] [18:28:06] Operating System: Windows 7 Premium Edition x86 SP1 (6.1.65536.7601)
--[Information] [18:28:06] .Net Framework: 4.5 (4.5.50709)
--[Information] [18:28:06] AviSynth: 2.6.0.3 (09-03-2013) - portable
--[Information] [18:28:06] DevIL: 1.6.6 (26-05-2004)
--[Information] [18:28:06] AvisynthWrapper: (02-01-2009)
--[Information] [18:28:06] Haali Matroska Splitter: 1.13.138.14 (14-04-2013)
--[Information] [18:28:06] Haali DSS2: (14-04-2013)
--[Information] [18:28:06] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [18:28:06] LinqBridge: 1.0.0.0 (28-05-2009)
--[Information] [18:28:06] MediaInfo: 0.7.64.0 (05-07-2013)
--[Information] [18:28:06] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [18:28:06] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [18:28:06] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [18:28:06] 7z: 9.20 (18-11-2010)
-[Information] Update detection
--[Information] [18:28:06] Automatic update is disabled
-[Information] Log for job1 (video, GIJ.mkv.avs -> GIJ.mkv.h264)
--[Information] [18:28:43] Started handling job - 14-08-2013
--[Information] [18:28:43] Preprocessing
--[Information] [18:28:43] Avisynth input script
---[NoImage] LoadPlugin("D:\PROGRAMI\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("G:\x264\TF\GIJ.mkv", cachefile="G:\x264\GIJ.mkv.ffindex", threads=1)
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] Spline36Resize(640,256) # Spline36 (Neutral)
---[NoImage] #denoise
--[Information] [18:28:44] resolution: 640x256
--[Information] [18:28:44] frame rate: 24000/1001
--[Information] [18:28:44] aspect ratio: 5:2 (2.500)
--[Information] [18:28:44] Job commandline: "D:\PROGRAMI\MeGUI\tools\x264\x264.exe" --crf 21 --keyint 240 --sar 1:1 --output "G:\x264\GIJ.mkv.h264" "G:\x264\GIJ.mkv.avs"
--[Information] [18:28:44] Process started
......
---[Information] [18:29:49] x264 [info]: kb/s:1422.46
---[Information] [18:29:49] encoded 1108 frames, 17.24 fps, 1422.46 kb/s
--[Information] [14-Aug-13 6:29:50 PM] Final statistics
---[Information] [18:29:50] Constant Quality Mode: Quality 21 computed...
---[Information] [18:29:50] Video Bitrate Obtained (approximate): 1422 kbit/s
--[Information] [18:29:50] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.h264
---[Information] General
----[Information] Format: AVC
----[Information] FormatString: AVC
----[Information] FileSize: 8216973
----[Information] PlayTime:
---[Information] Video
----[Information] ID:
----[Information] StreamOrder:
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount:
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode:
----[Information] ScanType: Progressive
----[Information] Codec: AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay:
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
--[Information] [18:29:50] Postprocessing
---[Information] [14-Aug-13 6:29:50 PM] Deleting intermediate files
--[Information] [18:29:50] Job completed - 14-08-2013
-[Information] Log for job2 (mux, GIJ.mkv.h264 -> GIJ.mkv.mp4)
--[Information] [18:29:50] Started handling job - 14-08-2013
--[Information] [18:29:50] Preprocessing
--[Information] [18:29:50] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.h264
---[Information] General
----[Information] Format: AVC
----[Information] FormatString: AVC
----[Information] FileSize: 8216973
----[Information] PlayTime:
---[Information] Video
----[Information] ID:
----[Information] StreamOrder:
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount:
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode:
----[Information] ScanType: Progressive
----[Information] Codec: AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay:
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
--[Information] [18:29:50] Job commandline: "D:\PROGRAMI\MeGUI\tools\mp4box\mp4box.exe" -add "G:\x264\GIJ.mkv.h264#trackID=1:fps=0.0:name=" -tmp "G:\\x264" -new "G:\x264\GIJ.mkv.mp4"
--[Information] [18:29:51] Process started
--[Information] [18:29:51] Standard output stream
--[Information] [18:29:51] Standard error stream
---[Information] [18:29:52] AVC-H264 import - frame size 640 x 256 at 23.976 FPS
---[Information] [18:29:55] AVC Import results: 1108 samples - Slices: 63 I 731 P 314 B - 1 SEI - 32 IDR
---[Information] [18:29:55] Stream uses forward prediction - stream CTS offset: 2 frames
---[Information] [18:29:55] Saving G:\x264\GIJ.mkv.mp4: 0.500 secs Interleaving
--[Information] [18:29:55] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.mp4
---[Information] General
----[Information] Format: MPEG-4
----[Information] FormatString: MPEG-4
----[Information] FileSize: 8227224
----[Information] PlayTime: 00:00:46.212
---[Information] Video
----[Information] ID: 1
----[Information] StreamOrder: 0
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount: 1108
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode: CFR
----[Information] ScanType: Progressive
----[Information] Codec: AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay: 0
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
--[Information] [18:29:56] Postprocessing
---[Information] [14-Aug-13 6:29:56 PM] Deleting intermediate files
----[Information] [18:29:56] Successfully deleted G:\x264\GIJ.mkv.h264
--[Information] [18:29:56] Job completed - 14-08-2013
-[Information] Log for job3 (video, GIJ.mkv.avs -> GIJ.mkv.h264)
--[Information] [18:29:56] Started handling job - 14-08-2013
--[Information] [18:29:56] Preprocessing
--[Information] [18:29:56] Avisynth input script
---[NoImage] LoadPlugin("D:\PROGRAMI\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("G:\x264\TF\GIJ.mkv", cachefile="G:\x264\GIJ.mkv.ffindex", threads=1)
---[NoImage] #deinterlace
---[NoImage] #crop
---[NoImage] Spline36Resize(640,256) # Spline36 (Neutral)
---[NoImage] #denoise
--[Information] [18:29:56] resolution: 640x256
--[Information] [18:29:56] frame rate: 24000/1001
--[Information] [18:29:56] aspect ratio: 5:2 (2.500)
--[Information] [18:29:56] Job commandline: "D:\PROGRAMI\MeGUI\tools\x264\x264.exe" --crf 21 --keyint 240 --sar 1:1 --output "G:\x264\GIJ.mkv.h264" "G:\x264\GIJ.mkv.avs"
--[Information] [18:29:56] Process started
--[Information] [18:29:56] Standard output stream
--[Information] [18:29:56] Standard error stream
---[Information] [18:29:58] avs [info]: 640x256p 1:1 @ 24000/1001 fps (cfr)
---[Information] [18:29:58] x264 [info]: using SAR=1/1
......
---[Information] [18:31:03] x264 [info]: kb/s:1422.46
---[Information] [18:31:03] encoded 1108 frames, 16.96 fps, 1422.46 kb/s
--[Information] [14-Aug-13 6:31:03 PM] Final statistics
---[Information] [18:31:03] Constant Quality Mode: Quality 21 computed...
---[Information] [18:31:03] Video Bitrate Obtained (approximate): 1422 kbit/s
--[Information] [18:31:03] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.h264
---[Information] General
----[Information] Format: AVC
----[Information] FormatString: AVC
----[Information] FileSize: 8216973
----[Information] PlayTime:
---[Information] Video
----[Information] ID:
----[Information] StreamOrder:
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount:
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode:
----[Information] ScanType: Progressive
----[Information] Codec: AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay:
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
--[Information] [18:31:03] Postprocessing
---[Information] [14-Aug-13 6:31:03 PM] Deleting intermediate files
--[Information] [18:31:03] Job completed - 14-08-2013
-[Information] Log for job4 (mux, GIJ.mkv.h264 -> GIJ.mkv.mkv)
--[Information] [18:31:03] Started handling job - 14-08-2013
--[Information] [18:31:03] Preprocessing
--[Information] [18:31:03] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.h264
---[Information] General
----[Information] Format: AVC
----[Information] FormatString: AVC
----[Information] FileSize: 8216973
----[Information] PlayTime:
---[Information] Video
----[Information] ID:
----[Information] StreamOrder:
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount:
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode:
----[Information] ScanType: Progressive
----[Information] Codec: AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay:
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
--[Information] [18:31:03] Job commandline: "D:\PROGRAMI\MeGUI\tools\mkvmerge\mkvmerge.exe" -o "G:\x264\GIJ.mkv.mkv" "G:\x264\GIJ.mkv.h264" "--compression" "0:none" --ui-language en
--[Information] [18:31:04] Process started
--[Information] [18:31:04] Standard output stream
---[Information] [18:31:05] mkvmerge v6.3.0 ('You can't stop me!') built on Jun 28 2013 20:09:41
---[Information] [18:31:05] 'G:\x264\GIJ.mkv.h264': Using the demultiplexer for the format 'AVC/h.264'.
---[Information] [18:31:05] 'G:\x264\GIJ.mkv.h264' track 0: Using the output module for the format 'AVC/h.264 (unframed)'.
---[Information] [18:31:05] The file 'G:\x264\GIJ.mkv.mkv' has been opened for writing.
---[Information] [18:31:06] 'G:\x264\GIJ.mkv.h264' track 0: Extracted the aspect ratio information from the MPEG-4 layer 10 (AVC) video data and set the display dimensions to 640/256.
---[Information] [18:31:06] The cue entries (the index) are being written...
---[Information] [18:31:06] Muxing took 0 seconds.
--[Information] [18:31:04] Standard error stream
--[Information] [18:31:06] MediaInfo
---[Information] File: G:\x264\GIJ.mkv.mkv
---[Information] General
----[Information] Format: Matroska
----[Information] FormatString: Matroska
----[Information] FileSize: 8231239
----[Information] PlayTime: 00:00:46.213
---[Information] Video
----[Information] ID: 1
----[Information] StreamOrder: 0
----[Information] Width: 640
----[Information] Height: 256
----[Information] FrameCount: 1108
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode: CFR
----[Information] ScanType: Progressive
----[Information] Codec: V_MPEG4/ISO/AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.500
----[Information] AspectRatioString: 2.500
----[Information] Delay: 0
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default: Yes
----[Information] DefaultString: Yes
----[Information] Forced: No
----[Information] ForcedString: No
--[Information] [18:31:06] Postprocessing
---[Information] [14-Aug-13 6:31:06 PM] Deleting intermediate files
----[Information] [18:31:06] Successfully deleted G:\x264\GIJ.mkv.h264
--[Information] [18:31:06] Job completed - 14-08-2013

Seams to work.

[LigH]

Testing 10-bit encoder and external muxer.

10bit enoding generates error.

Well, this is suspicious:

"D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe" -L "D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe"

I believe you wanted to have

"D:\PROGRAMI\MeGUI\tools\x264\avs4x264mod.exe" -L "D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe"

or simply

"D:\PROGRAMI\MeGUI\tools\x264\x264-10b.exe"

[detmek]

Actually, I just want it to work. :D
It is Kurtnoise's test build (http://forum.doom9.org/showthread.php?p=1640346#post1640346).
For 8-bit input avs4x264mod is not required unless future plans for MeGUI include support for higher bitdepth input files.

@Kurtnoise
You should probably move 10-bit checkbox to x264 configuration dialog. That should not be global option as using 64-bit version.
I mean, if one have 64-bit Windows he will always want to use x64 binary. But, one will not alway want to encode with 10-bit precision due to lack of hardware support (cellphone, tablet, TV, Blu-Ray/multimedia player).
If you move 10-bit checkbox to x264 configuration dialog we can create different presets for 8-bit and 10-bit encodes.

[LigH]

avs4x264mod.exe is required for calling a 64-bit x264.exe to work with 32-bit AviSynth... maybe there is just a copy-and-paste issue.

32 vs. 64 bit architecture on one hand, and 8 vs. 10 bit component resolution on the other hand, are two independent decisions. Therefore you have four builds provided by binary compiling distributors. MeGUI might need to be able to configure custom EXEs for all four variants, if it doesn't demand a specific naming convention for all four of them.

[detmek]

Right, sorry. I use 32-bit Windows so I have never used avs4x264mod. Forgot it even exists.

In current implementation it is easy to switch between all four binaries. I don't know how easy would be to move 10-bit checkbox to x264 configuration dialog and control from there which binary to use.

[Kurtnoise]

Ok, I moved the 10-bits Encoding support in the x264 config panel...

=> 2nd Test build (http://kurtnoise.free.fr/megui/)...

:thanks:

[detmek]

I did some testing. Findings:
- command line is correct
- muxing works correct
Bugs:
- when I activate 10-bit encoding, H.264 profiles are not greyed out right away and can be set to Baseline or Main, which reslults in incorrect command line. x264 configuration dialog needs to be reopened.
- if you activate 10-bit encoding, set Main or Baseline profile and save preset, after reopening profile selection will be greyed out but --profile will be still present in command line
- when you select MP4 for output, just for video and click on Queue, Video Output extention will be changed to .h264. But, if you click Queue one more time, error message will show up: "Video output file name does not have correct extention. Based on current settings it shoud be mp4".

[Kurtnoise]

Could you retry the same thing but using the x264 scratchpad instead ?

[detmek]

If you mean that I should test profile selection with scrathcpad profile, it is the same.
BTW, more info: In order to reproduce that, "Show Advanced Settings" must be checked first. If you first activate 10-bit encoding everything works fine. Also, if you check 10-bit encoding, than check Advanced Settings and that deacitivate 10-bit encodins, AVC Profiles will still be greyed out.

[Kurtnoise]

Fixed (http://kurtnoise.free.fr/megui/MeGUI-r2385_20130816.7z), hopefully...

[detmek]

Well... partially, and probably because I didn't noticed in time but, if Main or Baseline profile is selected and you enable 10-bit encoding, AVC Profiles are greyed out but --profile main/baseline will stay in command line.
BTW, thanks for your effort to implement 10-bit encoding.