MeGUI: bug reports and feature requests

[Zathor]

I'm only getting 2325 from the updater

Wait a little bit until the second server syncs or run the updater several times.

[Zathor]

I am totally confused right now after trying to read the mentioned PDF file. Where do you find in that PDF the values for vbv-bufsize and vbv-maxrate?


The funny thing is, that MeGUI actually seems to know about the correct values. When you have specified High Profile @ Level 4.1 or 4.2 for example and you specify VBV Buffer Size higher than 78125 (78126 for example) and/or you specify VBV Maximum Bitrate higher than 62500 (62501 for example), then it will throw the following warning/error message:
So MeGUI already seems to know what the correct limits are.
Where is it pulling that knowledge from?
Maybe you can use this already available "knowledge" for applying the correct VBV restrictions for each Profile @ Level?
It should be the same for maxrate and bufsize. At least that is what I understand from before and after the changes I made.

EDIT: Found it on page 292. The changes will be in 2331.
EDIT2:

2331 [x264] fixed restricted vbv-bufsize value too low for some levels

[Zathor]

The VBV restrictions are not being represented on the "Rate Control" tab.
Correct, it works as desired.

[Zathor]

But may i ask why it's desired?
What's the reasoning behind it?
I do not want to overwrite user defined values if possible. Therefore 0 is more or less "auto" and values > 0 will be reduced if the value is too high.
EDIT: while thinking about is this is inconsistent with other values like e.g. bframes. Maybe I will change it tomorrow.

And why is it represented on the Rate Control tab for some target playback devices while for the rest of the target playback devices and all AVC Profiles @ Levels it's not?
I do not understand this question. It is available for all devices and levels. Just set it to a value > 0 and < the restrictions.

Setting the AVC Level drop-down list to Level 1 results in --level 1.1 on the command line instead of --level 1.0.
Thx - fixed in my local branch.

[SacredCultivator]

Sorry to ask but what exactly does "2327 [x264] added "stillimage" to the psy tunings and moved "zerolatency" and "fastdecode" to the misc tab" do? Like any benefits of selecting them?

[LigH]

Tunings are a slightly complex option, there are different kinds of values and dependencies: you may only select one of the "psy tunings" (using a combobox as selection control here makes sense), but "zerolatency" and "fastdecode" are additional tunings which may be combined with one of the "psy tunings" (therefore they should not be in the combobox list, but have a separate control).

[Rat Killer]

2330 [OneClick] fixed not removing chapter option if selected input file has no internal chapters
2329 [x264] added vbv restrictions based on the selected AVC level
2328 [x264] added AVC levels 1b and 5.2
2327 [x264] added "stillimage" to the psy tunings and moved "zerolatency" and "fastdecode" to the misc tab
2326 [File Indexer] enhanced index file selection behavior
2325 [MKV Muxer] improved playback performance with some players (requires MkvMerge 5.9.0+)
2324 [OneClick] avoid muxing into intermediate MKV file in some cases if using a DVD source
2323 [OneClick] set "Force using Key-Frames for chapters marks" even if "Don't encode video" is checked
2322 [OneClick] fixed a problem when aborting during automatic deinterlacing
2321 [OneClick] fixed a problem with multiple subtitle extraction caused by 2318

As you are working on AVC levels in x264, I have a minor bug that has been present for some time. Using level 4.1, the profile currently uses 5 reference frames for 1080p video. This is not correct, for 1080 resolution the limit for 4.1 is 4 ref frames. For 720 resolution it is 9. I have been needing to manually override to correct this. It effects a number of hardware players using Broadcom chips including my Tivo.

Hey, THANKS for all your continued work on meGUI.

[Zathor]

Using level 4.1, the profile currently uses 5 reference frames for 1080p video.
I just tried to reproduce that and failed. 1920x1080 for L4.1 is correctly calculated and the result is 4. Please provide more details how to reproduce that.
EDIT: Maybe you have selected the preset "slow" which results in --ref 5. This is correct as at this moment the video size is not known. During the start of the video job this value is verified and reduced to 4. You can find that in the log of the video job.

[Zathor]

2334 [x264] extended apple device profile support and removed/merged some others
2333 [x264] set AVC level, "zerolatency" and "fastdecode" effects also in the advanced settings
2332 [x264] fixed AVC level 1.0 encoded as 1.1

[Overdrive80]

In my case, the migration is wrong. I dont know if other users happens too. Megui shows --vbv-bufsize 1 --vbv-maxrate 1

