MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio

[Sharktooth]

just HKLM\SOFTWARE\MeGUI which contains just one key that is the path for the update_cache folder. check your system for viruses/malwares...

[[ReX]]

just HKLM\SOFTWARE\MeGUI which contains just one key that is the path for the update_cache folder. check your system for viruses/malwares...

I'm pretty sure i have no viruses/malwares.
The funny thing is that this issue happens only on version 0.3.0.2008. :eek:

Suggestion: Add h264 on MP4 Muxer extensions, when MKVE Wizard/MKVExtractGUI demux AVC stream, it use that extension. It's easy to rename from .h264 to .264 but could be nice to have this extension added.

[magic144]

hi guys

I am trying to reencode a BD source with MPEG2 video.

I have extracted the .m2v with eac3to.
I used the d2v creator tool to run dgindex on the .m2v and produce the appropriate accompanying .d2v

When I subsequently fire up the AVISynth script creator tool, I cannot get the Autocrop function to work.

I can see it working if I choose the source as one of the source .m2ts file, but NOT with the .d2v file...

Am I doing something wrong, or is there an issue here?

thanks,

m

[Sharktooth]

if it works with the m2ts should work with the d2v too.
avisynth doesnt distinguish between the sources once they're loaded thru a plugin.
however can you see the preview?

[rack04]

hi guys

I am trying to reencode a BD source with MPEG2 video.

I have extracted the .m2v with eac3to.
I used the d2v creator tool to run dgindex on the .m2v and produce the appropriate accompanying .d2v

When I subsequently fire up the AVISynth script creator tool, I cannot get the Autocrop function to work.

I can see it working if I choose the source as one of the source .m2ts file, but NOT with the .d2v file...

Am I doing something wrong, or is there an issue here?

thanks,

m

I've noticed that auto crop can take a fair amount for time with very large files, i.e. HD DVD and Blu-ray. How long did you give it?

[magic144]

yup, I can see the preview window as per normal, no problem

I can also manually adjust crop margins, although this is prone to crashing quite frequently if I do it too many times or perhaps just too fast - don't know exactly the origin of that particular problem

the Autocrop button for the .d2v source, however, just seems to stubbornly do nothing...

I'm running on Vista 32-bit Home Premium.
When I press Autocrop on an .m2ts source, the cursor changes to Vista's "I Am Thinking" icon before the appropriate adjustment is made visually on-screen.
When I press Autocrop on a .d2v source, no such processing seems to occur and nothing happens on-screen.

I'm sure I've done this without issue on a .dga file (which I would assume to be the analagous operation in the h.264 domain)

Can anybody confirm whether or not the Avisynth script creation tool's Autocrop works for them on .d2v sources using the latest MeGUI (preferably also under Vista)?

@Rack04 - I believe I gave it longer than when it was seen to work with the .m2ts file of the same source - although admittedly the .m2ts was merely one of a number of constituent .m2ts files in the total playlist - I will give it another go tonight and leave it be for a while to see what happens

[Sharktooth]

... it you can see the preview, autocrop will work...

[magic144]

okay thanks - I will fire it up again tonight and set it going and leave it - perhaps I was just too impatient yesterday for some reason

I will report back later - cheers for the responses

[magic144]

OK, so I got to try it out at lunch...

My findings are these...

Autocrop is 'working'. It just comes back with 0,0,0,0 cropping if I run the full .d2v file as input (within just a few seconds).

Tried a couple of other experiments.
Using DGIndex, I manually created .d2v files from various ranges of the entire .m2v file. Any amount of video from the very start through to not-quite-the-end seem to allow Autocrop to locate the top and bottom black bars OK.
Any amount of video from just after the beginning through to the very end also seems to allow Autocrop to do its work OK (though taking too short of a clip just near the end seems to confuse it slightly - probably due to the end credits).

It seems odd that the entire file fails to work with Autocrop given that the separate (and overlapping) video segments I tried that include the beginning and end worked OK. I guess I'll just have to take the numbers that the sub-clip gives me and hand-edit them into the .avs file for now.

m

[Sharktooth]

sadly, autocrop is not and cant be perfect.

[magic144]

understood - I guess it's yet another thing I have to keep in the back of my mind in my workflow :-)
I must write this stuff down!!

