MeGUI: bug reports and feature requests

[Blue_MiSfit]

Nice job, gentlemen! MeGUI is quite usable now - and with a lot of spit 'n' polish compared to the old versions!

I've been using Lord_Mulder's simple launcher up until now, but this is quite useful when I need a queue ;)

~MiSfit

[Zathor]

With the stable build knocking on the door I will not add or change things at the moment beside main bugs. The only other thing is to add support for the new DGIndexNV build 2001 which has a new cli syntax. This seems to be a bigger change because the film handling is moved from the dgi project file to the Avisynth DGSource call but I think it is necessary to add this to the stable build. Therefore I will release (hopefully only one) last dev build before going public.

Additionally I would like to change the version number schema used. With every release to the stable branch I will increase the build number (0.3.1.1060) and set the revision to 0 (0.3.2.0). With every development build I will increase the revision while not changing the build number. With this schema I am able to push out updates to the development server for every small fix. The changelog will include updates for every revision but as soon as a new build number is released I will merge these revision entries. The major and minor version numbers (0.3.1.1060) will not increase at all. Any other suggestions/ideas?


And now to some postings of the last days:

iirc, mainly AAC & subtitles streams (SRT,SSA,VobSub)...
Thanks, the test is still outstanding.

AutoEncode "problem".
Encoded tracks can't be modifed (set up language etc) in adaptive muxer[...]Of cource I can mux it after encoding, but it's not so comfy :)

Please add this as a feature request:
http://sourceforge.net/tracker/?atid=798479&group_id=156112
It is not on my list for the next few days and if not added there it may be lost.

It's still asking for closing the temporary workers here in build 0.3.1.1060.
Just to bring this back ontopic :helpful:
I agree that a temporary worker should be closed automatically without question because it is a temporary worker. Nevertheless I will not add/change it before the stable build and therefore please open a feature request or you have to keep up reminding me.

I noticed that a new version of it [mediainfo] was released and u have been fixing/tweaking stuff in meGUI so i thought i would just ask
Thanks, I have thought that there may be an important fix because of your posting. @all: Please carry on posting new versions of mediainfo or any other tool we are using in MeGUI.