[locotus]

2334 [x264] extended apple device profile support and removed/merged some others
2333 [x264] set AVC level, "zerolatency" and "fastdecode" effects also in the advanced settings
2332 [x264] fixed AVC level 1.0 encoded as 1.1

2334
Wish to know which profile is similar to the WDTV removed. Using
default profile, file size get widely wrong, set 1.60GB get 643MB.

[Zathor]

In my case, the migration is wrong. I dont know if other users happens too. Megui shows --vbv-bufsize 1 --vbv-maxrate 1

Do you know which profile/level and which vbv settings you have used before the change?
EDIT: Found the problem. Fix is on the way...

[Zathor]

When you're not using "No Target Size (use profile settings)", but instead are using "File Size" or "Average Bitrate" in the MeGUI AutoEncode settings, then, according to MediaInfo, the following happens
even though --vbv-bufsize 78125 --vbv-maxrate 62500 (for example) have been specified in the x264 configuration dialog of MeGUI.
Please post the log. Which vbv values have been sent to the encoder?

[Zathor]

1. Why does MeGUI default to CRF 20, even though the x264 default CRF value is 23? Clicking "Load Defaults" in the the x264 configuration dialog results in CRF being set to 20, even though x264 defines a value of 23 as the default.
23 is detected as x264 default. But yes, the MeGUI default should be changed to 23.

So, IMHO there should be an "Auto" and a "High Profile" entry in the AVC Profile drop-down list. The "Auto" entry should not do anything (defining no profile) and the "High Profile" entry should add --profile high on the command line.
It cannot be changed so easily. It will case a lot more troubles than the VBV change (and that already cased too much) because the profile is used in several places to calculate the command line. What I can do is always applying a --profile high. But that will also cause problems. So it is the best to not change it at all. It has not produced any problems in the last years.

2334
Wish to know which profile is similar to the WDTV removed. Using
default profile, file size get widely wrong, set 1.60GB get 643MB.
The WDTV profile has been renamed so that you do not need to select another (e.g. default) profile.

[Zathor]

Anyway, i would consider this a bug. "File Size" and "Average Bitrate" AutoEncode settings should not make --vbv-bufsize --vbv-maxrate exceed the values specified in the x264 configuration dialog IMHO.
A bug in x264 or MeGUI? If in MeGUI please explain in detail which parts need to be changed.

[Zathor]

2336 [x264] set default --crf value to 23
2335 [x264] fixed applying wrong vbv values (--vbv-bufsize 1 and --vbv-maxrate 1)

[locotus]

Fast reading never help, find WDTV, Thanks.

[locotus]

Undersize problem seems to be solved in 2336.
Thanks again.,

[hello_hello]

Any idea as to why every so often MeGUI decides to fudge the aspect ratio a little when resizing to square pixels? Well I think I've noticed it do the same when using anamorphic encoding in the past, but it definitely does it sometimes when the SAR should be 1:1.

Yesterday I was running a bunch of encodes, one set of DVDs, same script each time (aside from each script encoding a different episode) and same square pixel resizing. Several encoded with the correct aspect ratio, then according to MPC-HC, MeGUI started fudging it a little. I checked the log file and sure enough, MeGUI was no longer setting the SAR to 1:1. Oddly enough, I was running encodes on two PCs and MeGUI started fudging the aspect ratio at about the same time in both cases.

I couldn't remember whether there were jobs in the queue when I updated MeGUI, so thinking that might be the cause I deleted the remaining jobs and loaded them again. Everything went back to normal for a while and so far MeGUI hasn't fudged the aspect ratio on one PC, but while running some test encodes I realised it started doing it again on the second PC. When I reloaded the same script and ran the encode again though, the aspect ratio was fine.

So far I can't duplicate the problem reliably enough to point to what may be causing it, but how does MeGUI determine the aspect ratio it's going to use when it actually runs the encoding job? And could it for some reason get the calculation slightly wrong? As an example, here's the log file from two encodes. The scripts are identical (aside from the source) yet for the first MeGUI correctly set the SAR to 1:1, while for the second, not so much.....
When I ran the second encode again the correct 1:1 SAR was used.

