MeGUI Bug-Report Thread [Archive] - Page 32

Henrikx

7th December 2006, 23:27

remo7

8th December 2006, 00:15

Avisynth is installed ?
http://www.avisynth.org/
You have to install Avisynth manually (AVI_Mux GUI,also)
Look at Settings !
http://gleitz.info/wiki/index.php/Bild:MeGUI_Settings_Program_Path.jpg
Picture ist from German MeGUI Wiki !

MeGui Wiki (english),you can find here :
http://mewiki.project357.com/wiki/Main_Page

ok here is my settings pic:
http://img293.imageshack.us/img293/5241/ads305zmnnq8.th.jpg (http://img293.imageshack.us/my.php?image=ads305zmnnq8.jpg)

and I instaled Avisynth again (AviSynth_160906)

now eveythings ok and thanks u very much man.

edit :
ohh no, now I have a problem but this is litle tah others.

what about this, why it is doing that?
http://img293.imageshack.us/img293/5068/uo351o351olbw1np0.th.jpg (http://img293.imageshack.us/my.php?image=uo351o351olbw1np0.jpg)

ChronoCross

8th December 2006, 00:38

because your script values for convolution3d are wrong

check the manual

remo7

8th December 2006, 01:07

because your script values for convolution3d are wrong

check the manual

ok but I m trying now and always it is giving same wrong.

how I must do it? convolution3d ?

chipzoller

8th December 2006, 03:15

Not to be pushy, but did anyone from the dev. team ever look into that VobSub indexing problem I mentioned here (http://forum.doom9.org/showthread.php?p=900392#post900392)?

check

8th December 2006, 09:14

development has stopped pending someone finishing whatever-it-is that berriman got halfway through before vanishing.

chipzoller

9th December 2006, 00:52

Yeah I was wondering if dev. had stopped on megui since there haven't been any app releases in a while.

Sharktooth

10th December 2006, 04:01

no, development is just "paused" coz we're "a bit" busy with real life issues.

elguaxo

11th December 2006, 15:29

http://img185.imageshack.us/img185/8933/greywb6.th.png (http://img185.imageshack.us/img185/8933/greywb6.png)

The Greyscale option in the XviD Encoder Configuration adds the -grey parameter to the commandline, but this option is not supported by xvid_encraw.

Greyscale is part of the zones: http://forum.doom9.org/showthread.php?p=913754#post913754

Sharktooth

11th December 2006, 17:37

we only support official xvid_encraw builds.

elguaxo

11th December 2006, 17:58

we only support official xvid_encraw builds.

Do you mean that at my report? I have tested the latest xvid_encraw that was updated by MeGUI itself, and then I tested another xvid_encraw build just in case. Both didn't accept the -grey parameter. See here: http://forum.doom9.org/showpost.php?p=913745&postcount=603

Edit: if there is a version that supports -grey, where can I get it? Thanks!

squid_80

12th December 2006, 02:59

xvid_encraw from xvid's cvs doesn't have a -grey option. Can't get much more official than that.

Sharktooth

12th December 2006, 04:30

oh, sorry...then...
"Huston... we have a problem!"

I suppose a zone should be set then... What would be the correct commandline?

squid_80

12th December 2006, 04:40

If you want to leave the greyscale option where it is in MeGUI and have it affect the whole encode, add the G flag to all existing zones or if there aren't any make a new weight 1.0 zone starting at frame 0 e.g. -zones 0,w,1,G
Since it's a zone option though it might be better to move the setting onto the Zones tab page.

Sharktooth

12th December 2006, 14:33

Yes, it should be moved into zones options. I just didnt know the commadline parameter/flag to set. Thanx.

unskinnyboy

17th December 2006, 12:54

berrinam

17th December 2006, 12:59

If you set the source type yourself, you don't need to analyse.

I'll look into it, though.

berrinam

17th December 2006, 13:15

I found *a* bug (there may be more -- who knows). Here's a quick fix before I sleep (just overwrite your megui.exe with the one here):

http://www.savefile.com/files/345598

remo7

17th December 2006, 13:42

I updated the core to 0.2.4.1005 this morning and I have started getting this error on all the d2v's I tried analyzing since then:

http://img226.imageshack.us/img226/4286/meguierrorue3.png

I tried specifying the source type myself, but same error. Anyone else getting this?

yes man so I have same problem.
it s after update.
how can I take it back or ...

and I know my .vob is progresif and after this step I have a problem more.
it is on bitrate calculator. there is not .avi section when I chose the xvid.

http://img442.imageshack.us/img442/1006/ads305zfdgm3.th.jpg (http://img442.imageshack.us/my.php?image=ads305zfdgm3.jpg)

help please, thanx u.

and my english is not well sorry.

Carpo

17th December 2006, 14:41

I found *a* bug (there may be more -- who knows). Here's a quick fix before I sleep (just overwrite your megui.exe with the one here):

http://www.savefile.com/files/345598

does that link work for anybody else

edit: works now :)

