MeGUI Bug-Report Thread [Archive] - Page 12

Doom9

13th February 2006, 06:34

Please can you make sence of thisYou need to wrap paths that include spaces with "s.. so start with "D:\Mpegs\psp\Me Gui\x264.exe". MeGUI doesn't have to do that for technical reasons.

berrinam

14th February 2006, 11:50

Hey bob0r, try build 0.2.3.2090 out for the x264 dialog. I've redone a lot of it, so the momentarily flashing checkboxes should be gone, and I've done some checking for all the bugs you mentioned.

FooFighter007

14th February 2006, 20:57

>I use the current 2090 version and came across a Problem in the calculator window. In the former releases the Area "Results" displayed >all vital infos as Average Bitrate when I changed my parameters in the "Total Size" area. Now it stays zero.

! after a recompile from cvs it was ok - ignore this posting !

Regards,

Foo

Sharktooth

17th February 2006, 14:26

MP3 audio config dialog has something weird.
also when selectin VBR the bitrate is grayed out.

dimzon

17th February 2006, 16:26

MP3 audio config dialog has something weird.
also when selectin VBR the bitrate is grayed out.
fixed

bkman

18th February 2006, 13:54

Bug in buld 2091: In bitrate calculator Number of Frames value changes to different values as you enter one. Eg. try 62650 @ 25fps and you will get 62500 instead. And right after this, clearing and typing any other number will return as a 0 instead.

berrinam

18th February 2006, 14:10

Sharktooth

18th February 2006, 14:14

http://sourceforge.net/tracker/index.php?func=detail&aid=1396777&group_id=156112&atid=798476

foxyshadis

19th February 2006, 08:41

Minor bitrate calc error: It seems you can't paste numbers into any of the numeric fields, which can slow things sometimes. :p (Maybe this is related to the onKeyDown/onChange issue?)

Oh, and when the preview is closed, it switches back to the last application, not the main megui window, which is quite annoying if you're quickly opening up a lot of scripts in it.

Raithmir

19th February 2006, 10:32

With 2090 I am still having problems with the shutdown when finished.

If I select the tick box before I start a job (any job, could be audio encode), then it's fine. However, if it is not ticked and I've already started a job but decide I want it to shut down after its finished and tick the box, then it doesn't shut down.

Raithmir

19th February 2006, 14:08

Also, I've created my own audio encoding profiles, if I load my ac3 audio then select a profile from the drop down box, clicking on queue give an error "audio input/output types are incompatible". I have to click on config, then on ok without changing anything, adding it to the queue then works fine.

Raithmir

19th February 2006, 14:12

...and another related to profiles. On the main input tab, select your video profile, and click on config. The profile box on the configuration window isn't populated, then clicking ok on the configuration window blanks out the profile selection when you return to the main window.

Mutant_Fruit

19th February 2006, 14:19

I've figured out why the digits keep changing in the framerate field. Basically, i think the "isUpdating" boolean isn't being used correctly. When the user is typing in a framenumber, in certain cases that number is getting overwritten by the "UpdateTotalFrames" method, which recalculates the number of frames based on the "seconds" textbox.

Ok, i'm performing some refactoring on the calculator to hopefully sort that out...

Mutant_Fruit

19th February 2006, 16:53