-[Information] Log for job8 (video, 0602 The Big Salad.avs -> 0602 The Big Salad.mkv)
--[Information] [30/03/13 2:40:27 PM] Started handling job
--[Information] [30/03/13 2:40:27 PM] Preprocessing
--[Information] [30/03/13 2:40:27 PM] Avisynth input script
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\dgindex\DGDecode.dll")
---[NoImage] DGDecode_mpeg2source("D:\0602 The Big Salad.d2v")
---[NoImage] QTGMC(InputType=1)
---[NoImage] crop(4, 4, -2, -4)
---[NoImage] Spline36Resize(704,512)
--[Information] [30/03/13 2:40:27 PM] Job commandline: "C:\Program Files\MeGUI\tools\x264\x264.exe" --level 4.1 --preset slow
--crf 18.0 --vbv-bufsize 78125 --vbv-maxrate 62500 --no-fast-pskip --colorprim bt470bg --transfer bt470bg --colormatrix bt470bg
--sar 1:1 --output "D:\0602 The Big Salad.mkv" "D:\0602 The Big Salad.avs"
--[Information] [30/03/13 2:40:27 PM] Encoding started
--[Information] [30/03/13 4:22:28 PM] Standard output stream
--[Information] [30/03/13 4:22:28 PM] Standard error stream
---[NoImage] avs [info]: 704x512p 1:1 @ 25/1 fps (cfr)
---[NoImage] x264 [info]: using SAR=1/1
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64 SlowShuffle
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: frame I:348 Avg QP:15.53 size: 71525
---[NoImage] x264 [info]: frame P:11422 Avg QP:18.52 size: 17518
---[NoImage] x264 [info]: frame B:21255 Avg QP:21.11 size: 3162
---[NoImage] x264 [info]: consecutive B-frames: 11.4% 2.1% 18.8% 67.6%
---[NoImage] x264 [info]: mb I I16..4: 5.7% 73.9% 20.3%
---[NoImage] x264 [info]: mb P I16..4: 0.3% 3.0% 0.9% P16..4: 41.9% 27.8% 19.5% 0.0% 0.0% skip: 6.6%
---[NoImage] x264 [info]: mb B I16..4: 0.0% 0.2% 0.1% B16..8: 46.4% 7.8% 1.9% direct: 2.2% skip:41.5% L0:33.4% L1:51.5% BI:15.2%
---[NoImage] x264 [info]: 8x8 transform intra:71.7% inter:68.0%
---[NoImage] x264 [info]: direct mvs spatial:99.9% temporal:0.1%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 92.4% 93.0% 80.6% inter: 27.1% 30.6% 8.4%
---[NoImage] x264 [info]: i16 v,h,dc,p: 45% 12% 7% 36%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 11% 4% 9% 13% 13% 12% 12% 12%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 9% 3% 9% 14% 15% 13% 12% 12%
---[NoImage] x264 [info]: i8c dc,h,v,p: 41% 21% 23% 15%
---[NoImage] x264 [info]: Weighted P-Frames: Y:2.0% UV:0.7%
---[NoImage] x264 [info]: ref P L0: 63.1% 13.9% 14.4% 3.7% 3.5% 1.3% 0.0%
---[NoImage] x264 [info]: ref B L0: 91.4% 6.7% 1.3% 0.5%
---[NoImage] x264 [info]: ref B L1: 97.2% 2.8%
---[NoImage] x264 [info]: kb/s:1769.54
---[NoImage] encoded 33025 frames, 5.40 fps, 1769.55 kb/s
--[Information] Final statistics
---[Information] [30/03/13 4:22:29 PM] Constant Quality Mode: Quality 18 computed...
---[Information] [30/03/13 4:22:29 PM] Video Bitrate Obtained (approximate): 1771 kbit/s
--[Information] [30/03/13 4:22:29 PM] MediaInfo
---[Information] File: D:\0602 The Big Salad.mkv
---[Information] General
----[Information] Format: Matroska
----[Information] FormatString: Matroska
----[Information] FileSize: 292444098
----[Information] PlayTime: 00:22:01.000
---[Information] Video
----[Information] ID: 1
----[Information] StreamOrder: 0
----[Information] Width: 704
----[Information] Height: 512
----[Information] FrameCount: 33025
----[Information] FrameRate: 25.000
----[Information] FrameRateOriginal:
----[Information] FrameRateMode: CFR
----[Information] ScanType: Progressive
----[Information] Codec: V_MPEG4/ISO/AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 1.375
----[Information] AspectRatioString: 1.375
----[Information] Delay: 0
----[Information] Title:
----[Information] Language: en
----[Information] LanguageString: English
----[Information] Default: Yes
----[Information] DefaultString: Yes
----[Information] Forced: No
----[Information] ForcedString: No
--[Information] [30/03/13 4:22:30 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [30/03/13 4:22:30 PM] Job completed
-[Information] Log for job9 (video, 0603 The Pledge Drive.avs -> 0603 The Pledge Drive.mkv)
--[Information] [30/03/13 4:22:30 PM] Started handling job
--[Information] [30/03/13 4:22:30 PM] Preprocessing
--[Information] [30/03/13 4:22:30 PM] Avisynth input script
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\dgindex\DGDecode.dll")
---[NoImage] DGDecode_mpeg2source("D:\0603 The Pledge Drive.d2v")
---[NoImage] QTGMC(InputType=1)
---[NoImage] crop(4, 4, -2, -4)
---[NoImage] Spline36Resize(704,512)
--[Information] [30/03/13 4:22:30 PM] Job commandline: "C:\Program Files\MeGUI\tools\x264\x264.exe" --level 4.1 --preset slow
--crf 18.0 --vbv-bufsize 78125 --vbv-maxrate 62500 --no-fast-pskip --colorprim bt470bg --transfer bt470bg --colormatrix bt470bg
--sar 1392:1397 --output "D:\0603 The Pledge Drive.mkv" "D:\0603 The Pledge Drive.avs"
--[Information] [30/03/13 4:22:30 PM] Encoding started
--[Information] [30/03/13 6:04:07 PM] Standard output stream
--[Information] [30/03/13 6:04:07 PM] Standard error stream
---[NoImage] avs [info]: 704x512p 1392:1397 @ 25/1 fps (cfr)
---[NoImage] x264 [info]: using SAR=1392/1397
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 Cache64 SlowShuffle
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: frame I:361 Avg QP:15.63 size: 74268
---[NoImage] x264 [info]: frame P:12704 Avg QP:18.61 size: 18326
---[NoImage] x264 [info]: frame B:19860 Avg QP:21.05 size: 3389
---[NoImage] x264 [info]: consecutive B-frames: 17.0% 1.8% 18.0% 63.3%
---[NoImage] x264 [info]: mb I I16..4: 5.1% 74.9% 20.0%
---[NoImage] x264 [info]: mb P I16..4: 0.3% 2.4% 0.7% P16..4: 42.1% 27.8% 20.4% 0.0% 0.0% skip: 6.3%
---[NoImage] x264 [info]: mb B I16..4: 0.0% 0.2% 0.1% B16..8: 47.0% 8.0% 2.0% direct: 2.4% skip:40.3% L0:33.2% L1:50.9% BI:15.9%
---[NoImage] x264 [info]: 8x8 transform intra:72.3% inter:65.2%
---[NoImage] x264 [info]: direct mvs spatial:99.9% temporal:0.1%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 93.7% 93.9% 84.2% inter: 30.2% 33.4% 10.2%
---[NoImage] x264 [info]: i16 v,h,dc,p: 41% 11% 10% 38%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 14% 10% 4% 9% 14% 13% 12% 12% 12%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 13% 9% 3% 9% 15% 14% 13% 12% 12%
---[NoImage] x264 [info]: i8c dc,h,v,p: 43% 21% 21% 15%
---[NoImage] x264 [info]: Weighted P-Frames: Y:1.6% UV:0.8%
---[NoImage] x264 [info]: ref P L0: 66.1% 13.5% 12.7% 3.2% 3.1% 1.3% 0.0%
---[NoImage] x264 [info]: ref B L0: 91.8% 6.5% 1.2% 0.5%
---[NoImage] x264 [info]: ref B L1: 97.5% 2.5%
---[NoImage] x264 [info]: kb/s:1985.90
---[NoImage] encoded 32925 frames, 5.40 fps, 1985.90 kb/s
--[Information] Final statistics
---[Information] [30/03/13 6:04:07 PM] Constant Quality Mode: Quality 18 computed...
---[Information] [30/03/13 6:04:07 PM] Video Bitrate Obtained (approximate): 1987 kbit/s
--[Information] [30/03/13 6:04:07 PM] MediaInfo
---[Information] File: D:\0603 The Pledge Drive.mkv
---[Information] General
----[Information] Format: Matroska
----[Information] FormatString: Matroska
----[Information] FileSize: 327176448
----[Information] PlayTime: 00:21:57.000
---[Information] Video
----[Information] ID: 1
----[Information] StreamOrder: 0
----[Information] Width: 704
----[Information] Height: 512
----[Information] FrameCount: 32925
----[Information] FrameRate: 25.000
----[Information] FrameRateOriginal:
----[Information] FrameRateMode: CFR
----[Information] ScanType: Progressive
----[Information] Codec: V_MPEG4/ISO/AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 1.372
----[Information] AspectRatioString: 1.372
----[Information] Delay: 0
----[Information] Title:
----[Information] Language: en
----[Information] LanguageString: English
----[Information] Default: Yes
----[Information] DefaultString: Yes
----[Information] Forced: No
----[Information] ForcedString: No
--[Information] [30/03/13 6:04:08 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [30/03/13 6:04:08 PM] Job completed

[Zathor]

Sorry, I cannot reproduce that as well.

[Wam7]

http://i45.tinypic.com/qo83gn.jpg

I'm going from a .mkv to a .mp4 container. My one click profile has always worked fine but on a particular .mkv I'm getting this message. Any reason why?

[Zathor]

I'm going from a .mkv to a .mp4 container. My one click profile has always worked fine but on a particular .mkv I'm getting this message. Any reason why?

Please post the complete log

[Wam7]

Please post the complete logThere is nothing in the logs. It just shows this message. After closing the window and pressing 'go', the 'go' button just stays ghosted out and does not come back on.

[Zathor]

There is nothing in the logs. It just shows this message. After closing the window and pressing 'go', the 'go' button just stays ghosted out and does not come back on.

Nevertheless please post the log as the mediainfo of your source file is included there.

[hello_hello]

Sorry, I cannot reproduce that as well.

Any ideas as to where I could start to look, or how MeGUI decides on the aspect ratio it's going to use? Checking encodes today to discover the last 7 or 8 hours of encoding was in vain has taken some of the fun out of it. I guess for the moment I'm going to have to try to check the command line in the log file as each encode starts.

-[Information] Log for job2 (video, video.avs -> video.mkv)
--[Information] [02/04/13 5:51:36 AM] Started handling job
--[Information] [02/04/13 5:51:36 AM] Preprocessing
--[Information] [02/04/13 5:51:36 AM] Avisynth input script
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
---[NoImage] FFVideoSource("E:\video.mkv", threads=1)
---[NoImage] crop(6, 8, -4, -8)
---[NoImage] Spline36Resize(1280,536)
---[NoImage] QTGMC(InputType=1, preset="medium")
--[Information] [02/04/13 5:51:37 AM] Job commandline:
"C:\Program Files\MeGUI\tools\x264\x264.exe" --level 4.1 --preset slow --tune film --crf 18.0
--keyint 240 --vbv-bufsize 78125 --vbv-maxrate 62500 --no-fast-pskip --colorprim bt709 --transfer bt709 --colormatrix bt709
--sar 67:68 --output "D:\video.mkv" "D:\video.avs"
--[Information] [02/04/13 5:51:37 AM] Encoding started
--[Information] [02/04/13 1:45:10 PM] Standard output stream
--[Information] [02/04/13 1:45:10 PM] Standard error stream
---[NoImage] avs [info]: 1280x536p 67:68 @ 24000/1001 fps (cfr)
---[NoImage] x264 [info]: using SAR=67/68
---[NoImage] x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.1 Cache64
---[NoImage] x264 [info]: profile High, level 4.1
---[NoImage]
---[NoImage] x264 [info]: frame I:1855 Avg QP:14.47 size: 84798
---[NoImage] x264 [info]: frame P:54215 Avg QP:17.45 size: 26909
---[NoImage] x264 [info]: frame B:117403 Avg QP:20.01 size: 6996
---[NoImage] x264 [info]: consecutive B-frames: 5.6% 4.1% 24.9% 65.4%
---[NoImage] x264 [info]: mb I I16..4: 8.3% 73.5% 18.2%
---[NoImage] x264 [info]: mb P I16..4: 2.6% 10.4% 1.9% P16..4: 38.9% 24.1% 13.1% 0.0% 0.0% skip: 8.9%
---[NoImage] x264 [info]: mb B I16..4: 0.2% 0.9% 0.2% B16..8: 42.3% 8.5% 1.8% direct: 4.0% skip:42.1%
L0:34.7% L1:50.2% BI:15.1%
---[NoImage] x264 [info]: 8x8 transform intra:70.1% inter:73.7%
---[NoImage] x264 [info]: direct mvs spatial:100.0% temporal:0.0%
---[NoImage] x264 [info]: coded y,uvDC,uvAC intra: 75.7% 76.0% 51.4% inter: 26.0% 26.4% 2.4%
---[NoImage] x264 [info]: i16 v,h,dc,p: 36% 13% 10% 42%
---[NoImage] x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 8% 7% 8% 12% 14% 11% 12% 11%
---[NoImage] x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 16% 7% 6% 9% 15% 16% 12% 11% 10%
---[NoImage] x264 [info]: i8c dc,h,v,p: 44% 21% 21% 14%
---[NoImage] x264 [info]: Weighted P-Frames: Y:2.9% UV:1.5%
---[NoImage] x264 [info]: ref P L0: 57.5% 11.6% 20.1% 4.8% 4.6% 1.3% 0.0%
---[NoImage] x264 [info]: ref B L0: 89.0% 8.6% 1.7% 0.6%
---[NoImage] x264 [info]: ref B L1: 97.5% 2.5%
---[NoImage] x264 [info]: kb/s:2695.19
---[NoImage] encoded 173473 frames, 6.11 fps, 2695.19 kb/s
--[Information] Final statistics
---[Information] [02/04/13 1:45:15 PM] Constant Quality Mode: Quality 18 computed...
---[Information] [02/04/13 1:45:15 PM] Video Bitrate Obtained (approximate): 2696 kbit/s
--[Information] [02/04/13 1:45:15 PM] MediaInfo
---[Information] File: D:\video.mkv
---[Information] General
----[Information] Format: Matroska
----[Information] FormatString: Matroska
----[Information] FileSize: 2438870286
----[Information] PlayTime: 02:00:35.270
---[Information] Video
----[Information] ID: 1
----[Information] StreamOrder: 0
----[Information] Width: 1280
----[Information] Height: 536
----[Information] FrameCount: 173473
----[Information] FrameRate: 23.976
----[Information] FrameRateOriginal:
----[Information] FrameRateMode: CFR
----[Information] ScanType: Progressive
----[Information] Codec: V_MPEG4/ISO/AVC
----[Information] CodecString: AVC
----[Information] Format: AVC
----[Information] AspectRatio: 2.353
----[Information] AspectRatioString: 2.35:1
----[Information] Delay: 0
----[Information] Title:
----[Information] Language: en
----[Information] LanguageString: English
----[Information] Default: Yes
----[Information] DefaultString: Yes
----[Information] Forced: No
----[Information] ForcedString: No
--[Information] [02/04/13 1:45:17 PM] Postprocessing
---[Information] Deleting intermediate files
--[Information] [02/04/13 1:45:17 PM] Job completed

[Zathor]

Any ideas as to where I could start to look, or how MeGUI decides on the aspect ratio it's going to use?
I will provide a special build for you.

[Zathor]

Any ideas as to where I could start to look, or how MeGUI decides on the aspect ratio it's going to use?
Please try build 2338. If we are not able to find the problem with the default log, I will really create a special build for this kind of problem.

[Overdrive80]

Any ideas as to where I could start to look, or how MeGUI decides on the aspect ratio it's going to use? Checking encodes today to discover the last 7 or 8 hours of encoding was in vain has taken some of the fun out of it. I guess for the moment I'm going to have to try to check the command line in the log file as each encode starts.

Maybe megui adjust DAR output to format more proper.

DAR=SARxPAR

In you case, DAR=1280x536=2.38

DARx/DARy=(SARx/SARy)*(PARx/PARy);

DAR=(1280/536)*(67/68)=85760/36448=2.35

Maybe auto-adjust DAR´s desviation to standarized format.

[superhil]

Previously I posted in wrong section.
Here is my post.
Kindly need your help :)

Hi All,
I'm a newbie here.
I tried to reencode a video with original FPS 23.976 using "One-Click" method, i only changed CRF and preset to "very slow". Everything else on default.

Accidentally, after reencoding, FPS change to 27.xxx, with the same duration.
It's really weird.
I've tried 3 times, but always got the the same result, (On the last try , I redownload the MeGUI)

Do you know what could be the problem?

Thank you very much

I just found out what's the problem.
After deinterlacing process, total frames / total length is no more 23.976
That's why it becomes 27.xxx fps

Still, it's weird because original fps is 23.976


I'm using the latest beta version 2338

[Zathor]

Please post the full log file of the whole process.

[hello_hello]

Please try build 2338. If we are not able to find the problem with the default log, I will really create a special build for this kind of problem.

Cheers. I probably won't do another "batch" of encoding for a few days or so, but I'll report back.

Is there anyway resizing in the script could effect the SAR used? It's just that I did a bunch of encoding yesterday without any SAR issues, but there was no cropping or resizing included in any of those scripts. Maybe that's just a co-incidence though.....

For the record, I noticed/reported the same problem back in November, so it's not confined to just the recent versions of MeGUI.
http://forum.doom9.org/showthread.php?p=1601053

To be honest, the main reason I've noticed is because (and I don't know whether this is particular to just my PC setup) when I open video which doesn't have a 1:1 PAR with MPC-HC and DXVA decoding, the bottom half of the picture displays as a grey block for the first few frames. I don't know why that happens, but it happens 100% of the time, so I always know when the PAR isn't 1:1. If it wasn't for that, the slightly "fudged"aspect ratios probably would have generally gone unnoticed. So I kind of wonder whether it's a common problem but I just happen to be the one noticing it because of the way my setup displays anamorphic video.