unskinnyboy

17th December 2006, 15:03

I found *a* bug (there may be more -- who knows). Here's a quick fix before I sleep (just overwrite your megui.exe with the one here):

http://www.savefile.com/files/345598OK, that error is gone, but now it doesn't seem to want to finish analyzing (tried with a couple of d2v's):

http://maxupload.com/img/6A1FFDF3.jpghttp://maxupload.com/img/3B72E0D9.jpg

If you set the source type yourself, you don't need to analyse. That isn't intuitive to the end user though. Maybe you should say that in the GUI. I thought the option for manually specifying the source type was to aid MeGUI in the analysis.

cc979

17th December 2006, 15:44

found a cosmetic bug in megui 0.2.4.1005

http://img90.imageshack.us/img90/3526/meguibug01hy4.th.png (http://img90.imageshack.us/my.php?image=meguibug01hy4.png)

keep up the good guys

quinn

17th December 2006, 17:45

Using 0.2.4.1005, does not happen with 0.2.3.2193

Found this crash bug whenever I use "AutoEncode". When I click "Add additional content", and click the que button I get:

MeGUI encountered a fatal error
Reason: Object reference not set to an instance of an object.
Stacktrace: at

MeGUI.AdaptiveMuxWindow.containerFormat_SelectedIndexChanged(Object sender, EventArgs e)

oddball

17th December 2006, 18:42

DVD9 bitrate calculation seems to be off. It came out oversized once I muxed in the AC3 track to an MKV file (I took the AC3 track into account by loading it in the bitrate calculator). It was off by quite a large amount so I could not burn it to a DVD9.

Henrikx

17th December 2006, 20:02

This Bug is unfortunately not repaired...:confused:
http://forum.doom9.org/showthread.php?p=897420#post897420

Limobar

17th December 2006, 20:37

I just used DGIndex via MeGUI on a PAL dvd. The number of frames that is shown in the Avisynth Script Creator is not correct (114560, while the correct number is 143200).

The film length and audio bitrate stated in the bitrate calculator are probably because of this also incorrect.

When I use the exact same version of DGIndex directly (outside MeGUI), the d2v file is correct (143200 frames). The film length and audio bitrate are then also correct in the Bitrate Calculator.

berrinam

17th December 2006, 21:51

I just used DGIndex via MeGUI on a PAL dvd. The number of frames that is shown in the Avisynth Script Creator is not correct (114560, while the correct number is 143200). MeGUI detected that force film was required, and adjusted accordingly. This caused the frame count to be reduced to 80% (143200 * 80% = 114560), and the framerate *should* have been adjusted accordingly. Are you sure it hasn't?

Warpman

17th December 2006, 21:51

clicking [...] on the right side of "Video Output" results in an Open file dialoge, of cause is should be Save file.

Using 0.2.4.1005

chros

17th December 2006, 21:56

Bug at the latest (0.2.4.1005) and this http://www.savefile.com/files/345598 version:
The sharktoth profiles are totally unuseable for me.
Try on the main page:
- select an avs input
- seletct eg. HQ-Insane
- press config
- at the mode select: Const quality (it should do a 1pass encode)
- press OK here, then press Enqueue: see at the queue tab that megui created a 2pass encode

