MeGUI: General Questions and Troubleshooting Thread

[TheRyuu]

In the latest development version,
Is anyone else getting a screwed up aspect ratio on xvid encodes? It doesn't seem to effect h264 (mkv) encodes.

Just ran a 10hour encode and it plays back like super wide screen.

Is this a know bug?
Also, is there any way to fix this without a re-encode (I know that the resolution is correct on it too).

Thanks.

I guess I'll roll back to the latest stable version for now.
Anyone know how to fix the ar problem without a re-encode?

[foxyshadis]

Might be assigning the AR to both the bitstream and the container, what container do you use for xvid?

If that is the case, you should be able to fix it with mpeg4modifier.

[berrinam]

Searching the web suggests the definitions of DAR & PAR are well established, but that for SAR isn't - sometimes it means PAR, as you use, & sometimes DAR/PAR.Indeed, a web search does show much less ambiguity with PAR than I thought. But a number of pages also use SAR to mean PAR, including x264, so I think that's all ok.

What term do you use for DAR/PAR?No term, just video width/height.

It's also not terribly important which you treat as the derived quantity as long as the arithmetic is precise, however I'd still be inclined to go with DAR as the derived value as ime (quite limited), one tends to work with a small set of possible PARS all of which can be represented precisely as the ratio of two four digit integers. I think in practice if you wish to store DAR precisely you'd need more. Not important, just a personal choice.I don't think precision is a big concern here. Internally in MeGUI, all calculations are being done with the C# "decimal" type, which has 28 decimal digits of precision. Given that very few calculations are actually done, I think it stays very precise, and the errors in calculation are dwarfed by the (intentional) rounding done of the AR to make it fit better on standard displays. The default "acceptable error" is 5%, which I found acceptable by testing (YMMV), so I think there's a pretty big margin for error in AR calculation anyway. And even if you set that to 0%, you're likely to get a significant aspect error when you round the resizing to mod16, anyway.

As to the representation of ARs, in general, with fractions, the stuff I said about precision above means that I don't really see the point of doing it. MeGUI used to use that representation internally, to dubious advantages.

Yes, by PAR I mean pixel aspect ratio and by DAR display aspect ratio. With this definition I have understood SAR is equivalent to PAR, no? (hopefully _I_ haven't made a fundamental error here ;))You're correct.

I think here our points of view will differ a little. Definitely, for the user, DAR is more intuitive, unless they've spent enough time pondering about the whole matter.

To me, PAR is "everything" - it will define everything else. Once I know what the PAR of the source is, I can derive every other value simply from that fact. This, I have to admit, undoubtedly will somewhat cloud my view in this.This reasoning is misinformed. If you know the PAR and the resolution then you can calculate the DAR. But similarly, if you know the DAR and the resolution you can calculate the PAR. In this sense, they are equivalent.

[berrinam]

Might be assigning the AR to both the bitstream and the container, what container do you use for xvid?MeGUI generally does that, but I'm not aware that this was a problem. I think that wizboy's problem is indeed a MeGUI bug: I think the commandline for xvid currently doesn't include the AR.

[berrinam]

why guys would you dot your filenames ??? MP4Box cares about dots in filename. So, uses a normal way to name your file. That's the best thing you can do first...I didn't know about this problem with MP4Box. If it is a real concern, then MeGUI should at least notify the user of it when they have a bad filename, and preferably provide a workaround as well.

[TheRyuu]

MeGUI generally does that, but I'm not aware that this was a problem. I think that wizboy's problem is indeed a MeGUI bug: I think the commandline for xvid currently doesn't include the AR.

Problem is, the bug wasn't here before the latest development revision.

I'll try mpeg4modifyer.
Thanks.

In the mean time, I'll roll back to the latest stable revision. If there is anything I can do to help fix that bug let me know. :p

The container was avi just to let you know. And the problem only effects xvid encodes.

Edit:
I think I traced down the problem.
Megui isn't assuming squar pixels and is setting the pixel AR to 16:9 or something along those lines.
So like a video of 704x396 is already 16:9, is being 16:9ed again after it's already 16:9 if you get what I'm saying :p (I don't know of any other way to put it, like super stretched wide screen).
Not sure if this is due to not specifying it in the command line to xvid_encraw.

Out of curiosity, why does this problem only effect the latest development release?

mpeg4modifier worked great btw :)

[berrinam]

I recently made some changes to handling of AR. xvid got left out. Hence the bug.

[pablobhz]

Hello, i'm new on this forum.
I've searched a bit around, but found no answer. Then i decided to post here.
My megui decided to crash as hell. I try to import my avs script to encode there, and it crashes. It looks like its an problem with x264.exe, but i tried to encode with another script, and it worked fine. I've just made a fresh install of windows, thinking about something with him, but no clue.
also...i have a x2 3600+ 1gb ram GeForce 7100GS M2N4-SLI
its a fine cpu for encoding.
Well, i'll also post my script. Maybe there's something with it, dunno.

Thanks for the attention. The crash message is some classical "megui found an error and it has to be closed"(I don't know how it is english).

Thanks.


Import("C:\Arquivos de programas\AviSynth 2.5\plugins\LimitedSharpenFaster.avs")
LoadPlugin("C:\Arquivos de programas\AviSynth 2.5\plugins\fft3dfilter.dll")
AudioDub(DGDecode_mpeg2source("MoetanRIP.d2v",cpu=4,info=3,iPP=true, moderate_v=20),DirectShowSource("MoetanRIP T01 2_0ch 448Kbps DELAY 0ms.ac3"))
ColorMatrix(d2v="MoetanRIP.d2v",interlaced=true)
tfm(order=-1,pp=5)
fft3dfilter()
LimitedSharpenFaster()
LanczosResize(720,480)
converttoyv12()
Trim(172,36854)

[check]

Remove the lines one by one until you isolate which causes the problem.

[Kurtnoise]

Sorry again, I wasn't clear enough. I was merely referring to your choice of par presets for pal & ntsc 4:3 & 16:9. Yours differ (last time I checked) slightly from those given by Jukka Aho.
The presets in Yamb are the same defined by the standard...

Out of interest, why does mp4box care? What does it do with the names?
MP4Box is vey sensitive with filenames because we can pass some options in it.

I didn't know about this problem with MP4Box. If it is a real concern, then MeGUI should at least notify the user of it when they have a bad filename, and preferably provide a workaround as well.
not really a big deal imo...I know that MP4Box raises errors during the mux process when subtitles have several dots in their filenames. I got also the same issue with few audio streams.

[Adub]

@pablobhz
If you load the script with MPC or virtualdub, what does it say?

[Maccara]

This reasoning is misinformed. If you know the PAR and the resolution then you can calculate the DAR. But similarly, if you know the DAR and the resolution you can calculate the PAR. In this sense, they are equivalent.

Not really misinformed - I just didn't put it well. ;) PAR is "everything" to me, because I do not change PAR (resize), unless I'm doing a format conversion (NTSC -> PAL/1:1) and I'm using sampling rate & line length as a basis for the calculations (when known), so PAR is intuitive here.

But, you of course are right. If we know any 2 of DAR/PAR/resolution reliably, we can derive rest. I just happen to usually know the PAR & cropped resolution with my my sources. But of course, with DVDs', the DAR is well defined too (assuming, of course, the DVD is mastered ok), so in that sense they're indeed equivalent.

Thanks for the interesting discussion! I'm glad to know, in megui this is at least handled correctly (seen too many "professionals" to get these wrong too, so I have learned to test / ask myself how it is done in software, which in this case unfortunately only raised questions as there were a couple of bugs :)).

[pablobhz]

@pablobhz
If you load the script with MPC or virtualdub, what does it say?

If i load the script with MPC or Vdub, it plays fine.
Well, i found out the problem is with LimitedSharpenFaster()
I checked and i've unpacked dlls correctly in AviSynth's plugin folder. But for some reason it isn't working.

I was talking about this problem with a friend, he said it coud be some problem of RemoveGrain dll's.
I will try some things and i hope it works.
Thanks everyone for attention and help.

[Edit]: I found out LimitedSharpenFaster.avs wasn't in the plugins folder. I fixed it, but megui keeps crashing. My plugins folder is a mess, is there something with it ? I always used it as it is, and i never had problems.

[ChrisW77]

I find it a bit strange that these audio problems aren't such a big deal.
I mean, if I can't name my own files how I want them to be named, ie with dots, and I can't name them using long filenames (so the dots are taken out but the filename still exists), and lastly (even more confusing as to why) why I can't write the muxed file back to the same drive/partition. :confused:

Whats the purpose of actually bothering to have a MP4 muxer if it doesn't work properly ?

These are bugs, plain and simple. Not being able to write back to the same drive, is just plain stupid, as is the long filenames.

Shame, as this is one of the best GUIs out there, ruined by a non-working mp4 muxer.

[mroz]

The presets in Yamb are the same defined by the standard...

Got a reference? I'd like to be able to compare it to Jukka Aho's analysis (http://lipas.uwasa.fi/~f76998/video/conversion/) which fits with my understanding, is well written from a technical point of view & links to several technical resources. Did you read this btw?

I can then forward such info to Jukka; if he doesn't wish to comment I'd just drop the issue again, as I don't have the relevant background to argue the case more stongly without first doing a lot more research.

Maybe Maccara can comment?

MP4Box is vey sensitive with filenames because we can pass some options in it.

Got a link to info on the details? I imagined it'd be something along those lines, but still can't see why that couldn't be implemented cleanly. Code should adhere to standards strictly when it comes to output, but as a general rule of thumb, tollerate malformed input if it can be done without ambiguity, imo.

Not a big deal, no, but if the problem can be identified & easily fixed it might as well be.

[Maccara]

Maybe Maccara can comment?


Without checking anything, I'd say we're probably talking about rounding differences here. What are the actual values used in mp4box which you think are different? (I haven't used that myself yet)

Jukka Aho gives mathematically correct values. However, in practice slightly different values are generally used (particularly for NTSC) due to rounding differences. Difference, however, is quite small and probably doesn't matter. (I think Jukka mentions in the change history he has updated the values at some point)

There will be even more variability between DVDs due to different mastering and for analogue captures due to different hardware/drivers - even cameras have slight differences. (and the dvd differences have on many occasion raised the argument, that generic par values should be favored over itu values - which is fine by me, as long as "itu" compliance is not then claimed and I have to have the option to input my own values in that case ;))

[mroz]

The differences are tiny, around 0.3% (unlike the difference between these values & those Nero Recode uses; that's about 2 to 3% last time I checked).

yamb aho yamb/aho

4:3 pal 12:11 128:117 351/352 = 0.997159
ntsc 10:11 4320:4739 4739/4752 = 0.997264

16:9 pal 16:11 512:351 as above
ntsc 40:33 5760:4739


Edit: mp4box doesn't know PAR presets; the above values are supplied by the gui Yamb to mp4box

[pablobhz]

If i load the script with MPC or Vdub, it plays fine.
Well, i found out the problem is with LimitedSharpenFaster()
I checked and i've unpacked dlls correctly in AviSynth's plugin folder. But for some reason it isn't working.

I was talking about this problem with a friend, he said it coud be some problem of RemoveGrain dll's.
I will try some things and i hope it works.
Thanks everyone for attention and help.

[Edit]: I found out LimitedSharpenFaster.avs wasn't in the plugins folder. I fixed it, but megui keeps crashing. My plugins folder is a mess, is there something with it ? I always used it as it is, and i never had problems.

Hi
I'm posting again, because i've found no clue about what is happening. I've verified all configs, all files and my megui is still crashing with LimitedSharpenFaster()
I don't know what more i can do. Maybe an filter to use instead of LimitedSharpenFaster ? Sorry, but i'm asking help since i've no more ideas.
Also checked RemoveGrain DLL's and they're allright.
Thanks
Pablo
p.s: I've used to quote the message, so anyone who reads wil know what is it about.

[PlazzTT]

I've just installed meGUI on my new system, and I'm getting this error when I try to load any d2v into the AVS Generator:
http://i23.tinypic.com/fcm98o.png

I would try the suggestions given, but it's a D2V file, and not an AVS :/

[Maccara]

The differences are tiny, around 0.3%

Yup, just different rounding used during calculations. There also may be a difference, if fractions (for resolutions) is floored, or rounded up (itu ntsc mathematically "correct" x res 710.85, and if that is used for the calcs and is done with 710 or 711 pixels, there's a slight difference).

I don't even remember myself, if it is specified anywhere when and which way values should be rounded - I've just used full precision myself usually, as does Jukka.

I'd say there's nothing to worry about - I'm not even 100% sure if not rounding for calculations is absolutely the correct way to go, so I won't argue if yamb provided values are more correct or Jukka's. ;)

(Edit: I just whipped up a quick test in excel and if I floored the numbers to 5 significant numbers, I got mostly the same values as yamb provided - this is less difference than there is between some different cameras/lenses geometry)

[foxyshadis]

Berrinam, consider something like this in scripts if any cropping is done?

global MeGUI_darx = 1823
global MeGUI_dary = 1000
xSource(...)
original = last
etc
UpdateDAR(original, last)

function UpdateDAR(clip old, clip new) {
global MeGUI_darx = MeGUI_darx * new.width / old.width
global MeGUI_dary = MeGUI_dary * new.height / old.height
}

[trooper11]

I ddint see this posted yet, so Ill ask.

Im trying to analyse the source material in the avisynth script creator and it continues to fail, giving an error.

'Source detection couldnt determine the source type'

The file is an mkv that opens and previews fine in MeGUI. Is there anything I can do to get around this? This is running on a Windows XP pc by the way. Thanks

[pablobhz]

oh
my file started to crash on MPC too.
For some reason, don't know. It was working fine on MPC.
Maybe is there something i can use instead of LimitedSharpenFaster() . But its strange, since the person who uses this told me he never had problems.
Thanks
btw, the error happens after i enqueue the job. For those who haven't readed about my problem, just look 4 messages ago, something around it. Thanks
Pablo

[ChrisW77]

Just tried Yamb, as it's a front-end for MP4box, and it worked using long filenames, dotted filenames, and wrote back to the same drive.
This proves it's not a mp4box problem, it's a megui problem.

[berrinam]

Berrinam, consider something like this in scripts if any cropping is done?

global MeGUI_darx = 1823
global MeGUI_dary = 1000
xSource(...)
original = last
etc
UpdateDAR(original, last)

function UpdateDAR(clip old, clip new) {
global MeGUI_darx = MeGUI_darx * new.width / old.width
global MeGUI_dary = MeGUI_dary * new.height / old.height
}

Nice idea, but I think the cropping problem is fixed now: MeGUI prints the correct dar in the first place (as it used to do).

Out of interest, would that Avisynth script work? I would have thought it would complain that you're redeclaring the globals, MeGUI_darx and MeGUI_dary.

[mroz]

I'd say there's nothing to worry about - I'm not even 100% sure if not rounding for calculations is absolutely the correct way to go, so I won't argue if yamb provided values are more correct or Jukka's. ;)

Thanks for the feedback & explanation. I'll buy that & shut up now :)

[rack04]

I see that the bug report for the automatic shutdown was closed. Can anyone else verify that this feature is fixed? It still doesn't work on my end.

[mroz]

Odd behavour from 2.6.1026 (not posted to bugtracker as currently not repeatable):

Queued up a huffy prerender on a 3 minute 720p d2v source (with a slow deblocking avs) followed by an x264 encode. Reused the prerender output as source for five more x264 encodes at various bitrates. Came back this morning & all looks fine; queue done on the expected timescale; files play.

...Then notice a minimised dialogue - Status: 99.91%.

Use minimise then restore to make it visible. It's from a 2nd pass of x264, I assume the final encode, claiming to be stuck at frame 8547 of 8555 (though all output within is frozen). Out of curiosity I try to alter priority; as perhaps expected this throws a stacktrace - object ref is not an instance of an object, indicating I assume that the gui has been left lying around after the underlying encode completed.

Clicking abort results in the usual warning dialogue which when ok'd makes no difference.

Manually closing the window does get rid of it.

[Blue_MiSfit]

I'm not sure why the following command line (lifted from my MeGUI log from an encode last night) split my output MKV into close to 2000 pieces, but it sure did.


Job commandline: "C:\Program Files\megui\tools\mkvmerge\mkvmerge.exe" -o "J:\Movies Work\Knocked Up\Knocked Up-muxed.mkv" --aspect-ratio 0:37/20 -A -S "J:\Movies Work\Knocked Up\Knocked Up.mkv" -a 0 -D -S "J:\Movies Work\Knocked Up\Knocked T01 3_2ch 448Kbps DELAY 0ms.ac3" --split 0M --no-clusters-in-meta-seek


I don't recall selecting anything that would split the output...

It seems like the --split 0M flag wouldn't be needed? Maybe this should have been left out. Either way, I don't have the original encoded H.264 only MKV anymore and just 2000 little pieces... :)

I'm using 0.2.6.1026, and did x264 with hq-slowest 2 pass, and muxing ac3...

Ideas??

~MiSfit

[Kurtnoise]

weird...I can't reproduce this here. You use AutoEncode or something else ?

I see that the bug report for the automatic shutdown was closed. Can anyone else verify that this feature is fixed? It still doesn't work on my end.
using the last dev build, it works fine here...

[nurbs]

I just did a quick check and the auto shutdown doesn't work for me either. I do nothing fancy, just normal encoding. The countdown window appears, but it doesn't shut down then. This is on WinXP SP2 with the latest dev build (0.2.6.1026).

[Kurtnoise]

Try this build (http://www.mediafire.com/?3mt8stwsrde) or this one (http://www.mediafire.com/?09r42uxsx2x)...

[nurbs]

Shutdown works with the second build. :thanks:
The first doesn't work.

[berrinam]

I'm not sure why the following command line (lifted from my MeGUI log from an encode last night) split my output MKV into close to 2000 pieces, but it sure did.


Job commandline: "C:\Program Files\megui\tools\mkvmerge\mkvmerge.exe" -o "J:\Movies Work\Knocked Up\Knocked Up-muxed.mkv" --aspect-ratio 0:37/20 -A -S "J:\Movies Work\Knocked Up\Knocked Up.mkv" -a 0 -D -S "J:\Movies Work\Knocked Up\Knocked T01 3_2ch 448Kbps DELAY 0ms.ac3" --split 0M --no-clusters-in-meta-seek


I don't recall selecting anything that would split the output...

It seems like the --split 0M flag wouldn't be needed? Maybe this should have been left out. Either way, I don't have the original encoded H.264 only MKV anymore and just 2000 little pieces... :)

I'm using 0.2.6.1026, and did x264 with hq-slowest 2 pass, and muxing ac3...

Ideas??

~MiSfitLike Kurtnoise, I can't reproduce this. I would really appreciate it if you detailed your exact steps, because a number of people have mentioned this. If possible, could you work out exactly what you did (including file formats), check that it is reproducible, and then post it on the SF bug tracker please?

[Blue_MiSfit]

Will do - I just tried again last night (Explicitly selecting no split this time) and got the same results.


What I did:

1) VOB Source, Indexed with DGIndex 1.5.0 b6
2) AviSynth script was a simple MPEG2Source, and ColorMatrix with no extra filters
3) Loaded script into video source. Started with HQ-Slowest for x264 as a baseline, and selected a CQM - M4G HRM v2. Adjusted keyframe intervals for FILM material (240/24)
4) Made a new profile for this called HQ-Transparent
5) Set MKV output
6) Selected Auto Encode
7) Set MKV as container, checked "add aditional content", and set 2.2 GB as target size. Set splitting to "no splitting"
8) Selected 5.1ch AC3 as audio 1 - set as English and named "English 5.1). Verified that MKV was selected and splitting was set to "No splitting"
9) Go and Start Encoding.

