Log in

View Full Version : MeGUI: General Questions and Troubleshooting Thread


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 [52] 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186

bottomsup
20th July 2008, 20:23
you havent the rigth VFW decoder installed. obviously that's not a megui problem but you can fix it installing a VFW DV decoder (since avisource or opendlmlsource filters want both VFW decoders).

The odd thing is that I have ffdshow installed, WMP 11 and WMP classic both play this file fine. Only analyze in megui doesn't work.

EDIT: Resolved. Apparently this is some wierd bug with Xfire of all things. They install a codec on the system which corrupts ffdshow. Updating Xfire resolved this.

Sharktooth
21st July 2008, 01:47
So the only multichannel option is to Upmix it to 5.1- right?
right. it depends on the encoders, so if that will change then megui will be able to support other channel configs.

Mr Alpha
21st July 2008, 16:33
Thanks, poisondeathray. That solved it. I am now yet another step closer to not being a noob.

mparter
21st July 2008, 17:18
If your just wanting good quality and not interested in just hitting a particular size, using Const. Quality of anywhere from 18 to 22 will make for a pretty good looking encode, IMO. Just click on Config after selecting the XBox-PS3 profile, and select Const. Quality on the drop down. Then change the value to 20, which I normally choose for VC-1 stuff. The lower the value the more the size will grow, but at a certain point it's hard to see the benefit of the size growth you experience. You never know for sure what the final size will be, but you're ensured of a good looking encode.

Like I said above, this is just my opinion, but I think it's shared by more than a few.

Cheers mate. Started an encode running yesterday evening which should've finished this afternoon (almost 24 hours!!). I set this to around 19000 I think which was spitting out around about 9.5Gb.

LOGiC
23rd July 2008, 10:28
@all,

sorry guys for the following question. I am not sure if this is kind of off-topic, but it is related to x264 and MeGUI as well. I just started working with re-encoding since I got an AVCHD-capable standalone Blu-Ray player. In my settings, I can choose 24p output just for BD-Video. Panasonic support told me that it would be played for other video, if the information is contained in the video. Would probably be just a flag or something like that.

So my question is, when re-encoding something into x264, will there be any chance, probably after the encode, to bring such an information to the stream, a similar flag as it is in a BD-structure to tell a player to output 24p ?

Thanks in advance.

If this definately is the wrong thread, I really apologize for it.

Sharktooth
23rd July 2008, 11:20
Cheers mate. Started an encode running yesterday evening which should've finished this afternoon (almost 24 hours!!). I set this to around 19000 I think which was spitting out around about 9.5Gb.
If you're concerned about speed, use faster profiles/presets.
The encoding time does not depend on MeGUI but on the encoder and settings used.

@LOGiC: megui is a GUI, hence, the answer is no.

Taurus
23rd July 2008, 14:27
@shark:
Where can I read about the AutoGuess feature in x264 version 915?

Thank you

Taurus

Sharktooth
23rd July 2008, 14:34
x264 git changelog. look at the diff if you want, or ask x264 devs.

Taurus
23rd July 2008, 14:48
x264 git changelog. look at the diff if you want, or ask x264 devs.

Thank you
I looked at the changelog, but not to much info there :p.
Well, maybe in a few days a x264 dev will give some explanations.

Dark Shikari
23rd July 2008, 14:48
Thank you
I looked at the changelog, but not to much info there :p.
Well, maybe in a few days a x264 dev will give some explanations.Based on --bitrate, --vbv-maxrate, --ref, fps, and resolution, x264 tries to guess the right --level value.

Not much else to it.

Taurus
23rd July 2008, 17:11
Based on --bitrate, --vbv-maxrate, --ref, fps, and resolution, x264 tries to guess the right --level value.

Not much else to it.
OOh, I like guessing :)
Dark, thanks for the short explanation.
A few encodes later maybe guessing will become knowledge ;)

Frank_UK
23rd July 2008, 19:49
I have just updated to MeGUI 0.3.0.1017
After using AviSynth script creator two video preview windows remain open. I cannot find a way to close them.
Any workaround?

Sharktooth
23rd July 2008, 19:53
they're not supposed to be closed.
READ THE CHANGELOG.
if you have a lowres display and you want to reduce them click on halfsize or quartersize buttons.

