MeGUI: General Questions and Troubleshooting Thread

[wthreex]

why avisynth script creator only for "File Indexer"

when i use "One Click encoder" i can see it ...

and when i put code in avisynth Profile handly .. erorr :

http://i.imgur.com/IpC3DqA.png

[lolmaster]

Can we use MEGUI from command line?
What i need to do is encode several audio tracks using MEGUI.
Can it be done using CMD or BAT file?
Please put a link that shows how to do that.
Thanks

[LigH]

I believe MeGUI is a bit too complex, it would be very elaborate to manage the queue based conversion with command line parameters. For audio-only conversions you may use BeHappy as alternative, it is based on AviSynth as well, but it is also rather single file oriented. I guess LameXP may be more batch conversion friendly.

[tebasuna51]

Audio encoding using command line?

You can use ffmpeg or eac3to (both included in MeGUI build).

[hello_hello]

Feature Request:

Would it be possible to make the processing rate (fps encoding speed) displayed by MeGUI a bit more responsive to actual changes in encoding speed?

If, for example, I create a script where the first half has no filtering, while the second half has slow filtering that instantly halves encoding speed, MeGUI will display a fairly steady processing rate for the first half, but after the point where the slow filtering commences the processing rate it displays declines very, very slowly, often taking many minutes before it once again reflects the true processing rate. I'm not sure how it works.... I guess displaying some sort of average taken over a period of time..... but if that's the case, is there any chance of making it more responsive to changes in actual processing speed?

Thanks.

I guess technically this isn't the feature request thread. Sorry about that.

[hello_hello]

I only ask, because I thought I'd manage to cause every conceivable MeGUI error, but today's one was new. It happened when I added an indexing job to the queue at the same time an encoding job finished, which may just be co-incidence, but does anyone know what this error means in human-speak? Just out of curiosity....

http://s24.postimg.org/8rmb2jyph/Me_GUI_error.gif

Thanks.

[LigH]

A "semaphore" is usually a variable with a special purpose, e.g. to remember if a function can be executed now or has to be postponed because another task uses it already, or to remember the depth of a stack (adding an entry increases it, removing decreases, and when the count is back to 0, the stack should be empty, and the program knows e.g. that you can safely quit without losing data).

This error message will tell only a programmer what he would have to look for. A user will not know how to avoid it, because he won't know which semaphores the author programmed.

[hello_hello]

I think I get the gist of it. Thanks.

[ryszardzonk]

Guys I know You must have heard this question many times already nevertheless I would kindly ask of showing the way to run MeGUI under Linux. Is it possible? Last week I have spend trying to run it with wine 1.8 or mono 4.2.2.10 but with no luck. I looked at the native Linux apps like ogmrip and handbrake but they do not show same level of customisation possible. I grew accustomed to semi automatic way of encoding with MeGUI for my TV recordings where I hand picked specific preset for specific tv show and only needed to enter in avisynth script (trim) values to cut the unwanted parts out.
Please any hits at running MeGUI under Linux are welcomed :thanks:

[jones1913]

Please any hits at running MeGUI under Linux are welcomed
In my experience complex .NET applications wont run well in wine, which is obviously true for megui.
And simply trying to start this with mono wont work, the application needs source adjustments to run with mono.

Regarding porting:
Most application tools used by megui should be available in linux as native versions or can run with wine. Megui itself can probably tweaked to run with mono.
Biggest problem I see is the avisynth dependency.

If I remember correctly someone tried to port megui to QT toolkit some years ago. It seems he had no success (at least I see none).

[hello_hello]

I'm right there myself (MeGUI in Linux) as I start the journey towards being as free of Windows as possible.

I've installed XP in VirtualBox. I've still got to run Windows Update to check the dot net framework is current enough, but then I was going to try running MeGUI on XP in VirtualBox. Anyone know how much of a performance hit I should expect encoding that way? Is it worth it?

[LigH]

To finally drop Windows, it may currently be necessary to move to technologies which are indeed "cross-platform", like VapourSynth. Now that there is a way to run it with a portable Python, Selur's Hybrid will most probably develop towards a cooperation with VapourSynth, to become an even more powerful cross-platform alternative to MeGUI.

