MeGUI: bug reports and feature requests

[Carpo]

sounding good :)

[[ReX]]

This (http://doom10.org/index.php?topic=55.msg397#msg397) tool may come in handy for x64+x264.

I can't test it (no x64 OS atm).

[forum king]

ok guys i need some info'''
i have been doing whatever dear Zathor has asked us to..
today i have installed megui in separate folder as he said..
now my biggest concern is how to work with the presets.. see what i do is i try to re encode my DVDs and the other HD content to a smaller size i mean to a video bit rate of b/w 500 and 600.. previously i used to use HQ insane or slower then started using Unrestricted 2 pass HQ.. but now as the interface is totally changed i dont have a clue what to use ...

i tried to tweak one x264 by adding high profile , automated 2 pass , turbo , deblocking -1 : -1 , adaptive Bframes - 2 optimal , mv pridiction - auto , trellis 2 always , and MV algorithm - Multihex and sunpixel refinement to 9 ... i mean tried to make it look like unrestricted 2 pass..

the quality came out good but the video was jerky :(...

so please suggest me which profile to use and if i need to tweak something what should they be , so that i can workaround to a bit rate b/w 500 to 600.

thanks

Glenn

[SacredCultivator]

For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.

[nakTT]

For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.
So far no issue for me.

Anyone else please share your experience.

[Zathor]

i tried to tweak one x264 by adding high profile , automated 2 pass , turbo , deblocking -1 : -1 , adaptive Bframes - 2 optimal , mv pridiction - auto , trellis 2 always , and MV algorithm - Multihex and sunpixel refinement to 9 ... i mean tried to make it look like unrestricted 2 pass..

the quality came out good but the video was jerky :(...

so please suggest me which profile to use and if i need to tweak something what should they be , so that i can workaround to a bit rate b/w 500 to 600.

Sadly I am no profile / x264 settings expert. Maybe you can solve it yourself if you compare a new file with an old working file (for example use mediainfo and compare the x264 settings).

For some reason, with the latest update... It always says there are updates... Only for the avisynth plugins... I see them in my update cache folder but even after I install/force install, and restart the client... it says there are updates again... Not too sure if anyone else is experiencing this.
EDIT: Thanks, problem found.
EDIT2: fix in first posting

[forum king]

Sadly I am no profile / x264 settings expert. Maybe you can solve it yourself if you compare a new file with an old working file (for example use mediainfo and compare the x264 settings).

No issues buddy :)
Thanks for the awesome effort :)
i ll try as you said... also if you come across something or someone then please suggest...
god bless
Glenn

[simonb1975uk]

Hi,

I'm a newbie but have been lurking for a long time now so please be gentle with me. Am using the new MeGui but when I try and convert my audio tracks via NeroAAC to .mp4, MeGui produces an error. The log says 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt', then MeGui will crash. I am using the 'Nero *scratchpad*' Encoder Setting and the only thing I have changed there is 'Downmix to stereo'. Video encoding works fine, just audio encoding has stopped working. I am using Windows 7 Pro 64-bit.

[kool]

Download Nero Digital Audio (http://www.nero.com/eng/downloads-nerodigital-nero-aac-codec.php), creat folder neroaacen in C:\Program Files\megui\tools\.
Extract the contents of the zip file to your desktop and move the contant of win32 folder to "C:\Program Files\megui\tools\neroaacenc\".

in MeGUI, go to Options -> Settings -> Program Paths. Look for the entry with NeroAacEnc and click the browse icon to the right. Find neroaacenc.exe which should be in the "megui\tools\neroaacenc\" folder if you followed the instructions above.

[simonb1975uk]

kool,

I did as you suggested but received the same error.

[rack04]

Hi,

I'm a newbie but have been lurking for a long time now so please be gentle with me. Am using the new MeGui but when I try and convert my audio tracks via NeroAAC to .mp4, MeGui produces an error. The log says 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt', then MeGui will crash. I am using the 'Nero *scratchpad*' Encoder Setting and the only thing I have changed there is 'Downmix to stereo'. Video encoding works fine, just audio encoding has stopped working. I am using Windows 7 Pro 64-bit.

What are you trying to convert? You say "my audio tracks" but give no indication of the format. Try enabling/disabling "Force decoding via DirectShow".

[simonb1975uk]

Sorry the format is the .ac3 file created after I have run DGIndex.

[rack04]

Sorry the format is the .ac3 file created after I have run DGIndex.

What is the exact file name? I have had problems in the past with special charaters used in file names.

[simonb1975uk]

Enabling 'Force Decoding via DirectShow' did it. Many thanks.

[kool]

great to hear that you fix it.

[forum king]

This one gave me good results ( in previous 1057 build by zathor in which we had to download 1056 and then apply the patch )
cabac=1 / ref=8 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=-2 / threads=6 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=597 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00



this is the one i have been able to make.now ( in the latest build standalone by zathor )


cabac=1 / ref=8 / deblock=1:-1:-1 / analyse=0x3:0x133 / me=umh / subme=9 / psy=1 / psy_rd=1.0:0.0 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=2 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=6 / sliced_threads=0 / nr=0 / decimate=1 / mbaff=0 / constrained_intra=0 / bframes=3 / b_pyramid=0 / b_adapt=2 / b_bias=0 / direct=3 / wpredb=1 / wpredp=2 / keyint=250 / keyint_min=25 / scenecut=40 / rc_lookahead=60 / rc=2pass / mbtree=1 / bitrate=539 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00

now the diff in these two are obviously deblocking ( that i can correct :P )
but the lower one has these two settings extra which i am not able to find out how to remove or :P

fast_pskip=1
sliced_threads=0

can someone suggest me via screen which option are these :P and how can i totally disable them so that the lower profile looks exactly like the upper one .. or if its ok to have them :P

[Zathor]

fast_pskip=1
sliced_threads=0
can someone suggest me via screen which option are these :P and how can i totally disable them so that the lower profile looks exactly like the upper one .. or if its ok to have them :P

Great that you figured it out!

fast_pskip=1 ==> Misc, "No fast P-Skip"
sliced_threads is a new feature since r1364 and is disabled by default. So I assume that sliced_threads=0 is no problem at all compared to your old encoding.

[forum king]

Great that you figured it out!

fast_pskip=1 ==> Misc, "No fast P-Skip"
sliced_threads is a new feature since r1364 and is disabled by default. So I assume that sliced_threads=0 is no problem at all compared to your old encoding.
thanks mate :) love ya :)
also i would like to ask if you can link us all to the latest profiles made by someone trusted which are totally compatible with your build and latest x264 ...
coz despite numerous searches i was not able to get hold of compatible ones ( for sure )...
coz you know once everything is fixed guys like me who dont have too much of an experience try and rip acc to presets...

regards
Glenn

[Adub]

I reverted the event handler back to the old one. The problem with the old handler is that the value will be only processed if the control lost the focus or the up/down slider is used. Btw I changed ALL NumericUpDown events so that the user experience is the same for all controls.



Great! Thanks for fixing this Zathor. Works like a charm now.

[SacredCultivator]

@Zathor: Tried the new version and those avisnyth plugins work like a charm now, thanks!

[Zathor]

;1353401']This (http://doom10.org/index.php?topic=55.msg397#msg397) tool may come in handy for x64+x264.
I only did a few tests and it seems to be not faster than pipebuf + avs2yuv. Can anyone confirm?

[forum king]

hi Zathor :)

mate i donno whats gone wrong i have reinstalled windows coz megui was not working in user interface ( something got messed earlier )

i have done everything right :(
but my re encodes are all coming out jerky
any ideas


please help.


EDIT : man i have tried everything but the re encodes are jerky
what do i do :(

EDIT 2 : ok looks like its not the fault of megui o4 x264 there is something wrong in the windows then coz i used 1051 version that i had backedup and it also produced similar famy rip

any ideas please..

[JoeH]

I was thinking that when you add the new version of MeGUI to the "stable" servers and thousands begin downloading the updates, what will probably most confuse users will be the new + old profiles confusion - they'll have their old profiles, plus new profiles, with no easy way to distinguish them.

Here is what I would suggest:
1. Move all old profiles to a backup folder
2. Install only new profiles
3. Remove STx264 from the update servers
4. Display a message stating that the old profiles have been moved to the backup folder (maybe with a link) and that they are available there if needed.

[Zathor]

EDIT 2 : ok looks like its not the fault of megui o4 x264 there is something wrong in the windows then coz i used 1051 version that i had backedup and it also produced similar famy rip
any ideas please..
Sorry, no idea. If you have reinstaled your PC which kind of video filters / codec do you have installed afterwards? Maybe one of them - or your source file - is causing the trouble.

I was thinking that when you add the new version of MeGUI to the "stable" servers and thousands begin downloading the updates, what will probably most confuse users will be the new + old profiles confusion - they'll have their old profiles, plus new profiles, with no easy way to distinguish them.

Because of the lack of negative feedback I have already added the version 1059 (more or less the lastest 1058 renamed to 1059) to the official development server. I did it an hour ago...


Here is what I would suggest:
1. Move all old profiles to a backup folder
2. Install only new profiles
3. Remove STx264 from the update servers
4. Display a message stating that the old profiles have been moved to the backup folder (maybe with a link) and that they are available there if needed.
1./4. I do not know what is more confusing - to lost the old profiles or have the old and the new ones. The old ones are working more or less. The new settings will revert to default values (mostly bad at all).
2./3. STx264 can only be found on the stable server. The development server do not have these profiles.

[forum king]

@ Zathor .. no mate i havent done anything fancy..
after setting windows up
i installed CCCP
avisynth
1056 and updated with ur server.. ( also did a standalone installation nas is there on page one ) ( also used a 1051 backup.. but all producing video which are like jerky as when you see a video in an old mobo with low memory )

the system is quad core amd with 8GB ddr2 ram no graphics card..
was ripping well on it before this.. but 2 days back megui suddently lost its User interface though it could be seen running in task manager.. thats whay did a reinstall.

[Guest]

Start a new thread, forum_king. Analyzing why your rips are jerky is off topic in here.

[forum king]

Start a new thread, forum_king. Analyzing why your rips are jerky is off topic in here.
Ok thanks dear..
duely noted.

love ya zathor

[Triccotracco]

Gentlemen,

please test as much as possible, if there are some issues don't exitate to post. Thank you Zathor for the big work, from my site I continue to test as my knowledge permits.

:thanks::thanks::thanks:

[AiDz0r]

well guys :( i am giving up
looks like i cant use the latest megui builds and the benefits of x264.
i have done everything as was said here and at the troubleshooting thread..
but it just wont work out..
i used the latest build by Zathor ( the 2nd one ) and installed it in a separate folder..
used unrestricted 2 pass HQ with SLower settings
it will do the first pass and give a STANDARD ERROR STREAM error upon second always..
sometimes the same error on first pass as well..


can someone please please please guide me how should i go about it all.. i have been trying to do this from last 3 days in TOTALO vain.

it looks i ll have to go back to 1051 :(
Just as forum king said, I'm having the same problem. but i searched up and i guess its because of the presets? Is there any ready-working presets available? for normal video encoding.
http://img26.imageshack.us/img26/6562/15796918.jpg

[stax76]

@newbie

The root of the most problems reported about MeGUI is newbies trying to use a application designed for experts. There are applications that take much better care about newbies.

Generally if a software don't work you start with the most simplest scenario and then modify it until it breaks to understand where and why it breaks. In a video encoding scenario this would be using a simple AviSynth script that don't contain any filter other than AVISource with a simple XviD source file and encode it with the command shell with a x264 command line that don't contain any switches switches other then IO, this would like like this:

x264.exe --output "<target>" "<source>"

If this works then you would use the script and command line in MeGUI, then you add settings until it breaks. Verify if it might be a encoder or decoder problem, try different x264 versions, try players with different playback engines like VLC and SMPayer, if all fails investigate the OS and the hardware. Don't reinstall your OS, be a man and fix it, use system recovery if necessary.

Recently I told a user I don't have much time to assist him with a particular issue I've not given a high priority, I told him to investigate it himself and tell me if he finds out something. Apparently he was strong and didn't give up, a few days later he came back and told me exactly where and why it breaks, he uploaded sample files and told me how to reproduce the problem. It took me 2 minutes to find the problem and 2 more to fix the code.

Maybe a good idea to tell more often users to trying to find out what the problem is themselves, many just come and tell that it crashes but don't provide enough details that it would allow for anything more then guesswork.

[nakTT]

Hi,

Any chance for us to get x264 rev1376 from our update server?

:thanks:

[poisondeathray]

@AiDz0r - I've seen several very similar crashes reported by some people (good luck trying to find the exact post with this search system :) ), and the fix was to replace the x264.exe version with another build. Apparently there was some incompatiblity isssue with jeeb's build and that specific system/cpu/os or whatever.

Try a build from the url below, backup the old x264.exe (make a copy just in case), and replace it with a renamed one that you downloaded from the below (ie. rename it to x264.exe and put in the same directory)

http://komisar.gin.by/

[poisondeathray]

@nakTT , you can download and manually replace the x264.exe if you want from the x264 build thread. You can backup (make a copy) of the original in a folder

Just be aware the various builds can have different patches applied

[AiDz0r]

@newbie

The root of the most problems reported about MeGUI is newbies trying to use a application designed for experts. There are applications that take much better care about newbies.

Generally if a software don't work you start with the most simplest scenario and then modify it until it breaks to understand where and why it breaks. In a video encoding scenario this would be using a simple AviSynth script that don't contain any filter other than AVISource with a simple XviD source file and encode it with the command shell with a x264 command line that don't contain any switches switches other then IO, this would like like this:

x264.exe --output "<target>" "<source>"

If this works then you would use the script and command line in MeGUI, then you add settings until it breaks. Verify if it might be a encoder or decoder problem, try different x264 versions, try players with different playback engines like VLC and SMPayer, if all fails investigate the OS and the hardware. Don't reinstall your OS, be a man and fix it, use system recovery if necessary.

Recently I told a user I don't have much time to assist him with a particular issue I've not given a high priority, I told him to investigate it himself and tell me if he finds out something. Apparently he was strong and didn't give up, a few days later he came back and told me exactly where and why it breaks, he uploaded sample files and told me how to reproduce the problem. It took me 2 minutes to find the problem and 2 more to fix the code.

Maybe a good idea to tell more often users to trying to find out what the problem is themselves, many just come and tell that it crashes but don't provide enough details that it would allow for anything more then guesswork.

Well fist of all, i did search it and couldn't find anything related. Yet I'm here to get help not advise and again this is a forum to help other people get feedback and so on. It's more like you don't even understand why its giving an error so you're just getting away with it and tired to find out what's making the error. I tried everything, and as always i do a research on the forum and other forum to find solution then i post my comment for help. if i did find the solution why would i bother... and you have totally misunderstood me, I can playback my videos I tried re-installing re-updating my MEGUI and not using the old system by using "Zathor's patched build" and none of them work well in encoding, I could use normal basic commands, but their not useful, when I could make my video better why wouldn't I?

[Inspector.Gadget]

Note that "playback works fine" isn't the same as "DirectShowSource (and AVISource, which uses VFW) is able to access the correct filters and they work without incident".

[medp7060]

Well fist of all, i did search it and couldn't find anything related. Yet I'm here to get help not advise and again this is a forum to help other people get feedback and so on. It's more like you don't even understand why its giving an error so you're just getting away with it and tired to find out what's making the error. I tried everything, and as always i do a research on the forum and other forum to find solution then i post my comment for help. if i did find the solution why would i bother... and you have totally misunderstood me, I can playback my videos I tried re-installing re-updating my MEGUI and not using the old system by using "Zathor's patched build" and none of them work well in encoding, I could use normal basic commands, but their not useful, when I could make my video better why wouldn't I?

Do not get disappointed. I am also starting to learn x264 encoding recently, although I have been doing Xvid encoding for a number of years. There was time when I was called "Nut" or "Monkey" by some experts, but I still keep reading and try to learn the basics. It will take time to get familiar with a well-designed GUI such as MeGUI and many others. I do not know what is your problem, but based on Xvid experience, before you load it into MeGui, first try to player it (the script) using Windows Media Player, by doing that, it will tell you what is the basic problem. Then start to solve it from there.

[nakTT]

@nakTT , you can download and manually replace the x264.exe if you want from the x264 build thread. You can backup (make a copy) of the original in a folder

Just be aware the various builds can have different patches applied
Thanks for the reply bro.

The builds with patches will not going to have any effect on normal user right?

:thanks:

[Zathor]

Any chance for us to get x264 rev1376 from our update server?
Did not notice that there has been a new one. Thanks for the information - new file online.

...the fix was to replace the x264.exe version with another build. Apparently there was some incompatiblity isssue with jeeb's build and that specific system/cpu/os or whatever.

If jeeb's build really is the source of the problem I will switch to another one. Can anyone confirm that jeeb's build is crashing and another build not?

The builds with patches will not going to have any effect on normal user right?
The patched builds are needed if you want to use the --nal-hrd switch and this switch is needed if you want to follow the BluRay specs. So if your target device is not BluRay you can disable this switch in the profile and can use an unpatched build.

[nakTT]

Did not notice that there has been a new one. Thanks for the information - new file online.
No problem. Will be happy to let you know when the next update available.

The patched builds are needed if you want to use the --nal-hrd switch and this switch is needed if you want to follow the BluRay specs. So if your target device is not BluRay you can disable this switch in the profile and can use an unpatched build.
Is that mean there will be some kind of negative effect if I use patched version (e.g Jeeb) if my target is not BluRay (just normal mkv file to be played on my PC)?


:thanks:

[prOnorama]

@ nakTT: you can just go to x264.nl, grab the vanilla x264 1376 build and replace the patched build in the Megui\Tools\x264 folder

(I've never used JEEB's builds with MeGUI, always vanilla since I don't need the nal-hrd patch for Blu-ray compatibility)

[nakTT]

@ nakTT: you can just go to x264.nl, grab the vanilla x264 1376 build and replace the patched build in the Megui\Tools\x264 folder

(I've never used JEEB's builds with MeGUI, always vanilla since I don't need the nal-hrd patch for Blu-ray compatibility)
Thanks for the reply.

BTW, vanilla = Original (no patch whatsoever) right? Sorry for my english.;)

:thanks:

[Triccotracco]

BTW, vanilla = Original (no patch whatsoever) right?

Yes vanilla = Unpatched, BTW also jeeb's builds are good IMO.

[nakTT]

Yes vanilla = Unpatched, BTW also jeeb's builds are good IMO.
Thanks for the reply bro.

:thanks:

[JoeH]

1./4. I do not know what is more confusing - to lost the old profiles or have the old and the new ones. The old ones are working more or less. The new settings will revert to default values (mostly bad at all).
2./3. STx264 can only be found on the stable server. The development server do not have these profiles.

OK. I was referring to when you move over the new builds to the "Stable" servers.

[Alf Bundy]

First, thank you for your work Zathor.

By fixing that : - (zathor) [x264Config] fix an issue where custom profile settings may be lost,
you earned the Nobel Prize of ABF (Annoying Bug Fixing).

http://img290.echo.cx/img290/9768/yahoo6lp.gif



Second : Since the 1059 update, I got an error when closing MeGUI :

http://img20.imageshack.us/img20/8459/meguiclosingerror.png

The part in french says "object's reference is not defined to an object's instance" (translation might not be accurate, but even in french it makes no sense to me, so ...)

I'm on WinXP SP3 and this closing error does not happen all the time.

- When I start MeGUI and close it without doing anything -> no error.
- When I start MeGUI and use it to encode a single WAV to AAC -> no error when closing.
- But when I encode multiples WAV's or video scripts, I have to kill MeGUI from the task manager.


I didn't find any other problem with 1059.


Thanks again !

[Zathor]

Since the 1059 update, I got an error when closing MeGUI[...]The part in french says "object's reference is not defined to an object's instance" (translation might not be accurate, but even in french it makes no sense to me, so ...)

There should be more details in the log file. Can you send it to me, please (PM)?

[[ReX]]

In Subpixel Refinement/subme, the tooltip says that x264's default is 7, it actually is, but in x264 configuration dialog "6" is actually the default but the result is 7. So you won't get 6.

[Zathor]

;1354397']In Subpixel Refinement/subme, the tooltip says that x264's default is 7, it actually is, but in x264 configuration dialog "6" is actually the default but the result is 7. So you won't get 6.
Thanks, I found a line in the source code where subme defaults incorrectly to 6. I'm unsure if this is the problem you have described but nevertheless this has been fixed. You have to wait a little bit (maybe up to a few days) before I can upload a new build because of ongoing other changes.

[[ReX]]

Thanks, I found a line in the source code where subme defaults incorrectly to 6. I'm unsure if this is the problem you have described but nevertheless this has been fixed. You have to wait a little bit (maybe up to a few days) before I can upload a new build because of ongoing other changes.

That's it. Don't worry, I'll just add "--subme 6" in Custom Command Line. :p

[Alf Bundy]

about a fatal error when closing MeGUI
There should be more details in the log file. Can you send it to me, please (PM)?

Well, there's nothing in the logs about this error. Only encoding related stuffs.

... And I can't reproduce it anymore !
I tried a dozen of multiple video & audio encodes, and MeGUI closed normally with no error.

So don't worry about that. If it happen again, I will check the log tab and send you the log file.


But I noticed something else in the logfile :

[Information] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.1.1059
--[NoImage] OS : Windows XP Professional x64 SP3 (5.1.196608.2600)
--[NoImage] Latest .Net Framework installed : 3.5 (3.5.30729.01)
--[NoImage] Avisynth Version : 2.5.7.0

My XP is 32bit, not 64bit. So I thought it would write x86 (I may be wrong).
There's absolutely no issue with that. MeGUI works great.
It's only (probably useless) for your information. :o