And the bigger problem is that the complete profile system is broken: if you enter a bitrate (eg. 4000) at Automated 2pass mode, it will do the default 1000 kbps encode :(

At least I could see that how amazing the codec at 1000 kbps with a 1280*720 resolution ... :)

Edit: I can circumvent the problem until it will be fixed: after I have choosed the HQ-Insane profile, select the desired setting then press new.

Carpo

17th December 2006, 21:58

atm i know just how berrinam feels - you have a working program - and you think hell why not update it and add some new features - and then it breaks!!! :D

Limobar

17th December 2006, 22:47

MeGUI detected that force film was required, and adjusted accordingly. This caused the frame count to be reduced to 80% (143200 * 80% = 114560), and the framerate *should* have been adjusted accordingly. Are you sure it hasn't?

I'm not sure what you mean. Where do you mean the framerate should have been adjusted accordingly?

After creating the 80% avisynthscript, I used the Bitrate Calculator and found out there were some 'strange' things. I didn't start an encode, because of the values in the Bitrate Calculator.

http://pixel.bitsplitter.com/Pics/MeGUI Bitrate Calculator.JPG

1. Actual movie length is 1h35m28s.
2. Actual bitrate is 384 kbit/s.
3. Actual framerate is 25fps.
4. Actual framerate is 1791 kbit/s.

dngnta

18th December 2006, 04:49

When core updated itself from 0.2.3.2192 to 0.2.4.1005, d2v creation became buggy.

I work from MPEG-2 TV captures (NTSC), so the framerate should be 29.970 (so that I can properly run IVTC or ->60fps conversion on it). However, looking at the d2v the framerate gets written out as 23976 (24000/1001). This is wrooong.

Running dgindex manually, I get the correct framerate written in the d2v file.

berrinam

18th December 2006, 04:51

[EDIT: look to 0.2.4.1007 for the solution to your problems]

@Limobar: it seems like you have an interesting video, which is FILM (normally 29.376fps) but is actually 25fps. I would appreciate it if you could do a few things for me:
Create a d2v file without using MeGUI (so the fps is correct -- 25fps). Send it to me (or upload it here). I'm particularly interested in the very beginning and the end.
Tell me whether this source is genuinely film, which means that two out of every five frames are combed. If you can recognise this yourself, then please do. If not, run your 25fps d2v file through MeGUI's interlace detection (in Avisynth window) and tell me what it says. It would be better to use 0.2.3.2193 for that, since it actually works right now, and it also provides more diagnostic information.

If you want to encode your video right now, then just skip MeGUI for the DGIndex step, and everything should be fine.

berrinam

18th December 2006, 04:55

I work from MPEG-2 TV captures (NTSC), so the framerate should be 29.970 (so that I can properly run IVTC or ->60fps conversion on it). However, looking at the d2v the framerate gets written out as 23976 (24000/1001). This is wrooong.

This is a result of automatic force film detection which MeGUI runs, which will trigger DGDecode's IVTC if deemed necessary. If you want to overrule this, then you can turn Auto Force Film off in the settings.

shadowchen

18th December 2006, 05:08

When core updated from 0.2.3.2192 to 0.2.4.1005,the interface was like this,I think this is a bug.fix it plz.

dngnta

18th December 2006, 09:31

This is a result of automatic force film detection which MeGUI runs, which will trigger DGDecode's IVTC if deemed necessary. If you want to overrule this, then you can turn Auto Force Film off in the settings.
What exactly "deems" it necessary? The file is 100% "video". There is *NO* reason why it should be detected as film.

Frankly, with the default settings it now fucks up all encodes made from TV captures. This *should not happen*.

berrinam

18th December 2006, 11:00

Perhaps this is a bug in MeGUI then. The correct behaviour deems it necessary when it is >95% film.

berrinam

18th December 2006, 11:41

@Limobar and @dngnta: 0.2.4.1007 should fix your problems.

snyft