Patch for calculator is up on sourceforge (https://sourceforge.net/tracker/index.php?func=detail&aid=1434639&group_id=156112&atid=798478). Should have that fixed up nicely, also fixed a bug or two that i noticed with the numeric updown controls which resulted in isUpdating not resetting to false.

Sharktooth

19th February 2006, 19:34

patch committed

Doom9

20th February 2006, 12:56

@Raithmir: does your shutdown problem ocurr when you have megui minimized to the try, or can you reproduce it when it's on screen as well?

shon3i

20th February 2006, 15:01

dimzon

20th February 2006, 15:03

I have same problem and i ask for this problem few times. Nothing change since build 2033.
Can you try such experiment:

Create AVS:

Version() + Version() + Version() + Version() + Version()

Unload every program from memory and system tray

Run MeGUI and try autoshutdown feature again (without sending MeGUI to system tray)

Does bug reproduced?

Doom9

20th February 2006, 15:03

I have same problem and i ask for this problem few times. Nothing change since build 2033.And me and others have repeatedly asked for additional information (see the post right above yours) and never gotten an answer..

shon3i

20th February 2006, 15:09

Run MeGUI and try autoshutdown feature again (without sending MeGUI to system tray)
Same thing. Only shutdown when i abort the job

dimzon

20th February 2006, 15:13

Same thing. Only shutdown when i abort the job

does you perform Unload every program from memory and system tray before? Can you post here list of running processes?

shon3i

20th February 2006, 15:20

Unload every program from memory and system tray Only in memory is explorer and some system porcesses total nuber of proceses is 25 .I dont have problems with shutdown windows and in virtualdub shutdown work fine and other programs like gordianknot.

Sharktooth

20th February 2006, 15:40

again... for everyone that has the shutdown problem...
does your shutdown problem ocurr when you have megui minimized to the try, or can you reproduce it when it's on screen as well?

Kostarum Rex Persia

20th February 2006, 15:41

Well, same bug happens on my machine. I unloaded from memory and system tray every program, but bug still remain.

Sharktooth

20th February 2006, 16:26

... does your shutdown problem ocurr when you have megui minimized to the try, or can you reproduce it when it's on screen as well?

shon3i

20th February 2006, 18:29

... does your shutdown problem ocurr when you have megui minimized to the try, or can you reproduce it when it's on screen as well?
I tried everything what you and dimzon says but nothing help. Only work when i abort job or job duration <1min and audio encoding but not in tray.

Raithmir

20th February 2006, 19:38

@Raithmir: does your shutdown problem ocurr when you have megui minimized to the try, or can you reproduce it when it's on screen as well?

I've never used the minimise to tray function. I usually leave the main form and the progress window open on screen overnight, although it'll sometimes be minimised to the task bar.

shon3i

20th February 2006, 21:36

I've never used the minimise to tray function. I usually leave the main form and the progress window open on screen overnight, although it'll sometimes be minimised to the task bar.
Aslo like Raithmir

bkman

21st February 2006, 08:22

The Bitrate Calculator behaves very weirdly when entering the number of frames
Description: See http://forum.doom9.org/showthread.php?p=787432#post787432
Status: Not yet solved

Seems to be fixed in build 2092. But now changing Length in Seconds is not updating the frames, and the bitrate doesn't get recalculated.

Sharktooth

21st February 2006, 08:26

yes, mutant_fruit patch.

Raithmir

21st February 2006, 17:29

Build 2091

Not sure if this is a bug or just the way it has been coded (in which case consider this a feature request :)). I had several jobs in the queue and started it going, I later decided I wanted it to end after the current job so moved the running job to the bottom of the queue expecting it to finish that job then realise it's at the end of the queue and stop. However, it finished the job and started again from the top of the queue.

Doom9

21st February 2006, 18:22

@Raithmir: if you want to stop the queue... press stop ;) The currently active job will be processed till the bitter end, and then megui will gracefully stop. Queue position just signifies when in relation to the start a job will be processed.. not if it will or not... only status (anything not in waiting state will not be processed) can help you there, or stopping the queue.

Mutant_Fruit

21st February 2006, 18:30

yes, mutant_fruit patch.
*cough* whoops. I'll fix that in the next hour or so. :stupid:

Mutant_Fruit

21st February 2006, 23:17

Patch will be on sourceforge in 2 mins. Should be all good now. Had to move one line of code 2 lines down :P

Sharktooth

22nd February 2006, 23:11

patch committed

Sharktooth

22nd February 2006, 23:29

is it correct when selecting MP3 the second audio track radio button gets greyed out?
or is it a bug? (in that case a patch is ready)

Doom9

22nd February 2006, 23:37