[hello_hello]

Zathor, I just thought I'd report back to let you know I ran a bunch of encodes yesterday using version 2338 and had no problem with MeGUI fudging the SAR, so the problem seems to have mysteriously disappeared just as it mysteriously appeared. Odd.....

No doubt if it happens again I let you know. ;)

Thanks.

[rhaz]

Hi. I am using MeGUI 2341 and been using it for a year now. So there's the thing. Every time I save an .avs of *.h264 (extracted from .mkv) MeGUI always quits. It saves the .avs, but it also quits. And every time I have to relaunch the program to do further settings (i.e. add .avs to queue for encoding).

MeGUI doesn't quit when saving .avs from DVD .vob, for example.

Cheers.

[Zathor]

Hi. I am using MeGUI 2341 and been using it for a year now. So there's the thing. Every time I save an .avs of *.h264 (extracted from .mkv) MeGUI always quits. It saves the .avs, but it also quits. And every time I have to relaunch the program to do further settings (i.e. add .avs to queue for encoding).
Is there anything mentioned in the log file?
Also please post the AVS script. Have you tried to use the file indexer on the MKV file?

[rhaz]

Is there anything mentioned in the log file?
Also please post the AVS script. Have you tried to use the file indexer on the MKV file?

No, there is nothing in the log files when it happens, probably it just crashes fast and that's it. And I don't think if any .avs script will help, because like I said it happened to me hundred times when saving .avs from HD source.

