MeGUI: bug reports and feature requests

[kthxbye]

With the newest update, when I try to disable MBtree and run an encode, it's still using MBtree although I did uncheck it in the settings!

It creates an .stats.mbtree file, yet does not show it in the commandline. When I open the .mkv file, mediainfo shows "mbtree=1" though. I did not check MBtree in the settings. Any info on this?

-edit- adding "--no-mbtree" to the commandline fixes this problem temporarily, but I didn't have to use this before...

[Zathor]

When you run the updater and it for some reason you press cancel, especially if its the core your updating. It will try and install the half downloaded .zip and bork MeGUI. Would there be some way if a user presses cancel while it is downloading a update it would automatically delete the incomplete .zip from the \update_cache\ dir.

The easiest way (in my opinion) to do this is to just download to something like filename.zip.temp and then rename to filename.zip when it completes. That should prevent you from getting a partial file even if your system crashes during the download.

I have added a zip file crc check before the archive will be extracted.

[Zathor]

With the newest update, when I try to disable MBtree and run an encode, it's still using MBtree although I did uncheck it in the settings!

It creates an .stats.mbtree file, yet does not show it in the commandline. When I open the .mkv file, mediainfo shows "mbtree=1" though. I did not check MBtree in the settings. Any info on this?

-edit- adding "--no-mbtree" to the commandline fixes this problem temporarily, but I didn't have to use this before...

As soon as I uncheck the mbtree check box "--no-mbtree" will be added to the command line. Please give me more details for reproducing the problem.

[Zathor]

I also like how you have hard set the dir for FFMSIndex, wouldn't this be a good idea to do this for the other indexers as well or could there be an option for the default output dir in the settings to be ignored for indexing?
Because there is no reference to the video file inside of the ffindex file I had to lock the location. This should be no big problem because the index file is rather small.

[kthxbye]

As soon as I uncheck the mbtree check box "--no-mbtree" will be added to the command line. Please give me more details for reproducing the problem.

I'm using MeGUI 0.3.4.6 (latest update) on Windows 7 64bit. If I check or uncheck "Use MB-Tree" in the configuration dialog, nothing happens in the commandline. If I select another profile and check/uncheck "Use MB-Tree" nothing happens either.

What else do you need to know? I'll gladly provide the information :)

[Zathor]

I'm using MeGUI 0.3.4.6 (latest update) on Windows 7 64bit. If I check or uncheck "Use MB-Tree" in the configuration dialog, nothing happens in the commandline. If I select another profile and check/uncheck "Use MB-Tree" nothing happens either.

What else do you need to know? I'll gladly provide the information :)

I found only a problem if the fast preset is beeing used. If this is not your problem please reset the profile to the default values (misc\default settings) and try again.

0.3.4.7
- [UpdateCacher] + [UpdateWindow] + [MainForm] added offline install capability
- [UpdateCacher] + [UpdateWindow] zip files will be verified before extracting
- [UpdateCacher] improved proxy support
- user.config will be migrated to new version if possible
- [x264Encoder] mbtree can be disabled while fast preset is active

[kthxbye]

I found only a problem if the fast preset is beeing used. If this is not your problem please reset the profile to the default values (misc\default settings) and try again.

That seems to have fixed the problem, thanks!

Just for verification, I had to redo all the settings:

program --level 3.1 --pass 2 --bitrate 1750 --stats ".stats" --deblock -3:-3 --bframes 6 --b-adapt 2 --ref 8 --no-mbtree --aq-strength 0.9 --merange 32 --me tesa --direct auto --subme 10 --partitions all --trellis 2 --psy-rd 0.9:0 --no-dct-decimate --no-fast-pskip --sar 40:33 --output "output" "input"

Any strange things in here? :)

[cryphog]

Stable or Development build? Which is the better of the two to use?

[buzzqw]

here proxy isn't working :(

would be better to use something like wget/download.exe ?

BHH

[Alf Bundy]

Hi :)


I've just tried FFindexer and FFVideoSource().
When I enqueue the script, I get a message box telling me "colorspace is not YV12, do you want to add ConvertToYV12() at the end of the script ?"

I say Yes and then I get this message :

http://img502.imageshack.us/img502/237/ffvideosource.png

If I click Yes, the job is enqueued properly and the encode runs fine.

Should I worry about this ?


PS: Thank you for your work Zathor. :thanks:

[Zathor]

here proxy isn't working :(

Can you send me any proxy data (server, port, uid, pwd) so that I can check it myself? And please provide the complete log of the update window.

[buzzqw]

pm send

thanks

BHH

[Zathor]

I've just tried FFindexer and FFVideoSource().
When I enqueue the script, I get a message box telling me "colorspace is not YV12, do you want to add ConvertToYV12() at the end of the script ?"