is it correct when selecting MP3 the second audio track radio button gets greyed out?yes.. at least for avi. but all those limitations are no more in my dev builds (which don't even compile as of now).

Raithmir

23rd February 2006, 08:42

Doom9

23rd February 2006, 09:24

But that just stops it at the end of the current pass doesn't it?Yes, but the answer also gives what you want. There are 3 ways to stop the queue: abort (stops processing right away and goes to sleep), stop (stops processing once the current job has been completed and then goes to sleep) or make sure no job eligible for encoding is in the queue anymore (by either deleting jobs in status waiting, or changing their status to postponed). With these, you should be able to handle any scenario you can come up with. It's one a one click thing, but show me another program that covers the above three scenarios and what you want as one click.. I haven't seen one and the tab is overloaded as it is so I don't want to add another button.

Sharktooth

23rd February 2006, 10:56

@berrinam: could you update the bug-list?
this one
The Bitrate Calculator behaves very weirdly when entering the number of frames
Description: See http://forum.doom9.org/showthread.ph...432#post787432
Status: Not yet solved
is fixed in 0.2.3.2093

Doom9

23rd February 2006, 11:10

a few things about the list:
The audio section only allows one profileIs a feature request, not a bug.
MeGUI shows BeSweet commandlines when processing an AviSynth audio encodeSame here
It would also be useful if each bug listed would be linked with corresponding posts where it has been reported, so that if there are any questions, they can be addressed to the proper person. For instance I strongly suspect that
Jobs with errors are still flagged as 'done', instead of 'error'refers to x264 aborting without giving any notice.. so that would be a matter of reading exit codes

berrinam

23rd February 2006, 12:28

...
The audio section only allows one profileIs a feature request, not a bug.

Well, when this was first posted, you said that it didn't used to behave like that, but it does now. So it is 'unexpected behavior', which I view as a bug.
MeGUI shows BeSweet commandlines when processing an AviSynth audio encode
Same here
[/quote]
Similarly, AviSynth audio processing runs a commandline program with a commandline relevant to that encoder. Yet it tells the the user that it is running a completely different commandline (ie the BeSweet one). I would say that is a bug, because it is telling the user something incorrect.

Doom9

23rd February 2006, 13:00

a bug is something not working out as it should. Audio encoding still works just fine regardless of the commandline.. if you'd not get the codec you wanted, then that would be a bug, but showing a commandline where none should be, that's cosmetics.. the application doesn't do anything better if it shows no commandline in case avisynth is used for audio encoding.
Perhaps we both misundertood the profile thing.. I was thinking about the one click window, you probably about the main window. But in the main window, profile -> settings, with no ties whatsoever to the actual streams. But you can have two kinds of settings (works perfectly here). What could make sense is that once you switch audio stream, you set the profile to -1 so that you don't raise the wrong impression that a stream can have a profile (it cannot and never should in the future.. profiles are just settings with a name, nothing more.. and streams have settings, not profiles.

ChronoCross

23rd February 2006, 19:36

hmm anyone know what this means? I encoded the 5.1 fine but the stereo won't encode.

Channels=2, BitsPerSample=16, SampleRate=48000Hz
C:\Documents and Settings\ChronoCross\My Documents\My Downloads\Encoding Tools\MeGUI\audio\neroraw.exe -o "C:\Documents and Settings\ChronoCross\My Documents\WEDDING_CRASHERS\VIDEO_TS\Wedding T02 2_0ch 192Kbps DELAY -33ms.mp4" -rr 48000 -rb 16 -rc 2 -cbr 128 -codecquality_high -aacprofile_lc Error:
MeGUI.AviSynthException: m2AudioAC3Source: error in file "C:\Documents and Settings\ChronoCross\My Documents\WEDDING_CRASHERS\VIDEO_TS\Wedding T02 2_0ch 192Kbps DELAY -33ms.ac3"
at MeGUI.AviSynthAudioEncoder.encode()

Tima

23rd February 2006, 19:49

Cannot open d2v file in avisynth script creator.

---------------------------
AviSynth error
---------------------------
AviSynth script error:

Script error: there is no function named "Mpeg2Source"
---------------------------
ОК
---------------------------

I use build 2093. All settings are default.

ChronoCross

23rd February 2006, 20:02

that bug has been around since at least 2089.

Tima

23rd February 2006, 20:03

that bug has been around since at least 2089.
Maybe, but I haven't seen it in the buglist.. ;)

Mutant_Fruit

23rd February 2006, 20:15

Are you sure you have dgdecode installed and accessible to AviSynth?

Tima

23rd February 2006, 20:22

Are you sure you have dgdecode installed and accessible to AviSynth?

Yes, it's my fault.. I previously used to make avs script by Gordian Knot, and completely forgot that GK knows where to get dgdecode.dll but MeGUI doesn't..

Nevertheless, IMHO, it would be better for MeGUI to take dgdecode.dll from the path to DGMPGDec, specified in Settings, so there'll be no need for me to keep dgdecode.dll in two places (and update them both as well ;))..

Raithmir

23rd February 2006, 20:29

or changing their status to postponed

Well I didn't know you could do that to be honest, I'd not noticed that before ;)

I wasn't wanting an extra button, it's just that to me it would seem more logical for it stop when it reaches the end of the queue, not cycle back round again *shrugs* no biggie, I know I can set them to postponed now.