Also I use File Indexer on .h264 which I first extract from the actual .mkv with MKVExtractGUI.

It doesn't crash on .vob or any other format, only from .h264.

Also my PC is very very old (since like 2005) and maybe it has something to do with that, because I noticed it works very slow with loaded .avs of .h264. I am also on Windows XP SP3. Maybe there's not enough RAM or something and it just crashes on that point when saving the .avs.

Also there's 1/10 chance when it doesn't crash from .h264 sometimes either. But that's rare event.

[AMED]

@rhaz,

When you do the file index, does it work if you select DGindex instead of FFMSindex?

[rhaz]

@rhaz,

When you do the file index, does it work if you select DGindex instead of FFMSindex?

@AMED,

When I do File index for .h264 all options are greyed out and unselectable and DGAVCIndex file indexer is always selected by default (and the only option available).

I tried File Indexer on .vob it gives DGIndex by default, other options are greyed out, except that FFMSindex, but then I get recommendation message that it should be used only for .MKV and etc.

[AMED]

@AMED,

When I do File index for .h264 all options are greyed out and unselectable and DGAVCIndex file indexer is always selected by default (and the only option available).

I tried File Indexer on .vob it gives DGIndex by default, other options are greyed out, except that FFMSindex, but then I get recommendation message that it should be used only for .MKV and etc.Have you tried keeping the video as MKV and using FFMSIndex?