[MimiK75]

when I try to open a .dga file in AVS Script Creator get this error:

Direct Show Error
Unable to render the file. You probably don't have the correct filters installed

:thanks:

[LigH]

MeGUI does not support DGAVCDec anymore (obsolete since FFMS2 and L-SMASH Works are reliable). So it doesn't know anymore that it used to be loaded with DGAVCSource and tries DirectShowSource as last chance.

[MimiK75]

MeGUI does not support DGAVCDec anymore (obsolete since FFMS2 and L-SMASH Works are reliable). So it doesn't know anymore that it used to be loaded with DGAVCSource and tries DirectShowSource as last chance.


thank you so much .. I was coming out crazy trying to figure out what could have happened

(exscuse for my bad english)

[hello_hello]

To finally drop Windows, it may currently be necessary to move to technologies which are indeed "cross-platform", like VapourSynth. Now that there is a way to run it with a portable Python, Selur's Hybrid will most probably develop towards a cooperation with VapourSynth, to become an even more powerful cross-platform alternative to MeGUI.

I forgot about Hybrid. It'll definitely be worth another look.
Cheers.

[Acrasia]

Is there a reason why L-SMASH isn't an option when I'm indexing an m2ts or h264 file? And why isn't dgindex an option anymore?

[LouieChuckyMerry]

Is there a reason why L-SMASH isn't an option when I'm indexing an m2ts or h264 file? And why isn't dgindex an option anymore?

From the LSMASHSource AviSynth Wiki (http://avisynth.nl/index.php/LSMASHSource):

Recommended for MP4, MOV, ISO Base Media and its derived file formats.

:) .

[hello_hello]

From the LSMASHSource AviSynth Wiki (http://avisynth.nl/index.php/LSMASHSource)

Except....... ;)

LSMASHSource/LWLibavVideoSource (http://avisynth.nl/index.php/LSMASHSource/LWLibavVideoSource)

MeGUI's file indexer (MeGUI 2672) will definitely index m2ts files with L-Smash for me. H264 streams, not so much. I guess that functionality was never added.
You can work around it by creating a script to open a h264 file yourself. Something like:

LoadPlugin("C:\Program Files\MeGUI\tools\lsmash\LSMASHSource.dll")
LWLibavVideoSource("D:\video.h264")

The first time you open the script, L-Smash should create an index file. If you have Avisynth installed you could open it with any program capable of opening scripts. You can either use the script as the source video for MeGUI's script creator, or you can use the *.lwi index file as the source.

And why isn't dgindex an option anymore?

For what sort of file type? It probably will be if the m2ts/ts file contains mpeg2 video, although I don't work with m2ts files much, so I can't remember for certain.

[LouieChuckyMerry]

Except....... ;)