I got the same messages. You can try to set the colorspace with FFVideoSource(source,colorspace=YV12)

[AMED]

i tried with colorspace=YV12 and i got avisynth script error: i don't know what "YV12" means

LoadPlugin("C:\Program Files (x86)\megui\tools\ffms\ffms2.dll")
FFVideoSource("E:\The_Naked_Gun\The Naked Gun.mkv", colorspace=YV12)
#deinterlace
#crop
#resize
#denoise

I'm testing with a DVD ripped with makemkv.

EDIT: Found out why it isn't working, it should be like this.
LoadPlugin("C:\Program Files (x86)\megui\tools\ffms\ffms2.dll")
FFVideoSource("E:\The_Naked_Gun\The Naked Gun.mkv", colorspace="YV12")
#deinterlace
#crop
#resize
#denoise

that stops the colorspace not YV12 errors appearing in MeGUI.

[Alf Bundy]

Thank you Zathor & AMED.
Problem solved for me too.

[yaous]

I'm using MeGUI 0.3.4.7

When I set modes:const. quality,

Temp. Blur of est. Frame complexity(cplxblur) and

Temp. Blur of Quant after CC(qblur) are disabled.

and when I set modes:const. quantizer,

all the options in [Quantizers] box of [Rate Control] tap are disabled except credits quantizer.

and AQ is activated in const. quantizer mode.

Is this normal?

[Zathor]

I'm using MeGUI 0.3.4.7

When I set modes:const. quality,

Temp. Blur of est. Frame complexity(cplxblur) and

Temp. Blur of Quant after CC(qblur) are disabled.

and when I set modes:const. quantizer,

all the options in [Quantizers] box of [Rate Control] tap are disabled except credits quantizer.

and AQ is activated in const. quantizer mode.

Is this normal?

I do not know. These things have been disabled since I am involved in the development. If someone agrees that this is incorrect I will change it - sadly I have no time to check it myself (e.g. with x264 --fullhelp or the Wiki).

[Zathor]

0.3.4.8
- [ffmsReader] + [ScriptServer] FFVideoSource defaults to the YV12 colorspace
- [VideoUtil] improved the ConvertToYV12() handling

[MajorX]

How can i encode a dual audio file with MeGUI ...i tried with adding Track 2 but it encode the first track not the second..how can i use the DGIndex???

[yaous]

I do not know. These things have been disabled since I am involved in the development. If someone agrees that this is incorrect I will change it - sadly I have no time to check it myself (e.g. with x264 --fullhelp or the Wiki).

http://forum.doom9.org/showthread.php?t=153672

from that post,

It seems that

--qpmin/max/step, --ip/pbratio and --chroma-qp-offset are adjustable in CQP mode.

and AQ is not used in CQP mode.

[Knuffi]

How can i encode a dual audio file with MeGUI ...i tried with adding Track 2 but it encode the first track not the second..how can i use the DGIndex???

You have to press the "Enque" button on both tabs - "Track 1" and "Track 2".

[Zathor]

http://forum.doom9.org/showthread.php?t=153672

from that post,

It seems that

--qpmin/max/step, --ip/pbratio and --chroma-qp-offset are adjustable in CQP mode.

and AQ is not used in CQP mode.

Thanks.

I have to change the handling for the upcoming new x264 build (superfast preset, nal-hrd, ...) and will have a look at your findings, too.

[Zathor]

0.3.4.9
- x264 - some CQP mode adjustments
- x264 - added superfast preset support (requires x264 revision 1509 or higher)

[hajj_3]

Can you make it so that the widths of the columns in the "queue" tab are saved instead of reverted back to default when you upgrade the megui version please.

[Zathor]

Can you make it so that the widths of the columns in the "queue" tab are saved instead of reverted back to default when you upgrade the megui version please.
Since 0.3.4.7 these settings are migrated if possible. At least it is working for me.

[hajj_3]

the main window is but the width of the columns in the "queue" tab didn't migrate for me.

[Zathor]

After a quick test I can say that beside the "Owner" column the other columns are being saved. I did not check the source code, but it looks in general as it is working.

[cryphog]

Hello Zathor! Thanks for the great work on MeGUI! I just have a question about the stable server, Is it gonna get updated any time soon or should I switch over to the development server? Thanks

[Zathor]

A new stable build will be released together will all recent tools as soon as I think that MeGUI and the tools are ready for this step. With the fresh commit of the new x264 I would like to wait at least a week before I decide if this is gonna be a stable release.

[AMED]

@Zathor
I just gave your update zip crc check a go by canceling the core update mid download. Once i reopened MeGUI, it prompted me that the core update still needed to be downloaded and installed.

[JoeH]

0.3.4.9
- x264 - some CQP mode adjustments
- x264 - added superfast preset support (requires x264 revision 1509 or higher)