[rhaz]

Have you tried keeping the video as MKV and using FFMSIndex?

Well. It didn't crash, but how's that a solution?

[LigH]

Raw H.264 video streams often have the disadvantage that some important details are missing (e.g. usually it does not contain the framerate), which would be known if it was still multiplexed in a container. This may already be a reason that decoders fail because they believe they are in an undefined state.

The documentation of FFMS2 clearly recommends using the MKV container, it is the best supported container for this AviSynth source plugin.

Using FFMS2 for MKV files is quite recommended, because it is one of the most up-to-date software-only decoders for AviSynth:
DGDecNV (DGSource) requires an Nvidia GPU of the CUDA generation (more exactly: with a PureVideo decoder chip of at least generation VP2) and a registration (cheap, but not free of charge), therefore must be enabled manually;
DGAVCDec is outdated for ages, its libav library version does not even support PAFF interlacing yet (and all more modern versions are incompatible or not frame-exact);
DirectShowSource / DSS2 will probably not be able to handle raw H.264 video streams as long as you don't install a source filter which can detect and open them (but I don't know any free H.264 raw source filter)

It may require a limitation of the decoding threads, though, unless it is clearly documented that the threading issues have been fixed: FFVideoSource(..., threads=1)

[Shevek]

How feasible is it to add a "Wait" option before a job in the queue, either as a property of the job itself, or as an additional job placed before.