LSMASHSource/LWLibavVideoSource (http://avisynth.nl/index.php/LSMASHSource/LWLibavVideoSource)

:o

Improve Your Reading Comprehension (http://www.wikihow.com/Improve-Your-Reading-Comprehension)


MeGUI's file indexer (MeGUI 2672) will definitely index m2ts files with L-Smash for me. H264 streams, not so much.

Curiously, why wouldn't one simply mux the .h264 as an .mp4 or .mkv or a .ts then index it? Thanks.

[LigH]

Just to play naive: Does your abbreviated "with L-SMASH" mean exactly "with LSMASHVideoSource" (this source filter) or "with L-SMASH Works" (this AviSynth plugin = LSMASHSource.dll)?

Indeed, the File Indexer can use L-SMASH Works to use LwLibavVideoSource for indexing an MPEG-2 TransportStream container (M2TS). It won't use LSMASHVideoSource, because M2TS is not a derivative of ISO Base Media containers; and LSMASHVideoSource would not write an index file either, even if the container would be supported, instead it would rely on a keyframe index chunk in the container.

But a raw H.264 video file has no container. And there are hardly any source filters which can read it in raw format. One reason may be that raw H.264 video may lack some important attributes you can usually only keep in a surrounding container format (e.g. the framerate, IIRC). Furthermore, a container will also improve the indexing speed because scanning the bitstream byte-by-byte would take much effort, while a container may already include some elements to improve GOP-wise seeking.

[hello_hello]

Curiously, why wouldn't one simply mux the .h264 as an .mp4 or .mkv or a .ts then index it? Thanks.

I've no idea. I'm not sure I've ever indexed a raw h264 stream myself. Except for yesterday, to see if L-Smash would do it.

[szabi]

Hi

Since today morning update, whatever file trying to index megui turning crash.
APPCRASH
MeGUI.exe
1.0.2627.0
5681523a
MSVCR120.dll
Even FFMS is selected it does try using L-SMASH and doing crash.
Any suggestion?

bye

[LigH]

Do you also have a log of this event? It may be corrupt when MeGUI crashed; still, it shall be interesting to see if one can get more details out of it.

[szabi]

Hi

Sorry, I deleted everything and did clean install.

bye

[Glarioo]

Is it allowed to delete the "update_cache"?

[LeXXuz]

When I use DGIndexNV as file indexer, x264 shows a warning in MeGUIs logfile about the wrong framerate while encoding for Blu-ray:
[Warning] the selected device does not support 239760/10000 fps with a resolution of 1920x1080. Supported are 24000/1001, 24/1, 25/1, 30000/1001 and 30/1.

It seems DGIndex reports 239760/10000 as framerate and not 24000/1001. Is this just a typo or really an error?

[tebasuna51]

DGIndexNV report the fps stored in the source, then maybe your source have a inaccurate value.
Use Assumefps(24000,1001) in your avs script.

[LeXXuz]

I'm not so sure about that. Source file is Blu-ray video. The very same file indexed with L-SMASH or FFMSindex reports correct frame rate in MeGui. Tested this with multiple files now.
I guess DGI reports wrong frame rate. Or might be rounding fps value to just 6 digits. :confused:

[LigH]

Just open the dgi file with a text editor and look for yourself. I don't have one available right now...

[LouieChuckyMerry]

Is it allowed to delete the "update_cache"?

I regularly cull the "obsolete" and duplicate files, leaving a single file of each type, and I've never had a problem. I think (ha ha) that MeGUI automatically reverts to an older version if the updated version proves problematic, which is why I keep the newest backup. Someone more knowledgeable than I might offer insight...

[tebasuna51]

I'm not so sure about that. Source file is Blu-ray video. The very same file indexed with L-SMASH or FFMSindex reports correct frame rate in MeGui. Tested this with multiple files now.

From BD sources I always obtain fps, at end of DGI files, like:

FPS 24000 / 1001
FPS 24000 / 1000
FPS 30000 / 1001

Check your DGI files, like LigH say, to know if is a GDIndexNV problem or a MeGUI problem.

[LeXXuz]

Ah. It's at the very end of the file. Always wondering where this value is stored. :D

Well I guess it's my DGIndex then: :(

SIZ 1920 x 1088
FPS 239760 / 10000
CODED 150145
PLAYBACK 150145
0.00% FILM
ORDER 0


Btw adding AssumeFPS(24000/1001) to Avisynth script gives me a video with exact 23.000fps :confused:

[Groucho2004]

Ah. It's at the very end of the file. Always wondering where this value is stored. :D

Well I guess it's my DGIndex then: :(
No, these values are stored in your stream. DGIndexNV just doesn't normalize them.

Btw adding AssumeFPS(24000/1001) to Avisynth script gives me a video with exact 23.000fps :confused:Had you read the documentation (http://avisynth.nl/index.php/AssumeFPS) you would know that this is the expected result. Try "AssumeFPS(24000, 1001)", just for fun.

[LeXXuz]

Had you read the documentation (http://avisynth.nl/index.php/AssumeFPS) you would know that this is the expected result. Try "AssumeFPS(24000, 1001)", just for fun.

Oh my god!!! :eek: Please make a hole where I can jump into! :D Ofcourse it should be 24000,1001. Sorry for that typo. :o

[LigH]

AssumeFPS even supports string presets. :D

[Glarioo]

I regularly cull the "obsolete" and duplicate files, leaving a single file of each type, and I've never had a problem. I think (ha ha) that MeGUI automatically reverts to an older version if the updated version proves problematic, which is why I keep the newest backup. Someone more knowledgeable than I might offer insight...

Thanks. Gonna keep that update cache file, just for security.

[LigH]

I was told that t's updater mirror requires a lot less traffic than worried about; so maybe it is not so urgent anymore to disable rarely used packages?

[hello_hello]

Thanks. Gonna keep that update cache file, just for security.

If you have the "always backup files when needed" setting in MeGUI's options enabled, it won't delete the old files in the update cache or old log files. If the option is unchecked, MeGUI will delete the old files sooner or later.

[tebasuna51]

Like I say before my preferred AviSynth audio decoder at the moment is LWLibavAudioSource().
I make a test recoding to flac a TrueHD track from a dolby_atmos_truehd_sample.m2ts file.

Here are the relevant parts of the log.
First the resumed MediaInfo of source:

-[Warning] Log for job1 (audio, dolby_atmos_truehd_sample.m2ts -> dolby_atmos_truehd_sample.flac)
--[Information] [21/03/2016 10:43:51] MediaInfo
---[Information] [21/03/2016 10:43:51] File: D:\Test\AudioN\TrueHD\dolby_atmos_truehd_sample.m2ts
---[Information] General
----[Information] Format: BDAV
---[Information] Video
----[Information] StreamOrder: 0-0
---[Information] Audio
----[Information] StreamOrder: 0-1
----[Information] Format: Atmos / TrueHD / AC-3
----[Information] Channels: Object Based / 8 / 6
----[Information] ChannelPositionsString2: Object Based / 3/2/2.1 / 3/2/0.1
---[Information] Audio
----[Information] StreamOrder: 0-2
----[Information] Format: AC-3
----[Information] Channels: 6
---[Information] Audio
----[Information] StreamOrder: 0-3
----[Information] Format: AC-3
----[Information] Channels: 2
---[Information] Audio
----[Information] StreamOrder: 0-4
----[Information] Format: AC-3
----[Information] Channels: 6
---[Information] Audio
----[Information] StreamOrder: 0-5
----[Information] Format: AC-3
----[Information] Channels: 6
---[Information] Audio
----[Information] StreamOrder: 0-6
----[Information] Format: AC-3
----[Information] Channels: 6
---[Information] Audio
----[Information] StreamOrder: 0-7
----[Information] Format: AC-3
----[Information] Channels: 6

Like you can see there are a
0-1 TrueHD Atmos 7.1/AC3 5.1 'core'
0-3 AC3 2.0
0-2,0-4,0-5,0-6,0-7, 5 AC3 5.1
eac3to also detect 1 TrueHD+AC3, 1 AC3 2.0 and 5 AC3 5.1

Now the MeGUI log continue with:

...
--[Information] [21/03/2016 10:43:51] Trying to open the file with LWLibavAudioSource()
--[Information] [21/03/2016 10:43:53] Successfully opened the file with LWLibavAudioSource()
--[Warning] [21/03/2016 10:43:55] channel count mismatch! The input file is reporting 0 channels and the AviSynth script is reporting 2 channels
--[Information] [21/03/2016 10:43:55] Avisynth script
---[NoImage] LoadPlugin("D:\Programa\megui\tools\lsmash\LSMASHSource.dll")
---[NoImage] LWLibavAudioSource("D:\Test\AudioN\TrueHD\dolby_atmos_truehd_sample.m2ts")
---[NoImage] # detected channels: Object Based / 8 channels / 6 channels
---[NoImage] # detected channel positions: Object Based / 3/2/2.1 / 3/2/0.1
---[NoImage] AudioBits(last)>24?ConvertAudioTo24bit(last):last
---[NoImage] return last

1) First problem, seems MeGUI report 0 channels input from the string: "Object Based / 8 channels / 6 channels"

2) Second problem, AviSynth report 2 channel when we expect 8 channels from first audio track.

After that MeGUI log continue without problems until output a flac 2.0.

We expect 8 channels because:

LWLibavAudioSource(string source, int stream_index = -1, bool cache = true, bool av_sync = false, string layout = "", int rate = 0)
...
[Arguments]
+ stream_index (default : -1)
The stream index to open in the source file.
The value -1 means trying to get the first detected audio stream.

But seems than (default : -1) here is not the first detected audio stream (StreamOrder: 0-1 TrueHD)
Reading the .lwi file generated by LWLibavAudioSource (The resumed first lines):

<LibavReaderIndexFile=13>
<InputFilePath>D:\Test\AudioN\TrueHD\dolby_atmos_truehd_sample.m2ts</InputFilePath>
<LibavReaderIndex=0x00000208,0,mpegts>
<ActiveVideoStreamIndex>+0000000000</ActiveVideoStreamIndex>
<ActiveAudioStreamIndex>+0000000004</ActiveAudioStreamIndex>
Index=0,Type=0,Codec=28,...,Width=1920,Height=1080,Format=yuv420p,ColorSpace=2
Index=4,Type=1,Codec=86019,...,Channels=2:0x3 ,Rate=48000,Format=fltp,BPS=32
Index=2,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=3,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=5,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=6,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=7,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=8,Type=1,Codec=86019,...,Channels=6:0x60f,Rate=48000,Format=fltp,BPS=32
Index=1,Type=1,Codec=86061,...,Channels=8:0x63f,Rate=48000,Format=s32 ,BPS=24
...

Seems than LWLibavAudioSource("source", stream_index = -1) output the <ActiveAudioStreamIndex>, currently the Index=4,..,Channels=2

3) New problem, for what the Index of 2.0 is 4 when MediaInfo say 3?
For what the indexer show 6 tracks 5.1 when MediaInfo/eac3to detect 5?

Using BeHappy LWLibavAudioSource("D:\Test\AudioN\TrueHD\dolby_atmos_truehd_sample.m2ts", stream_index=4) I obtain the same flac 2.0 than using MeGUI.
Using LWLibavAudioSource("D:\Test\AudioN\TrueHD\dolby_atmos_truehd_sample.m2ts", stream_index=1) I obtain the flac 7.1
And also can obtain 6 (index 2,3,5,6,7,8) 5.1

[Doom4Ever]

Hello

Opened "AVS SCRIPT CREATOR" AND then opened the input
and click on the one click encoder

In the Avisynth profile> config >template

My template is:
LoadPlugin("C:\path\MeGUI\MeGUI_2624_x86\tools\avisynth_plugin\VSFilter.dll")
<input>
<resize>
textsub("c:\1.ssa")



After click on the "Go" Operation begins

After finishing the application gives me a few files with this extension:



.ac3
.ass
.m4a
.avs
.lwi





while it should give me a video files

Please help me how i can solve that.

[LigH]

Please publish your logfile.

[Glarioo]

If you have the "always backup files when needed" setting in MeGUI's options enabled, it won't delete the old files in the update cache or old log files. If the option is unchecked, MeGUI will delete the old files sooner or later.

I have the "always backup files when needed" disabled now.
Thanks for your help.

[Doom4Ever]

Please publish your logfile.

Where i can get logfile?
Please give me address.

[LigH]

Where you installed MeGUI, in the subdirectory "logs", named with date and time.

[Doom4Ever]

Where you installed MeGUI, in the subdirectory "logs", named with date and time.

Attached:

[Doom4Ever]

I choose "automated 2 pass" and it's work.

Please give me a subtitle that i can HardSub it with MeGUI.
In the Avisynth setting what commands should i enter?

[Vincent Vega]

guys, how do i set up x265 lossless in megui x265 UI?
if i just add --lossless in misc->commandline the 'encode mode' setting (crf/qp/bitrate) still remains and is passed to encoder and these are not needed for lossless i think..

[LigH]

MeGUI does not yet support x265 completely, because the set of command line options is still not "final". You may possibly pair your custom command line option with qp 0 (it is one piece of completely lossless encoding already).

[Vincent Vega]

thanks man, thats sort of what i thought, here from what i understood any qp<=4 implies lossless, right?
http://x265.readthedocs.org/en/default/lossless.html#lossless-encoding

about x265 UI, why not megui start to add at least those options that already exist, then overtime add/adjust as needed.. is just right now encoding with x265 in megui is extremely user unfriendly