[shortkud]

I just updated via the auto updater to the latest version of everything and now everything I attempt to encode crashes x264.exe

[Sharktooth]

try replacing x264 with the one on x264.nl and see if it works

[shortkud]

try replacing x264 with the one on x264.nl and see if it works

Still crashing :\. Any other details I can provide that would help diagnose the issue?

[Avenger007]

:script::logfile:

[magic144]

question about the use of ColorMatrix in the AviSynth script creator...

I've read a lot about ColorMatrix, but there seems to be as much information as misinformation flying about.
I thought that the way in which the script creator is using it (which is just ColorMatrix(hints=true)), it would try and do a rec.709 to rec.601 conversion

however, it was also my understanding that HD encoded material was to be rec.709

can someone explain why the apparent scripted 709->601 conversion? or have I got this wrong??

I had a look at the h.264 output from MeGUI/x264 using DGAVCIndex and it appeared to indicate rec.709 (or at least rec.709 by default since it was not explicitly indicated in the stream) - from the DGAVCIndex manual - "Note that if the stream does not declare the colorimetry, then ITU-R BT.709* is reported for HD video"

cheers,

m

[Sharktooth]

x264 r985 should fix the crashing bug, just let megui auto-update.

[shortkud]

x264 r985 should fix the crashing bug, just let megui auto-update.

Thanks

[NiGHTsC]

Can someone teach me how to make a batch ".bat" file so I can encode my 37 AVI(WMV9&MP3) files into MP4 with video and audio?

this is AVS setting
DirectShowSource("J:\001.avi",fps=23.9759856527702,audio=false)
#deinterlace
#crop
#resize
#denoise
my profile of video, encoding to x264
--pass 2 --bitrate 1000 --stats ".stats" --ref 3 --mixed-refs --no-fast-pskip --bframes 2 --b-pyramid --bime --weightb --trellis 1 --analyse p8x8,b8x8,i4x4,p4x4 --merange 24 --threads auto --thread-input --progress --no-psnr --no-ssim --output "J:\@MP4.mp4" "J:\@MP4.avs"
and audio, encoding to NeroAAC into MP4
<?xml version="1.0"?>
<GenericProfileOfAudioCodecSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Name>456</Name>
<Settings xsi:type="NeroAACSettings">
<ImproveAccuracy>true</ImproveAccuracy>
<ForceDecodingViaDirectShow>false</ForceDecodingViaDirectShow>
<DownmixMode>KeepOriginal</DownmixMode>
<BitrateMode>VBR</BitrateMode>
<Bitrate>128</Bitrate>
<Delay>0</Delay>
<DelayEnabled>false</DelayEnabled>
<AutoGain>false</AutoGain>
<Profile>Auto</Profile>
<Quality>0.23</Quality>
<CreateHintTrack>false</CreateHintTrack>
</Settings>
</GenericProfileOfAudioCodecSettings>

Thank you.

[Sharktooth]

...and what a .bat file has in common with with megui?

[NiGHTsC]

Hm, I don't know, that's why I'm asking lol...
I thought it's encoding like Mencoder...
Thanx then.


==========
by the way, is there any faster way to do my jobs?
using my MeGUI Video/Audio profiles.

I'll merge them into MP4 one by one later, but it's the encoding messing me up.

Thanx again.

[Sharktooth]

please open a new thread...

[NiGHTsC]

I see, cause I have seen people asked it here so I thought it's the right place.
My bad, thanx anyway.

[DontAsk]

I have a suggestion: Make the Avisynth Script Creator return to the frame you have selected when you use the Preview AVS Script button or the Auto Preview.

[Sharktooth]

Post it in the feature request tracker of the megui project on sourceforge

[Hotpocketdeath]

Is anyone aware of the problem I have mentioned in this post about the cutter being totally broken?
http://forum.doom9.org/showthread.php?t=141685

It's been like this for quite a number of weeks and gone through several updates without correction.

I have about 40-50 videos waiting to be encoded with probably many more on the way that I use the cutter for.

[Frank_UK]

I have a Avisynth profile named default with the following settings:

Colour Correction

Clever (TM) anamorphic encoding

Encode non-mod 16

This profile will encode to x264 at original broadcast resolution.

This has always worked correctly until 0.3.0.3001