In the end I have nearly 2000 tiny little MKV files, most under 3 MB in size. The video looks _great_ but audio is desynched in all the pieces.

I'm guessing either MKVMerge is at fault, or MeGUI is passing it an incorrect command line.

I have all the latest tools via auto-update as of 10-18.


***MeGUI log (end deleted for size's sake):

Generating jobs. Desired size: 2.2 GB

Desired size of this job series: 2.2 GB
Split size of this job series: 0 bytes

Looking for job processor for job...

Processor found!



------------------------------------------------------


Starting job job1 at 12:33:28 AM

Starting preprocessing of job...

Doing bitrate calculation...
Desired video size after subtracting audio size is 1866915KBs. Setting the desired bitrate of the subsequent video jobs to 1917 kbit/s.
Preprocessing finished!

successfully started encoding

Processing ended at 1:55:05 AM

----------------------

Log for job job1

Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --pass 1 --bitrate 1917 --stats "J:\Movies Work\Knocked Up\Knocked Up.stats" --keyint 240 --min-keyint 24 --bframes 3 --b-pyramid --direct auto --filter -2,-1 --subme 1 --analyse none --me dia --threads auto --thread-input --sar 3083:2500 --cqmfile "D:\x264 Matricies\High Bitrate\Transparent\M4G HRM V2.cfg" --progress --no-dct-decimate --no-psnr --no-ssim --output NUL "J:\Movies Work\Knocked Up\Knocked Up.avs"
avis [info]: 720x480 @ 23.98 fps (191270 frames)
x264 [info]: using SAR=3083/2500
x264 [info]: using cpu capabilities: MMX MMXEXT SSE SSE2 3DNow!
x264 [info]: slice I:1931 Avg QP:22.55 size: 36705
x264 [info]: slice P:59137 Avg QP:24.54 size: 15189
x264 [info]: slice B:130202 Avg QP:26.18 size: 7170
x264 [info]: mb I I16..4: 36.4% 0.0% 63.6%
x264 [info]: mb P I16..4: 18.3% 0.0% 0.0% P16..4: 80.4% 0.0% 0.0% 0.0% 0.0% skip: 1.3%
x264 [info]: mb B I16..4: 0.8% 0.0% 0.0% B16..8: 23.6% 0.0% 0.0% direct:65.5% skip:10.1%
x264 [info]: final ratefactor: 24.77
x264 [info]: direct mvs spatial:99.5% temporal:0.5%
x264 [info]: kb/s:1908.0

encoded 191270 frames, 39.07 fps, 1908.18 kb/s

----------------------

Starting postprocessing of job...

Job completed successfully and deletion of intermediate files is activated

Postprocessing finished!

End of log for job1
-------------------------------------------------------


Looking for job processor for job...

Processor found!



------------------------------------------------------


Starting job job2 at 1:55:05 AM

Starting preprocessing of job...

Preprocessing finished!

successfully started encoding

Processing ended at 11:54:03 AM

----------------------

Log for job job2

Job commandline: "C:\Program Files\megui\tools\x264\x264.exe" --pass 2 --bitrate 1917 --stats "J:\Movies Work\Knocked Up\Knocked Up.stats" --keyint 240 --min-keyint 24 --ref 10 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --filter -2,-1 --subme 6 --trellis 2 --analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --sar 3083:2500 --cqmfile "D:\x264 Matricies\High Bitrate\Transparent\M4G HRM V2.cfg" --progress --no-dct-decimate --no-psnr --no-ssim --output "J:\Movies Work\Knocked Up\Knocked Up.mkv" "J:\Movies Work\Knocked Up\Knocked Up.avs"
avis [info]: 720x480 @ 23.98 fps (191270 frames)
x264 [info]: using SAR=3083/2500
x264 [info]: using cpu capabilities: MMX MMXEXT SSE SSE2 3DNow!
x264 [info]: slice I:1931 Avg QP:16.65 size: 52900
x264 [info]: slice P:59137 Avg QP:19.17 size: 19881
x264 [info]: slice B:130202 Avg QP:20.52 size: 4866
x264 [info]: mb I I16..4: 12.9% 80.4% 6.7%
x264 [info]: mb P I16..4: 2.0% 8.6% 0.4% P16..4: 46.3% 21.7% 19.4% 0.0% 0.0% skip: 1.5%
x264 [info]: mb B I16..4: 0.2% 0.6% 0.0% B16..8: 19.3% 1.8% 3.8% direct: 0.9% skip:73.4%
x264 [info]: 8x8 transform intra:78.5% inter:99.4%
x264 [info]: direct mvs spatial:88.7% temporal:11.3%
x264 [info]: ref P 53.7% 19.4% 7.2% 5.3% 3.0% 3.8% 2.3% 1.9% 1.3% 2.0%
x264 [info]: ref B 72.7% 13.9% 4.1% 3.2% 1.3% 1.4% 1.1% 0.9% 0.6% 0.8%
x264 [info]: kb/s:1916.8

encoded 191270 frames, 5.33 fps, 1917.10 kb/s
desired video bitrate of this job: 1917 kbit/s - obtained video bitrate (approximate): 1919 kbit/s
----------------------

Starting postprocessing of job...

Job completed successfully and deletion of intermediate files is activated

Found intermediate output file 'J:\Movies Work\Knocked Up\Knocked Up.stats', deleting...
Deletion succeeded.

Postprocessing finished!

End of log for job2
-------------------------------------------------------


Looking for job processor for job...

Processor found!



------------------------------------------------------


Starting job job3 at 11:54:03 AM

Starting preprocessing of job...

Preprocessing finished!

successfully started encoding

Processing ended at 11:56:07 AM

----------------------

Log for job job3

Job commandline: "C:\Program Files\megui\tools\mkvmerge\mkvmerge.exe" -o "J:\Movies Work\Knocked Up\Knocked Up-muxed.mkv" --aspect-ratio 0:37/20 -A -S "J:\Movies Work\Knocked Up\Knocked Up.mkv" --language 0:English --track-name "0:English 5.1" -a 0 -D -S "J:\Movies Work\Knocked Up\Knocked Up T01 3_2ch 448Kbps DELAY 0ms.ac3" --split 0M --no-clusters-in-meta-seek
mkvmerge v2.1.0 ('Another Place To Fall') built on Aug 19 2007 13:39:56
'J:\Movies Work\Knocked Up\Knocked Up.mkv': Using the Matroska demultiplexer.
'J:\Movies Work\Knocked Up\Knocked Up T01 3_2ch 448Kbps DELAY 0ms.ac3': Using the AC3 demultiplexer.
'J:\Movies Work\Knocked Up\Knocked Up.mkv' track 1: Using the MPEG-4 part 10 (AVC) video output module.
Track 1 of 'J:\Movies Work\Knocked Up\Knocked Up.mkv': Extracted the aspect ratio information from the MPEG-4 layer 10 (AVC) video data and set the display dimensions to 888/480.
'J:\Movies Work\Knocked Up\Knocked Up T01 3_2ch 448Kbps DELAY 0ms.ac3' track 0: Using the AC3 output module.
Warning: 'J:\Movies Work\Knocked Up\Knocked Up.mkv': A track with the ID 0 was requested but not found in the file. The corresponding option will be ignored.
The file 'J:\Movies Work\Knocked Up\Knocked Up-muxed-001.mkv' has been opened for writing.


The cue entries (the index) are being written...
The file 'J:\Movies Work\Knocked Up\Knocked Up-muxed-002.mkv' has been opened for writing.


The cue entries (the index) are being written...
The file 'J:\Movies Work\Knocked Up\Knocked Up-muxed-003.mkv' has been opened for writing.


The cue entries (the index) are being written...
The file 'J:\Movies Work\Knocked Up\Knocked Up-muxed-004.mkv' has been opened for writing.


I will post this on the SF page, as soon as I figure out how to!

~MiSfit

[Blue_MiSfit]

Reported. Let's hope this gets identified quick! :)

I haven't checked on MeGUI in awhile (a few months) and have noticed some very nice improvements. Great work guys!!

~MiSfit

[Kurtnoise]

@nurbs: great...just a request from me : could you test the Avisynth Creator in this build (http://www.mediafire.com/?2semmomqfae) please ? It's just to know if the Save Dialog event works fine...


@Blue_MiSfit: I'm trying to reproduce your issue but for the moment I can't...

[nurbs]

@Kurtnoise13: The Avisynth Script Creator works fine for me.

[Sharktooth]

@Blue_MiSfit: i cant reproduce it too

[Blue_MiSfit]

I will try erasing and re-installing all of meGUI and let it auto update everything. It's possible it got goofed up when I did my last big update.

[trooper11]

I was just wondering if there had been any progress on getting around the mediainfo problem in vista.

I tried downloading and installing the latest mediainfo (7.5.3 versus the 7.4.4 used in megui by default) and copied the mediainfo.dll to the megui folder, but megui still crashes whenever I try to open a video in the avisynth script creator.


I see a mediainfowrapper.dll file that isnt included with the mediainfo install, so I dont know if that file needs to be updated as well or not.

It definitely seems to be an issues with the mediainfo interaction. I even went as far as disabling preview, but that didnt change things either. I am using the latest build fo megui (2.6.1027).

[Sharktooth]

mediainfo in included in megui. you dont need to manually update it and however the version included with megui is 7.5.3...

[Morte66]

A question out of curiosity...

meGUI has the option to do a pre-rendering job the huffYUV (or it'll be back soon). huffYUV encodes in YUY2, but the AviSynth scripts associated with meGUI usually work in YV12. So there is presumably some conversion going on. I was wondering, is this lossless (data transposition), or nearly lossless (just arithmetic roundings), or not lossless (e.g. blocks getting merged/split)?

Or have I just completely misunderstood the whole thing?

[Kurtnoise]

by definition, huffYUV is a lossless codec.

[mroz]

That doesn't answer Morte66's question. There's potentially a colour space conversion involved.

As it happens, Mencoder does Megui's huffy encode & it insists on YV12 input (indeed, if your script doesn't output YV12 it will add a call to ConvertYV12() at the end).

So if your script works in YV12 there are no problems, however if, say, you were using YUY2 in your script there would be data loss as the conversion would take you from chroma shared between 2 pixels to shared between 4 pixels.

As an aside, I've seen nasty results from chaining just two colourspace conversions. Scenario: I was using VDub to do a huffy encode which by default was encoding in YV12 space, however I couldn't get VDub to accept YV12 input, so as a quick fix added a conversion to YUY2 (I figured this would be ok as it is more refined than YV12). It turned out the conversions from YV12 to YUY2 to YV12 introduced a nasty yellow colour cast. In the end I configured VDub to encode in YUY2 & got rid of the colour cast. Always keep colour space conversions to a minimum. Which reminds me, I should have looked into why VDub wouldn't accept YV12 for me...

[Morte66]

So if your script works in YV12 there are no problems, however if, say, you were using YUY2 in your script there would be data loss as the conversion would take you from chroma shared between 2 pixels to shared between 4 pixels.

But AFAICT huffYUV encodes in YUY2 (or RGB), not YV12. At least it says so here (http://neuron2.net/www.math.berkeley.edu/benrg/huffyuv.html) . And I see no YV12 option on the ffdshow encoder. What makes you say it encodes in YV12? Is there a newer version kicking about or something? I'm confused...

[Morte66]

by definition, huffYUV is a lossless codec.

HuffYUV is lossless, but a stream starting in YV12 and going to huffYUV YUY2 and back to YV12 may not be lossless. That's what I'm trying to clarify.

To put it another way, if you took a YV12 stream and did ConvertToYUY2().ConvertToYV12(), would that be a lossless process?

[mroz]

But AFAICT huffYUV encodes in YUY2 (or RGB), not YV12. At least it says so here (http://neuron2.net/www.math.berkeley.edu/benrg/huffyuv.html) . And I see no YV12 option on the ffdshow encoder. What makes you say it encodes in YV12? Is there a newer version kicking about or something? I'm confused...

I assume that description applies to that specific implementation. Megui uses Mencoder which contains its own. The only thing I can say for certain is that it will insist on YV12 input as I said - I've read the source code which inserts the conversion if the format isn't YV12 (see MPlayer sources trunk\libmpdemux\demux_avs.c around lines 259-282).

As to the ffdshow implementation, it allows a choice of YUY2 & YV12. I'm using rev 1058 Mar 22 2007 though I have no reason to assume this is a new option. See VFW config -> Encoder tab -> Generic options -> colourspace.

[Morte66]

I assume that description applies to that specific implementation. Megui uses Mencoder which contains its own. The only thing I can say for certain is that it will insist on YV12 input as I said - I've read the source code which inserts the conversion if the format isn't YV12 (see MPlayer sources trunk\libmpdemux\demux_avs.c around lines 259-282).

As to the ffdshow implementation, it allows a choice of YUY2 & YV12. I'm using rev 1058 Mar 22 2007 though I have no reason to assume this is a new option. See VFW config -> Encoder tab -> Generic options -> colourspace.

Ah, got it. That all makes sense. Thanks.

[rack04]

Should the input DAR in the avisynth creator automatically select the correct DAR of the source? The last .ts OTA HD recording I tried it defaulted to 1:1.

[Raere]

I've been seeing lots of new de-interlacing filters lately. I see that Yadif was added, and that's awesome. But, are there plans to add support for NNEDI or MCBob? I have no idea how to use them, and it'd be good to have them built into the avisynth script creator for correct usage.

[Sharktooth]

write a feature request in the appropriate place.

[vazel]

Can someone tell me why I would be getting interlace artifacts in the encode from a video megui detected as progressive? This scene doesn't have these artifacts in the DVD. From what I've seen of the other action scenes in the encode they don't have interlace artifacts although I haven't seen the entire encode don't feel like doing that right now. This scene is very jerky does that have something to do with it? I can upload a sample if that helps although this scene has gore in it.

http://la.gg/upl/vlcsnap-290451.png (http://la.gg)

[Selur]

probably hybrid material that isn't detected as such,...

[Sharktooth]

yup... hybrid stuff is always a PITA.

[rack04]

Should the input DAR in the avisynth creator automatically select the correct DAR of the source? The last .ts OTA HD recording I tried it defaulted to 1:1.

Can anyone comment on this?

[fields_g]

Can someone tell me why I would be getting interlace artifacts in the encode from a video megui detected as progressive? This scene doesn't have these artifacts in the DVD. From what I've seen of the other action scenes in the encode they don't have interlace artifacts although I haven't seen the entire encode don't feel like doing that right now. This scene is very jerky does that have something to do with it? I can upload a sample if that helps although this scene has gore in it.


I work with a lot of hybrid and have noticed that I have much more problems with the "TIVTC + TDeint(EDI) -- slow" vs. "TIVTC" alone. Make sure you are using "TIVTC" as your deinterlacer in your AVS script creator.

Wanna post your scripts?

[vazel]

I already deleted it but I'll be sure that when I reencode the movie to take your advice.

[berrinam]

I work with a lot of hybrid and have noticed that I have much more problems with the "TIVTC + TDeint(EDI) -- slow" vs. "TIVTC" alone. Make sure you are using "TIVTC" as your deinterlacer in your AVS script creator.
This is why the order of these two has been changed in MeGUI, so that TIVTC is first.

[vazel]

What do I put in the field order, do I choose 'top field first'? For source type I have it set to 'Hybrid film/interlaced. Mostly film'
I'm new to all this. Are these settings okay?

http://la.gg/upl/Clipboard02_30.jpg (http://la.gg)

[berrinam]

Should the input DAR in the avisynth creator automatically select the correct DAR of the source? The last .ts OTA HD recording I tried it defaulted to 1:1.

Files that are opened with DirectShowSource or AviSource are assumed to have SAR of 1:1. Generally this won't mean DAR of 1:1 except in the case where hres=vres.

Files that are opened via mpeg2source should have the DAR autodetected by parsing the d2v file. I believe that *.ts files can and should be done using d2v files (ie they need to be indexed first) so if you did it with DirectShowSource, then that's a bad idea, and if you did it with DGIndex, then it could be right, your stream could be wrong, DGIndex could be wrong, or MeGUI is parsing the d2v file wrong.

[rack04]

Files that are opened with DirectShowSource or AviSource are assumed to have SAR of 1:1. Generally this won't mean DAR of 1:1 except in the case where hres=vres.

Files that are opened via mpeg2source should have the DAR autodetected by parsing the d2v file. I believe that *.ts files can and should be done using d2v files (ie they need to be indexed first) so if you did it with DirectShowSource, then that's a bad idea, and if you did it with DGIndex, then it could be right, your stream could be wrong, DGIndex could be wrong, or MeGUI is parsing the d2v file wrong.

Yes I am using the d2v file. Has any changes been made to this because using this same procedure used to result in the correct DAR being selected?

[Sharktooth]

Yes, updated dgindex...

[berrinam]

I suspect it was a bug introduced by - (berrinam) Fix #1812842 (ITU 4:3 is wrong)

Can you post the beginning of your d2v file please? I want the stuff before all of the numbers. It should look something like this: Stream_Type=1
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=720x576
Field_Operation=0
Frame_Rate=25000 (25/1)
Location=0,0,0,7ff4d

Can you also post what the correct DAR should be please?

EDIT: I suspect it should be fixed in SVN rev297. But can you please still post the information so I can add it as a testcase? Thanks.

[rack04]

I suspect it was a bug introduced by - (berrinam) Fix #1812842 (ITU 4:3 is wrong)

Can you post the beginning of your d2v file please? I want the stuff before all of the numbers. It should look something like this: Stream_Type=1
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=720x576
Field_Operation=0
Frame_Rate=25000 (25/1)
Location=0,0,0,7ff4d

Can you also post what the correct DAR should be please?

EDIT: I suspect it should be fixed in SVN rev297. But can you please still post the information so I can add it as a testcase? Thanks.

I'm sorry but I'm out of town till Friday. I'll post it then.

[rack04]

I suspect it was a bug introduced by - (berrinam) Fix #1812842 (ITU 4:3 is wrong)

Can you post the beginning of your d2v file please? I want the stuff before all of the numbers. It should look something like this: Stream_Type=1
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=720x576
Field_Operation=0
Frame_Rate=25000 (25/1)
Location=0,0,0,7ff4d

Can you also post what the correct DAR should be please?

Here is the information that you requested.

Stream_Type=2
MPEG2_Transport_PID=31,34,31
Transport_Packet_Size=188
MPEG_Type=2
iDCT_Algorithm=6
YUVRGB_Scale=1
Luminance_Filter=0,0
Clipping=0,0,0,0
Aspect_Ratio=16:9
Picture_Size=1920x1080
Field_Operation=0
Frame_Rate=29970 (30000/1001)
Location=0,0,0,feba9

The DAR should be ITU 16:9 NTSC (1.822784) and in MeGUI it is defaulted to 1:1. I'll update to the latest version and try it again.

[Carpo]

Warning: The AC3 track 0 from 'D:\dvdrwork\VTS_02_1 T01 3_2ch 448Kbps DELAY 0ms.ac3' contained 896 bytes of non-AC3 data which were skipped. The audio/video synchronization may have been lost.

is the error i see in megui when trying to mux the film im working on atm, have ripped the video in dvd decrypter - with ripitforme, using full disc mode and ifo mode, and all versions of dgindex from 1.49 to lastest 1.50 beta, and still the error remans.

i have even tried the suggestion of moving the slide bar along in dgindex and clipping out the first few frames still the problem remains

is this a bug, user error, or just a fluke of luck? ;)

[Kurtnoise]

Try to extract your audio streams with DVDDecrypter instead of DGindex and redo a mux...

[Carpo]

tried the raw option and it seems to have muxed ok without that error - will give it a play and seem how its turned out, just out of interrest the file from dgindex was 380meg where as the one form dvd decrypter was 386meg - does that sound right ?

[rack04]

The DAR should be ITU 16:9 NTSC (1.822784) and in MeGUI it is defaulted to 1:1. I'll update to the latest version and try it again.

Updated version works great. Thanks for the bug fix.

[Kurtnoise]

seem how its turned out, just out of interrest the file from dgindex was 380meg where as the one form dvd decrypter was 386meg - does that sound right ?
sounds right for me...maybe a bug in DGindex or something.

[Carpo]

ok - strange as its only done it to me on this film - all the others i have done have been fine

[Sharktooth]

upgrading to 0.2.6.1033 may be problematic
please read this BEFORE upgrading: https://forum.doom9.org/showthread.php?p=1058892#post1058892

[mutha88]

Excuse me mates, but how can i extract/transcode or wahatever a DTS stream from a Matroska file?

I wish to add the DTS stream from one file to another.How can i do that? THANK YOU in advance!:thanks:

[setarip_old]

@mutha88

Hi!

See my response (and please answer my questions posted there) to your other (Duplicate) posting.

Multiple posting of the same question is a violation of the rules of the DVD9 Forum...

[Al79]

What do I put in the field order, do I choose 'top field first'? For source type I have it set to 'Hybrid film/interlaced. Mostly film'
I'm new to all this. Are these settings okay?

http://la.gg/upl/Clipboard02_30.jpg (http://la.gg)

U can use the autodetect option, if that doesn't work, try with dgindex, and see what say, video type, field order... etc, u can find dgindex, in ur megui folder, megui--tools-dgindex... if u still have problems, check the guides section, i hope this help u

p.d. engrish ftw xD

[rack04]

With the latest DGDecode update the zipped file remains unzipped in the \tools\dgindex folder. Do I manually unzip this into this folder?

[Kurtnoise]

Relaunch the updater...

[rack04]

Relaunch the updater...

No change.

[Kurtnoise]

did you close MeGUI first ?

[rack04]

did you close MeGUI first ?

Yes I did close MeGUI first.

[Sharktooth]

oh.. not a big problem. just delete the zip file...
it is there by mistake but the dgdecode plugin is updated.

[rack04]

oh.. not a big problem. just delete the zip file...
it is there by mistake but the dgdecode plugin is updated.

Where is the dgdecode plugin saved?

http://i11.photobucket.com/albums/a199/rack04/untitled-2.jpg

[Sharktooth]

into the avisynth plugin directory. however trust me... that zip was erroneously placed into the dgindex zip.

[rack04]

into the avisynth plugin directory. however trust me... that zip was erroneously placed into the dgindex zip.

Perfect. Thanks.

[decayed.cell]

Question/Feature request: Would it be possible for MeGUI to only download components needed for encoding what the user wants? i.e. I only use MeGUI to encode clips for my iPod using x264 and thus don't need to download all the other external components for MeGUI which I will never use

[Sharktooth]

just uncheck the updates you dont want to download.

[decayed.cell]

just uncheck the updates you dont want to download.
I tried that, but when MeGUI errored because not enough components were present (figures :p) this happened when I ran the updater again

http://img451.imageshack.us/img451/9067/errorna5.th.jpg (http://img451.imageshack.us/my.php?image=errorna5.jpg)

[Sharktooth]

where did you get megui? you should ALWAYS use the installer to install it...

[decayed.cell]

where did you get megui? you should ALWAYS use the installer to install it...
Link as described here (http://forum.doom9.org/showthread.php?t=131145)

It works fine again after I've uninstalled and installed again, but choosing to download all updates instead

[Sharktooth]

The installer comes with sharpziplib. it's a bit "unrealistic" megui couldnt find it unless you deleted the lib or your local copy of the installer was corrupt.

[decayed.cell]

The installer comes with sharpziplib. it's a bit "unrealistic" megui couldnt find it unless you deleted the lib or your local copy of the installer was corrupt.
Well the first time I installed it was with all the core packages and only DGIndex, and after that went haywire when I tried to update again I uninstalled and ran the same installer but updated fully. So it's a bit "unrealistic" that the installer was corrupt too =)

[Sharktooth]

then something went wrong during the update and the sharpziplib was mysteriously deleted...

[~bT~]

I am unable to update MeGUI now for a long time. Everytime it crashes with this error message:

http://i2.tinypic.com/5yssw0p.jpg

Any help appreciated.

EDIT: Solved. Installed latest version and had to update twice as it crashed 1st time round.

[andrewwan1980]

(MeGUI 0.2.5.1007)

1. One Click Encoder

The Avisynth profile '' could not be properly configured. Presumably the profile no longer exists.


2. If I set the Target One Click profile, does that override the Advanced Config & Encoder Config tabs?

[Sharktooth]

0.2.5.1007 is OUTDATED. Try the latest dev version.

[rack04]

When muxing a x264 codec with mkv file format the fps doesn't automatically set. Using x264 with mp4 file format the mux automatically sets the fps. Is this by design?

[Sharktooth]

what megui version you have?
before reporting possible bugs ALWAYS try the latest dev version. If you experience the same problem than report it.

[rack04]

what megui version you have?
before reporting possible bugs ALWAYS try the latest dev version. If you experience the same problem than report it.


I am using 0.2.6.1034

[Sharktooth]

ok, thanks.

[ACrowley]

Bugs Build 0.2.6.1034

-encoding Log is not saved after encoding
-Elapsed Time still resets after 24h.

[Kurtnoise]

Bugs Build 0.2.6.1034

-encoding Log is not saved after encoding
video or audio encoding ?

-Elapsed Time still resets after 24h.
this hasn't been fixed yet...

[ACrowley]

@Kurtnoise

Video encoding Log isnt saved.. I dont use Audio Encoding in megui but i assume audio log wont save too

Elapsed Time not fixed yet....Ok, but why is it so hard to fix ?

[Kurtnoise]

Video encoding Log isnt saved.. I dont use Audio Encoding in megui but i assume audio log wont save too
your assumption for Audio Encodings is wrong...all works fine here.

Elapsed Time not fixed yet....Ok, but why is it so hard to fix ?
Probably because developpers are not motivated to fix and test encodings more than 24h. :stupid:

[Kurtnoise]

@Acrowley: about Time Elapsed issues: try this build (http://www.mediafire.com/?emabblo2xij) please and report feedback.

[ACrowley]

@Acrowley: about Time Elapsed issues: try this build (http://www.mediafire.com/?emabblo2xij) please and report feedback.


i will test it ..THX

AH, Video enc log is saved again:) Dont know why it wasnt saved after updateing to latest Build 1034.

EDIT:
You made the Megui internal Time independet from System Time in your test build ,right ?
When i change the Windows Clock the ElapsedTime/fps in status windw is stable....in older builds it was changing with the Windows Clock :)

I will report back later after the 24h Border if its stable now...

[joran]

Hey everyone, hoping you guys could help with a question I had. I am encoding DVDs to watch from a standalone player using DVDDecrypter, MeGUI, and mkvmerge. I'm fairly new to x264 encoding and it's been a fun process learning about the ins and outs of it, but one thing I haven't been able to figure out despite looking around a lot:

My player (unfortunately) does not support, or at least doesn't obey, any DAR flags set in MKVs (it's a TViX 4100SH in case anyone is interested). I've therefore had to resize the anamorphic DVD for it to display correctly. I'm curious as to what the better approach would be for this given, say, a 720x480 NTSC DVD (2.35 DAR), cropped to remove borders down to 720x368. Should I now:

a) resize to 720x304
b) resize to 864x368
c) something else?