This is my scenario:

I have an Nvidia rig and use DGIndexNV.

I often use my computer via RDP through a Terminal Services Gateway. This runs using a software GPU and therefore starting any index or encode job fails because CUDA cannot be initialised.

However, in my experience, connecting to the computer after the job has started is fine - once CUDA has initialised, switching to the RDP GPU allows the index/encode job to carry on and succeed.

What I would like to be able to do then, is add a delay before any index or encode job (probably 1 or 2 minutes, but fully customisable preferably), start the queue, then disconnect the RDP session, wait for the allocated delay to pass so that the index/encode job will start and successfully initialise CUDA. Then I can reconnect RDP.

Is this feasible?

TIA

Shevek

[disklib]

Is the File Indexer programmed to maintain the last Audio Demux setting in between Queue'ing up multiple files?

Example: Indexing a handful of VOB's, one of which has no audio. Open the File Indexer, input a VOB with audio track and the Audio Demux section defaults to "All Audio Tracks" - next input the VOB with no audio track and it automatically changes to "No Audio" - next input a VOB with audio track and the setting remains on "No Audio". Similarly if I start off with the no audio track VOB first it defaults to "No Audio" and then sticks to that when inputting a VOB that does have audio.

When I say "stick" I mean it doesn't change itself back to "All Audio Tracks" automatically. That setting is available, it just needs to be selected manually.

