View Full Version : MeGUI: bug reports and feature requests
Guest
20th January 2010, 18:30
i have build 2.0.0 beta 3 Use the latest build: DGDecNV build 2003!
TheProfosist
21st January 2010, 01:21
Use the latest build: DGDecNV build 2003!
hmm i though that was what i had because i just went to this site yesterday to get it http://neuron2.net/dgdecnv/dgdecnv.html
homefully 2003 will fix some of the huge pixelation that i just got when encoding also
TheProfosist
21st January 2010, 01:47
ok dled 2003 got dgi file. still using dgindexnv outside megui because i need to crop but i can now put a dgi files right into the script editor which is good. but im having problems with the fieldop option because i dot know how to tell the difference between something being 3:2 pulldown or interlaced
Guest
21st January 2010, 01:55
"Build 2003" and "2.0.0 beta 3" are not the same thing!
I recently went to the 4 digit build number.
I answered your 3:2 versus interlaced question in the DGNV thread.
TheProfosist
21st January 2010, 02:09
"Build 2003" and "2.0.0 beta 3" are not the same thing!
I recently went to the 4 digit build number.
I answered your 3:2 versus interlaced question in the DGNV thread.
yep got it! thanks for all the help! i must have just started useing the day u switched
CIHx264
21st January 2010, 07:37
Hi Zathor, thanks for taking over megui and putting in, what must be a lot of work.
I may have found a bug in the x264 configuration.
In the Frame-Type tab if I set the B-Pyramid to disabled, and then move the Presets slider to any position the B-Pyramid stays disabled.
But if I set it to normal and then move the slider, it stays on normal on every position except Ultra Fast where it is set to disabled. Moving it back to a slower setting B-Pyramid stays disabled.
Is this how it’s supposed to work?
Puncakes
21st January 2010, 09:35
BeSplit doesn't appear to be included, but is required for the audio cutter. It's also called from the main megui directory rather than a folder in the tools directory. Are these intended? If not, the latest BeSplit can be found here (http://ffdshow.faireal.net/mirror/tmp/besplitv0.9b7.zip).
MOS-Marauder
21st January 2010, 12:26
Use the latest build: DGDecNV build 2003!
MeGui still uses 2002 ;)
Chris
I found something out... If i want to Crop a Source i cannot use NV Resize due Dimensions are not ok then. (error Message bust be Multiple by.... and so on.)
Is there a way to do the cropping also in the DGI Source Line?
Edit: found a bad but working solution.... I Cropped with DGIndexNV and after creating the AVS in MeGUI (Enabling NV Resizer) i entered manually in the AVS the final Resolution. Quick n Dirty but worked due in MeGui i cannot go over the input resolution ..eg if its 1244x720 i cannot enter 1280x720.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Im not sure if i have to enter left/right as positive or neg (2 or -2 for example like @ avisynth)
Chris
jmrenrav
21st January 2010, 19:56
I have a small request if possible.
Can you add an option for 2 pass encoding via Nero AAC Encoder? I have ran into some problems with the encoder giving me an error message, especially 5.1 HE audio. I manually created a 5.1 Wav using Besweet and replicated the same errors. Once I enabled the 2 pass option, everything worked great.
Errors were generated using directshow and avi input with MeGUI.
jmrenrav
21st January 2010, 20:02
MeGui still uses 2002 ;)
Chris
I found something out... If i want to Crop a Source i cannot use NV Resize due Dimensions are not ok then. (error Message bust be Multiple by.... and so on.)
Is there a way to do the cropping also in the DGI Source Line?
Edit: found a bad but working solution.... I Cropped with DGIndexNV and after creating the AVS in MeGUI (Enabling NV Resizer) i entered manually in the AVS the final Resolution. Quick n Dirty but worked due in MeGui i cannot go over the input resolution ..eg if its 1244x720 i cannot enter 1280x720.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Im not sure if i have to enter left/right as positive or neg (2 or -2 for example like @ avisynth)
Chris
Are you talking about when you crop it comes up with numbers divisible by 2 and you change it to a uneven number it gives you that error message?
I found a workaround by converting it to RGB32 before the crop and then back to YV12 after resize. I don't even like the idea of having one line of movie cropped if it's not needed ;)
Inspector.Gadget
21st January 2010, 20:07
If you need to crop by uneven numbers to reach an ultimately even width or height, you can pad the picture with AddBorders() and then crop it evenly (including cropping the borders) in the YV12 colorspace to end up with the same result as if you were able to crop by an odd number.
jmrenrav
21st January 2010, 20:29
If you need to crop by uneven numbers to reach an ultimately even width or height, you can pad the picture with AddBorders() and then crop it evenly (including cropping the borders) in the YV12 colorspace to end up with the same result as if you were able to crop by an odd number.
Oh wow that might help me alot, so here is an example of my current
# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\Widescreen\A KNIGHTS TALE WS\VIDEO_TS\VTS_01_1.d2v", info=3)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, threads=0)
#deinterlace
ConvertToRGB32()
crop( 5, 54, 0, -59)
Spline36Resize(720,368) # Spline36 (Neutral)
ConvertToYV12()
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
and I could clean it up to look something like this...
# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("E:\Widescreen\A KNIGHTS TALE WS\VIDEO_TS\VTS_01_1.d2v", info=3)
#deinterlace
addborders(1, 0, 0, 1)
crop( 5, 54, 0, -59)
Spline36Resize(720,368) # Spline36 (Neutral)
LoadPlugin("C:\Program Files (x86)\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise
Wouldnt need any color space conversions this way, nice!
salatoimikud
21st January 2010, 22:22
When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22
But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.
What the hell? :devil:
Zathor
21st January 2010, 23:34
I may have found a bug in the x264 configuration.
In the Frame-Type tab if I set the B-Pyramid to disabled, and then move the Presets slider to any position the B-Pyramid stays disabled.
But if I set it to normal and then move the slider, it stays on normal on every position except Ultra Fast where it is set to disabled. Moving it back to a slower setting B-Pyramid stays disabled.
Is this how it’s supposed to work?
Simply: yes :rolleyes:Of course it is not perfect but as long as you cannot lock a value this behaviour is more or less necessary. Otherwise every slider move will revert the value back to a default value. Ideas are welcome!
BeSplit doesn't appear to be included, but is required for the audio cutter. It's also called from the main megui directory rather than a folder in the tools directory. Are these intended? If not, the latest BeSplit can be found here (http://ffdshow.faireal.net/mirror/tmp/besplitv0.9b7.zip).
BeSplit has not been included in the past as I know and I do not know why. You can specify the path to BeSplit in the MeGUI settings.
MeGui still uses 2002 ;)
It should be updated at the weekend.
Maybe it is possible to make it that way that the Cropping Paramters are entered in the .dgi file by MeGui on enabling HW Resize? (CLIP 16 20 0 0 - top/bottom/left/right)
Can you create a feature request at the sourceforge project page, please? Otherwise it may get lost.
Should NV resize be the default option if DGIndexNV is used?
Can you add an option for 2 pass encoding via Nero AAC Encoder? I have ran into some problems with the encoder giving me an error message, especially 5.1 HE audio. I manually created a 5.1 Wav using Besweet and replicated the same errors. Once I enabled the 2 pass option, everything worked great. Errors were generated using directshow and avi input with MeGUI.
Please create a feature request. Thanks!
When i use Megui version 0.3.1.1056 then i have
x264 DXVA-SD-Insane profile 2 pass encoding FPS ~22
But when i use 0.3.3.0 then same profile 2 pass encoding FPS is only ~3.
What the hell? :devil:
http://forum.doom9.org/showthread.php?p=1366376#post1366376
quantum5uicid3
22nd January 2010, 00:10
since jeeb appears to be afk, here's the komisar 1400kGIT generic builds for testing.
http://www.mediafire.com/?uynmhizymyt
NAL HRD 1.0 is included
MOS-Marauder
22nd January 2010, 00:50
Na u get me wrong.
Normally i do Crop and Resize in Megui.
When i enable NV Resize avisynth does the following...
Inputs the already resized Video and THEN appys the (now wrong) crop values from MeGui.
So i ask for a way IF enabling NV Resize that MeGui alters the DGI files with the Values and disables the crop in the avs File.
Chris
MOS-Marauder
22nd January 2010, 00:52
It should be updated at the weekend.
...
Can you create a feature request at the sourceforge project page, please? Otherwise it may get lost.
Should NV resize be the default option if DGIndexNV is used?
No need to hurry done it already manualy (even if Megui still shows 2002)...
Ok i do. I can say this only for me, but if i use NV i always use the Deinterlace (if nessesary) and always the NV Resizer.
Chris
tebasuna51
22nd January 2010, 01:49
Can you add an option for 2 pass encoding via Nero AAC Encoder?
Is not possible.
For the 2 pass encode NeroAacEnc need a physical wav file like input. And AviSynth send the audio data to NeroAacEnc STDIN.
Xvid or x264 can do 2 pass because in first pass write the 'stats' file and the second pass read this file. This method isn't supported by NearoAacEnc.
BTW, I think Nero developers are working in the problem (the crash with HE encode).
Zathor
22nd January 2010, 20:45
I have updated a few tools (x264, mkvtoolnix, dgindexnv). I'm only writing this because I have moved to the x264 build from Komisar and replaced the avs4x264 file with a new one from alwa. This should fix the problem with DGDecode_mpeg2source but I did not test it and therefore vfw4x264.exe is still used for x64.
Can you please try out the avs4x64 file and compare it in terms of speed to vfwx264? (Simply rename avs2x264 to vfw2x264)
Poutnik
22nd January 2010, 21:24
Note that I am not very familiar with 32 to 64 process piping, or with piping at all.
Proces explorer I/O monitoring shows VFW4x264 and X264_64 are exchanging about 40 MB of data per second.
Is it real writing /reading to/from disk of temporary passover files ?
CIHx264
22nd January 2010, 22:59
Simply: yes :rolleyes:Of course it is not perfect but as long as you cannot lock a value this behaviour is more or less necessary. Otherwise every slider move will revert the value back to a default value. Ideas are welcome!
Zathor, I’m now very confused.
Slider in position -Very Fast-
P-frame Weighted Prediction = Disabled
Adaptive B-Frames = 1-Fast
B-Pyramid = Disabled
M.E. Algorithm = Diamond
Subpixel Prediction = 01-QPel SAD
MV Prediction Mode = Spatial
Trellis = 0-None
Slider in position -Medium-
P-frame Weighted Prediction = Smart
Adaptive B-Frames = 1-Fast
B-Pyramid = Disabled
M.E. Algorithm = Hexagon
Subpixel Prediction = 07-RD on all frames
MV Prediction Mode = Spatial
Trellis = 1-Final MB
Slider in position -Very Slow-
P-frame Weighted Prediction = Smart
Adaptive B-Frames = 2-Optimal
B-Pyramid = Disabled
M.E. Algorithm = Multi hex
Subpixel Prediction = 10-QP-RD
MV Prediction Mode = Auto
Trellis = 2-Always
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo. Does this indicate that we should never use B-Pyramid settings or should it be treated as the items on the Main tab that are not affected by the slider.
I would have expected B-Pyramid to change from Disabled in Very Fast to Normal in the Medium position of the slider. With Strict added somewhere along the way.
Thank you for your patience.
nurbs
22nd January 2010, 22:59
Note that I am not very familiar with 32 to 64 process piping, or with piping at all.
Proces explorer I/O monitoring shows VFW4x264 and X264_64 are exchanging about 40 MB of data per second.
Is it real writing /reading to/from disk of temporary passover files ?
The data passed from vfw4x264 to x264_64 is the uncompressed video after avisynth processing (width x height x 12 bits per frame). That's much more then the harddisk IO because only the compressed streams are read and written.
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo. Does this indicate that we should never use B-Pyramid settings or should it be treated as the items on the Main tab that are not affected by the slider.
I would have expected B-Pyramid to change from Disabled in Very Fast to Normal in the Medium position of the slider. With Strict added somewhere along the way.
b-pyramid isn't used by any of the presets, because it didn't work with mb-tree until a month or so ago. The presets haven't changed since then. Dark Shikari mentioned that he is thinking about making --b-pyramid normal default, because it should give better quality and speeds things up a little. The speedup is more noticeable when you use many b-frames with --b-adapt 2. --b-pyramid strict is only there for blu-ray compatibility. It helps fast forwarding but hurts compression in comparison to normal.
Alf Bundy
22nd January 2010, 23:05
Can you please try out the avs4x64 file and compare it in terms of speed to vfwx264? (Simply rename avs2x264 to vfw2x264)
Just updated to x264 1400 and made 2 quick tests :
- Test 1 : Source MPEG-2 decoded with DGmultiSource()
640x480 25fps (44min 35")
avs4x264.exe - Fast 1st pass : avg FPS = 72,92fps - 15min 16"
vfw4x264.exe - Fast 1st pass : avg FPS = 80,73fps - 13min 49"
- Test 2 : Source VC-1 ES decoded with DGmultiSource()
1280x544 23.976fps (1000 frames)
avs4x264.exe
- Fast 1st pass : avg FPS = 27,04fps - 36 sec
- 2nd pass : avg FPS = 3,5fps - 4min 46"
vfw4x264.exe
- Fast 1st pass : avg FPS = 27,69fps - 36sec
- 2nd pass : avg FPS = 3,51fps - 4min 45"
Win7 x64, C2D E7400 @ 3Ghz, GPU = NV 9800GTX+
MeGUI 0.3.3.0, DG tools build 2005
PS : about MeGUI's version , in update (dev. server) I see Existing version 0.3.3.0 / latest version 0.3.2.3
Is that normal ?
CIHx264
22nd January 2010, 23:23
b-pyramid isn't used by any of the presets, because it didn't work with mb-tree until a month or so ago. The presets haven't changed since then. Dark Shikari mentioned that he is thinking about making --b-pyramid normal default, because it should give better quality and speeds things up a little. The speedup is more noticeable when you use many b-frames with --b-adapt 2. --b-pyramid strict is only there for blu-ray compatibility. It helps fast forwarding but hurts compression in comparison to normal.
Thank you, that answers my question. So is it OK to use B-Pyramid with the slider in the Slow position (all items up to date, stable server) or should I wait until it is officially added?
nurbs
22nd January 2010, 23:39
Whatever you prefer. There is no technical (except for blu-ray), quality or speed related reason not to use it as far as I know. Personally I use it.
MOS-Marauder
23rd January 2010, 11:17
I have updated a few tools (x264, mkvtoolnix, dgindexnv).)
I love You ;)
Btw i wrote the Feature Request @Sourceforge.
Chris
Zathor
23rd January 2010, 12:25
Just updated to x264 1400 and made 2 quick tests
Thank you very much. So at least based on your and my tests there is no need to switch back to avs2x264.
PS : about MeGUI's version , in update (dev. server) I see Existing version 0.3.3.0 / latest version 0.3.2.3
Is that normal ?
Thanks - fixed.
Zathor, I’m now very confused.
All the settings change with the slider position, as would be expected.
All except B-Pyramid, it stays the same in all positions including Placebo.
The whole preset handling in MeGUI is in parts confusing. Beside my rather small changes the complete interface has to be reworked. But I would like to wait so that the new things like the device, resize, ... handling in x264 will be revealed.
Btw i wrote the Feature Request @Sourceforge.
Thanks!
TheSane
23rd January 2010, 13:18
I Have a question. I installed my pc wiht Windows 7, before it runs with Windows Vista.
When i now want to recode a Movie (BR) and select 2pass (vbr) the first Job don't comes to an end and shows no progress. It makes no difference if i use predefined or self configured profile. When i use a 1pass (ex. BR Standard), it will start and show progress.
So i think i have a problem with the first pass job. How can i fix it?
Triccotracco
23rd January 2010, 14:07
The whole preset handling in MeGUI is in parts confusing. Beside my rather small changes the complete interface has to be reworked. But I would like to wait so that the new things like the device, resize, ... handling in x264 will be revealed.
:goodpost::thanks:
7ekno
23rd January 2010, 22:03
Well done Zathor!!!
I have only just come back to GUI's since MeGUI broke (which forced me to CLI/CMD files) ...
This is an awesome job, you rock for reviving the MeGUI project!!
Just a big thanks from an old user that appreciates the effort ;)
7ek
Zathor
23rd January 2010, 22:54
0.3.3.1
- [VobinputWindow] added mts as supported file extensions
- [MainForm] added information to the main window title if auto update is activated and the development server is used
- [VobinputWindow] Removed warning if no audio can be found. Feature request #2847468
- [JobWorkerWindow] Temporary worker will be closed automatically. Feature request #2928875
- [DAR] + [ARChooser] added 4:3 and 16:9 DAR
AMED
24th January 2010, 02:28
Is there any chance of changing the default supported file mask in the HD-DVD\Blu-ray Stream Extractor(in file mode) from mkv to all supported files?
Zathor
24th January 2010, 06:43
Is there any chance of changing the default supported file mask in the HD-DVD\Blu-ray Stream Extractor(in file mode) from mkv to all supported files?
Which file extensions are missing?
AMED
24th January 2010, 06:58
nothing is missing, it just defaults to look for only .mkv's and not to all supported files. so you have to keep manually changing it if you are not dealing with .mkv's.
http://img204.imageshack.us/img204/6634/mkv.th.png (http://img204.imageshack.us/i/mkv.png/)
nesta
24th January 2010, 10:38
I have a problem with x264 encoding in latest development build. It wont use my set reference frames in config or custom command line. No matter what I set, it always uses 3. Also noticed most changes made in profile config dont seem to update the command line often.
Elbart_
24th January 2010, 13:38
Because next to everything is done via custom commandline instead of the dialog, i.e. BluRay 2-pass: Picture (http://i49.tinypic.com/2008pjl.png)
nesta
24th January 2010, 21:10
Yes but even when i edit the custom command line, ill check final encode after in mediainfo, avinaptic, etc.. and it still didnt use the settings i set. I check megui log to see the settings used and there will be no mention of reference frames and other options that i set in profile and custom command line. It seems to have a mind of its own :p
Zathor
24th January 2010, 21:15
Please post your log and profile so that we can reproduce it.
Zathor
24th January 2010, 23:46
0.3.3.2
- [HDBDStreamExtractor] changed default file input type
- [InputBox] set initial focus to text box. Feature request #2938589
- [InputBox] if text box has focus pressing "enter" will call the ok event and "escape" the cancel event
- [tsMuxeR] fix final m2ts file creating in OneClick. Bug #2936118
Poutnik
25th January 2010, 07:58
The data passed from vfw4x264 to x264_64 is the uncompressed video after avisynth processing (width x height x 12 bits per frame). That's much more then the harddisk IO because only the compressed streams are read and written.
Dealing with uncompresed video is obvious to me.
I was just curious why Process Explorer marks tis data flow by same way as reading source by vfw4x264 and writing encoded h264 by x264_64..... ( i.e I/O read bytes/s, I/O write bytes/s)
aMvEL
25th January 2010, 10:33
Indexing a dvd-folder with multiple vob-files with dgindexnv only indexes the first (selected) vob, in contrary to dgindex which indexes all vobs when you select the first.
Is this intended, or a bug? Because as of now I have to manually open dgindexnv and select all vobs and index them.
Zathor
25th January 2010, 13:24
Indexing a dvd-folder with multiple vob-files with dgindexnv only indexes the first (selected) vob, in contrary to dgindex which indexes all vobs when you select the first.
Is this intended, or a bug? Because as of now I have to manually open dgindexnv and select all vobs and index them.
Bug or not - it should be investigated (and changed). It may be a problem in the behavior of DGIndex/DGIndexNV or MeGUI.
buzzqw
25th January 2010, 14:55
any hope for fixing the proxy support (for live update)?
BHH
Alf Bundy
25th January 2010, 15:20
Bug or not - it should be investigated (and changed). It may be a problem in the behavior of DGIndex/DGIndexNV or MeGUI.
It's the behavior of DGindexNV.
If you open only the file _0 of a such a sequence :
VOB_0
VOB_1
VOB_2
DGindexNV doesn't autoload _1 and _2.
Zathor
25th January 2010, 15:59
any hope for fixing the proxy support (for live update)?
BHH
I do not have/need a proxy and therefore I cannot reproduce and fix it.
Zathor
25th January 2010, 16:00
It's the behavior of DGindexNV.
If you open only the file _0 of a such a sequence :
VOB_0
VOB_1
VOB_2
DGindexNV doesn't autoload _1 and _2.
Ok, in this case the best way is to post this to the DGIndexNV thread (if not done already) as a feature request.
stax76
25th January 2010, 16:30
@Zathor
Use:
-i file1, file2
Unfortunately there is a comma as separator needed, this isn't common practice but for a GUI usually no problem, in some situations it is a problem (operating system or application not having a appropriate macro)
aMvEL
25th January 2010, 17:18
Ok, in this case the best way is to post this to the DGIndexNV thread (if not done already) as a feature request.
Well, DGIndexNV acts just like DGIndex-regular ... none of them open all vobs automatically ... so you need to select and open all files at once.
I'm guessing MeGUI opens all vobs with DGIndex/DGAVCIndex, because it indexes the whole movie with those tools.
So the same thing needs to be implemented when using DGIndexNV, since you can't select multiple files for indexing with MeGUI, only one single file.
Zathor
25th January 2010, 17:24
any hope for fixing the proxy support (for live update)?
BHH
Ok, I did a quick test with a proxy without authentication and I could download files without problems.
stax76
25th January 2010, 17:25
none of them open all vobs automatically
DGIndex should still have such auto load feature and neuron2 didn't want to implement it for other index applications.
All index applications have CLI documentation!
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.