MeGUI: General Questions and Troubleshooting Thread

[Sharktooth]

i see it all green when i play the souce in MPC... and the encode looks the same.
so the file is probably corrupt... that's why avisynth or the decoder crash bringing down the rest...
ill re-download and try to watch it with another player/decoder.

@Alborz: there is no best as per forum rules. if you have doubts, look at the first post in the new megui presets thread. however rica's suggestion is good.

@saint-francis: it is probably an hybrid source. try asking in the avisynth forum, there you can find some experienced users.

[rica]

@saint-francis: it is probably an hybrid source. try asking in the avisynth forum, there you can find some experienced users.

I agree it is an hybrid source which added to each ohter.
So the recipe would be graph + manual avs in that case as well imho but not avisynth script creator.

[Sharktooth]

@SynchronousArts: the file you linked is probably corrupt. i cant play it correctly with any player including mplayer, VLC, MPC and QuickTime.

[SynchronousArts]

I downloaded the MOV file from Mediafire to test it and it plays fine for me...?
Do you have the ProRes Codec installed? It needs to be installed on your system after Quicktime. I think it requires 7.3 but I have 7.5 installed on my machine.
You can get it from here: http://www.apple.com/support/downloads/appleproresquicktimedecoder10forwindows.html.

Sorry for all the mess.

[Sharktooth]

ah... found the problem. QTInput does not support ProRes as well as ProRes is not a directshow codec.
you need to transcode the file using quicktime coz other softwares cant use the ProRes codec...

[Inspector.Gadget]

It seems that the newest update to Avimux GUI (1.17.8) doesn't work properly on Windows Vista Home Premium 32-bit. When double-clicking the executable in the avimux_gui folder in the MeGUI tools folder, an error message appears, stating "AVI-Mux GUI has stoped working...A problem caused the program to stop working correctly. Please close the program." This error persists after deleting the whole AVI-Mux GUI folder, deleting any references in the registry to AVI-Mux GUI, deleting all prefetch files, and reinstalling from either MeGUI's automatic update or from the newest binary on the author's own site. I know the author has specifically disclaimed any attempts to ensure his software works on Vista, but I doubt it is any malicious doing on his part. Any ideas?

Edit: Setting the AVI-Mux GUI executable to "Windows XP SP2" fixes this error. I'll report back if I run into any more problems.

[XhmikosR]

Yes, under Vista you have to set it to Windows XP SP2 compatibility mode and it works fine. Version 1.17.7 didn't have this.

[Sharktooth]

was the previous version workin with vista? if so i will restore it.

[Inspector.Gadget]

was the previous version workin with vista? if so i will restore it.

It was working with Vista. I never had to set the compatibility with the previous version. Here is the changelog from 1.17.7 to 1.17.8, in case there's some improvement that would make a reversion undesirable:

# Version 1.17.8

* new
o The CTextFile class is redone. Text files can now be handled in UTF-16 big and little endian (with BOM only), UTF 8 (with BOM only) and the local charset of your windows installation
o Added highlighting for streams that are default and for streams that AVI-Mux GUI cannot put into AVI files (this visual feature can be disabled)
o When creating XML files, now STL is used
o Matroska tags can be used to create several titles for one matroska stream. Note that this is, as far as I know, not yet supported by players or filters.
o The BitStream class is redone. Reading AAC audio is now faster.
o The widht and height of the settings window is increased if the right-bottom-most button is cropped.
o There is now a setting to enable, disable or leave unchanged the cleartype font setting
* fixed bugs
o When opening Matroska files containing Vorbis audio streams, the vorbis audio streams' titles were not imported
o A crash occurred when opening a matroska file containing Tags with no target
o The windows size should not be restored correctly and on the correct screen when restarting AVI-Mux GUI
o The delay setting was printed in the wrong place for A_MS/ACM audio tracks in matroska files
o DTS streams with frames of 2012 bytes got a wrong duration because the PCMSampleCount header field was not used. This made the audio go out of sync
o When the size estimation of a Vorbis audio track failed, a crash occurred
o AC3 and DTS: The LFE channel was ignored. This caused incorrect channel information to be written in headers. This did not affect replay on most players, but I got a report that a Nero AVI file parser interpreted this difference between header and real stream data as a broken file.
o AC3: Due to some rounding that (erroneously) occurred when reading AC3 audio files with 44.1 kHz, such streams were muxed incorrectly.
o Nowadays, there is no long double anymore in Visual Studio. Due to this, when trying to write 80 bit floats into matroska file, a 64 bit float was written instead and padded with 2 zero bytes. This is fixed. IMPORTANT: 80 bit floats are no longer allowed in the matroska specification. 80 bit floats can only be selected when matroska v1/v2 enforcement is disabled.
o the file name in the START command in scripts was converted to UTF-8, then it was interpreted as 8859-1 and again converted to UTF-8, which led to disrupted file names
o a crash occurred when dropping an XML chapter file onto an edition in the chapter editor