I guess I'm wondering whether a) will mean throwing away information unnecessarily and losing quality, or b) will mean upscaling without any quality benefit. Ideally I'd like to retain as much information as possible from the DVD, so I was leaning toward b), but given that the whole image needs to be resized to fit the screen anyway it may just be worse to do it twice - once while encoding and once while playing.

Also, this is a bit weird, but I've discovered that when using MeGUI to encode anamorphically, my player _will_ show the image correctly if I tell MeGUI to use an MKV container instead of MP4 for the video. This only happens if I don't mux any audio in - as soon as I use MeGUI, mkvmerge or anything else to try and add audio, subtitles, or chapters, suddenly it stops playing in the correct aspect ratio. Even running mkvmerge to re-package the original MKV without adding any other tracks will break it. Is there anything about the x264.exe MKV output code that would make it any different than mkvmerge or MeGUI's muxer? It's a bit baffling.

[RandomEngy]

If you just have a simple script like:

AviSource("d:\docs\heavy_test.avi")
ConvertToYV12()

Is it supposed to automatically bring over the audio track? I've got a source avi file with PCM audio but it always comes out silent.

I've also tried to do an audio encode with

WavSource("d:\docs\heavy_test.avi")

But the file is also silent. Is there something I'm doing wrong?

[ACrowley]