18th December 2006, 14:03

Anywhere that i can download 0.2.4.1002 because of the new version i cant load avs: http://img344.imageshack.us/my.php?image=errorsp9.jpg

i forgot i use a Swedish version of xp so i will translate it:
"The instruction on "random numbers/letters" referenced to the memory on "Random numbers/letters"
It couldent perform a memory task. Following error returned: "The memory could not be written".

As Hobojobo i can load avs with 0.2.3.2192.

Hobojobo

18th December 2006, 14:55

I can't load avs files either.
With MeGui 0.2.4.100x I get an error message:

The file .... .avs cannot be opened.
Please make sure it's a valid AviSynth script and that....
Error message for your reference: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

With the 0.2.3.2192 everything went just fine.

Limobar

18th December 2006, 16:26

@Limobar: it seems like you have an interesting video, which is FILM (normally 29.376fps) but is actually 25fps. I would appreciate it if you could do a few things for me:
Create a d2v file without using MeGUI (so the fps is correct -- 25fps). Send it to me (or upload it here). I'm particularly interested in the very beginning and the end.
Tell me whether this source is genuinely film, which means that two out of every five frames are combed. If you can recognise this yourself, then please do. If not, run your 25fps d2v file through MeGUI's interlace detection (in Avisynth window) and tell me what it says. It would be better to use 0.2.3.2193 for that, since it actually works right now, and it also provides more diagnostic information.

Link to the requested files and info. (http://download.yousendit.com/CA1BD5E607002E0E)

The source is 100% video, according to DGIndex.
The source is progressive, according to MeGUI.

With version 0.2.4.1007 the source gets processed like it should. Thank you for the quick response. :thanks:

deets

18th December 2006, 17:42

i seem to have a prob with 1008. its not taking the name of the file i put in video output and just uses the name from the avs file

Thunderbolt8

18th December 2006, 17:52

ye, sometimes its even complaining you cant use the same file name, because the ones just being encoded and written, although you already tried to change it like 3 times.

wadim

18th December 2006, 19:06

After autoupdating to 0.2.4.1008 i got interface screen messed up, look at screen, what should i do? http://img182.imageshack.us/img182/3392/untitled1zl6.th.jpg (http://img182.imageshack.us/my.php?image=untitled1zl6.jpg)

JarrettH

18th December 2006, 20:31

In the audio config box I can only check Delay Correction on or off...will it detect the delay from the file name? The usual box I input it in is blanked out.

DeathTheSheep

18th December 2006, 23:02

I did a simple test with 1008. I selected my input AVS (file.avs), and right under it, I quickly changed the filename to file2.264 (No, I did not click the browse button "...").

It didn't work. The output file was 'file.264' which overwrote my old file.264 (which, in some people's cases had been 12-hour encode suddenly lost).

This is the simplest case possible--load avs, save file. And it failed. It didn't save the file with the right name, instead overwriting the old one. Just thought I should report this little yet huge bug before more people start complaining (to me of all people!) that their MeGUI doesn't work.

tecxx

19th December 2006, 02:47

i'm having the same problem as wadmin, but on windows.

the main screen is totally messed up. note that i use "large fonts" in windows system settings, that might be the reason. old version worked fine though....

wadim

19th December 2006, 03:11

I use "large fonts" too, that is the problem i think

dngnta

19th December 2006, 03:28

The file size or average bitrate settings in the Automatic Encoding dialogue is ignored, and it sets always "--btrate 1000" like this:

This job is linked to the next job: job2-2
Starting preprocessing of job...
Preprocessing finished!
Starting job job2-2 at 11:17:03
encoder commandline:
--pass 1 --bitrate 1000 --stats "C:\movies\puuh08.stats" --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --vbv-maxrate 25000 --me dia --merange 12 --threads 2 --thread-input --progress --no-psnr --no-ssim --output NUL "C:\movies\puuh08.avs"

The problem occured when the GUI was tweaked a bit, probably around 0.2.4.1004 or 0.2.4.1005.

Sharktooth

19th December 2006, 03:46