View Full Version : MeGUI - x264/XviD/lavc/Snow encoder with MP4/MKV/AVI output & audio
Xor
14th August 2015, 01:44
The used call with all command line parameters is missing in your log.
Furthermore, there is apparently no AC3 audio stream, only raw PCM.
i use tools>hd streams extractor
how to grab FULL command line?
tebasuna51
14th August 2015, 02:29
...how to grab FULL command line?
Is not necesary.
Seems there are some corrupt data in your ISO file or maybe the playlist have more than one m2ts with different tracks.
If the mpls have more than one m2ts try open each one (Select file as input) to see if there are different track 3 and 4.
BTW to extract PCM tracks use always wav or w64 output, never use raw or pcm.
LigH
14th August 2015, 07:27
Alright, tebasuna51 will know MeGUI better. :) — But if you are still interested, I would guess it may be stored in the log file.
tebasuna51
14th August 2015, 10:57
Alright, tebasuna51 will know MeGUI better. :) — But if you are still interested, I would guess it may be stored in the log file.
Not the full MeGUI, but yes the HD Streams Extractor like a eac3to GUI.:p
It generate a command line like this (replace the upper case with the selected/generated value):
eac3to BD_FOLDER_INPUT PLAYLIST_NUMBER) TRACK_NUMBER: OUTPUT.EXT PARAMETERS
With:
EXT can be selected in 'Extract As'
PARAMETERS can be added manually in '+Options'
When eac3to analyze a playlist show the tracks of first m2ts, if there are only one the message:
[a04] The ts pcm reader received a PCM block in an unexpected format. <WARNING>
only can be corrupt data.
But if there are a second m2ts with a track 4 PCM 5.1 the ts pcm reader can detect the change (pcm blocks in ts container have a little header).
Is a know problem when there are different tracks in m2ts's in the same playlist. The only solution is extract the audio track from each m2ts and convert them to the common desired format.
Glarioo
27th August 2015, 18:42
Hey guys. I'm new here.
Is it normal that the Reframes are displayed differently by media info than set by MeGui (one-click mode)? Or did i something wrong. I've tried "Restore Defaults" with no result.
LigH
27th August 2015, 19:19
Which video format?
And how old is your MediaInfo?
I know there was a mistake interpreting the references of AVC video in case of B-frame pyramid enabled (one reference array space had to be reserved for the pyramid details), but MediaInfo should have corrected that a while ago, I believe?!
Zathor
27th August 2015, 19:31
Hey guys. I'm new here.
Is it normal that the Reframes are displayed differently by media info than set by MeGuide (one-click mode)? Or did i something wrong. I've tried "Restore Defaults" with no result.
Please post your log file of the encoding.
Glarioo
27th August 2015, 20:49
Thanks for the quick response!
I've encoded the same movie today again, same "problem".
Here's the log file.
Video format was AVC, i think. (MKV container).
I use the latest version of MediaInfo (0.7.76).
sneaker_ger
28th August 2015, 04:15
I know there was a mistake interpreting the references of AVC video in case of B-frame pyramid enabled (one reference array space had to be reserved for the pyramid details), but MediaInfo should have corrected that a while ago, I believe?!
I assume you refer to this:
http://forum.doom9.org/showthread.php?p=1470506#post1470506
I don't think MediaInfo has changed anything so this is normal. (His log isn't approved yet but I guess that's indeed where the difference comes from.)
Glarioo
30th August 2015, 15:07
When i disable B-Pyramid in the x264 configuration dialog (Frame-Type), the problem is solved (post #3105).
However, i do not know if this is allowed.
LigH
30th August 2015, 16:09
Better trust in x264 doing a great job in the given limits, and do not panic over MediaInfo not explaining this header analysis verbosely. Most probably x264 won't exhaust the reference frame limit in every GOP, anyway, will often be satisfied with less references per frame than allowed.
Glarioo
31st August 2015, 17:39
Did some test with B-Pyramid enabled (normal) and disabled. I see no difference. The quality of the movie, in both encodes, is very good.
Glarioo
10th September 2015, 19:40
My installed version of Avisynth is 2.5.8. In options - settings - main configuration is "Always use the included version of Avisynth" unchecked. Should i checked it or just leave it? I always use one click mode of MeGui.
LigH
10th September 2015, 19:53
This is not at all related to the B-frame pyramid.
And in general, you may want to update to AviSynth v2.60 final, eventually ...
Whether you always want to use the AviSynth+ version included in MeGUI, I don't know; if you are going to use very complex script functions like QTGMC, you may not want to. Not until AviSynth+ got fixed. It may leak memory and drop speed. But there seems to be serious effort now.
Glarioo
11th September 2015, 13:53
Thanks LigH. I just wanted to know if the included, newer version of AviSynth is "better" than my installed version. I gonna use my installed version until AviSynth+ got fixed, like you said. I don't use complex script functions, i have no experience with those things. I just use One-Click, sometimes automated 2-pass, but most of the time Const. Quality (CRF-18). Preset medium or slow it depends...
BTW, this question had nothing to do with B-Pyramid. My apologize 'cause i confused you a little.
Xor
14th September 2015, 07:42
Hi,
i want try to create a HEVC 4k (4096 PX) with Megui and source a normal untouched bluray x264.
On Megui select X265 but connot permit to upscaling over 1920.
how to proceed using Megui to upscaling?
Or what do you recommend different encoder? which ?
Thank's
AMED
14th September 2015, 08:22
Hi,
i want try to create a HEVC 4k (4096 PX) with Megui and source a normal untouched bluray x264.
On Megui select X265 but connot permit to upscaling over 1920.
how to proceed using Megui to upscaling?
Or what do you recommend different encoder? which ?
Thank'sEdit the Avisynth profile you are using, Extra setup tab and tick Upsizing allowed.
hello_hello
14th September 2015, 08:32
Hi,
i want try to create a HEVC 4k (4096 PX) with Megui and source a normal untouched bluray x264.
On Megui select X265 but connot permit to upscaling over 1920.
how to proceed using Megui to upscaling?
Or what do you recommend different encoder? which ?
Thank's
I assume you've not enabled "upsizing" in the script creator's Avisynth profile configuration? If that's the problem, once it's enabled you should be able to use the script creator's resizing to upscale to 4k. I still think it'd be better if "upsizing" was enabled by default. I rarely use the OneClick encoder so I don't know how upscaling applies there.
Isn't 4K for the masses 3840x2160 rather than 4096 wide? I just thought I'd mention it.....
https://en.wikipedia.org/wiki/Blu-ray#Ultra_HD_Blu-ray
https://en.wikipedia.org/wiki/Ultra-high-definition_television#Resolution
stax76
14th September 2015, 15:27
This is not at all related to the B-frame pyramid.
And in general, you may want to update to AviSynth v2.60 final, eventually ...
Whether you always want to use the AviSynth+ version included in MeGUI, I don't know; if you are going to use very complex script functions like QTGMC, you may not want to. Not until AviSynth+ got fixed. It may leak memory and drop speed. But there seems to be serious effort now.
Yes, it looks QTGMC works with ref 1773, I'll downgrade AviSynth+ in my next release, the discussion is here:
http://forum.doom9.org/showthread.php?p=1736551#post1736551
hello_hello
14th September 2015, 22:41
My installed version of Avisynth is 2.5.8. In options - settings - main configuration is "Always use the included version of Avisynth" unchecked. Should i checked it or just leave it? I always use one click mode of MeGuI.
Zathor switched the "included" Avisynth to Avisynth 2.6 very recently. At least on the development update server. The "included" Avisynth is no longer Avisynth+ (due to a few recent problems with that version).
It might be an idea to uninstall your old Avisynth 2.5.8 and install Avisynth 2.6, given it's the current version.
It shouldn't matter whether MeGUI uses the "included" Avisynth or the "installed" Avisynth.
Glarioo
27th September 2015, 17:47
Uninstalled Avisynth 2.5.8 and installed Avisynth 2.6.0.6 (downloaded from Videohelp). Encoded some Harry Potter movies (1, 2, 3 and 4). A quick look at the MKV's tells me that everything looks fine.
Zebbik
18th November 2015, 13:26
Hi,
I've got this warning when I run MeGUI application. I am not an expert on that and I don't exactly know what may be wrong and cause it. I have copied a part of a log.
[Warning] Versions
-[Information] [18/11/2015 11:30:52] MeGUI: 2525
-[Information] [18/11/2015 11:30:52] Operating System: Windows 7 Enterprise Edition x64 SP1 (6.1.65536.7601)
-[Information] [18/11/2015 11:30:52] .Net Framework: 2.0.50727.5420
-[Information] [18/11/2015 11:30:52] .Net Framework: 4.0.0.0
-[Information] [18/11/2015 11:30:54] AviSynth+ portable: 2.6.0.5 (02-01-2014)
-[Information] [18/11/2015 11:30:57] AvisynthWrapper: (02-01-2009)
-[Warning] [18/11/2015 11:30:57] Haali Matroska Splitter not installed properly.
-[Warning] [18/11/2015 11:30:57] Therefore DSS2() and certain functions of FFVideoSource() and the HD Streams Extractor may also not work.
-[Warning] [18/11/2015 11:30:58] Please download and install it from http://haali.su/mkv/
-[Information] [18/11/2015 11:30:58] Haali DSS2: not installed
-[Information] [18/11/2015 11:30:58] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
-[Information] [18/11/2015 11:30:58] LinqBridge: 1.0.0.0 (28-05-2009)
-[Information] [18/11/2015 11:30:58] MediaInfo: 0.7.72.0 (07-01-2015)
-[Information] [18/11/2015 11:30:58] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
-[Information] [18/11/2015 11:30:58] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
-[Information] [18/11/2015 11:30:58] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
-[Information] [18/11/2015 11:30:58] 7z: 9.20 (18-11-2010)
MeGUI is on a USB HDD. I hope that's not why the problem appears!
LigH
18th November 2015, 15:21
You have MeGUI version 2525. The most current development version is 2620. The use of Haali Media Splitter is quite deprecated now for many features. Please update after switching to the development update server, then check if this warning still appears. Anyway, you may possibly not need it except for a few specific uses.
Zebbik
19th November 2015, 09:51
You have MeGUI version 2525. The most current development version is 2620. The use of Haali Media Splitter is quite deprecated now for many features. Please update after switching to the development update server, then check if this warning still appears. Anyway, you may possibly not need it except for a few specific uses.
Hi and thanks for the answer. I use either x264 or XviD (unfortunately I still need to deal with XviD) in MKV or AVI container. If that's possible, could explain when I would need to worry about the Haali Splitter? What is it for?
As to the version, the MeGUI2525 seems to be the most up-to-date at SourceForge (the link (http://sourceforge.net/projects/megui/files/megui-stable/)).
thanks
LigH
19th November 2015, 10:11
Haali Media Splitter used to be helpful for reading different video formats, supporting FFMS2 while it depended on its help, and demultiplexing streams from HD formats to be processed separately. Also it was a common DirectShow splitter filter for the Matroska container (*.mkv).
Today it is rather obsolete since FFMS2 uses no special Matroska splitter anymore, but libavformats instead, just like L-SMASH Source always did (and was much more reliable this way). Regarding DirectShow filters, "LAV Filters" substituted both ffdshow and Haali Media Splitter in most cases.
_
You may have downloaded the latest "stable" MeGUI release; but the "stable" versions last long and miss a lot of recent updates from the "development" branch. Development versions of MeGUI are usually well tested, and new bugs won't last long, so it is usually recommendable to switch to the development update server in the MeGUI options.
nekrovski
19th November 2015, 14:59
Can anyone tell me why MeGUI keeps crashing?
It's been a while since I've done some encodings. I'm on windows 10 now. Opening MeGUI, going to tools -> avs script creator -> video input
I select the video, the preview comes up totally blank and after closing the preview it crashes. Sometimes after selecting the video, MeGUI starts loading, 15 seconds pass by and I get some DirectShowSource timeout error.
Event viewer says this
Faulting application name: MeGUI.exe, version: 1.0.2525.0, time stamp: 0x54fc5b03
Faulting module name: DirectShowSource.dll_unloaded, version: 2.6.0.3, time stamp: 0x55332925
Exception code: 0xc00001a5
Fault offset: 0x00010600
Faulting process id: 0x13d0
Faulting application start time: 0x01d122d0f24746d6
Faulting application path: C:\Users\X\Desktop\MeGUI_2525_x86\MeGUI.exe
Faulting module path: DirectShowSource.dll
Report Id: c1372567-e047-4ce1-a20c-45663d17eec5
Faulting package full name:
Faulting package-relative application ID:
I have avisynth installed.
LigH
19th November 2015, 15:07
Why do you prefer DirectShowSource, despite all recommendations to use it only when native AviSynth plugins (like DGDec*, L-SMASH Source or FFMS2) fail?
Such a crash is probably caused by issues with an installed DirectShow filter or DirectShow as a whole (Windows 10 is going to deprecate it). Native AviSynth decoders don't depend on installed DirectShow filters. Furthermore, DirectShow filters are not always tuned for optimal quality, sometimes instead for performance with possible quality loss, down to skipped frames (which will ruin your conversion).
Native plugins will just have a little disadvantage that they usually need an index file being generated. But in general, their reliability is better today than ever before.
nekrovski
19th November 2015, 15:15
Why do you prefer DirectShowSource, despite all recommendations to use it only when native AviSynth plugins (like DGDec*, L-SMASH Source or FFMS2) fail?
Such a crash is probably caused by issues with an installed DirectShow filter or DirectShow as a whole (Windows 10 is going to deprecate it). Native AviSynth decoders don't depend on installed DirectShow filters. Furthermore, DirectShow filters are not always tuned for optimal quality, sometimes instead for performance with possible quality loss, down to skipped frames (which will ruin your conversion).
Native plugins will just have a little disadvantage that they usually need an index file being generated. But in general, their reliability is better today than ever before.
Thanks for your reply.
I use DirectShow because that's how I was taught several years back after following a tutorial.
Now, you recommend I should click File indexer?
LigH
19th November 2015, 15:34
Yes, that would be the recommended procedure in these days.
In case of doubt, show us a MediaInfo analysis of your source, and a description of the desired target (especially when a playback device may require some compatibility), then we can give more specific recommendations. Sometimes it may be useful to use the HD streams extractor if a source contains audio formats which need a special processing because the target format would not support them.
nekrovski
19th November 2015, 16:27
In case of doubt
There's no doubt since I don't really understand these things, but since file indexer seems to do the job DirectShow was supposed to, I think it's fine.
Thanks for your support!
Glarioo
6th December 2015, 08:29
I'm using MeGui 2624. Since the last update (saturday 5/12/2015) i get this error: LoadPlugin: unable to load "C:\Users\Gebruiker\Documents\Blu Ray\MeGUI_2525_x86\tools\lsmash\LSMASHSource.dll", Module not found. Install missing library?
These tools have been updated: FFmpeg, L-SMASH Works and mkvmerge. The movie that fails since the last update was working well a day earlier.
LigH
6th December 2015, 10:03
Thank you - already reported in the MeGUI bug reports (http://forum.doom9.org/showthread.php?p=1748780#post1748780) thread. I believe we have 3 current big threads related to MeGUI now.
Zathor
6th December 2015, 21:44
Yes, maybe it would be a good idea to close this thread here as the information in the thread start is outdated.
Glarioo
7th December 2015, 10:26
Yesterday evening i've installed the new update (LSMASHWorks r804) and MeGUI is working perfectly again.
LigH
7th December 2015, 10:35
Rather looks like the L-SMASH Source version was downgraded a bit (r82x => r804), until there is a reliable updated version again.
tebasuna51
7th December 2015, 12:50
Yes, maybe it would be a good idea to close this thread here as the information in the thread start is outdated.
Yes, I also think so.
Please use only:
MeGUI: General Questions and Troubleshooting Thread (http://forum.doom9.org/showthread.php?t=105920)
MeGUI: bug reports and feature requests (http://forum.doom9.org/showthread.php?t=151159)
Thread closed.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.