When Avisynth script creator is loaded my default profile is loaded with all the correct settings, however the video is resized to mod 16.

I did not notice this the first time I used 0.3.0.3001 and I had to re-encode.

Selecting encode non-mod 16 again stops the resize.

[brogan]

Hello,


Quick question for you guys. I've been using RipBot for a bit & wanted to give MeGUI a shot...How does it handle DTS audio? Do I have to transcode it to AC3 or another format or would I be able to copy the stream? If I wanted to add a DTS audio track to a video file, how would I do that w/out it being changed? Sorry for the newb-ish question but I couldn't much about this searching, all I came up w/was changing a DTS track to other formats...


:thanks::thanks::thanks:

[Frank_UK]

My bug ID: 2152972 has been closed with a message from kurtnoise13 "fixed in rev 808." - Thanks
How do I download and install "rev 808"

[Nightshiver]

Wrong thread.

[Sharktooth]

@Frank_UK: ill make a new build tonight.

@brogan: you need to install a directshow DTS decoder, like ac3filter.

[Frank_UK]

@Sharktooth - Thanks for build 0.3.0.3003; working correctly again now.

@kurtnoise13 - Thanks for fixing bug ID: 2152972; working correctly again now.

[unranger]

Probably a bug in XviD configuration dialog.
I was trying to use MeGUI 0.3.3004 to call xvid_encraw.exe for XviD encoding.
I manually added zone options in the "Custom Command Line" field under "Advanced" tab of "XviD configuration dialog" window (Input->Encoder Settings->"XviD: *scratchpad*"->Config)
I put in the custom command line field
-zones 0,w,1.0,0KOC
I got from the command line display field below
program -i "input" -single -bitrate 700 -smoother 0 -nopacked -closed_gop -threads 1 -o "output" -zones 0.w.1.0.0KOC
Notice that commas were automaticly replaced by dots.

Then, when trying to encode, xvid_encraw.exe complained: xvid [error]: Zone error, bad parameters 0.w.1.0.KOC

[Sharktooth]

post the bug in the megui bugtracker on sourceforge.

[Ryu77]

Just a little bug I noticed. It may have been addressed before though...

When using the bitrate calculator in MeGUI and loading in a 1536Kbs DTS audio track, it was actually detected as 1510Kbs.

I overlooked this and did a 8 hour 1080p encode, only to realise at the end I was 8MB over a DVD-9! Doh!!

[Sharktooth]

https://forum.doom9.org/showthread.php?p=1198618#post1198618

[Ryu77]

post the bug in the megui bugtracker on sourceforge.

Done... I didn't realise that you could do this without being a member (ie: logged in).

:-)

[Frank_UK]

I use x264: CE-Highprofile to encode my video. I find the quality to be superb.

I understand that this is now an obsolete profile, I have been advised to use x264: Unrestricted 2pass Balanced instead.

Is there any real advantage to move to the new profile? As I find the quality of the old profile superb.

[Sharktooth]

check by yourself.

[SeeManRun]

Hi guys. This has been bothering me for a while, so I downloaded the meGUI source and implemented the feature on my own, and would like to contribute it to the program if you find it useful. What I did was add another field (not sure I like the GUI implementation, but it is easily changed) that shows the frames per second for more limited amount of time rather than overall. The problem I have with the current scheme is that once you get a couple hours into your encoding, any changes to the CPU usage aren't reflected in the frames per second display. I implemented it using a deque, which I had to import since it seems C# doesn't have such a structure, at least to my limited knowledge. The deque keeps track of the current frame rate and after a certain amount of time, 2 minutes for example, starts sliding and using the values to measure the FPS.

If you guys find this useful, let me know and I will submit my code for review. My only issue is how to represent it in the GUI, which I added another textbox for, which I am not convinced I like, but simply adding it to the current FPS reading might make that display look too cluttered.

SMR

[Bitlord]

Hi, i was going to convert a dvd to h264+aac .mkv, then when i was going to convert the audio with nero aac (multichannel 128 kbps) i get an error. I tried reinstalling and trying winamp aac and faac, but it gives the same result.
And in the log it says like this :

"An error occured"
"Stacktrace
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath
at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count
at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count
at MeGUI.AviSynthAudioEncoder.encode()
Inner exception: null
Output from encoder via stderr
Output from encoder via stdout: ERROR: Could not initialize SBR"