ZombiePimp
23rd July 2008, 20:13
I noticed, just like the bug report said, that the preview window needed to be initially opened when opening an avs script for anamorphic encodes to work properly. I seem to remember that it was OK to close the preview window though, even immediately after it opened; anamorphic encode worked fine.

Basically, I think removing the "Open Preview after AViSynth script selection" option would have been enough to work around the bug.

Sharktooth
23rd July 2008, 20:18
ok, lets keep it for some days so ppl will learn to NOT close it unless it's absolutely necessary.
or we just find another way to keep the SR info without keeping the preview open...

Archimedes
23rd July 2008, 20:20
In the XviD configuration dialog I-Frame boost is set to 100 (default setting). But the default value of xvid_encraw is 10 (parameter kboost). Is the default setting in MeGUI correct this way?

ZombiePimp
23rd July 2008, 20:20
OK, but I'm saying I'm pretty sure its OK to close it at any time. It just needs to be initially opened.

Zep
23rd July 2008, 20:50
ok, lets keep it for some days so ppl will learn to NOT close it unless it's absolutely necessary.
or we just find another way to keep the SR info without keeping the preview open...

ouch I am stuck with this window on screen for 11 hours lol

yeah double clicking 4 times in the bar hides it thank goodness lol

((( atom )))
23rd July 2008, 22:00
Hmm, I just crashed megui -> out of memory with about 12 preview-windows open.. Isn't there a simpler way of writing the ar somewhere?

Menedas
23rd July 2008, 22:21
I have never mentioned a problem with anamorphic encode and closed preview window. And I use this quite often.

Let the user decide to let the preview window open, not the programm. Just make a message informing the user of problems when closing the window and not prescribe the user how he should use the programm. Thank you.

ZombiePimp
23rd July 2008, 23:14
Really, the preview window can be closed at any time without affecting anamorphic encodes. It just needs to be initially opened when you load the script. There's no reason for meGUI to force it to stay open.

You can quickly confirm this by checking the job's XML file for the DAR section. I tested this in a previous version by clicking Enqueue and AutoEncode while the preview window was closed (but initially opened when loading the avs script). Both did add the DAR section.

Tae
24th July 2008, 01:08
Huh. I wonder if that is why I hated the Anamorphic encoding. Never looked right to me, so I don't use it. Didn't see a benefit either since encoding to suggested res was always fine.

cy
24th July 2008, 01:52
Anamorphic encoding is a good thing imo.
I do hope a better solution can be found than keeping these preview windows open because it certainly clutters the desktop (or taskbar).

Tae
24th July 2008, 02:14
Anamorphic encoding is a good thing imo.
I do hope a better solution can be found than keeping these preview windows open because it certainly clutters the desktop (or taskbar).

When I tried it, the aspect was incorrect, but I close the window. What does anamorphic do for you anyway?

Noddy_Bujeca
24th July 2008, 02:28
this is really stupid, i dont know why there was a need for this last update (regarding the unclosable preview window), nor do i care. it's just a nuisance...
i always used anamorphic and never had a problem!

i'll download the version before the last one.
hope it returns to normal in "some days", otherwise i'll just keep with the other version.......

more than 1 year pass since register... have to be something like this to make me post for the very first time... oh my...


good encodes o/

Sharktooth
24th July 2008, 02:33
ill fix tomorrow. believe me, it was necessary.

cy
24th July 2008, 02:38
@ Tae:

Well, it allows for a higher resolution at playback with a smaller encoded filesize.

Tae
24th July 2008, 02:50
@ Tae:

Well, it allows for a higher resolution at playback with a smaller encoded filesize.

Well I will need to test it again and leave the window open to see if that corrects the problems I had with AR.

Sharktooth
24th July 2008, 02:55
fixed. the close/minimize/maximize buttons in the preview are back.
update is coming.

cy
24th July 2008, 02:56
Thank you Sharktooth.

~bT~
24th July 2008, 03:10
^ updated but there is an issue with the slider mate :)

Sharktooth
24th July 2008, 03:12
what issue?
oh... maybe i understood... it's covered by another control @ original size... damn visual studio designer bugs...

~bT~
24th July 2008, 03:15
what issue?

http://maxupload.com/img/F02AA50D.jpg

Sharktooth
24th July 2008, 03:23
should be fixed... another update is coming.

~bT~
24th July 2008, 03:27
:thanks:

edit: better than last but still not perfect :) no worries tho, can live with it.