Thanks Zathor! Works great. It's exciting to see the new improvements in X264, and equally exciting to see how quickly you are keeping up! :thanks:

[Zathor]

I just gave your update zip crc check a go by canceling the core update mid download. Once i reopened MeGUI, it prompted me that the core update still needed to be downloaded and installed.
So it is working as expected, isn't it? :)

Thanks Zathor! Works great. It's exciting to see the new improvements in X264, and equally exciting to see how quickly you are keeping up! :thanks:

:eek:

[alexcel]

Hi Zathor:

This is an old bug.

When selecting keep input resolution in one click encoder, the program passes wrong aspect ratio AR to encoder and muxer.

Typically, one click encoder in MeGui passes the AR as if the frames were cropped. But as the frames are not cropped when "Keep input res" is set, the resulting AR is wrong

My last encode, was a 16:9 PAL film. The final AR in the mkv file should be 16:9 also, but is was 2,525. One click thought the black bars were going to be cropped, but they were not

Please Help. :thanks:

Here I add a extract from the log, I have marked in red what I think is wrong

--- OneClick postprocessor
----[NoImage] Desired size: null
----[NoImage] Split size: null
----[NoImage] Auto-detect aspect ratio now: True
----[NoImage] Aspect ratio: 1,823361
----[NoImage] Output resolution: 720x416 [I](frame was not cropped, should be 720*576)
----[NoImage] AVC level: Level 3
----[NoImage] Resolution adjusted for AVC Level: 720x416
----[NoImage] Automatic deinterlacing: True
----[NoImage] Deinterlacing used: #Not doing anything because the source is progressive
----[NoImage] Generated Avisynth script
-----[NoImage] global MeGUI_darx = 154
-----[NoImage] global MeGUI_dary = 61

[AMED]

So it is working as expected, isn't it? :) Yes works perfectly, thanks for the feature :)

EDIT: now i think of it, would it possible to show an error box to the user if one of the downloads are corrupt. Without this a user might wonder why an update is not applying.

[Octo-puss]

Just a question: http://sourceforge.net/projects/megui/ seems to be updated. Is it this patched build or did the devs come back?

[rapscallion]

No, not a patched build on sourceforge. That's 3.3, while patched is ver 3.4.9

[Carpo]

here is a strange little issue, i was trying to encode a video with 3.4.9, the first pass went fine but when i tried to do the 2nd pass x264.exe would not run and megui would not encode the 2nd pass, i thought i may have been something my end so i backed up the jobs folder and removed megui, i then reinstalled it and updated to 3.4.9 again, but the jobs will not show up in the queue nor can i load them when i click on the load tab, nothing happens, i could redo the first passes but one of them took 12 hours so i don't really wish to do that again.

Is this a known error or is there something wrong on my end?

[Octo-puss]

No, not a patched build on sourceforge. That's 3.3, while patched is ver 3.4.9

Okay. But what is going on there, then? I'm confused as hell :D I believe all the devs simply disappeared few months ago.

[rapscallion]

@carpo. You don't mention the output or if it's automated 2 pass that you're using.

I have never been able to get the jobs to reload, all the way back to ver 1051.

If, in fact, you used automated 2 pass there's a method I've used in the past and it worked.

1. Reload your avs script. Select the same preset/settings as before, under "config"
2. Enqueue the jobs, then delete job 1.
3. Still in "config" and then "main". Under "modes" click on the dialog box for passes and change "automated 2 pass" to " 2pass 2nd pass".
4. Go back to the "queue" tab and start job 2.

This should work as long as the 1st pass files are still in the same dir. Good luck !

Edit: As to why it borked job2 in the first palce, I can't answer.
I'm running 3.4.8 w/no problems.

[rapscallion]

Okay. But what is going on there, then? I'm confused as hell :D I believe all the devs simply disappeared few months ago.
Then you haven't been following this thread, or even the last couple of pages. Zathor has picked up the development since last December and is doing a great job.

[Carpo]

@carpo. You don't mention the output or if it's automated 2 pass that you're using.

I have never been able to get the jobs to reload, all the way back to ver 1051.

If, in fact, you used automated 2 pass there's a method I've used in the past and it worked.

1. Reload your avs script. Select the same preset/settings as before, under "config"
2. Enqueue the jobs, then delete job 1.
3. Still in "config" and then "main". Under "modes" click on the dialog box for passes and change "automated 2 pass" to " 2pass 2nd pass".
4. Go back to the "queue" tab and start job 2.

This should work as long as the 1st pass files are still in the same dir. Good luck !

Edit: As to why it borked job2 in the first palce, I can't answer.
I'm running 3.4.8 w/no problems.

Yes your right i forgot about that, and yes it is automated 2 pass, sorry about that, just really tired here atm ;-) i will try your suggestions - thanks