@Kurtnoise

No, Elasped Time resets to zero at 0.00 Time with Test Build

[kurt]

My player (unfortunately) does not support, or at least doesn't obey, any DAR flags set in MKVs (it's a TViX 4100SH in case anyone is interested). I've therefore had to resize the anamorphic DVD for it to display correctly. I'm curious as to what the better approach would be for this given, say, a 720x480 NTSC DVD (2.35 DAR), cropped to remove borders down to 720x368.
There should be no resizing necessary at all. Could you plz try these samples on your TviX? http://home.arcor.de/evil.bert/test/xvid.parsimpleblocks.rar

A user of the german doom9 forums reported they will be decoded correctly. If not you may have to update your firmware. I encoded the files with a par flag (-par 4 because the source is PAL) set in the bitstream with xvid_encraw and then muxed in mkv with mkvmerge (I didn't do any changes in the latter regarding DAR/PAR).

For a NTSC source you should try -par 5 with xvid_encraw or --sar 40:33 with x264. Either paramter can be set in MeGUI as well under "custom command line".

[mroz]

If you just have a simple script like:

AviSource("d:\docs\heavy_test.avi")
ConvertToYV12()

Is it supposed to automatically bring over the audio track? I've got a source avi file with PCM audio but it always comes out silent.

It should work. See the docs (http://avisynth.org/mediawiki/AviSource).

I assume the audio plays when you watch the avi in a media player? Try GraphEdit to see if it plays it; if it doesn't, fix your codecs & repeat.

Try opening the file in your script using DirectShowSource. If that still doesn't work demux the audio & try opening the audio track.

[joran]

There should be no resizing necessary at all. Could you plz try these samples on your TviX? http://home.arcor.de/evil.bert/test/xvid.parsimpleblocks.rar

A user of the german doom9 forums reported they will be decoded correctly. If not you may have to update your firmware. I encoded the files with a par flag (-par 4 because the source is PAL) set in the bitstream with xvid_encraw and then muxed in mkv with mkvmerge (I didn't do any changes in the latter regarding DAR/PAR).

For a NTSC source you should try -par 5 with xvid_encraw or --sar 40:33 with x264. Either paramter can be set in MeGUI as well under "custom command line".

Thanks - I tried the samples and they all play correctly, no aspect ratio problems at all. I tried using MeGUI to encode using both --sar 1201:1000 and --sar 40:33. It plays fine when I tell MeGUI to output to MKV, but when I output to MP4 and use mkvmerge to create an MKV out of the MP4, it plays stretched.

Oddly enough, if I take the sample AVI and use mkvmerge to turn it into an MKV, it plays fine. But when I take my MKV and re-merge it into another MKV, it doesn't play correctly.

Here are my AVS script and x264 command line for reference:


# Set DAR in encoder to 47 : 20. The following line is for automatic signalling
global MeGUI_darx = 47
global MeGUI_dary = 20
DGDecode_mpeg2source("Source.d2v",info=3)
ColorMatrix(hints=true)
#deinterlace
crop( 0, 54, 0, -58)

#resize
Undot() # Minimal Noise

__film = last
__t0 = __film.trim(5000, 6000)
__t0


x264.exe --crf 18.0 --ref 3 --mixed-refs --bframes 16 --b-pyramid --bime --weightb --filter -2,-1 --subme 1
--analyse p8x8,b8x8,i4x4,i8x8 --8x8dct --me umh --threads auto --thread-input --sar 1201:1000 --progress --no-psnr --no-ssim

[kurt]

@ joran: strange....on your computer you have the correct AR with the mp4 file and on the tvix you have not? If so you may have to report your problem to the TviX-Guys...

[joran]

@kurt: Well, I'm actually less inclined to think it's a problem with the TViX now given that it plays those sample files fine, and it plays an MKV created by MeGUI fine as well. It's only when I tell MeGUI to output to MP4 and use mkvmerge to make an MKV that the picture plays distorted.

I have no clue what could cause this at all, though - I've tried using an older version of mkvmerge (2.0.2 instead of 2.1.0) with the same result. I've tried manually setting the DAR to 2.35 as well as setting the pixels to 835x368, 47x20, 10809x4600 in mkvmerge, all without success. I can't figure out what is different between the MKV produced by x264.exe / MeGUI and the one produced by mkvmerge that is causing the problem...

[Sharktooth]

AR is usually stored in 2 places. In the video bitstream and the container. If those, for various reasons, do not match then there could be problems depending on the software/hardware used for playback.

[joran]

Is there any tool out there that would let you inspect the AR stored in the bitstream?

As far as I can tell, they should be in sync. The cropped resolution is 720x368. I tell MeGUI to use Clever anamorphic encoding, no overcrop or resize is required. MeGUI is telling x264 to use a SAR of 1201:1000, which by my calculations is correct:

368/720 * 47/20 = about 1201:1000, I guess 1081:900 would be more precise but it's close enough.

I'm telling MKVMerge to use display pixels of 864 x 368, to stretch the image horizontally out to 2.35 AR.

Maybe I'm doing something wrong?

ETA: I just loaded up the MP4 from MeGUI into VLC. In the stream info dialog, it lists both the Resolution and Display Resolution as 720x368. That seems wrong, since I expect the DR to be different, but the player displays the image fine and in a 2.35 AR. So I'm still confused.

[mroz]

AR is usually stored in 2 places. In the video bitstream and the container. If those, for various reasons, do not match then there could be problems depending on the software/hardware used for playback.
So possibly the player firmware could be improved, but still, this issue shouldn't normally arise, surely? Am I wrong to think generally the ar match?

Given problems arise from changing containers doesn't it seem most likely it's the ar in the container that becomes the problem? Once the vid stream is encoded none of these processes are going to alter the ar info embedded in it.

Is there a tool to inspect both stream & container aspect ratio? This does amount to a bug in one of the Megui tools it seems.

Does this player handle mp4s? If so, does the mp4 output direct from x264 play with the correct ar?

Edit: @joran - You could try a simple test encode where the ARs are pretty much guaranteed to match unless something's very wrong, by sticking with a simple SAR in x264 & corresponding exact dar in MVKMerge, eg with x264 override Megui's choice of SAR with 6:5 & stick with the 864 x 368 in MKVMerge. That'd be my first try if I couldn't find a tool to read/write the ARs directly.

[joran]

@mroz: The player does support mp4, I've been able to play various QT encodes, but unfortunately the box doesn't want to play this particular mp4 for whatever reason. It may be the lack of an audio track or something in the container that it doesn't like. It's probably not the H.264 stream itself since the same stream packaged in an MKV plays fine (albeit with a bad AR).

[mroz]

Hm, so maybe it doesn't like mp4box. That's annoying.

When you play back the working mkv compared to the problem one, on your desktop machine, do they both display using /exactly/ the same AR? If they do that doesn't tell you much, but if there's any difference it could certainly explain the problem.

[joran]

Well this is bizarre: playing back the x264-created MKV file using VLC, it's horribly off-ratio. It plays back in a thin vertical strip about 200x1000. It may have something to do with x264.exe writing the MKV display at 10809x4600. The same file plays back perfectly on the standalone box.

Re-muxing the working MKV with mkvmerge, leaving all settings alone, displays the same in VLC (horribly wrong) but on the standalone it displays in 1.95 aspect ratio (720x368 square-pixel).

I've tried to use mkvinfo to compare the working MKV with the non-working MKV (both of which have the exact same video stream), but there don't seem to be any glaring differences.

[RandomEngy]

It should work. See the docs (http://avisynth.org/mediawiki/AviSource).

I assume the audio plays when you watch the avi in a media player? Try GraphEdit to see if it plays it; if it doesn't, fix your codecs & repeat.

Try opening the file in your script using DirectShowSource. If that still doesn't work demux the audio & try opening the audio track.

Demuxing the audio with MeGui results in a silent audio file. I can extract to wav with virtualdub and try to mux it in in MeGui and it's still silent. It's also silent when I use DirectShowSource.

I can open it with GraphEdit and see the 48khz PCM wav track. I don't know what you mean by seeing if it "plays" it.

[St Devious]

Encoding status window disappears after first pass , and doesn't show up at all during second pass .

[mroz]

@joran: maybe VLC & your standalone simply don't like such large integers in the components of the aspect ratio. Why not replace them with 108x46 & test that on both?

@RandomEngy: The PCM track is I assume audible when you play the source avi, yes? When you open it in GraphEdit, click on play - does it play & can you see the video & hear the audio?

[joran]

Well, at this point I guess it's time to give up:

I just tried out Handbrake encoding a small test file from an anamorphic DVD. It plays flawlessly on my standalone box. I open up mkvmerge, load the MKV and save it out to another file, and it's broken - aspect ratio blown away. Could it be an issue with mkvmerge, of all things? mkvinfo states the two MKV files have the exact same values for pixel and display ratios.

So, the direct MKV output from both MeGUI and Handbrake works fine, but I want to add additional audio tracks (commentary, etc) as well as subtitles and chapters, which requires me to use mkvmerge. But using mkvmerge for any working MKV will bust the display ratio, so I guess I'm back to resizing down and encoding non-anamorphically.

Are there any other MKV muxers I could try out? The muxing/writing application flags for the working files are "Haali Matroska Splitter"\"x264" and "libmkv"\"Handbrake"

ETA @mroz: I had the same thought, but the big numbers are what x264/MeGUI is spitting out, and that file plays fine on the standalone. In order to lower the values I'd have to use mkvmerge which seems to be the kiss of death for my standalone, heh. Just to be sure, I tried a few variations (108x46, 47x20, 864x368) none of which worked.

[kurt]

Are there any other MKV muxers I could try out?
you could try gdsmux (wich is part of haali media splitter). Chapters should be possible, subtitles too I think.

One more question: did you try to encode a mp4 file direct from commandline? (without meGUI) and after that just muxing with mkvmerge?

[RandomEngy]

@RandomEngy: The PCM track is I assume audible when you play the source avi, yes? When you open it in GraphEdit, click on play - does it play & can you see the video & hear the audio?

Yes, it's audible when I play the source AVI. I can hear audio and see video when I play it in GraphEdit.

[andrewwan1980]

Can someone tell me the exact settings that go into NeroAACEnc.exe when used with MeGUI please? Assuming default settings except: Downmix multichannel to Stereo, AAC-LC, CBR (container: MP4-AAC, codec: ND AAC).

I want to compare the command-line settings used by MeGUI with AutoMKV.

[rack04]

Can someone tell me the exact settings that go into NeroAACEnc.exe when used with MeGUI please? Assuming default settings except: Downmix multichannel to Stereo, AAC-LC, CBR (container: MP4-AAC, codec: ND AAC).

I want to compare the command-line settings used by MeGUI with AutoMKV.

Do the encode and then check your MeGUI logs. The command-line will show there.

[mroz]

Yes, it's audible when I play the source AVI. I can hear audio and see video when I play it in GraphEdit.
I'm puzzled that the audio plays in GraphEdit but loading the avi with DirectShowSource gives silent audio. What filters are involved in the chain?

You could try saving the working graph out of GraphEdit & opening that with DirectShowSource. Iirc you might have to delete the rightmost filter from the graph first - the one doing the rendering. /Checks - yes, delete the last filter in the audio chain. Also, in the DirectShowSource call specify video=false (as it can only handle .grf files with 1 stream).

If that doesn't work I really am at a loss. See the DirectShowSource docs (http://avisynth.org/mediawiki/DirectShowSource), enable logging & try to make sense of the output. Last time I had a problem a helpful guru materialised & took a look at my log for me.

If DirectShowSource with the .grf file plays the audio, unless that's good enough, you'll still need to check the DirectShowSource log to work out why it doesn't play otherwise.

Sorry I can't be more help.

Edit: How big are the files? If large, can you trim off a sample which still has the same problem properties? If you can upload a sample I can at least check the problem is local to your set up.

Can someone with more of a clue help RandomEngy?

[Kurtnoise]

@Kurtnoise

No, Elasped Time resets to zero at 0.00 Time with Test Build
Could you try to test this build (http://www.mediafire.com/?cedeyzx13nu) please....


:thanks:

[saint-francis]

Encoding status window disappears after first pass , and doesn't show up at all during second pass .

If you have the status window minimized when a job finishes this happens. The new window will not show up. You need to go to view -> process status -> show all when this happens and the new window will appear.

Could this be considered a bug?

[Sharktooth]

no. it's intentional. if you have the main windows minimized it's supposed you're "working" with other softwares and dont want megui show anything on the screen, possibly causing problems to full-screen DX apps or games or changing the focus of the foreground window just to display the megui status window...

[ACrowley]

Could you try to test this build (http://www.mediafire.com/?cedeyzx13nu) please....


:thanks:

yes....i will report back ,THX

[RandomEngy]

I'm puzzled that the audio plays in GraphEdit but loading the avi with DirectShowSource gives silent audio. What filters are involved in the chain?

You could try saving the working graph out of GraphEdit & opening that with DirectShowSource. Iirc you might have to delete the rightmost filter from the graph first - the one doing the rendering. /Checks - yes, delete the last filter in the audio chain. Also, in the DirectShowSource call specify video=false (as it can only handle .grf files with 1 stream).

If that doesn't work I really am at a loss. See the DirectShowSource docs (http://avisynth.org/mediawiki/DirectShowSource), enable logging & try to make sense of the output. Last time I had a problem a helpful guru materialised & took a look at my log for me.

If DirectShowSource with the .grf file plays the audio, unless that's good enough, you'll still need to check the DirectShowSource log to work out why it doesn't play otherwise.

Sorry I can't be more help.

Edit: How big are the files? If large, can you trim off a sample which still has the same problem properties? If you can upload a sample I can at least check the problem is local to your set up.

Can someone with more of a clue help RandomEngy?

Okay, problem 1, with this line only:

DirectShowSource("d:\docs\heavy_test.avi", logfile="logfile.txt")

it says it does not recognize the named argument "logfile" but it says it's there in the wiki.

I tried deleting the audio renderer as you said in graphedit, then rendering just the audio stream to mp3 for starters:

DirectShowSource("g:\heavy_project\heavy_test_noaudiorender.grf", video=False)

However it fails and I get this in the log:

Starting job job1 at 5:19:33 PM

Starting preprocessing of job...

Preprocessing finished!

successfully started encoding

Processing ended at 5:19:35 PM

------------------------------------------------------

Log for job job1



Error:

------------------------------------------------------

End of log for job1
------------------------------------------------------

I also tried this for the whole video:

video = DirectShowSource("d:\docs\heavy_test.avi", audio=False)
audio = DirectShowSource("g:\heavy_project\heavy_test_noaudiorender.grf", video=False)

mixed = AudioDub(video, audio)

ConvertToYV12(mixed)

Except that this time it told me that there was an error on line 2: that the filter graph won't talk to me.

I've uploaded a small sample clip (http://engy.us/videos/heavy_test_short.avi) that's giving me problems. The video is encoded as lagarith lossless, audio as 16-bit 48khz PCM.

One more interesting thing is when I view the resulting MP4 file in graphedit, it shows a video pin and an empty "closed caption" pin.

[mroz]

Okay, problem 1, with this line only:

DirectShowSource("d:\docs\heavy_test.avi", logfile="logfile.txt")

it says it does not recognize the named argument "logfile" but it says it's there in the wiki.

...From version 2.57. I guess you must be using an older one. Try updating?

[RandomEngy]

Ahh, you're right, I installed a new one and it logs now.

http://engy.us/videos/heavy_test_log.txt

[mroz]

I tried deleting the audio renderer as you said in graphedit, then rendering just the audio stream to mp3 for starters:

DirectShowSource("g:\heavy_project\heavy_test_noaudiorender.grf", video=False)

Rather than complicating the situation with another encoder, just try playing the avs in something like VDub.

/snip

I've uploaded a small sample clip (http://engy.us/videos/heavy_test_short.avi) that's giving me problems. The video is encoded as lagarith lossless, audio as 16-bit 48khz PCM.

One more interesting thing is when I view the resulting MP4 file in graphedit, it shows a video pin and an empty "closed caption" pin.

I installed the lagarith codec 1.3.14. Your file plays fine here. An avs reading the file with avisource or directshowsource plays video & audio either way. I'm afraid I can't help - you need someone more knowledgeable. My best suggestion is to update avisynth to 2.57 & try again; assuming it fails, get a log from DirectShowSource & start a new thread concerning DirectShowSource's failure to decode the file, along with the log.

Edit: just seen your reply with the log; hopefully someone who can follow it will help, but you might need to start a new thread to catch their attention.

Edit2: That's odd. It looks as though DirectShowSource has accepted the audio & is decoding it. Is it possible the problem is between AVISynth & whatever is rendering the audio? I'm probably wrong though - just guessing really.

Do post again in this thread if you discover the cause.

[ACrowley]

Could you try to test this build (http://www.mediafire.com/?cedeyzx13nu) please....


:thanks:

What i can say now is that when i change the Windows Time over 0.00 the Time Elapaed is correct and stays over 24h..no reset to 0h

I hope it works real tonight when the encoding reaches 24h and 0.00 a Clock

[RandomEngy]

Hey, it lets me encode just fine using the x264 VFW codec if I do it through virtual dub. I think I'll just use that; I'm tired of banging my head against the wall with MeGUI.

[ACrowley]

@kurtnoise

Nice...your new Tets Build works perferct!
Elapsed Time is at 30h , and Remaining Time seems to work stable too

Thank you!

[Kurtnoise]

\0/...that's great.

[ACrowley]

yeah..but i must correct me, the Remaining Time is still unstable

Example :
1080p x264 2pass takes 30h. But the Remaining Time after 5h encoding is only 3h , few hours later its 10h ...etc etc etc

I can remember, in old Builds it was one static Value which was correct Remaining Time

[mroz]

I find it hard to believe it ever gave an accurate prediction for the end of pass two while it was in pass one, but it could be more helpful than it currently is. ATM I assume it predicts based on percentage progress (treating each of n passes as 100/n percent) assuming a progress rate of the current average since start. Naturally with a fast first pass one gets low estimates during the first pass, which then steadily climb.

A better simple solution would be to assume a progress rate based on a moving window average - ie just use average speed for the last s seconds of encoding.

As to a method that would give useful figures for final completion even during early stages, the only method I can conceive off would have to build up speed profiles for the various jobs. This could be done by logging average fps for each of the last j jobs, with these stats recorded for each pass (where applicable) of each defined profile (the stats might need to be wiped when a profile is edited). Initially when stats aren't available, it would have to fall back to the cruder method, but once you had a few runs in, it should give reasonable results.

Edit: re wiping stats, a better automated heuristic might be: flag when a profile is edited & if measured fps deviates significantly from the logged average, wipe the stats log for that profile.

[Kurtnoise]

yeah..but i must correct me, the Remaining Time is still unstable

Example :
1080p x264 2pass takes 30h. But the Remaining Time after 5h encoding is only 3h , few hours later its 10h ...etc etc etc

I can remember, in old Builds it was one static Value which was correct Remaining Time
:eek: Time Remaining code is the same since the beginning...I didn't modify it.

Maybe your CPU was busy by multiple tasks ?

[fleon]

I have a problem with megui: I installed and opened then i started to update megui with everything but when mencoder is completed I get and error also I reopened the program and tried to update another componet or external program I get the same error, I also have staxrip installed, this is the error:

http://img444.imageshack.us/img444/2793/meguiru7.th.jpg (http://img444.imageshack.us/my.php?image=meguiru7.jpg)

[uncertainty]

I have a problem with megui: I installed and opened then i started to update megui with everything but when mencoder is completed I get and error also I reopened the program and tried to update another componet or external program I get the same error, I also have staxrip installed, this is the error:

http://img444.imageshack.us/img444/2793/meguiru7.th.jpg (http://img444.imageshack.us/my.php?image=meguiru7.jpg)


I'm getting the same error message as you are with megui's auto updater. It just started yesterday with trying to update just the core. I'll just turn off auto updater till we get more feedback on this issue.

[Sharktooth]

do a clean install AND before updating set the auto-update to development server.
it should fix things until the "stable" folder on the auto-update server will be updated.

[St Devious]

do i have to auto-update everytime i install a new version of megui ?

[saint-francis]

Every time you do a clean install you do but if you just update the core through the auto update function you will only have to restart MeGUI.

[berrinam]

A better simple solution would be to assume a progress rate based on a moving window average - ie just use average speed for the last s seconds of encoding.I did that for one of the tools (the Avisynth analysis pass) and it was probably fine, but I since removed it when I simplified the code so that all the processors use the same time estimation code. I thought about a moving average, but I went for the current method because I'm lazy and the code without a moving window average looks nicer: no variables about the last update time. But that's just laziness. Please post this to the feature request tracker so that it doesn't get forgotten, and it will be seen to eventually.

[awx]

I'm getting this error when I try to open a D2V with the AVS Script Creator:
Cannot open video input
---------------------------
The file E:\XYZ\VTS_01_PGC_01_1.d2v cannot be opened.

Please make sure it's a valid AviSynth script and that AviSynth is properly installed.

You can check the validity of your script and AviSynth installation by opening the file in your favorite media player.

If that works, try opening the video in VirtualDub(Mod) as well. If the former works and the latter doesn't, install a YV12 codec.

Error message for your reference: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

I've tried doing several clean installs of MeGUI, reinstalling AVISynth and switching to the development update servers.

Any ideas what is wrong? MeGUI was working great until the new version came out.

[kumi]

Ditto, I reported it on the bug tracker.

[awx]

Ditto, I reported it on the bug tracker.
Where is your bug? I just checked the tracker on SF and cannot find it.

Also, I just finished a clean install of the .1038 version and this problem still exists for me.

[mroz]

Where is your bug? I just checked the tracker on SF and cannot find it.

Also, I just finished a clean install of the .1038 version and this problem still exists for me.

1832210 (https://sourceforge.net/tracker/index.php?func=detail&aid=1832210&group_id=156112&atid=798476)

[Sharktooth]

i "closed" the report since doing a clean install fixes the problem.
ensure you remove everything related to megui (including the update_cache folder) and then install the latest version.

[vtn54]

Dear Sharktooth, Clean install don't solve this problem, problem comes from the MediaInfoWrapper.dll in new version ,replacing it with old version solved this problem for me.

[kumi]

Confirmed, it's MediaInfoWrapper.dll.

MediaInfoWrapper.dll 0.7.5.3 = broken
MediaInfoWrapper.dll 0.7.4.4 = working again

Thanks vtn54.

[knary]

Hi

can you plz make MeGui doing 2-pass with Nero AAC

because that what i have read in NeroAACEnc docs


Multipass encoding:
-2pass : Enables two-pass encoding mode.
Note that two-pass more requires a physical file as input,
rather than stdin.
-2passperiod : Overrides two-pass encoding bitrate averaging period,
<number> : in milliseconds.
: Specify zero to use least restrictive value possible (default).


also here

I am pleased to announce the launch of FREE Reference Quality MPEG-4 Audio solution from Nero, in the command line form!

* First in the world FREE 2-Pass MPEG-4 AAC Encoder
* Compression Ratios ranging from ultra high (58 CDs fit on one!) to High-End Audio (2.5:1), for absolutely perfect audiophile encodings
* Crystal Clear, Award Winning Sound Quality at every compression ratio and bit rate!
* Support for Embedded Album Art (Covers, Booklets, Lyrics!)
* Store Entire Audio Album in a Single .mp4 File with all the Features of an Audio CD embedded inside, but at a fraction of the space!
* Reference Quality MPEG-4 Audio Codec
* Fully Compatible with the Latest Version of the State-of-the-art MPEG-4 Audio Standard (LC-AAC, HE-AAC and HE-AAC v2)

http://www.nero.com/nerodigital/eng/Nero_Digital_Audio.html

:thanks:

[Doom9]

@knary: that has been brought up a long long time ago. If you look at how megui works, you'd realize why it wasn't possible then and it's not possible now.

[ACrowley]

:eek: Time Remaining code is the same since the beginning...I didn't modify it.

Maybe your CPU was busy by multiple tasks ?


Mh... so far i can remember the Remaining Time was one static Value from encoding beginning on.
And the Value was more or less correct

In new Builds its sometimes 3h and later 30h again...it jumps around

I use Threads=0 on my X2 Dual Core for x264 encoding

But i dont think its a megui Problem :) I noticed the same on x264 cli

[DeathAngelBR]

Confirmed, it's MediaInfoWrapper.dll.

MediaInfoWrapper.dll 0.7.5.3 = broken
MediaInfoWrapper.dll 0.7.4.4 = working again

Thanks vtn54.

I get the error even with 0.7.4.4 :confused:

[ACrowley]

Thx for the new Update :=
Looks like the Remainig Time is stable now !
It starts with one Remaining Time and counts down to zero..
And the Encoding Time is correct

[oLex]

please, add ukrainian language to list of languages for muxing.

[SBaT]

0.3.0.1 dosent show in log tab for 1-pass or 2-pass any x264 [info] so no psnr,ssim or quants info. Same goes for log file that megui writes.

[berrinam]

Thx for the new Update :=
Looks like the Remainig Time is stable now !
It starts with one Remaining Time and counts down to zero..To be honest, I hadn't noticed any problems with this before. Out of interest, could you tell me what kind of job you were doing and what settings you used?

[ACrowley]

0.3.0.1 dosent show in log tab for 1-pass or 2-pass any x264 [info] so no psnr,ssim or quants info. Same goes for log file that megui writes.

Yes..
Is it bug or a "new Feature" ?! No x264 encoding Stast/Quants etc anymore with the newest Build

Its absolutly essentital for me to get my x264 Stats

Hope we get a fix soon!

[Kurtnoise]

http://forum.doom9.org/showthread.php?p=1069002#post1069002

[skystrife]

I had been running with --no-psnr and --no-ssim in the old version and was getting data on the quants. Hopefully this can be added back into the log?

TBH, I preferred the old, text-based log. Maybe there's a way to have the user choose what level of logging they want displayed?

[berrinam]

TBH, I preferred the old, text-based log.I found the old log a mess, with information everywhere. Why did you prefer it?

You know you can get a plain-text view of the log by going right-click->edit log?

[check]

Please return the full output from x264 to the MeGUI log. With the new log style it would presumably be added as a single collapsed element, so the cost is very little. Personally I find MeGUI almost useless without this information being available -- and I'd very much like to see it return.

[berrinam]

As I said in the development thread, any information missing from the new log is simply a bug. It has now been fixed in svn rev406. You'll have to wait for an update, though...

[check]

gwar, sorry for getting a little fired up then :p

[Sharktooth]

ill release an up to date build as soon as i can.

[avdw]

It still doesn't work, when converting the ac3 to mp3, it produces an mp3 that plays at about 50x the speed. Why Oh Why ?!?

AC3 plays perfect, problem must be in lame.

--[Information] [24/11/2007 21:21:16] Started handling job
--[Information] [24/11/2007 21:21:16] Preprocessing
--[NoImage] Job commandline: "C:\Program Files\megui\tools\dgindex\dgindex.exe" -SD=< -AIF=<N:\My DVDs\Midnight Express 16-9\VTS_01_1.VOB< -OF=<N:\My DVDs\Midnight Express 16-9\VTS_01_1< -exit -minimize -OM=2
--[Information] [24/11/2007 21:21:16] Encoding started
--[Information] [24/11/2007 21:22:44] Running auto force film
---[NoImage] Film percentage: -1
--[Information] [24/11/2007 21:22:44] Job completed
--[Information] [24/11/2007 21:22:44] Postprocessing
-[Information] Log for job5
--[NoImage] Job type: audio
--[Information] [24/11/2007 21:23:27] Started handling job
--[Information] [24/11/2007 21:23:27] Preprocessing
--[Information] [24/11/2007 21:23:27] Encoding started
--[Information] Input
---[NoImage] Channels: 2
---[NoImage] Bits per sample: 16
---[NoImage] Sample rate: 48000
--[NoImage] Commandline: C:\Program Files\megui\tools\lame\lame.exe -b 112 --cbr -h --silent - "N:\My DVDs\Midnight Express 16-9\VTS_01_1 T01 2_0ch 192Kbps DELAY 0ms.mp3"
--[Information] [24/11/2007 21:31:49] Job completed
--[Information] [24/11/2007 21:31:49] Postprocessing

[skystrife]

I found the old log a mess, with information everywhere. Why did you prefer it?

You know you can get a plain-text view of the log by going right-click->edit log?

The tree-based log may look pretty, but I honestly don't need to know the version info or the settings within the log, and the text-based log made it easier to see everything in one place rather than having to edit each and every tree to see my info.

Main beef atm is the lack of quant distribution info, but that will be fixed in the next update apparently.

I don't know really, I just liked it text-based. Maybe it's just because I've become used to it that way after so long, but the tree structure makes it more complicated than it was before (for me). Sure the log would get lengthy if you ran a ton of jobs in one session, but so long as you knew what each job was you could find your information fairly easily.

Also, with the current tree-based log, you're only getting minimal info at a glance. I preferred to be able to flip to my log tab and quickly be able to tell what job was what by looking at the input and see what my quant distribution was like after finding the correct job. Granted, I suppose I can get this by editing the log, but it's one extra step and I'm lazy I guess. =P

EDIT: Also, while I'm here, a neat feature that could be added to the bitrate calculator came to my mind. It currently allows user-inputted target filesizes, but doesn't seem to save these (at least, it doesn't on my system). If you could allow the user to save his/her own target filesizes that would be kind of neat. (I know a common size is 1/3CD or 233MB, it would be nice to have that as easily accessible as the 175MB.)

Just a thought, figured I'd share it. =)

[berrinam]

The tree-based log may look pretty, but I honestly don't need to know the version info or the settings within the log,That's debug information for bug-reports, not for the users. :)

and the text-based log made it easier to see everything in one place rather than having to edit each and every tree to see my info.Perhaps you would like a feature which opened every node of the treeview?

I don't know really, I just liked it text-based. Maybe it's just because I've become used to it that way after so long, but the tree structure makes it more complicated than it was before (for me). Sure the log would get lengthy if you ran a ton of jobs in one session, but so long as you knew what each job was you could find your information fairly easily.I believe that finding the job is much easier in the new tree-based log; simply because so many more jobs fit on one page, so you don't have to scroll. But perhaps you would be able to see more "at a glance" if we added some information to the job's root node -- instead of just calling it "Log for job33", we could call it "Log for job33 (video, InputFile -> OutputFile)". Would that be more useful?

From a technical point of view, I believe the new log is definitely superior as it provides better error logging capabilities. Also, it should make it easier to find jobs with warnings or errors, since the error/warning icons stand out from the standard info icons.

However, the main advantage of the new log is that it handles parallel job encoding correctly, whereas the old log just put the messages in the order they came, so multiple parallel jobs would clash with each other's log messages.

EDIT: Also, while I'm here, a neat feature that could be added to the bitrate calculator came to my mind. It currently allows user-inputted target filesizes, but doesn't seem to save these (at least, it doesn't on my system). If you could allow the user to save his/her own target filesizes that would be kind of neat. (I know a common size is 1/3CD or 233MB, it would be nice to have that as easily accessible as the 175MB.)This was added in version 0.3.0.1. The custom filesizes you select will be remembered and available next time you open the bitrate calculator.

[mroz]

Perhaps you would like a feature which opened every node of the treeview?

I was just going to suggest that.

Do nodes have different classifications, such as a distinction between debug levels or debug vs user info? If so, then options to expand/collapse nodes according to class would be handy, perhaps.

[skystrife]

That's debug information for bug-reports, not for the users. :)

Oh, alright then. =P

Perhaps you would like a feature which opened every node of the treeview?

That might be nice. I had an idea though, specifically regarding getting the quants information. I really don't like the idea of having to edit the log to find my quants info, so maybe I can expand the tree at some level in the job and see the quants info there?

I believe that finding the job is much easier in the new tree-based log; simply because so many more jobs fit on one page, so you don't have to scroll. But perhaps you would be able to see more "at a glance" if we added some information to the job's root node -- instead of just calling it "Log for job33", we could call it "Log for job33 (video, InputFile -> OutputFile)". Would that be more useful?

That would be an awesome feature and would make it really easy to figure out which job you actually wanted to be looking at! =)

From a technical point of view, I believe the new log is definitely superior as it provides better error logging capabilities. Also, it should make it easier to find jobs with warnings or errors, since the error/warning icons stand out from the standard info icons.

However, the main advantage of the new log is that it handles parallel job encoding correctly, whereas the old log just put the messages in the order they came, so multiple parallel jobs would clash with each other's log messages.

That's true; I didn't think about parallel encoding logging issues. The new log is most likely a step in the right direction but it could use some little adjustments here and there to make information just a bit more readily accessible.

This was added in version 0.3.0.1. The custom filesizes you select will be remembered and available next time you open the bitrate calculator.

Oh, nice. I'll have to grab it when the next build is put out (I can't use the current version because I need to have access to my quants info in the log, so I downgraded to the most recent stable).

[berrinam]

Do nodes have different classifications, such as a distinction between debug levels or debug vs user info? If so, then options to expand/collapse nodes according to class would be handy, perhaps.There are currently 4 levels: NoImage, Information, Warning, and Error, each of which is associated with an icon (or no icon, in NoImage's case). It's hard to add more levels because there are no system icons, so someone would have to make one for us.

It would be possible to filter the log by level, but I don't think that's particularly useful since the warnings and errors already stand out.

That might be nice. I had an idea though, specifically regarding getting the quants information. I really don't like the idea of having to edit the log to find my quants info, so maybe I can expand the tree at some level in the job and see the quants info there?I think you've misunderstood what I meant by going to edit log, but when 0.3.0.2 comes out I hope you will understand.

[avdw]

Dang, even that stupid avimux_gui can't produce a normal avi, what a pile of misconfigured horsesh1t

[sillKotscha]

you show a great source of knowledge here... as avimux_gui is THE tool for avi processing...

if you don't know what you are doing don't blame neither anyone else nor tools for your ignorance...

and as said 100red of times to you... if you don't like it don't use it - easy, isn't it ;)

and if you don't understand that and just wanna troll around, well here is the best place for people like you :)

cheerio

[mroz]

Dang, even that stupid avimux_gui can't produce a normal avi, what a pile of misconfigured horsesh1t

What don't you like about it? If you can be more descriptive & perhaps suggest how it should be configured by default, you could help everyone by filing an appropriate bug report.

I only use avi as an xvid container for standalones. For this I need no OpenDML & no RecLists, so I need to change the default config. Currently this requires a one off launching of AVIMux_GUI directly to permit the config, though this is more of a hassle if you need to change configs. Better would be if a Megui profile handled the config.

[MrAngles]

This seems like just an avisynth issue but I didn't see an avisynth troubleshooting thread so I figured I'd post it here.

After reinstalling windows on my pc I installed the K-Lite codec pack, .net framework, Avisynth 2.57 and the latest version of MeGUI. When I try to load a d2v into the avs script creator I get this message: AviSynth script error:
Script error: there is no function named "DGDecode_Mpeg2Source"
Looking in the plugins folder I saw that there were only 3 files (colors_rgb.avsi, DirectShowSource.dll and TCPDeliver.dll) which seemed odd, so I copied the plugins folder from a different pc, but that resulted in a different error: The file D:\CSI\2x13\VTS_02_1.d2v cannot be opened.
Please make sure it's a valid AviSynth script and that AviSynth is properly installed. You can check the validity of your script and AviSynth installation by opening the file in your favorite media player. If that works, try opening the video in VirtualDub(Mod) as well. If the former works and the latter doesn't, install a YV12 codec. Error message for your reference: External component has thrown an exception.

Anyone have any idea what I'm missing here? Everything works fine on my other PCs and worked great before I reinstalled windows.

[saint-francis]

The 24 hour + problem in the status window still persists. I thought this issue was addressed.

http://forum.doom9.org/showthread.php?p=1067743#post1067743

0.2.6.1039

- (Kurtnoise) [ProgressWindow] New format for Time Elapsed/Remaining.


Not that it's really a big issue.

[ACrowley]

The 24 hour + problem in the status window still persists. I thought this issue was addressed.

http://forum.doom9.org/showthread.php?p=1067743#post1067743

0.2.6.1039

- (Kurtnoise) [ProgressWindow] New format for Time Elapsed/Remaining.


Not that it's really a big issue.

yes, its fixed now, as he said with 0.2.6.1039

With this Build the Elapsed Time works again for +24h.
And the Remaining Timer works stable again too

To bad that the x264 Quants Log wont appears anymore ..otherwise i would be satisfied with megui ,for now

@Kurtnoise
please, can you make a fix for x264 Quants/log ?

[Kurtnoise]

@Saint-Francis: are you serious ? what does it look like ?

@ACrowley: it has been fixed. So, wait an update.

@MrAngles: you should install also DGdecode...

[ACrowley]

@ACrowley: it has been fixed. So, wait an update.


OK THX :)

0.3.0.1001 (includes 0.2.x branch fixes)
- (berrinam) Add missing output streams back to log (fixes #1836281)
- (Kurtnoise) [AutoEncodeWindow] mainform was being referenced in default constructor before it had ever
been assigned (#1836041). patch by Eamonh.
- (Kurtnoise) Removed unused code
- (Kurtnoise) more Audio Input FileType.

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?

[saint-francis]

@Saint-Francis: are you serious ? what does it look like ?


I am completely serious. I had just started encoding right before I made that post and the status window told me there was a little more than 1 hour left. This was clearly not the case since It was moving at about 2 fps. Maybe 15 minutes later it was at about 23 hours left. I can't post a screenshot right now because I'll be encoding for the next 20 hours or so but maybe I can later in the week.

[Sharktooth]

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?
http://en.wikipedia.org/wiki/Standard_streams

x264 uses stderr for quant info...

[Kurtnoise]

@Saint-Francis: what can I say...It works for somebody else. So, it should work also for you. Did you overclock your PC or something ? you're running multiple tasks ?

The x264 Quants/Infos are in Log/standard output stream/standard error Stream ? Why is it called "error stream" ?
stdout = standard output
stderr = standard error

This is the usual way to name console redirections when processes are running. depends mainly on the internal code used by the cli tools. Basically, stderr is used to return errors and stdout some other things.

[MrAngles]

@MrAngles: you should install also DGdecode...

Well I assumed that was the case, which is why I copied DGDecode.dll along with the rest of my plugins folder from one of my other PCs' installation of AviSynth. Should I be installing it a different way? And isn't it supposed to automatically come in the AviSynth installation? I don't remember manually installing it previously.

Also, I can't even encode audio to aac either... jobs error out immediately when I try to run them...

------------------------------------------------------


Starting job job1 at 2:49:18 AM

Starting preprocessing of job...

Preprocessing finished!

successfully started encoding

Processing ended at 2:49:19 AM

------------------------------------------------------

Log for job job1



Error:

------------------------------------------------------

End of log for job1
------------------------------------------------------

Maybe I should try different installation packages... I've got megui-0.2.6.1038.exe and Avisynth_257.exe, maybe there are problems with them

[Kurtnoise]

well...

0/ Remove everything.
1/ Install Avisynth.
2/ Install MeGUI package.
3/ Run the update.

and that should be fine...

[saint-francis]

@Saint-Francis: what can I say...It works for somebody else. So, it should work also for you. Did you overclock your PC or something ? you're running multiple tasks ?


Yeah the PC is pretty seriously overclocked and I always do a lot of other things with it at the same time. Nothing too intensive though; browse the internet, use Skype for voice chat, etc. Also I'm using an experimental script that I'm not really sure about. I'm still getting a handle on how avisynth and all of these exotic filters work.

[MrAngles]

well...

0/ Remove everything.
1/ Install Avisynth.
2/ Install MeGUI package.
3/ Run the update.

and that should be fine...

Honestly not trying to make things difficult here, but I've already done that a few times with the same results. My installation file for AviSynth has got to be bad because it only includes those three plugins files I mentioned earlier. Unless I'm crazy I remember AviSynth coming with all the main plugins used by MeGUI. I've tried three different installation packages for MeGUI, and each one errors out when trying to convert audio.

Maybe it would be helpful if somebody could send me links for working installation packages for both programs.

[Sharktooth]

where did you get megui?
you can get megui from the official page: http://sourceforge.net/project/showfiles.php?group_id=156112
also ensure you let it auto-update or you wont get the required avs filters...

[vtn54]

Honestly not trying to make things difficult here, but I've already done that a few times with the same results. My installation file for AviSynth has got to be bad because it only includes those three plugins files I mentioned earlier. Unless I'm crazy I remember AviSynth coming with all the main plugins used by MeGUI. I've tried three different installation packages for MeGUI, and each one errors out when trying to convert audio.

Maybe it would be helpful if somebody could send me links for working installation packages for both programs.
Which Windows you use? Vista or XP?

[MrAngles]

Which Windows you use? Vista or XP?
XP

where did you get megui?

Don't remember, but it's version 0.3.something. It appears that that was the problem, because using 0.2.6.1040 from your link took care of everything. Thank you, and I'll keep track of the link this time. I must have gotten a beta version by mistake.

Anyway, thanks for all the help, I'm back up and running.

[Sharktooth]

yes, 0.3.x is the development branch (consider it a sort of alpha). however im glad it works now:)

[rack04]

Is there anyway that MeGUI AviSynth script creator will accept raw h264 streams?

[Sharktooth]

have a look at this thread: https://forum.doom9.org/showthread.php?t=122598

[rack04]

have a look at this thread: https://forum.doom9.org/showthread.php?t=122598

Great thanks. Are there any plans to integrate this into MeGUI?

[Sharktooth]

yes, of course.

[rack04]

yes, of course.

Perfect. Thanks.

[rack04]

If I run "AutoEncode" with just the avs loaded will the AC3 audio be factored into the bitrate calculator when it is added as additional content?

[Sharktooth]

you have to specify both the video and the audio sources.
the audio will be re-encoded. if you want to keep the original ac3 track you should consider using the bitrate calculator.

[rack04]

you have to specify both the video and the audio sources.
the audio will be re-encoded. if you want to keep the original ac3 track you should consider using the bitrate calculator.

That's what I thought. Thanks.

[berrinam]

you have to specify both the video and the audio sources.
the audio will be re-encoded. if you want to keep the original ac3 track you should consider using the bitrate calculator.

Sorry, but that's not right. Any audio tracks added with "add additional content" will be considered in the AutoEncode bitrate calculation. If they are not, this is a bug and should be reported on the sourceforge tracker.

[rack04]

Sorry, but that's not right. Any audio tracks added with "add additional content" will be considered in the AutoEncode bitrate calculation. If they are not, this is a bug and should be reported on the sourceforge tracker.

It would seem that after adding additional content it would go back to the AutoEncode screen and not directly to the queue.

[berrinam]

I don't understand what you said. Can you rephrase it please?

Never-the-less, I believe my statement is correct, and if it isn't, this should be reported as a bug.

[Sharktooth]

oops, i did not realize it was about auto-encode.

[Razorholt]

I just upgraded to the version 3.0.0 and the AutoEncoder doesn't work anymore - I get a huge error message. :(

[SpicyViper]

I'm having some difficulty with the dts audio I demuxed from my VOB file using D2V creator. I have converted many DVDs to mp4 suitable for my iPod touch but they have all had AC3 audio. I selected the .dts file as the audio input and queued the job with the NDAAC-LC-96Kbps audio profile, MP4-AAC extension.
After starting the job, the following error is logged.

[Error] An error occurred
-[NoImage] Exception message
--[NoImage] Script error: syntax error
--[NoImage] (, line 1, column 71)
-[NoImage] Stacktrace
--[NoImage] at MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
--[NoImage] at MeGUI.AviSynthAudioEncoder.encode()
-[NoImage] Inner exception: null

Can anyone shed some light upon this noob's struggles?

[Sharktooth]

I just upgraded to the version 3.0.0 and the AutoEncoder doesn't work anymore - I get a huge error message. :(
3.0.0.x is an UNSTABLE under development branch...

[Sharktooth]

I'm having some difficulty with the dts audio I demuxed from my VOB file using D2V creator. I have converted many DVDs to mp4 suitable for my iPod touch but they have all had AC3 audio. I selected the .dts file as the audio input and queued the job with the NDAAC-LC-96Kbps audio profile, MP4-AAC extension.
After starting the job, the following error is logged.

[Error] An error occurred
-[NoImage] Exception message
--[NoImage] Script error: syntax error
--[NoImage] (, line 1, column 71)
-[NoImage] Stacktrace
--[NoImage] at MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace, AviSynthScriptEnvironment env)
--[NoImage] at MeGUI.AviSynthAudioEncoder.encode()
-[NoImage] Inner exception: null

Can anyone shed some light upon this noob's struggles?
There is an error in the avisynth script...

[neuron2]

DGAVCDec uses libavcodec. libavcodec often outputs harmless or recoverable errors in its log and this causes MeGUI to abort after a first pass. Can we have an option to tell MeGUI to ignore errors?

I can trick MeGUI into running the second pass by re-queuing the job and deleting the first pass only, but it is inconvenient and normal users may not think of it.

[SpicyViper]

There is an error in the avisynth script...

Thanks for your response Sharktooth, however I ended up converting the dts file to ac3 in BeSweet. After using the ac3 file as the input, meGUI had no problems transcoding it into mp4-aac and muxing it with the video.

I may have confused the situation by posting the incorrect error log! I didn't even create an avisynth script for this job. I do wonder though what would have kept meGUI from transcoding the dts audio. Do you know of anything obvious given that the ac3 audio worked fine?

[neuron2]

DGAVCDec uses libavcodec. libavcodec often outputs harmless or recoverable errors in its log and this causes MeGUI to abort after a first pass. Can we have an option to tell MeGUI to ignore errors?

I can trick MeGUI into running the second pass by re-queuing the job and deleting the first pass only, but it is inconvenient and normal users may not think of it. Never mind. I found a way to capture the av_log() function and prevent MeGUI from ever seeing the errors/warnings.

[Sharktooth]

@neuron2: we were already planning to add complete support for dgavcdec (at least it's on the todo list).

@SpicyViper: besweet has its own decoder for DTS. while MeGUI uses DirectShow. Probably you havent any DTS DirectShow filter installed so MeGUI cant decode the DTS stream. Install AC3Filter, FFDShow or any other DTS DirectShow decoder (and ensure they're properly decoding the DTS audio).

[fleon]

So I noticed that there is an option on megui to do an analysis pass, yesterday I used on this video that i have of a live concert, but megui didnt show me any results or anything about the analysis that it did, how can I see the results, for choosing a good bitrate or chosing whatever options that the analysis pass did

[Sharktooth]

the analysis pass is for determining the interlacing/TC not for compression tests. however you just made me have an idea...

[mroz]

So I noticed that there is an option on megui to do an analysis pass, yesterday I used on this video that i have of a live concert, but megui didnt show me any results or anything about the analysis that it did, how can I see the results, for choosing a good bitrate or chosing whatever options that the analysis pass did

All an analysis pass does is fetch each frame in turn as fast as possible for the script you supply as input, throwing away the frames themselves. It's up to the specific script to analyse the material & write it's results to some log. You can make use of this yourself, if you have a suitable script. What it isn't is an out of the box solution to provide you with any particular info on your arbitrary source.

[Nic-]

i've just update Megui to 0.2.6.1042 and go to http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en to update framework but this Microsoft .NET Framework 2.0 Service Pack 1 (x86) do not support window vista.

how to solve this problem ?

[Kurtnoise]

shit...install the last one (http://www.microsoft.com/downloads/details.aspx?familyid=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en) then.

erff, I need to update the link now.

[Sharktooth]

damn M$! have you tried using windows update?

[carlo_0000]

hi

i update megui 0.2.5.X to last version 0.2.6.X

1st i got a crash when open it, i deleted the old jobs, now it work

but sins i can't drag and drop my videos (mpg & vob)

whats wrong ?

when i drag and drop, nothing hapens

[ash925]

Please help! I just did a fresh reinstall of win xp pro and updated it with autopatcher(may) and afterwards tried installing megui .The thing is it never completes the update download ,each time it fails in between ,with 16 or 13 updates remaining and if it is resumed later ,it say the remaining file have a problem. I have uninstalled and reinstalled it a couple of times since ,but the problem persists.

[berrinam]

Have you installed AviSynth? If not, get it from here (http://sourceforge.net/project/showfiles.php?group_id=57023&package_id=72557), and report back after installing it and running megui again.

[ash925]

thanx berrinam it is working now.

[vtn54]

i've just update Megui to 0.2.6.1042 and go to http://www.microsoft.com/downloads/details.aspx?familyid=79BC3B77-E02C-4AD3-AACF-A7633F706BA5&displaylang=en to update framework but this Microsoft .NET Framework 2.0 Service Pack 1 (x86) do not support window vista.

how to solve this problem ?
I think you must search for vista version,My OS is vista 32bit with Microsoft .NET Framework 2.0 Service Pack 1 (x86) :

http://i13.tinypic.com/6z87tlh.jpg

[ArdenDag]

Hello,

I am trying to use lame to encode AC3 tracks from a recent DVD rip. The AC3 files are not corrupt, as far as I know (they play fine), however when I try and encode them, I get an error, but no message in the MeGUI log to tell me what the error is. Any idea what I might be missing?

Thanks,
Arden

[Kurtnoise]

I think you don't have an AC3 source filter which is required...to check this try to play your AC3 in graphedit. It it returns some errors, you have to install a source filter.

[ArdenDag]

I installed AC3Filter, but I just remembered I hadn't rebooted since the install. I will try again and update this post.

UPDATE: Still an error, no encode in MeGUI. Will check GraphEdit.

Arden

[Kurtnoise]

AC3Filter is just a decoder...you need also a source filter (AC3File (http://ac3filter.net/projects/ac3file)).

[ArdenDag]

Uh... You're confusing me. I open a file, it runs through a decoder filter (in this case, AC3Filter). That then runs to a decoder to convert the raw audio into something I can hear, in my case FFDshow, which then goes to my speakers.

I assume the same happens when a file is converted?

BTW, GraphEdit shows all pins connected, and like I said earlier, the file plays fine. So what, again, am I missing? (Your link is dead, btw)

UPDATE: Link works now... must have been a hiccup in the net. I downloaded an AC3 source filter from guliverkli and installed it. No dice. I installed AC3file, still no dice. No error is listed in MeGUI still. Any ideas?

UPDATE 2: I just attempted to do the conversion manually with BeSweet, and it works. Even more confused...

Arden

[check]

try and load it via an avisynth script:
directshowsource("file.ac3")

[ArdenDag]

The conversion works via BeSweet, but I wanted a quicker solution than having to manually load the AC3s into BeSweet every time (especially when I am working with TV shows...). Loading it via an avisynth directshowsource takes longer, no?

This worked on my system before my upgrade. I must be missing something that'll make this work easier.

Arden

[mroz]

Um, I thought Megui used Nic's Audio plugin to decode ac3 directly? If so, why all this talk about directshow filters?

What is reported in the log? What is the error?

[berrinam]

@ArdenDag: Try using this build of megui (http://megui.org/berrinam_patches/more-audio-loginfo.zip) and see if that gives you any more information in the log. Just simply copy the megui.exe in the zip file on top of your current megui.exe.

@mroz: MeGUI has the option of "Force decoding with directshow" for audio. And the audio encoder doesn't report much in the log (although it does report the error, I believe).

[daWsOn_s]

Hello, I've always encoded with megui in x264 with no problems. Now I want to use Xvid but the settings for that don't work. If set the bitrate from a profile (tried all of xvid's) or/and from the bitrate calculator it will compress ALWAYS at 700kbit! I'm getting crazy, why??

[daWsOn_s]

I tried to raise the bitrate to 4000kbit creating my own profile but it still does not respect the settings :angry:

Log for job job6

Job commandline: "C:\Programmi\megui\tools\xvid_encraw\xvid_encraw.exe" -i "G:\55.avs" -single -bitrate 4000 -smoother 0 -nopacked -qtype 1 -closed_gop -lumimasking -imin 3 -imax 5 -pmin 3 -pmax 5 -bvhq -bquant_ratio 162 -bquant_offset 0 -bmin 3 -bmax 5 -par 1:1 -threads 0 -avi "G:\55.avi"
xvid_encraw - raw mpeg4 bitstream encoder written by Christoph Lampert 2002-2003

Trying to retrieve width and height from input header
xvid [info]: Avisynth detected
xvid [info]: Input colorspace is YV12
xvid [info]: Input is 1280 x 720, 25.000fps (25/1), starting from frame 0
xvid [info]: Number of frames to encode: 4577, Bitrate = 4000kbps
xvid [info]: xvidcore build version: xvid-1.2.0-dev
xvid [info]: Bitstream version: 1.2.-127
xvid [info]: Detected CPU flags: ASM MMX MMXEXT SSE SSE2 TSC
xvid [info]: Detected cpus = 2, threads requested = 1, threads in use = 1
xvid [info]: Threaded input reading active

Tot: enctime(ms) =238531.00, length(bytes) = 48122365
Avg: enctime(ms) = 52.09, fps = 19.20, length(bytes) = 10509
I frames: 38 frames, size = 45365/ 1723886, quants = 3 / 3.03 / 4
P frames: 1800 frames, size = 21740/ 39133154, quants = 3 / 3.09 / 5
B frames: 2731 frames, size = 2660/ 7265261, quants = 4 / 4.17 / 8
N frames: 8 frames, size = 8/ 64
desired video bitrate of this job: 4000 kbit/s - obtained video bitrate (approximate): 2108 kbit/s
------------------------------------------------------

[berrinam]

From your log, MeGUI appears to be signalling the bitrate correctly, and XviD has correctly understood the desired bitrate to be 4000kbps. This means that the bitrate is going wrong for some reason.

You are only doing a single pass encode, which is not guaranteed to hit the desired size since it works by estimation only. Try doing a two-pass encode and see if that gets the bitrate more exactly.

Also, your clip is quite short (3 minutes only), which may limit the ability to reach the desired bitrate in a single pass. You could try encoding a longer clip (say, >30 minutes) and see if that fixes it.

[squid_80]

I frames: 38 frames, size = 45365/ 1723886, quants = 3 / 3.03 / 4
P frames: 1800 frames, size = 21740/ 39133154, quants = 3 / 3.09 / 5
B frames: 2731 frames, size = 2660/ 7265261, quants = 4 / 4.17 / 8

The minimum quantizer values are preventing the codec from compressing any less.

[berrinam]

Out of interest, why doesn't XviD go all the way down to the minimum quantizer, instead of staying just a bit above? Is it something like trellis seeing it as a good idea to use a higher quantizer from time to time?

[squid_80]

My guess is because it's a single pass, there's probably a few frames at the start before rate-control kicks in that don't use the optimal quantizer.

[daWsOn_s]

I don't understand even If I do two-pass the bitrate is completely wrong!

Why should I use different videos? I mean with VDM works perfectly and the bitrate is always respected even with one pass. So what's the problem here? Why the codec does that? :(

[mroz]

Squid_80 answered you ten hours ago. The problem isn't Megui's code or the codec, but rather the xvid command line - iow the xvid profile you're using.

The codec alters bitrate by changing how much it squashes the data, which is what the quantisers are describing. The profile you're using places considerable limits on minimum & maximum quantiser values, so when obeying that, xvid simply can't get up to your bitrate. Reduce the minimum quantiser if you feel it will benefit you.

I'm not a codec expert, but I've never understood why the xvid profiles in Megui are so restrictive of quantisers.

[daWsOn_s]

OK, the problem is that I don't know what the quantizer values are and/or do eheh :D

[mroz]

By the time they become relevant, your video is represented by blocks of integers describing the frequency components making up each small spatial block - more or less.

The main lossy step in the compression occurs when these values are divided through by some small integer constants -the quantisers. As the division is integer based, much precision is lost. That's also the reason for doing it, since it gives a smaller range of possible values, each of which is now more common. Consequently the data stream is more easily compressible by a lossless codec, which is what is then done.

So, the bigger your quantisers, the more the data ends up squashed. Hence as you want less squashing to give a higher bitrate, you need to use smaller quantisers.

The profile you're encoding with currently won't allow quantisers below about three. Try dropping this to two, though do check the resulting video to make sure you actually need the extra bandwidth to yield visible quality gains.

[Rumbah]

I didn't use Megui for some time and now I did an update and found something irritating.

The last time I used MeGui it used an avisynth plugin to decode AC3 sound. But now it uses Directshowsource. The problem is that I use some settings in ffdshow to adjust the audio to my PC speaker settings (3.1 output and pretty heavy dynamic compression). Now I have to switch the ffdshow audio settings every time I use MeGui to encode some audio.

Is there a way to switch Megui to use a plugin instead (i think it's Nicaudio).

EDIT: I use MeGUI 0.3.0.1004

[Sharktooth]

there are 2 possible solutions:
1 - make presets in ffdshow and keep the dshow decoding
2 - click the config button to edit the audio profile and disable the "Force Decoding via DirectShow" option.