http://maxupload.com/img/8B79AF46.jpg

Sharktooth
24th July 2008, 03:29
updated. is it ok now?
... after the update i spotted another minor visual bug (at halfsize and quartersize)... still introduced by the damn VS designer... ill fix it tomorrow... however the slider should show up correctly.

~bT~
24th July 2008, 03:38
^ its cool, better than before :)

Sharktooth
24th July 2008, 03:41
try with higher and lower resolutions too and if there are still problems, please report back here.

~bT~
24th July 2008, 03:49
its not as bad an issue as 1st time round. here it is with lower and higher resolutions.

http://maxupload.com/thumb/15A66896.jpg (http://maxupload.com/img/15A66896.jpg)
http://maxupload.com/thumb/7703B691.jpg (http://maxupload.com/img/7703B691.jpg)

Sharktooth
24th July 2008, 03:53
ill see what i can do tomorrow... almost 5AM here... need some rest...

((( atom )))
24th July 2008, 10:34
After having crashed yesterday while setting up some rips, I restarted megui and let it run the encodes that were queued up. Since I restarted, the preview-windows were all closed now and the ar is wrong for all of the encodes (the movie actually is a long line...).
Where does this problem come from, all of a sudden? I used to make tons of anamorphic encodes with no errors, ever...

Sharktooth
24th July 2008, 11:02
yep, that's the bug. it's been there since version 0.3.

LOGiC
24th July 2008, 11:24
yep, that's the bug. it's been there since version 0.3.

Sir, I've set up everything to start my first encoding tries. What do I need to take care of for getting the right AR, is there anything that needs to be done ?

Thank you in advance.

Regards,
Andy.

ZombiePimp
24th July 2008, 11:36
Sharktooth, to clarify, there are two separate bugs related to anamorphic encoding:

1.) Unchecking "Open Preview after AviSynth script selection" in the settings breaks all anamorphic encodes. This bug is also in version 0.2.

2.) As of version 0.3, some, but not all, anamorphic encodes end up wrong (even with bug #1 bypassed). These same encodes work fine in version 0.2.
I'm seeing exactly what is reported here:
http://sourceforge.net/tracker/index.php?func=detail&aid=2010131&group_id=156112&atid=798476

Sharktooth
24th July 2008, 11:47
1) has been disabled, it's no longer possible to uncheck it.

2) is still there. AR is not saved in the encoding params in the queue but only as a temp settings (coz it's calculated during the preview).

3) theres also a third bug. the AR reported to the encoder is sometimes completely wrong and overflows. that's due (i think) to mediainfo.

ZombiePimp
24th July 2008, 12:12
Yes, thank you for fixing #1. I think the third bug you refer to is what I was trying to convey in my #2.

Danguard
25th July 2008, 00:58
I still have this issue:

When i try to encode with oneclick profile a video i get always the same error (even when i tell him to not encode the audio tracks, so it should be just a muxing in the final mkv).
In attachment the log i have before megui crash

I checked the folder, and he wrote all the audio files correctly
The files are called:
1X02 T80 2_0ch 192Kbps DELAY 0ms
1X02 T81 3_2ch 448Kbps DELAY 0ms
1X02 T82 2_0ch 192Kbps DELAY 0ms
1X02 T83 2_0ch 192Kbps DELAY 0ms
1X02 T84 2_0ch 192Kbps DELAY 0ms

And this is the error i get:

http://forum.doom9.org/attachment.php?attachmentid=8606&stc=1&d=1215722851

Or this other one:

http://img136.imageshack.us/img136/544/error2uk3.jpg

Am i doing something wrong?

Sharktooth
25th July 2008, 01:52
OneClickEncoder does not work. it needs fixing.
it's a known bug/problem caused when we updated to dgindex 1.5.x.

anonova
25th July 2008, 07:51
1) has been disabled, it's no longer possible to uncheck it.
That's an interesting way to suppress that bug for the moment. I load up fairly heavy scripts, and now that the preview is forced, I have to wait several minutes to do anything. It's kind of hard to load multiple videos like that.

LOGiC
25th July 2008, 10:31
as this is a general question, as I've read right, Psy-RDO 0.5 has been integrated into meGUI. Is there any chance I can verify it is enabled ?

In general about x264 (sorry for being a little OT), is Trellis 1 on final MB better than Trellis2 always, what exactly does it do ?

Thanks.