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

[RobertoHN]

I'm trying to use MeGUI 2050 to create a M2TS file. I've been using MeGUI for a few years to create .MP4 files, but then my PS3 died and I got a Panasonic Blu-Ray player that won't play MP4 but will play M2TS files. How should this work? I set up the inputs and click "AutoEncode", then select Output Options: Container: M2TS and "Queue". The queue now contains four jobs: encode audio to .m4a, encode video to .264, mux video to mp4, and mux mp4 to m2ts. The first three steps complete OK. The last step fails with the error
SmartLabs tsMuxeR. Standard error stream: No tracks selected.

Can anyone tell me what I'm doing wrong? The full log text file is attached as Create-M2TS-Error.zip in case that's helpful.

EDIT: hmm, maybe it works better if I use AC3 audio instead of AAC...

What I suggest in your case, is not to use MeGUI to mux your final video (DON'T USE AUTOENCODE), instead of that, in MeGUI, try to reencode your video with RAWAVC file format and encode your audio according to the capabilities of your BR Player... Once you have your video file and audio file you can use tsMuxer (http://forum.doom9.org/showthread.php?t=134104) to mux your files into a m2ts container so you can play your video from a USB memory or you can use the option Bluray Disk so you can burn the video in a DVD 5 or 9 depending the size of the file.

[blah123]

I've got problems with 2 TSes (one 1920x1080 interlaced MPEG-4/AVC with mp2 | the second also AVC interlaced, but with AC3 and 720x576) and I try to "import" them to MEgui's AviSynth Script Creator and drag&drop them on "Video Input", i choose DirectShowSource and then I receive win message box with "MeGUI has stopped working" and I need to click "close down".
I have got ffdshow and haali media splitter installed.
(The same problem is with StaxRip.)

Then don't use DirectShowSource. How many times did we already preach that DSS shall be only the last hope when all other native input plugins fail?

The reason of your DirectShow system failing is hard to discover without analyzing your Windows installation at home, next to you. You probably installed too many concurring filters or "Codec Packs" which mess it up, who knows ...

Multiplex your Transport Streams into MKV (e.g. using gdsmux from the Haali Media Splitter installation), then feed the MKV as source for FFmpegSource.

Recently, finally showed another, addintional error:

link (http://imgur.com/EWoYk)

[Zathor]

Recently, finally showed another, addintional error:

link (http://imgur.com/EWoYk)
http://msdn.microsoft.com/library/d509d9f9.aspx

[flebber]

Would it be possible to have the oggenc encoder updated to the latest aotuv released 2011-05-04 http://www.rarewares.org/ogg-oggenc.php#oggenc-aotuv .

Megui currently using

C:\Rip\Megui\tools\oggenc2>oggenc2 --help
OggEnc v2.87 (libvorbis 1.3.2)

[swainjena]

I have been using MeGUI for encoding my cartoons DVDs. I use the x264:Unrestricted 2pass Anime_Toons Insane preset, but every time I encode a video, the video has a frame rate of around 17.982fps How can i control it to make 23.96 fps. Can anyone help ?

[Zathor]

I have been using MeGUI for encoding my cartoons DVDs. I use the x264:Unrestricted 2pass Anime_Toons Insane preset, but every time I encode a video, the video has a frame rate of around 17.982fps How can i control it to make 23.96 fps. Can anyone help ?

Please post your log file.

[LigH]

Funny that it turns out to have exactly 3/4 of the expected framerate. If it was 4/5, I would have guessed a double-IVTC. But so?!

[slipknot!]

hey guys, I just downloaded megui. Want to make a rip from a VOD recorded with "total recorder". But cannot find those cool presets by sharktooth for x264, where are they?

[djmasturbeat]

will you ever implement IFO processing,


I would also love to see this
including the features that were available in Stream Processing in DVD Decrypter. Very handy for segmenting audio by episode or even smaller sizes, for demuixng subs in a VOB shell to ocr with subrip, and a million other awesome things.
It would be great if this could be added into MeGUI and maybe even expanded upon to add new features.
but seeing where that all got LUK :( I won't hold my breath.

[LigH]

@ slipknot!:

Those presets had been made for an x264 version which is quite outdated now, and MeGUI is not compatible to anymore. "Target Playback Device" is the new philosophy which deprecated the x264 encoder presets.

The defaults of x264 are carefully chosen and well tested. Use the basic settings (Encoding Mode, Preset, Tuning, Target Playback Device). You will probably only need more if you already know the Advanced Settings in detail.

[Weirdo]

I'm opening a file on a network drive with the file indexer, and MeGUI reports: "MeGUI cannot write on the disc... please, select another output path to save your project". However, it won't allow me to change the output path. Does this mean that it also cannot read from a network drive?

[kws53]

Just downloaded 2106 and am having following problem with avs creation using FFMSindex. After frame serving an MKV fiile, MeGUI locks up with following error when attempting to display the video for AVS creation..."AviSynth script error: DirectShowSource:Timout waiting for graph to start."

Kurt

[Zathor]

Just downloaded 2106 and am having following problem with avs creation using FFMSindex. After frame serving an MKV fiile, MeGUI locks up with following error when attempting to display the video for AVS creation..."AviSynth script error: DirectShowSource:Timout waiting for graph to start."

Please post the AVS content. It seems you are not using FFVideoSource() and instead you are using DirectShowSource().

I'm opening a file on a network drive with the file indexer, and MeGUI reports: "MeGUI cannot write on the disc... please, select another output path to save your project". However, it won't allow me to change the output path. Does this mean that it also cannot read from a network drive?
If you are using the FFMSIndexer the output path cannot be changed.

[luke83]

@ slipknot!:

Those presets had been made for an x264 version which is quite outdated now, and MeGUI is not compatible to anymore. "Target Playback Device" is the new philosophy which deprecated the x264 encoder presets.

The defaults of x264 are carefully chosen and well tested. Use the basic settings (Encoding Mode, Preset, Tuning, Target Playback Device). You will probably only need more if you already know the Advanced Settings in detail.
I usually use the Preset for Anime found on Doom and everything works... at the moment XD

Those are the presets I use -> http://forum.doom9.org/showthread.php?t=139765

[kws53]

[QUOTE=Zathor;1556056]Please post the AVS content. It seems you are not using FFVideoSource() and instead you are using DirectShowSource().

Not sure what you mean here. The AVS file is not being created. I used 2050 without any problems (Tools>File Indexer>Selected MKV>Queued>Executed Queue) and the AVS file creation window would open automatically for cropping, etc. Now it doesn't and MEGUI throws the error I listed.

An example AVS file that was created historically with 2050 is shown below.

LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("U:\DEJA_VU\deja.mkv", threads=1).AssumeFPS(24000,1001)

crop( 0, 140, 0, -140)
LanczosResize(1280,532) # Lanczos (Sharp)

LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\Convolution3DYV12.dll")
Convolution3D("moviehq")

Kurt

[Zathor]

Not sure what you mean here. The AVS file is not being created. I used 2050 without any problems (Tools>File Indexer>Selected MKV>Queued>Executed Queue) and the AVS file creation window would open automatically for cropping, etc. Now it doesn't and MEGUI throws the error I listed.
Sorry, I did not get you in the first try.
In that case please post your complete log file. When using the file indexer there should be no "DirectShowSource". Maybe it is also required to upload (a part of) the source file, but that depends on your log.

[kws53]

Sorry, I did not get you in the first try.
In that case please post your complete log file. When using the file indexer there should be no "DirectShowSource". Maybe it is also required to upload (a part of) the source file, but that depends on your log.

Where would I get the log file? Perhaps you don't understand my process [which has not changed at all!] betwen MEGUI releases.

Step 1 - create MKV from VC1 with eac3to [never been problem for 2 years]
Step 2 - open MEGUI and go to <Tools> <File Indexer>
Step 3 - Input File = MKV file created in Step 1, wait for window to populate, then hit <Queue> [Note that "On Completion Load Files" and "and Close" are both checked].
Step 4 - Go to Queue and hit <Start>
Step 5 - this is where the difference is between MEGUI releases. RELEASE 2050 - after indexing, the AVS script creator window would open and the video file was opened for cropping. RELEASE 2106 - the indexing would end with the avisynth error described in my first posting.

When I hit the <OK> button on the error message the AVS window opens [mostly grayed out] and when reading the <Script> tab [contents all grayed out], the first two lines of "grayed out" script are:

LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("", threads=1)

Note that the ffindex file is not loaded and the FPS switch is missing. I believe that a switch on MEGUI's implementation of FFMSIndex in 2106 is missing or different than the implementation in 2050. I also note that FFMSIndex was upgraded as well in this new release. Perhaps that's the culprit...

Kurt

[Zathor]

The logs can be found in the MeGUI\logs folder. Nevertheless likely I have found & fixed the problem. Please update to 2111 and verify if the problem is solved. You have to switch to the development update server in the settings (Options\Settings\Extra Config\Auto Update).

[kws53]

The logs can be found in the MeGUI\logs folder. Nevertheless likely I have found & fixed the problem. Please update to 2111 and verify if the problem is solved. You have to switch to the development update server in the settings (Options\Settings\Extra Config\Auto Update).

Problem is solved. However I note that after indexing [all indexers], the video window opens at frame 0 for autocropping, whereas before it opened midway through the video. I prefer the midway location as it tends to have more contrast for manual adjustments.

Thanks for the fix.

Kurt

[Zathor]

Yes, that was an intended change because of input script which are not seekable. But... I merged this setting with the "Improved AVS Opening" in 2112.

[zelenin]

What is the reason for remove values in File Size Selector?

[Zathor]

The list was too long and (I assume) most people only need some of them and not all. As stated in the changelog you can add them back without problem.

[zelenin]

As stated in the changelog you can add them back without problem.
Ok. I search this option three times :-) Thank you

[lildimsum7]

i just updated, and now directshowsource isn't working for me. it crashes megui when i choose my avs script decoded by ffdshow. does anyone else have this problem?

[LigH]

There are so many specific issues with the whole DirectShow system (therefore it is usually discouraged as Very last help if everything else already failed"), and such an unspecific question from you (not even mentioning the exact details of the media file you are trying to load, and the complete script you are using).

I could well imagine that you once created an AVS file which does not use the "seek" parameter for DirectShowSource, but MeGUI now seeks to the middle when loading the preview. There are media types which fail seeking unless DirectShowSource got prepared. Try to create the script again from the AVS Script Creator dialog; maybe avoiding DirectShowSource this time, if possible.

[lildimsum7]

There are so many specific issues with the whole DirectShow system (therefore it is usually discouraged as Very last help if everything else already failed"), and such an unspecific question from you (not even mentioning the exact details of the media file you are trying to load, and the complete script you are using).

I could well imagine that you once created an AVS file which does not use the "seek" parameter for DirectShowSource, but MeGUI now seeks to the middle when loading the preview. There are media types which fail seeking unless DirectShowSource got prepared. Try to create the script again from the AVS Script Creator dialog; maybe avoiding DirectShowSource this time, if possible.

I don't know what happened earlier, but I reinstalled everything and my issue is now fixed. The problem was that I couldn't even open a video file to create my AVS Script. Each time I tried, MeGUI crashed.

[Weirdo]

There are some windows that do not display correctly on a "Medium - 125%" Windows DPI setting - the HD Streams Extractor for example.

[JarrettH]

When does megui makes its determination for the "fps based" GOP calculation? I noticed in the xml file for one of my pending jobs that the values chosen for a 23.97 fps movie were still 250 and 25 as opposed to 240 and 24.

:thanks:

[Zathor]

I could well imagine that you once created an AVS file which does not use the "seek" parameter for DirectShowSource, but MeGUI now seeks to the middle when loading the preview.
MeGUI has more or less since ever seeked to the middle of the video. Only between 2076 and 2112 the start position had been the first frame. you can revert that when you disable the option "improved avs opening".

When does megui makes its determination for the "fps based" GOP calculation? Directly before the encoding.

[jasonwc]

MeGUI currently ignores "--profile high" which makes it impossible to force MeGUI to encode at 8 bit color depth when using the 10 bit enabled x264 binary (unless there's some more specific option to force 8 bit color depth; i wasn't able to find such an option here (http://mewiki.project357.com/wiki/X264_Settings#). Is there any way to get around this setting up two instances of MeGUI - one with the regular binary and one with the 10 bit enabled binary? Perhaps MeGUI can add Hi10 to the drop down box for profiles to resolve this issue.

You can force the use of the High4:2:2 and High4:4:4 profiles with the --output-csp flag, but i420 can be used in any of the profiles.

[RazvanuZu]

How can I get 64 bit video decoders working with MeGUI? Is there any way to do this?

I have installed AviSynth64 but no luck. Is this because MeGUI is a 32 bit application?

[R=G]

What gets the best possible output for AVIs in Megui encoding? I usually use Megui for MKVs..I tried to make MP4s but that always comes out with audio issues and I never really see a concise guide on how to edit the audio into making it sync correctly.

[RobertoHN]

Hello, yesterday I tried to convert an HD m2ts file (20GB in size & 24Mbps of bitrate) to avi using MeGUI 2153 (svn)... after making the script with the AVS Script Creator option I used the Bitrate Calculator tool for having an idea on how big the avi file would be with a video bitrare of 5 Mbps and found out that 5 Mbps (5000 Kbps) the file would be around 4.19 GB what is acceptable to me considering it is a HD movie... My surprise is that after waiting almost 3 hours the final avi file is only 2.08 GB (the half size calculated by bitrate calculator) so I used MediaInfo and it says the avi file only has a video bitrate of 2543 Kbps and it makes sense, half in size means half in bitrate... so, my question is: Why if I've set in configuration a bitrate of 5000 Kbps the final video only has 2500?

I have installed avisynth 2.5, k-lite codec mega pack and MeGUI 2153 (svn).
This is the script:

DirectShowSource("C:\Users\User\Videos\BD-RIP\DEMUX\MyFile.mkv", fps=23.976, audio=false, convertfps=true).AssumeFPS(24000,1001)
#deinterlace
#crop
Lanczos4Resize(1280,720) # Lanczos4 (Sharp)
LoadPlugin("C:\Users\User\Videos\Blu-ray to AVI-MKV\MEGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise

These are the Encoder Settings - XVid Configuration:
http://img515.imageshack.us/img515/6458/encodersettings.png (http://img259.imageshack.us/img259/6458/encodersettings.png)

Thanks in advance.

[Adub]

It's a bit of a shot in the dark, but it's possible that the movie you are trying to encode got saturated in bitrate. This often happens with particularly dark movies (a la "Underworld" for example).

If you look into the logs that MeGUI stores for your encode, Xvid should have reported the achieved bitrate along with the commandline used to run the encode. If the achieved bitrate is lower than the requested bitrate, then it's very likely you reached saturation.

On the other hand, is there a reason why you are using Xvid instead of the more modern X264?

[RobertoHN]

It's a bit of a shot in the dark, but it's possible that the movie you are trying to encode got saturated in bitrate. This often happens with particularly dark movies (a la "Underworld" for example).

If you look into the logs that MeGUI stores for your encode, Xvid should have reported the achieved bitrate along with the commandline used to run the encode. If the achieved bitrate is lower than the requested bitrate, then it's very likely you reached saturation.

On the other hand, is there a reason why you are using Xvid instead of the more modern X264?


Thanks for your reply... I don't think this is the case, I don't have any technical prove to confirm this but it doesn't seem to be the case because this issue is happening with every video I try to encode (TV recording, animated pictures like Ice Age or Toy Story which are very clear and bright, etc)... Is it possible that the issue is being caused by anything else?

I'm not using x264 because I re-encode this movies to play them on my Apple TV and a Iomega multimedia hard drive and they are not x264 friendly... Apple TV plays x264 but when the bitrate is too high sometimes it's too much trouble to watch the movie and the Iomega multimedia hard drive does not support x264 at all.

Regards.

[tebasuna51]

... I don't think this is the case, I don't have any technical prove to confirm this but it doesn't seem to be the case because this issue is happening with every video I try to encode...

If you have the Min-Quantizers to 2, like is recommended, try with 1 and see if you obtain more bitrate:

[hello_hello]

Why if I've set in configuration a bitrate of 5000 Kbps the final video only has 2500?

Maybe try the same encode using one pass instead of 2, same Xvid settings except with Xvid in QC mode while using a quantizer of 2. The way I understand it that's maximum quality for Xvid, so a 2 pass encode using a higher bitrate will probably end up undersized. Maybe if you reduce the number of B frames or reduce the Min-Quantizers to 1 (as suggested) you'll achieve a larger file size. Someone else may be able to tell you if either will effect the perceived quality much.

[LigH]

In contrast to "wasting" ;) bitrate by allowing quantizer 1, which has the disadvantage that the distance between quantizer 1 and 2 is huge, you may also allow a finer quantization via custom matrices (http://www.ligh.de/software/CustQM.zip) (e.g. one of the HVS, Sharktooth's EQM, or even Selur's HDR or Didée's SixOfNine-HVS); but that may have the disadvantage of reduced consumer player compatibility.

[jauznevimco]

...question is: Why if I've set in configuration a bitrate of 5000 Kbps the final video only has 2500...

After update MeGUI from version 2008 to 2153 im have the same problem. MeGUI don't keep the bitrate and produce much smaler video file. I seting the file size to 2.1 gb (with sound file ~400MB), but MeGUI create file an approximately 1.3 GB instead of required 1.7GB.

[LigH]

With the used codec options and all the details about the video you described in your post above, this is easily possible... oh, you didn't mention any, at all.

If you used Xvid, I could wildly guess about "saturation", but if you didn't, I would have wasted efforts.

[kws53]

The logs can be found in the MeGUI\logs folder. Nevertheless likely I have found & fixed the problem. Please update to 2111 and verify if the problem is solved. You have to switch to the development update server in the settings (Options\Settings\Extra Config\Auto Update).

Zathor - have the same identical problem as I had in February, now for last month. Now using 2192 - same error "DirectShowSource: Timeout waiting for graph to start". Perhaps you can implement the same fix.

Cheers,
Kurt

[Zathor]

Please upload the log. I need to know what you are trying to do.

[kws53]

Please upload the log. I need to know what you are trying to do.

Here is log - error message comes when trying to load the video window after completion of the indexing.

[Information] Log for job63 (idx, twister1.mkv -> twister1.mkv.ffindex)
--[Information] [10/31/2012 7:15:52 PM] Started handling job
--[Information] [10/31/2012 7:15:52 PM] Preprocessing
--[Information] [10/31/2012 7:15:52 PM] Job commandline: "C:\Program Files\MeGUI\tools\ffms\ffmsindex.exe" -f "L:\TWISTER_NA\twister1.mkv" "B:\MEGUI ENCODES\twister1.mkv.ffindex"
--[Information] [10/31/2012 7:15:52 PM] Indexing started
--[Information] [10/31/2012 7:32:58 PM] Standard output stream
--[Information] [10/31/2012 7:32:58 PM] Standard error stream
--[Information] [10/31/2012 7:32:58 PM] MediaInfo
---[Information] File: B:\MEGUI ENCODES\twister1.mkv.ffindex
-[Information] Format:
-[Information] FormatString:
-[Information] FileSize: 1194382
-[Information] PlayTime:
---[Information] General
--[Information] [10/31/2012 7:32:58 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [10/31/2012 8:52:36 PM] Job completed

You fixed the exact same problem in February for me. [see post and string back in Feb]

Kurt

[Zathor]

The change done in Frebruary is still active and I cannot reproduce the problem this time. Therefore I cannot fix it. Please post the complete log file (with MediaInfo + Versions). Also please try older builds and find out when the problem started. E.g. try 2112 or 2153 (stable).

[plonk420]

does MeGUI use libav for AC3 encoding? (the ffmpeg option)

[LigH]

MeGUI supports Aften as AC3 encoder, via the BeHappy based AviSynth engine.

[ashneel83]

Hi guys

I'm trying to embed soft subs to a 1080p mkv file. First I extract audio and video separately using MKVExtractGUI. After extraction is complete, I get the video in H264 File format and audio in ADTS Audio file format. My subtitles are in SRT format.

Then I use MKV Muxer in MeGUI 2153 (svn) to mux the video, audio and subtitle together. Final result I get a MKV file with soft subs but the audio is missing. That's right no audio at all. I've retried the above procedure for like 5 times now but still no audio.

Can anyone help me out here please. Am I doing anything wrong?

[Zathor]

Please upload the log.

[ashneel83]

Please upload the log.


Please see attached log file. I've noticed in the log file it says "--[Warning] [11/3/2012 8:32:56 PM] No audio track found: D:\Extract\Brave_track2_eng.aac". But if I play this file in Windows Media Player or VLC, I can hear whole audio stream fine.

[Zathor]

Yes, your AAC file is not detected by mediainfo. Can you please try to use the current MeGUI development build or a current MeGUI build and post the output? Or you can upload the AAC file.