Update, it started the second pass, but its doing the same as before - vfw4x264.exe is taking one core (25%) but x264.exe is no where to be found in the task manager, that and the pc is not as loud as the fans aren't speeding up

update2: after looking in the log i see

--[Information] [30/03/2010 21:11:11] Encoding started
--[Error] An error occurred: x264 [error]: different bframes setting than first pass (8 vs 3)
--[Error] An error occurred: x264 [error]: x264_encoder_open failed

but like i say i have not changed anything between the passes

[rapscallion]

but like i say i have not changed anything between the passes
The only way to know that for sure is to check the log for the first pass to see what the bframes setting is. If it's different, then set the 2nd pass to match.

[Carpo]

The only way to know that for sure is to check the log for the first pass to see what the bframes setting is. If it's different, then set the 2nd pass to match.

if i had kept the logs when i reinstalled i would have, i have set it to redo the whole thing, will see if i get same issue as before, if i do then its not me :-) although i have noticed that the version of x264 that comes with the dev branch (3.4.9) (x264 1510) is slower than the stable tree, losing about 4 fps

[Octo-puss]

Then you haven't been following this thread, or even the last couple of pages. Zathor has picked up the development since last December and is doing a great job.

I have not, that's right. I was kinda busy and didn't need MeGUI at all. Guess the guys could at least hand over the Sourceforge access, but whatever... The most important is that development keeps going :)

[Zathor]

I have the sourceforge access since a few months so everything is fine. Therefore the patched builds mentioned on the first pages of this thread are now the official builds.

[rapscallion]

if i had kept the logs when i reinstalled i would have, i have set it to redo the whole thing, will see if i get same issue as before, if i do then its not me :-) although i have noticed that the version of x264 that comes with the dev branch (3.4.9) (x264 1510) is slower than the stable tree, losing about 4 fpsOk, I was going to suggest reverting back to 3.4.8 (x264 1471 Komisar's kgit generic)

That bframes mismatch was a little strange though.
You wouldn't really us "8", right ?

[JoeH]

I have the sourceforge access since a few months so everything is fine. Therefore the patched builds mentioned on the first pages of this thread are now the official builds.

But you did in fact update the SourceForge build to 3.3, even though that isn't the latest version.

[Carpo]

Ok, I was going to suggest reverting back to 3.4.8 (x264 1471 Komisar's kgit generic)

That bframes mismatch was a little strange though.
You wouldn't really us "8", right ?

its all set by megui profiles, i dont touch anything, and after doing another test run, the first pass went fine, but it wont call x264 for second pass and there is no errors in the logs, so will have to find the old version of x264 from somewhere

[Zathor]

But you did in fact update the SourceForge build to 3.3, even though that isn't the latest version.

Yes, I have updated the SourceForge installer build to 0.3.3. At the moment it is not necessary to update the installer because a connection to the intranet for the tools is mandatory - if only the tools will be updates or the tools and the main program doesn't matter. But this will change with the next stable release. I am planing to release an offline install package which includes all of the necessary files from the update server.

[livetolove92]

[Error] Log
-[Information] Versions
--[NoImage] MeGUI Version : 0.3.4.0
--[NoImage] OS : Windows Seven x64 (6.1.0.7600)
--[NoImage] Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
--[NoImage] Avisynth Version : 2.5.8.5
-[Error] Log for job1 (video, 720p1.mkv)
--[Information] [3/31/2010 8:46:50 AM] Started handling job
--[Information] [3/31/2010 8:46:50 AM] Preprocessing
--[NoImage] Job commandline: "C:\Program Files (x86)\megui\tools\x264\vfw4x264.exe" --preset slower --pass 2 --bitrate 2555 --stats "E:720p1.stats" --thread-input --bframes 5 --b-pyramid normal --b-bias 2 --interlaced --vbv-maxrate 31250 --sar 1:1 --output "E:\720p1.mkv" "E:\Track1.avs"
--[Information] [3/31/2010 8:46:51 AM] Encoding started
--[Error] An error occurred: x264 [error]: ratecontrol_init: can't open stats file
--[Error] An error occurred: x264 [error]: x264_encoder_open failed
--[NoImage] Standard output stream
--[NoImage] Standard error stream
---[NoImage] x264 [info]: 960x408 @ 23.98 fps
---[NoImage] x264 [warning]: interlace + direct=temporal is not implemented
---[NoImage] x264 [warning]: interlace + weightp is not implemented
---[NoImage] x264 [warning]: NAL HRD parameters require VBV max bitrate and buffer size to be specified
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [warning]: VBV bitrate (31250) > level limit (17500)
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
---[NoImage] x264 [warning]: VBV maxrate specified, but no bufsize.
--[Information] [3/31/2010 9:20:38 AM] Job completed

How can I fix it >.< . Plz