Thanks

P.s. Audio is from dvd, 3.1 ac3.

[Sharktooth]

Hi guys. This has been bothering me for a while, so I downloaded the meGUI source and implemented the feature on my own, and would like to contribute it to the program if you find it useful. What I did was add another field (not sure I like the GUI implementation, but it is easily changed) that shows the frames per second for more limited amount of time rather than overall. The problem I have with the current scheme is that once you get a couple hours into your encoding, any changes to the CPU usage aren't reflected in the frames per second display. I implemented it using a deque, which I had to import since it seems C# doesn't have such a structure, at least to my limited knowledge. The deque keeps track of the current frame rate and after a certain amount of time, 2 minutes for example, starts sliding and using the values to measure the FPS.

If you guys find this useful, let me know and I will submit my code for review. My only issue is how to represent it in the GUI, which I added another textbox for, which I am not convinced I like, but simply adding it to the current FPS reading might make that display look too cluttered.

SMR
please post a patch in the megui patches tracker on sourceforge. it will be reviewed and implemented if it makes sense.

[Sharktooth]

Hi, i was going to convert a dvd to h264+aac .mkv, then when i was going to convert the audio with nero aac (multichannel 128 kbps) i get an error. I tried reinstalling and trying winamp aac and faac, but it gives the same result.
And in the log it says like this :

"An error occured"
"Stacktrace
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath
at System.IO.FileStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count
at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count
at MeGUI.AviSynthAudioEncoder.encode()
Inner exception: null
Output from encoder via stderr
Output from encoder via stdout: ERROR: Could not initialize SBR"

Thanks

P.s. Audio is from dvd, 3.1 ac3.
from the wiki:
Other optional programs that MeGUI can use:
Nero AAC Encoder: This is the free Nero Digital AAC encoder which can be downloaded from this Nero webpage (http://www.nero.com/eng/downloads-nerodigital-nero-aac-codec.php). Extract neroAacEnc.exe and set the right path to it in Settings -> Program Paths -> Audio -> neroAacEnc
a similar procedure is needed for winamp encoder.

[Doom9]

@SeeManRun: I guess it's a matter of definition when you say accurate. There are encoders that show the effective FPS measured over the last X frames or X seconds, and then there's megui which calculates FPS not on those terms but over the entire movie. In the end, if you want to compare FPS measurements, the latter is much more useful because localized FPS measurements can very greatly with the complexity of the source.

Oh, and C# has a Queue with Enqueue and Dequeue methods.

[SeeManRun]

@SeeManRun: I guess it's a matter of definition when you say accurate. There are encoders that show the effective FPS measured over the last X frames or X seconds, and then there's megui which calculates FPS not on those terms but over the entire movie. In the end, if you want to compare FPS measurements, the latter is much more useful because localized FPS measurements can very greatly with the complexity of the source.

I suppose more accurate is not the right way to put it, but maybe more useful. I use a quad core CPU for my encoding, and when I need to use the computer for something else, its nice to know how much I am affecting the encode, which is why I created the patch. I'll check out the queue (I was a little surprised that there was none on my first check) and submit that patch as Sharktooth says.

[Ramir Gonzales]

When MeGUI is started x264 for the encoding, x264.exe simply crashes.
x264 core:65 r1016M dbc5ef0

Way to go !!!

[SeeManRun]

When MeGUI is started x264 for the encoding, x264.exe simply crashes.
x264 core:65 r1016M dbc5ef0

Way to go !!!

So very helpful. Check the log file at least.

[Bitlord]

from the wiki:

a similar procedure is needed for winamp encoder.

I already set the paths. And if i haven't, wouldn't it say that the file is missing? And it almost seems that only me has this problem.
:confused:

[Kurtnoise]

are you sure that your audio file from DVD is 3.1 ???

maybe that's why the encoder fails...

[SeeManRun]

please post a patch in the megui patches tracker on sourceforge. it will be reviewed and implemented if it makes sense.

Added the patch. I also looked at the queue class in C# and it doesn't support removing from both ends of the queue, which is why I brought in the deque class. Perhaps a little heavy duty for my use, but the compiler should strip out anything not used anyway :)