[Overdrive80]

Hi, an user of megui report me one issue.

Avs used:

# Set DAR in encoder to 137 : 72. The following line is for automatic signalling
global MeGUI_darx = 137
global MeGUI_dary = 72
LoadPlugin("X:\MEGUI\tools\ffms\ffms2.dll")
FFVideoSource("C:\Users\Elcebi\Desktop\ripeo blindness\VTS_02_1 - 0xE0 - Video - MPEG-2 - 720x576 (PAL) - 16~9 - Letterboxed.M2V", threads=1)
#deinterlace
crop(0, 12, 0, -12)
#resize
#denoise

Error log:

http://pastebin.com/zG3mfk2w

Snapshot:

http://img197.imageshack.us/img197/3955/errorsinx264.jpg

[LigH]

The documentation of FFMS2 reports to avoid elementary streams. It always recommends to multiplex into MKV before indexing.

Despite this being a small issue if FFMS2 finds a splitter or source routine to handle a specific input, there is still a chance that a corrupt stream may crash the decoder, regardless of a container.

[Zathor]

Hi, an user of megui report me one issue.

By default for this type of input MeGUI uses DGIndex in the file indexer. Does it also crash with it?

[Kurtnoise]

Better to use this one (https://github.com/nu774/fdkaac)...

[Kurtnoise]

Im part of the MeGUI devs and to use it into MeGUI, you have to use the one that I linked.

[Kurtnoise]

you cannot use it directly in the current version...you have to wait that a developper implement it.

My point was to use the one from Nu774 because there are more features and better support within Windows.

[LigH]

Means: "soon™" and "Patience, Padawan"? ;)

[Zathor]

I have an Nvidia rig and use DGIndexNV.

I often use my computer via RDP through a Terminal Services Gateway. This runs using a software GPU and therefore starting any index or encode job fails because CUDA cannot be initialised.

However, in my experience, connecting to the computer after the job has started is fine - once CUDA has initialised, switching to the RDP GPU allows the index/encode job to carry on and succeed.

What I would like to be able to do then, is add a delay before any index or encode job (probably 1 or 2 minutes, but fully customisable preferably), start the queue, then disconnect the RDP session, wait for the allocated delay to pass so that the index/encode job will start and successfully initialise CUDA. Then I can reconnect RDP.

Interesting request. I just did a quick test and it does not work for me if I disconnect the session (cuda init error). I have to logon locally to get it to work. Therefore I assume it cannot work as intended.