[ajeeb15]

when i finish of Encoding the mux have problem and it say

http://alamuae.com/up/uplong/1126852375659868.jpg

i want 2 know wut is da problem

[Sharktooth]

the problem is Yamb and not MeGUI... wrong thread.
also megui doesnt use Yamb for muxing... so what the ... ???

[SynchronousArts]

ah... found the problem. QTInput does not support ProRes as well as ProRes is not a directshow codec.
you need to transcode the file using quicktime coz other softwares cant use the ProRes codec...

:confused:

I must not have been clear in my original post. There is now a Quicktime plugin that handles ProRes decoding. I downloaded the plugin from Apples Website: http://www.apple.com/support/downloads/appleproresquicktimedecoder10forwindows.html

I am able to succesfully load Quicktime files with 1080i ProRes video into AVISynth using the QTInput dll. My setup here is complex so I did simplify my testing until there was nothing but a single source file on a local drive and the above AVS test file. My original setup was reading a 1080i ProRes quicktime that is stored on a FibreChannel array, served over Gb Ethernet to my PC, and read by QTInput by AVISynth.

I have played these AVS files with VirtualDub, MPC and WMP.
I have been able to encode with VirtualDub, ffmpeg, x264 and CCE-SP.

But when I tried to encode to AVC/x264 using MeGUI, I'm having MeGUI crash when I press the Enqueue or AutoEncode buttons. I was able to encode with MeGUI by making fake AVIs with AFVS, the AVS virtual filesystem.

I have been testing x264 for Bluray encoding and like MeGUI. Before the new ProRes decoder was available, a was encoding with MeGUI from Quicktimes that use the AJA Kona 2Vuy uncompressed Codec.

:thanks:

[Sharktooth]

i got the decoder but when i try to install it says i miss SSE2... but my CPU actually have them (athlon64)... so i cant test it.
however have you tried to reinstall avisynth 2.57 from scratch?

[SynchronousArts]

i got the decoder but when i try to install it says i miss SSE2... but my CPU actually have them (athlon64)... so i cant test it.
however have you tried to reinstall avisynth 2.57 from scratch?

Yes, I installed from scratch and swapped AVISynth.dll several times during my testing. Also tested on other machines that have single cores with standard AVISynth.

Is there a debug version available? I have dbgview on some of my machines and would test on them if so, otherwise I think there are probably other things to waste time on at this point. What a bummer that Apple does not care about those that have AMD CPUs.:mad:

[Sharktooth]

http://www.webalice.it/f.corriga/megui/debug/MeGUI.exe

[poisondeathray]

SynchronousArts - I had problems on my Vista x64 / Intel system with your file, so I tried my XP x86 / AMD system and it worked fine in MeGUI. I don't have time to figure out what is different besides the obvious Intel & Vista setup. My AMD setup is the same: avisynth 2.57, MeGUI 0.3.0.2008 using all the development server updates

Note: It didn't work unless I left the preview window open in MeGUI when queing the file. I verified this 3x and it worked only when I left the preview window open, but crashed when I closed the window before pushing enqueue button

http://www.megaupload.com/?d=P58ZIPCB

EDIT: the audio is SOWT which is a type of PCM WAV. If you enable the "uncompressed" setting to "16-bit integer" in the ffdshow audio config, you can do the audio with an .avs script using DirectShowSource() . (I still used QTInput() for the video)

Here is the clip with audio
http://www.megaupload.com/?d=8LBKZLU7

[kirtash]

hello, sorry if this is not the place for ask...
i have a problem, days ago, i can open a script with megui, but now, i can't o_o and is the same script... : S
i've revised the script and did again the .d2v...

Script:
MPEG2Source("D:\VTS_04_1.d2v")
cROP(4,4,-4,-4)
undot()
deen("c3d",0,8,3)
unfilter(3,3)
lumafilter()
blackmanresize(848,480)
Error: http://img362.imageshack.us/img362/7113/errorpf9.png

someone can help me?

[poisondeathray]

@kirtash:

LoadPlugin("PATH\DGDecode.dll")

[jeffy]

@kirtash: do you have the antivirus running? Seems like something is preventing the file from being open.

[SynchronousArts]

...

Note: It didn't work unless I left the preview window open in MeGUI when queing the file. I verified this 3x and it worked only when I left the preview window open, but crashed when I closed the window before pushing enqueue button



Interesting, I'm at home today and tested this with my laptop, but was not able to reproduce this, instead I always get a crash...

I'll test at work tomorrow with my other machines.

Thanks for the info.

[SynchronousArts]

hello, sorry if this is not the place for ask...
i have a problem, days ago, i can open a script with megui, but now, i can't o_o and is the same script... : S
i've revised the script and did again the .d2v...
...
someone can help me?

@kirtash, did you move the mpeg after creating the new d2v file? That error happens when MPEG2Source can't find the mpeg file. If so, remake a new d2v file and try again.

[kirtash]

@kirtash:

LoadPlugin("PATH\DGDecode.dll")
oh god! works!!!! thanks a lot!! ^.^


@kirtash: do you have the antivirus running? Seems like something is preventing the file from being open.
thanks for your time :) (yes, i had a new antivirus)

@kirtash, did you move the mpeg after creating the new d2v file? That error happens when MPEG2Source can't find the mpeg file. If so, remake a new d2v file and try again.
thanks for your time! :) (i don't moved the d2v, and i did again de d2v .-.)

thanks to everybody!

[Inspector.Gadget]

@ Developers - Are you planning to update to the new version of mkvmerge (2.30)? You've been so quick to update to new components recently I'm curious as to whether this upgrade breaks something or is otherwise not desired.

[Sharktooth]

simply missed it. ill make some tests and if there are no problems ill update it in the next days

[Dark Eiri]

Updating to mkvmerge 2.3.0 made the internal MKV Muxer break. Something about the --delay command.

[elguaxo]

There is no --delay anymore.

http://www.bunkus.org/videotools/mkvtoolnix/doc/ChangeLog
2008-08-20 Moritz Bunkus <moritz@bunkus.org>

* mkvmerge, mmg: The option "--delay" was removed. The option
"--sync" now only modifies the timecodes of a given
track. mkvmerge does not pad audio tracks with silence. "--sync"
works with all track types now, but using a stretch factor other
than 1 with audio tracks might not work too well during
playback. mmg's inputs for "Delay" and "Stretch by" can be used
with all track types. Fix for bug 287.

[Sharktooth]

ah... so if i understood the mkvmerge docs correctly --sync can be used in place of --delay
so why changing the option name then?

[rebkell]

ah... so if i understood the mkvmerge docs correctly --sync can be used in place of --delay
so why changing the option name then?

I'm confused, which is easy for me :) How does this work?

[Sharktooth]

if you dont use mkvmerge.exe manually it doesnt change anything for you.

[corporalgator]

Is there a way to disable the apply auto preview by default or give us the option to have it on or off by default? When I open the avisynth script creator, it is automatically checked, so I have to uncheck it.

Not a big deal, but sometimes I forget and then I have to uncheck it and reload the original video since if it is on, it goes straight to the preview view, which no longer lets you autocrop if you say adjust the crop manually and then want to see what the autocrop will do, but it just says "cannot autocrop without original video open." Also, it's much slower to crop manually with that option enabled.

Also, if you crop with autopreview enabled, but then disable it, cropping will no longer work forcing you to reopen the file.

I hope that is clear, but I can try and clarify if I need to.

[delxd]

Sup guys, i've got hold of a server and it has a Intel XEON 3.0GHZ, 8cores as you know... and when i tried to encode a video, even if i did set the encode to use 12threads the megui doesnt use more than 30% of the capacity of processing of the processor, so i would like to know how do i get megui to use at least 80% of the processor?

Ps: even set to HIGH it doesnt use more than 30%

thanks!

[jeffy]

Sup guys, i've got hold of a server and it has a Intel XEON 3.0GHZ, 8cores as you know... and when i tried to encode a video, even if i did set the encode to use 12threads the megui doesnt use more than 30% of the capacity of processing of the processor, so i would like to know how do i get megui to use at least 80% of the processor?

Ps: even set to HIGH it doesnt use more than 30%

thanks!

Post your log, please. What is the source (HD/SD)? How complicated is the input script? What profile have you used for encoding?

[Oline 61]

With MeGUI 0.3.0.2009 there is an --sar calculation error. I used the AVISynth Script Creator on a 720x480 d2v with DAR 16:9. I enabled auto crop and clever anamorphic resize to mod16. The DAR is correct (29/12) in the resulting .avs, but when I encode with x264 the calculated --sar values are wrong and huge.
[NoImage] Job commandline: "C:\tools\x264.967.modified.exe" --crf 26 --nf --no-cabac --subme 1 --partitions none --me dia --threads auto --thread-input --aq-mode 0 --sar 10864803788405:8796093022097 --progress --no-psnr --no-ssim --output "E:\BOURNE_SUPREMACY\VIDEO_TS\VTS_01_1.mp4" "E:\BOURNE_SUPREMACY\VIDEO_TS\VTS_01_1.avs"

[Sharktooth]

Is there a way to disable the apply auto preview by default or give us the option to have it on or off by default? When I open the avisynth script creator, it is automatically checked, so I have to uncheck it.

Not a big deal, but sometimes I forget and then I have to uncheck it and reload the original video since if it is on, it goes straight to the preview view, which no longer lets you autocrop if you say adjust the crop manually and then want to see what the autocrop will do, but it just says "cannot autocrop without original video open." Also, it's much slower to crop manually with that option enabled.

Also, if you crop with autopreview enabled, but then disable it, cropping will no longer work forcing you to reopen the file.

I hope that is clear, but I can try and clarify if I need to.
just click the Re-open original video player button

[Avenger007]

Since you already know the correct --sar then enter it as a custom command line option.
MeGUI still has some work to do with its AR calculations.

[Sharktooth]

Sup guys, i've got hold of a server and it has a Intel XEON 3.0GHZ, 8cores as you know... and when i tried to encode a video, even if i did set the encode to use 12threads the megui doesnt use more than 30% of the capacity of processing of the processor, so i would like to know how do i get megui to use at least 80% of the processor?

Ps: even set to HIGH it doesnt use more than 30%

thanks!
it's not a megui problem.
x264 encoding speed is limited by the avisynth script. it cant feed frames fast enough.
try using avisynth_MT but be aware that it is unstable

[Sharktooth]

With MeGUI 0.3.0.2009 there is an --sar calculation error. I used the AVISynth Script Creator on a 720x480 d2v with DAR 16:9. I enabled auto crop and clever anamorphic resize to mod16. The DAR is correct (29/12) in the resulting .avs, but when I encode with x264 the calculated --sar values are wrong and huge.
[NoImage] Job commandline: "C:\tools\x264.967.modified.exe" --crf 26 --nf --no-cabac --subme 1 --partitions none --me dia --threads auto --thread-input --aq-mode 0 --sar 10864803788405:8796093022097 --progress --no-psnr --no-ssim --output "E:\BOURNE_SUPREMACY\VIDEO_TS\VTS_01_1.mp4" "E:\BOURNE_SUPREMACY\VIDEO_TS\VTS_01_1.avs"
it's not the autopreview and that bug (already known) is there since some time. just specify the correct sar in the profile config (custom commandline options) until the bug is fixed.

[Tae]

Is there a way to downgrade the AVIsythGUI recent upgrade?

I have had nothing but trouble with the recent version.

Nevermind...I see that I can download older version from Sourceforge.

[Sharktooth]

i just made an update with a partial fix. check the dev thread.
tomorrow ill look at the remaining problems but in .2010 it should be as it was in the previous builds (auto-preview disabled by default).

[MrVideo]

Forgive me if this has already been answered somewhere. If so, please point me there.

This issue has been bothering me for a while, so I figured I finally ask about it.

Source: 720x480i
video: letterboxed
output desired: 640x360

When trying to cue the job, meGUI bitches that the 360 isn't a multiple of 16. That is true, when encoding MPEG-2. But, as I understand it, H.264 doesn't have that issue and that a 640x360 encode is legit. When I tell meGUI to do it anyway, the resulting video has a bunch on botton scan lines that look like video tape head switchover.

The workaround is to create 640x352, but that is not true 16:9.

What does it take to get meGUI to do 640x360 x.264 encodes?

Thanks.

[Sharktooth]

your decoder doesnt support non mod-16 resolutions.
that's not a megui problem.

[MrVideo]

your decoder doesnt support non mod-16 resolutions.
that's not a megui problem.

Would you mind explaining that cryptic response? Here is why I am confused by it. It is meGUI that is complaining when I try and place the job of the cue. There is no H.264 decoding going on. Hell, encoding hasn't even started yet.

[Sharktooth]

can you post a screenshot?

[MrVideo]

can you post a screenshot?

Here is the sequence of events:

1) Cropping (http://vidiot.com/meGUI-1.png)
2) Filter Setting (http://vidiot.com/meGUI-2.png)
3) meGUI Preview after save of script (http://vidiot.com/meGUI-3.png)
4) Error after clicking Enqueue (http://vidiot.com/meGUI-4.png)

If you need to see anything else, let me know.

Thanks.

[poisondeathray]

the resulting video has a bunch on botton scan lines that look like video tape head switchover.



The non-mod16 resolution of 640x360 works fine if your decoder and/or setup supports it.

You often get scan lines and other aberrations if your setup doesn't support non-mod16 resolutions. (an example is some hardware decoders will exhibit this if faced with decoding non-mod16 resolutions; you often get green lines in the borders)

The other possibility is that you have an deinterlacing artifact.

You can use still 640x368 and get true 16:9 resolution by using non-square pixels by changing the pixel aspect ratio (--SAR X:Y in MeGUI)

[MrVideo]

The non-mod16 resolution of 640x360 works fine if your decoder and/or setup supports it.

VideoLanClient is used to play the meGUI H.264 encoded, MKV wrapped file. As I understand it, H.264 isn't mod16. Is my understanding wrong?

The other possibility is that you have an deinterlacing artifact.

No problem at 640x352.

You can use still 640x368 and get true 16:9 resolution by using non-square pixels by changing the pixel aspect ratio (--SAR X:Y in MeGUI)

Just where is that set? I couldn't find anything in the config for meGUI.

What I don't like about goig to 368 from the 360 crop, is the interpreting of 360 lines to 368 lines. Then that gets interpreted again to 640x360, if one plays it that way, or if I fill my monitor, 1280x720 (letterboxed onto a 1280x1024 display). It is better to leave it at 360 which means that it will be 1:1. True that deinterlacing isn't perfect either, but I'd rather deinterlace 360->360 than 360->368.

I'd really like to get this to work at 640x360.

[MrVideo]

Just for grins, I thought I'd try something, and that is take my 704x360 crop and bump it up to 1280x720.

But the AviSynth script creator won't let me go any bigger than 720x480.

WHY?

EDIT: But if I manually edit the script and change it to 1280x720, it works. Bug?

[poisondeathray]

^You can just enter it manually in the last page of the creator (e.g. LanczosResize(x,y) ). Or you can just create a script manually without the creator

I'm assuming you cropped so there are no borders then resized to 640x360?

The --SAR X:Y is entered in the last configuration page, advanced tab, custom command line (encoder setting, not .avs script)

640x360 with 1:1 pixels works fine. I just tested it (mind you it wasn't an interlaced source) played with MPC and VLC correctly. Here is a tiny <1MB sample encode

http://www.mediafire.com/download.php?phktrlawifj

Perhaps you can post a screenshot or sample of the "error" you are experiencing?

[MrVideo]

^You can just enter it manually in the last page of the creator (e.g. LanczosResize(x,y) ). Or you can just create a script manually without the creator

That is what I did. Still, the creator shouldn't be forcing a max X or Y. That sounds like a bug to me.

I'm assuming you cropped so there are no borders then resized to 640x360?

Correct. The source was letterboxed, so the vertical cropping is to get rid of the bars. No need to encode those. Ad for NTSC video, the active area is really 704, not 720.

The --SAR X:Y is entered in the last configuration page, advanced tab, custom command line (encoder setting, not .avs script)

I was looking for a box to check and then enter a value.

640x360 with 1:1 pixels works fine. I just tested it (mind you it wasn't an interlaced source) played with MPC and VLC correctly. Here is a tiny <1MB sample

Plays just fine. But, what was your source? Mine was 720x480i MPEG-2 4:2:0.

Perhaps you can post a screenshot or sample of the "error" you are experiencing?

Did you look at the images that I linked to in the above posting?

[Sharktooth]

it's not a bug but an intended behaviour since upscaling is always useless unless you use ubercomplex resizing algos... in that case you have to edit the .avs manually... so...
btw, i cant see any problems in your screenshots except a couple of non cropped pixels at the bottom. where are those "scanlines"?
megui just let you proceed after notifying you the resolution was not mod16.
keep in mind some avs filters will require mod16 res too (dunno if yadif does), however it's ALWAYS better to stick with mod 16 res.
just a side note... h.264 always encode to mod16 even if the source isnt mod 16... it just pads the remaining pixels ...