Zathor, there is a small bug in the DG Creator (0.3.1.1060). It displays a warning that no audio tracks are found even if the file you select is a .vc1 or .h264 file.
I would like to remove it completely and independently of the source file. Nevertheless this will not be changed in the next days so please open a feature request (I think it is no bug because there isn't any audio information in these files and therefore the message is correct).

Not sure if you're accepting feature requests or not, but if so, would it be possible to add flac encoding support? I personally use flac a decent amount for archiving stuff from capture and would get good use out of batch converting from video files.
Thanks, new suggestions are welcome. Please open a feature request at sourceforge.

You mean this (http://forum.doom9.org/showthread.php?t=141829)tool? As I recall the issue was there and it eventually disappeared. I think that in it's last iterations the issue was not present but it was when merged with MeGUI. Correct me if I'm wrong.
Thanks, I will have a look at this problem - but very likely not in the next days.


@Zathor : what do you think about the Audio Interface that I made in my own branch (http://megui.svn.sourceforge.net/viewvc/megui/megui/branches/kurtnoise/) ? It's much clearer than the current one imo. Could be great to have it in the trunk or not ?
Thank you very much for your hint. I didn't know that you have some secrets there :) Sadly I had no time to have a look at it but I will add it after the stable build has been released.

[saint-francis]

Thanks, I will have a look at this problem - but very likely not in the next days.


Thanks for any effort at all. It's certainly not a show stopper so please take your time. I also posted about it to Greif in the original thread for the tool.

Thank you for all of your hard work.

[Lambpete]

That's a x264 problem and not MeGUI's fault. You can try a build from x264.nl to see if the problem exists with that build too.

except you can't set the filepath for x264 anymore :(


Any chance on getting this added back in Zathor ?


( I know there are workarounds.. but if it isn't too much trouble to bring that back it would be very useful )

[XhmikosR]

There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.

[TDC.net]

There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.

I second that, leave it fixed.

[TDC.net]

Thanks Zathor for all your improvements, I will create these feature requests.
Thanks again
Raist

[lnatan25]

There are pros and cons. In my opinion, it's better the way it is now.
Any option that takes control from the user cannot be considered a pro in any way.:rolleyes:

[Zathor]

except you can't set the filepath for x264 anymore :(
Any chance on getting this added back in Zathor ?
( I know there are workarounds.. but if it isn't too much trouble to bring that back it would be very useful )

As long as x264 is one of the automatic downloaded tools I will not readd this feature. It has not been an easy decision but I made this decision. Please understand that I will not respond anymore to this request until someone comes up with really good arguments.

Of course you can and should discuss this further! I love to read your opinions.

[nakTT]

There are pros and cons. In my opinion, it's better the way it is now. Just replace x264.exe.
I second that. IMHO the way it is now is better.

[quantum5uicid3]

i think mklink (http://technet.microsoft.com/en-us/library/cc753194%28WS.10%29.aspx)on vista/7 or junction (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx) on 2000/xp is a simple enough solution.

[TDC.net]

Any option that takes control from the user cannot be considered a pro in any way.:rolleyes:

Yes, it can!
Newbies will have less problems that way!

:p

[quantum5uicid3]

i have a feature request. can u add a constant quality mode that also creates the --pass 1/--slowfirstpass stats file for those instances that crf produces an undesirable result. i tried to do it in the custom command line, but can't figure out how to take advantage of the variable filename ".stats" file megui creates in the same directory as source.

[Lambpete]

As long as x264 is one of the automatic downloaded tools I will not readd this feature. It has not been an easy decision but I made this decision. Please understand that I will not respond anymore to this request until someone comes up with really good arguments.

Of course you can and should discuss this further! I love to read your opinions.

Maybe i missed something along the way, but what was the reason for its removal? was it just that it is automatically updated?

I personally have not used any of the automatically updated x264 builds for over a year.

I can respect that some people like it the way it is now.. but can someone explain the advantage of having to manually overwrite your x264.exe file instead of just updating the path?






Any option that takes control from the user cannot be considered a pro in any way.


I agree completely.


Yes, it can!
Newbies will have less problems that way!


I don't see how having the option to set your x264 path poses a problem to newbies learning to encode. I have overseen many the newbie through the process and that is certainly not one of the issues which has ever popped up.

And why should megui be catering to n00bs anyway?
I thought that's what handbrake was for? :P
( which coincidentally does force its users to use their custom x264 build which cannot be overwritten or updated )

[quantum5uicid3]

complications arise from UAC, a process starting processes outside of the program directory needs escalation i think. so not really so much a noob issue, but the unneccsary need to run megui escalated. don't be afraid of symlinks, they are your friend.

[aegisofrime]

I have an extremely puzzling problem that started recently, after I upgraded my Windows 7 RC to the final retail.

I can open .avs scripts, the preview window comes up just fine. After I enqueue and start the job, the job instantly ends with an error. I check the log and the only thing is says is "Standard error stream"

The same .avs script encodes fine with Lord Mulder's simple x64 launcher, so I don't think the problem lies with Avisynth.

I have tried uninstalling MeGUI, installing and updating to build 1060 but that doesn't solve it. :(

[Zathor]

I have an extremely puzzling problem that started recently, after I upgraded my Windows 7 RC to the final retail.

I can open .avs scripts, the preview window comes up just fine. After I enqueue and start the job, the job instantly ends with an error. I check the log and the only thing is says is "Standard error stream"

The same .avs script encodes fine with Lord Mulder's simple x64 launcher, so I don't think the problem lies with Avisynth.

I have tried uninstalling MeGUI, installing and updating to build 1060 but that doesn't solve it. :(

Please post your log, avs file and the source information.

[MOS-Marauder]

@Zathor... I found out why MeGui & DGNVTools crashed here.... The Nvidia Driver dont like it that i have all Memory Slots Occupied. Removing one solved it. (RAM is still OK..also the Removed one)


Chris

[stax76]

@Zathor... I found out why MeGui & DGNVTools crashed here.... The Nvidia Driver dont like it that i have all Memory Slots Occupied. Removing one solved it.

Interesting, was it the same or different memory, how many slots do you have?

[MOS-Marauder]

Interesting, was it the same or different memory, how many slots do you have?

4 Slots and all with the Same Riggs. 4x 2 GB Chaintech Apogee DDR2 Ram.


Chris

[Zathor]

Interesting, I have also the crashes and all my slots are occupied (2x2GB + 2x1GB DDR2)

Btw I have just released build 0.3.1.1061 to the dev update server.

- added force film and DAR detection for DGIndexNV
- added support for new DGIndexNV (requires build 2001 or higher)
- update MediaInfo library and its wrapper to the latest release (0.7.27)

[MuLTiTaSK]

@Zathor

regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?

[rapscallion]

Btw I have just released build 0.3.1.1061 to the dev update server.



Looks like you're getting close to a new stable build ?

I notice that the AVCHD presets have been added, thanks.

[nurbs]

regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?

It still uses DGSource and autostarts the CUVID Server.

[Zathor]

@Zathor

regarding the DGIndexNV crashes does MeGUI use DGSource("") with CUVIDServer or DGMulitSource("")?

By default it uses DGSource (more stable) but you can switch to DGMultiSource in the settings.

[hajj_3]

please can you add 1.778 to the DAR list as that is what tv shows air in, i have to manually add this each time i upgrade a build of megui:(

also is it possible to let it upscale for example, tv shows that air in 544x576, can you we not make them 720x400 when we encode them as the highest resolution i can choose is 544x320 which is poor, xvid will let you choose 720x400.

thanks zathor, you're doing a great job!

[MOS-Marauder]

By default it uses DGSource (more stable) but you can switch to DGMultiSource in the settings.

Where ? (Switch to DGMultiSource...)


Chris

[nurbs]

options->settings->external programs settings-> uncheck "use cuvid server"

[MOS-Marauder]

Ah Unchecking the Server uses Multi? .. Go and checking it...


Chris

[Triccotracco]

please can you add 1.778 to the DAR list as that is what tv shows air in, i have to manually add this each time i upgrade a build of megui:(
!

quoted!

also DAR 1.333 is also useful

:)

[lucassp]

Why are the new DXVA profiles unrestricted? Thanks!

[quantum5uicid3]

because your video card will play unrestricted with 16ref and 16bframes np

i'll be more specific,

1. i found no restriction info in the microsoft api doumentation here, although most of it is beyond my level.
http://www.microsoft.com/downloads/details.aspx?FamilyID=3d1c290b-310b-4ea2-bf76-714063a6d7a6&DisplayLang=en
2. nvidia has certainly solved the limitations that existed previously in all their cards supporting h264 decodinng (8400GS+, pretty much i think) by driver fixes
3. ive found no credible info that limitations still exist that aren't device specific.

[MuLTiTaSK]

@Zathor

:eek: great job you've done with MeGUI already seems like a different program awesome coding

script creator worked pretty flawless with DGIndexNV for me with no problems i have all memory slots on mobo filled so it might be a different source for the crashes reported
only way i could get MeGUI to crash was to use AviSynth cropping aside Nvidia Resizer only then preview window would get mental and crashes would occur note that MeGUI does'nt always crash doing this:)

System

MeGUI Version : 0.3.1.1061
OS : Windows Seven Ultimate Edition x64 (6.1.0.7600)
Latest .Net Framework installed : 3.5 SP1 (3.5.30729.4926)
Avisynth Version : 2.5.8.5


Source
Format : VC-1
Format profile : AP@L3
Codec ID : WVC1
Codec ID/Hint : Microsoft
Duration : 3h 6mn
Bit rate : 18.1 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Resolution : 8 bits
Colorimetry : 4:2:0
Scan type : Progressive
Bits/(Pixel*Frame) : 0.364
Stream size : 23.6 GiB (98%)

AviSynth resizing still frame (works)
http://img51.imageshack.us/img51/5154/ss20100111110557.th.jpg (http://img51.imageshack.us/i/ss20100111110557.jpg/)

AviSynth resizing playing (works)
http://img15.imageshack.us/img15/9808/ss20100111111103.th.jpg (http://img15.imageshack.us/i/ss20100111111103.jpg/)

Script
LoadPlugin("I:\MeGUI\tools\dgindexnv\DGMultiDecodeNV.dll")
DGMultiSource("J:\MeGUI\Watchmen.dgi",fieldop=0)
#deinterlace
crop( 0, 140, 0, -140)

Spline64Resize(1280,528) # Spline64 (Sharp)
LoadPlugin("I:\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise

__film = last
__t0 = __film.trim(134126, 140362)
__t0

job
[Information] Log for job19 (video, test.avs -> test.264)
-[Information] [1/11/2010 11:25:15 AM] Started handling job
-[Information] [1/11/2010 11:25:15 AM] Preprocessing
-[NoImage] Job commandline: "I:\MeGUI\tools\x264\vfw4x264.exe" --profile high --level 4.1 --preset slower --tune film --crf 18.5 --thread-input --vbv-maxrate 31250 --sar 1:1 --aud --output "J:\megui\test.264" "J:\MeGUI\test.avs"
-[Information] [1/11/2010 11:25:17 AM] Encoding started
-[NoImage] Standard output stream
-[NoImage] Standard error stream
--[NoImage] x264 [info]: 1280x528 @ 23.98 fps
--[NoImage] x264 [info]: using SAR=1/1
--[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
--[NoImage] x264 [warning]: VBV maxrate specified, but no bufsize.
--[NoImage] x264 [info]: profile High, level 4.1
--[NoImage]
--[NoImage] x264 [info]: frame I:97 Avg QP:14.85 size: 52150
--[NoImage] x264 [info]: frame P:2226 Avg QP:18.02 size: 19160
--[NoImage] x264 [info]: frame B:3914 Avg QP:20.20 size: 6300
--[NoImage] x264 [info]: consecutive B-frames: 4.1% 17.6% 45.2% 33.0%
--[NoImage] x264 [info]: mb I I16..4: 14.6% 73.0% 12.4%
--[NoImage] x264 [info]: mb P I16..4: 4.7% 9.4% 0.9% P16..4: 45.3% 13.4% 10.3% 0.2% 0.2% skip:15.8%
--[NoImage] x264 [info]: mb B I16..4: 0.2% 1.0% 0.2% B16..8: 40.9% 1.1% 1.3% direct: 5.6% skip:49.7% L0:43.8% L1:49.8% BI: 6.3%
--[NoImage] x264 [info]: 8x8 transform intra:65.7% inter:67.9%
--[NoImage] x264 [info]: direct mvs spatial:98.5% temporal:1.5%
--[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 63.2% 72.5% 43.8% inter: 19.4% 19.3% 1.6%
--[NoImage] x264 [info]: i16 v,h,dc,p: 67% 10% 7% 17%
--[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 9% 8% 8% 10% 14% 12% 14% 11% 14%
--[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 8% 8% 6% 10% 16% 13% 14% 11% 14%
--[NoImage] x264 [info]: Weighted P-Frames: Y:3.9%
--[NoImage] x264 [info]: ref P L0: 51.6% 14.0% 13.9% 6.1% 4.8% 3.6% 2.8% 1.6% 1.5% 0.1%
--[NoImage] x264 [info]: ref B L0: 75.5% 10.9% 5.8% 2.8% 2.2% 1.6% 1.2%
--[NoImage] x264 [info]: kb/s:2225.50
--[NoImage] encoded 6237 frames, 12.54 fps, 2225.50 kb/s
-[Information] Final statistics
--[NoImage] Constant Quality Mode: Quality 18 computed...
--[NoImage] Video Bitrate Obtained (approximate): 2225 kbit/s
-[Information] [1/11/2010 11:33:40 AM] Postprocessing
-[Information] [1/11/2010 11:33:40 AM] Job completed


btw could you share info with stax76 on how you got them working together or any findings you made along the way that could help him accomplish the same feat with StaxRip thanks again

keep up the great coding ;)

[MuLTiTaSK]

@Zathor

Nvidia Resizer no cropping still frame (works)
http://img687.imageshack.us/img687/5481/ss20100111124241.th.jpg (http://img687.imageshack.us/i/ss20100111124241.jpg/)

Nvidia Resizer no cropping playing (works)
http://img687.imageshack.us/img687/12/ss20100111124324.th.jpg (http://img687.imageshack.us/i/ss20100111124324.jpg/)

Nvidia Resizer cropping still frame (crash)
http://img519.imageshack.us/img519/1567/ss20100111124434.th.jpg (http://img519.imageshack.us/i/ss20100111124434.jpg/)

[Kurtnoise]

Please, resize your pictures or post only the link...

[MuLTiTaSK]

@Kurtnoise

done sorry about that:cool:

[Zathor]

btw could you share info with stax76 on how you got them working together or any findings you made along the way that could help him accomplish the same feat with StaxRip thanks again
We talked already about the findings. The problem seems to be that MeGUI (and StaxRip as I understand) are opening a lot of avisynth scripts internal - one after another but in a quick row. The only change from my side inspired by neuron2 was to add a small delay after one avs script is closed and before a new one is opened. This reduced the likelihood of crashes but they are still there. The CUVIDServer is more or less stable (I only get it to crash sometimes during the source analyze) and DGMultiSource is crashing for me during adding a already created avs file as a new job. But not always - it is not predictable. A solution could be to change the way MeGUI handles avs files in order to get information out of them (frames, size, ....) so that it is only needed to open the file once. That’s the reason I believe why some tools have no problems in opening and encoding these files. But to change this in MeGUI would be a huge task.

@all: Thanks for the large amount of bug reports and feature request at the sourceforge project page during the last two days. Ok, bugs are not good at all but it is great that you share your findings.

EDIT:
@Zathor
:eek: great job you've done with MeGUI already seems like a different program awesome coding
Thanks but that is not fair at all. The other developers like Kurtnoise had the hard job to develop the program and functions from scratch. I am only doing small changes here and there. So a big thanks to all of them!

[Capsbackup]

Hopefully I didn't miss this, or if it hasn't been discussed, how do you import the latest presets?
When I start MeGui, it asks if I want to update, and I say yes. It then updates several files, including the option to select the latest presets, but the pop up window that says MeGui needs to restart is selected before I can check all the presets to import.
I seem to remember from older versions of MeGui that you had to either cancel or select the presets before the pop up box to restart MeGui was displayed, thereby avoiding the present problem of restarting MeGui before selecting the presets.
This may just be a cosmetic issue, or maybe its just me, but I have now missed the last update option to import the latest presets on both of my computers.:o

[rapscallion]

Click on Options/update/...select preset collections.

check box "Tx264" and then click "update. Alternately, right click on Tx264 and select "force reinstall". Then just check the presets that you want to update. Then click "update". Done.

[Capsbackup]

Click on Options/update/...select preset collections.

check box "Tx264" and then click "update. Alternately, right click on Tx264 and select "force reinstall". Then just check the presets that you want to update. Then click "update". Done.

Thank you rapscallion, much appreciated. :)

[AnarkiNet]

Just updated to 0.3.1.1061 and DGDecNV reports "invalid license file" when I try and run it from megui but when i just double click the DGIndexNV exe it works fine.

[rack04]

Just updated to 0.3.1.1061 and DGDecNV reports "invalid license file" when I try and run it from megui but when i just double click the DGIndexNV exe it works fine.

Have you copied your license file to the directory MeGUI saved DGIndexNV?

[Richardw322]

Just a dumb question here. I have been using Ver 1051 (updated till 11-19) with Vista to now and it has been working fine. Problem is I want to clean install Win 7 on this machine. Can I just download the file from msg one and let it update or do I have to install an older (ver 1056) one first? I read the whole thread, but my head is spinning here. I keep seeing references to updating from a previous version.

[Lyle_JP]

Just got this downloaded. I've always like MeGui, but last night I tried to convert a half of a basketball game from an HD-PVR recording, and it stopped with a few hundred frames left to transcode. (99.89%)

It happened twice actually since the download. Set it @7pm last night, then got up @ 3am and re-did the encode. Still, same results.

Any ideas?

Sounds like a Jeeb's build problem (x264). No offense to Jeeb, but roughly 75% of his builds crash on me (usually at 99.99%, but sometimes just because I switch user and switch back). The ones from x264.nl are always rock solid. I've had good luck with Techouse's gcc builds as well (if you need the interlaced patch).

[rack04]

Does the MeGUI avisynth script creator default to fieldop=1 or does it analyze the output and determine the pulldown?

[rapscallion]

Sounds like a Jeeb's build problem (x264). No offense to Jeeb, but roughly 75% of his builds crash on me (usually at 99.99%, but sometimes just because I switch user and switch back). The ones from x264.nl are always rock solid. I've had good luck with Techouse's gcc builds as well (if you need the interlaced patch).
Your post is timely because last night I tried a test encode of a 1080i source (1061/jeebs 1376 /x264 AVCHD-2 pass preset) and got this warning in the error stream :
[NoImage] Standard error stream
---[NoImage] avs [info]: 1920x1080 @ 29.97 fps (17981 frames)
---[NoImage] x264 [warning]: interlace + weightp is not implemented

I've read on the Wiki that Megui is inefficient for interlace encodes so, in the past, I've unchecled the interlace box and encoded progressive.(ie 1920x1080i to 1280x720p)

What does the TH Interlace patch do and am I better off encoding with his build and do interlace or encode progressive ?

[zamwow]

Could you guys take the misc tab in x264 configuration out of the advanced settings? (and merge it with the main tab or something)

[Lyle_JP]

I think all the patch does is (blah blah blah... deleted)

Nevermind. The patch just "converts" 23.976 progressive HD material to 29.970 interlaced by flagging the progressive frames with pulldown info. This makes the stream compliant with the HD-DVD spec, among others (I guess Scenarist needs this too).

I haven't had any problems using weightp with interlaced encoding (but the only encoding I did was 480i and I only use it in blind mode).

[rapscallion]

From my post : "1061/jeebs 1376 /x264 AVCHD-2 pass preset"

Also, I'm encoding to rawavc, if that makea any difference.

Btw the encode completed successfully and the vid looks fine, but I'm still curious why I got that warning/error ?

Edit: wow! 16 posts in 6 years Lyle, you really are a post whore :)

[rapscallion]

I think all the patch does is (blah blah blah... deleted)

Nevermind. The patch just "converts" 23.976 progressive HD material to 29.970 interlaced by flagging the progressive frames with pulldown info. This makes the stream compliant with the HD-DVD spec, among others (I guess Scenarist needs this too).

I haven't had any problems using weightp with interlaced encoding (but the only encoding I did was 480i and I only use it in blind mode).
OK, Lyle thanks for the update. In the interim, I found this post in answer to interlace discussion:
Jeeb (http://x264.fushizen.eu/) or techouse (http://x264mirror.tk/) builds.

I'd suggest using 1352 since there is some bug reports from 1353/1354. Also if you use 1320+ you'll want to use x264 --weightp 0 to avoid video corruption in some standalones and coreavc, and you also won't lose 10-15% speed.

So, for the time being, I'm going to disable weightp as my encodes are for Standalone AVCHD.
However, per the warning , x264 disabled it anyway.