MeGUI: bug reports and feature requests

[hello_hello]

Don't forget kalehrl has tried opening the scripts with MPC-HC and the problem persisted, so it mightn't be Avspmod specific, unless he has the 64 bit flavour of MPC-HC and it can't open scripts if Avisynth is 32 bit. Can it open them if Avisynth is 32 bit? I don't actually know.

[hello_hello]

Should be, at least for the NT 5.x and 6.x versions.

I have some encodes running so I'll have to do it tomorrow, but I might try the same test with x64 LSmash to see if it produces a different error message. It occurred to me that midts and I were seeing the same error message when ffms2 wouldn't load, whereas kalehrl was trying to load LSmash and the error message was different.

Not that it'd help to fix anything, but I'm curious now.

[Groucho2004]

I have some encodes running so I'll have to do it tomorrow, but I might try the same test with x64 LSmash to see if it produces a different error message. It occurred to me that midts and I were seeing the same error message when ffms2 wouldn't load, whereas kalehrl was trying to load LSmash and the error message was different.

Not that it'd help to fix anything, but I'm curious now.How is this related to error messages thrown by Windows?

[hello_hello]

midts can't load ffms2. It results in an error message. I couldn't load ffms2 when I switched it for the 64 bit version (naturally) but the error message was the same as it was for midts.

kalehrl can't load Lsmash. His error message was different (not a 32 bit application). I'm curious to see if when I change Lsmash to 64 bit and try to load it, I get them same error message as I did for ffms2, or if I get the same error message as kalehrl.
ie If 64 bit ffms2 and 64 bit Lsmash result in different error messages. That's all.

[Groucho2004]

midts can't load ffms2. It results in an error message. I couldn't load ffms2 when I switched it for the 64 bit version (naturally) but the error message was the same as it was for midts.

kalehrl can't load Lsmash. His error message was different (not a 32 bit application). I'm curious to see if when I change Lsmash to 64 bit and try to load it, I get them same error message as I did for ffms2, or if I get the same error message as kalehrl.
ie If 64 bit ffms2 and 64 bit Lsmash result in different error messages. That's all.I think you're getting the error messages that various Avisynth versions produce mixed up with the error codes thrown by Windows. Windows just produces a code (0x1C, for example). The application that catches the error (usually via GetLastError()) is responsible for formatting it into a user readable format (usually via FormatMessage()). Unfortunately, many programs just throw the error code at the user who then has to figure out what it means.

[hello_hello]

I see..... I think. :)

So you're saying Windows can produce an error message such as 0xC1, and Avisynth will translate it into something else, such as "not a 32 bit application"?

Because the error message Avisynth displayed was 0xC1 for ffms2 x64, in my case.

Edit. Now I see, 0xC1 is the error code for "not a 32 bit application", but for some reason Avisynth isn't translating it.

Cheers.

[kalehrl]

That's the 64 bit version.

See above.
OMG this is so embarrassing!
You are right!
I've been using the 64bit AvspMod that I updated some time ago without even testing it at that time. I believe I downloaded the updated 64bit version from this forum.
Now, when I needed to do some encoding, I forgot all about the damn update and that it could be the cause of the problem. I downloaded the official version from the github and it works. I'm sorry for wasting everybody's time. Thank you all for your help. These post, which are not really related to MeGUI, could be deleted if an admin thinks so.

[Xor]

error

[Zathor]

so, here is a VOB sample in 16:9 with border:
https://mega.nz/#!5sgDQIyQ!w9x-gq8IM3c9PpPilAXGv093P42A5psdw_EPM7X1hZ4

and when use build 2624 one-click encoder with my avisynth profile, it will out put a 640x480,4:3 mp4. It's what my want.
https://mega.nz/#!B85DSarJ!leteVasSiGl7PvUvi4Am1ON778z05QQDpIhz0KcdD_k

but when use build 2722, it will out put a 640x480,16:9 mp4. I don't want this.
https://mega.nz/#!JtwBnRxJ!0QHo6tqvB0JQL-zPhF5oebSbd-514E4vFN9yhYHjJts

so, I wanna I can disable "auto detect display aspect autio".

I have tested it. My results:
2624 + 2722 produce the same "wrong" mp4 file with 16:9 AR. For me this is clear as MeGUI tries to keep up with the detected input AR of 16:9. Btw that is what will be selected in the OneClick settings: the INPUT aspect ratio. MeGUI assumes that the output AR must be the same as the input AR (if anamorph encoding is selected, otherwise 1:1 will be used as PAR). As you are changing the output in the script (autocrop & resize) MeGUI does not know that the input AR is not valid anymore for the output. Two suggestions to make it work:
- Do not resize - encode anamorph as the pixel information will be retained (as Tebasuna suggested)
- If you really want to resize: disbale the usage of ITU values in the settings, remove your resize & autocrop from the avs profile, enable the resize in the OneClick profile incl. autocrop together with a maximum width of 640. In my tests I ended up with a suare pixel 640:480 = 4:3 encode.

[hello_hello]

Is it possible MeGUI gets carried away with the file locking. This is all the same source file, and after the encode had finished. Why a source file is often locked by x264 before the script is encoded is something else I don't understand. If it wasn't for Unlocker I'd be living in a padded room by now.

https://s18.postimg.org/cp2080km1/unlocker.gif

And then MeGUI went and out-did itself, although that was a test script so admittedly I encoded it three times.

https://s22.postimg.org/8isqquo1t/unlocker2.gif

[Zathor]

But I think than is not the exact DAR of this sample.
Then I do other encode with:
- Selecting Generic non-ITU Input DAR: 16:9 (1.77778)
- Clever anamorphic...: Encode non-mod16
- Autocrop (without resize)

And I obtain a wrong output DAR 646x472 like with job25

@Zathor
For what the change of aspect ratio (avs) 1,337 to the undesired aspect ratio (job) 1.370?

With a --sar near 32:27 we can obtain a correct output DAR 630x472
How have you done that? I just did a manual encode (File Indexer, AVS Script Creator, X264) with your settings above and the output did had the correct AR.

[Zathor]

Is it possible MeGUI gets carried away with the file locking. This is all the same source file, and after the encode had finished. Why a source file is often locked by x264 before the script is encoded is something else I don't understand. If it wasn't for Unlocker I'd be living in a padded room by now.
And then MeGUI went and out-did itself, although that was a test script so admittedly I encoded it three times.

Hard to guess. MeGUI itself should not have any file handles open to those files. Two exceptions: AVS scripts opened by MeGUI or mediainfo information.
Could you please replace your megui.exe with these files? http://megui.org/megui_test.zip
In the log tab you will find a new "AviSynth" chapter where you can see when MeGUI uses avisynth and if it will be closed properly. if the encode is finished the last entry there should be that the count of avisynth sessions is 0 = no file lock.
EDIT: I uploaded another debug build. Btw. you can also try the new worker settings if you like. The window is not polished at all yet, but workers are started based on the rules on that page.

[hello_hello]

Thanks. I'll give it a spin after the current bunch of encoding jobs have finished. Probably tomorrow at this rate.

Mind you, a few days ago I tried moving the d2v files from six completed jobs but I couldn't because they were all locked, then the next few were movable, then a couple not, and sometimes it doesn't happen for days, so it's fairly intermittent. I'll keep my eye on the log file though and let you know what it contains when it happens next.

Cheers.

[tebasuna51]

How have you done that? I just did a manual encode (File Indexer, AVS Script Creator, X264) with your settings above and the output did had the correct AR.

I located the bug (at least in my side).

Beggining with Settings -> Main Configuration -> Use ITU Aspect Ratio NOT CHECKED
Now detected Input DAR is 16:9 (1.77778)

-[Information] Log for job1 (video, VTS_01_PGC_02_1.avs -> VTS_01_PGC_02_14.mkv)
---[NoImage] # Set DAR in encoder to 131 : 98. The following line is for automatic signalling
---[NoImage] global MeGUI_darx = 131
---[NoImage] global MeGUI_dary = 98
...
---[NoImage] crop(94, 4, -94, -4)
--[Information] [05/05/2017 13:13:25] resolution: 532x472
--[Information] [05/05/2017 13:13:25] aspect ratio: 131:98 (1.337)
--[Information] [05/05/2017 13:13:25] Job command line: ... --sar 7729:6517...

All correct.
Now manually select Input DAR in AviSynth Script creator to ITU 16:9 NTSC (1.823169)

-[Information] Log for job2 (video, VTS_01_PGC_02_1.avs -> VTS_01_PGC_02_15.mkv)
---[NoImage] # Set DAR in encoder to 137 : 100. The following line is for automatic signalling
---[NoImage] global MeGUI_darx = 137
---[NoImage] global MeGUI_dary = 100
---[NoImage] crop(94, 4, -94, -4)
--[Information] [05/05/2017 13:17:53] resolution: 532x472
--[Information] [05/05/2017 13:17:53] aspect ratio (avs): 137:100 (1.370)
--[Information] [05/05/2017 13:17:53] aspect ratio (job): 131:98 (1.337)
--[Information] [05/05/2017 13:17:53] Job command line: ... --sar 7729:6517...

The avs is correct but the job obey the Main Configuration instead the manual user selection.

Just the same (see previous post) if beggining with Settings -> Main Configuration -> Use ITU Aspect Ratio CHECKED

Full logs of both ways:

[sumirecccp]

thank you for Zathor and tebasuna51 for testing.
The best way to solve this problem I think is to add a "DAR select menu" on the one-click configuration dialog, so we can choose or ignore the DAR manually.

It's very useful in batch VOB converting I think.

tebasuna51 if you know megui's author please tell him this request.

https://image.ibb.co/eJa0J5/QQ_20170506012849.jpg

[stax76]

@sumirecccp

It can take time until attachments get approved, to show an image instantly you can use a image hoster like postimage.

megui is maintained by Zathor.

[hello_hello]

I located the bug (at least in my side).

Aren't they both wrong?

I think you're at least partly a victim of MeGUI's option for anamorphic aspect ratio fudging, which is 1% by default, although I don't know what it aims for when fudging is enabled. It's probably of no use unless you want to aim for a nice 4:3 or 16:9 aspect ratio, but for other aspect ratios I can't see much reason not to be accurate about it.

Anyway, I applied your cropping and checked the script.

Non ITU:
global MeGUI_darx = 2128
global MeGUI_dary = 1593
(1.3358)

SAR: 32:27

ITU:
global MeGUI_darx = 54720
global MeGUI_dary = 39943
(1.3670)

SAR: 5760:4739.
That's the old ITU SAR I MeGUI still uses, so it's what it should be.
https://forum.doom9.org/showthread.php?p=1058927#post1058927

If I change the option to 1%, I get display aspect ratios of 131:98 and 137:100 as you did.
SARs 7729:6517 & 8083:6650 respectively when I encoded them.

When you ran the encodes, did you resave/edit the script and add it to the queue without first reloading it into the Avsiynth script section (was it already loaded), or did you at least usie the "re-open video preview" button? Because that might explain the same SAR each time. Once you've loaded a script into the video section and MeGUI's done it's checking, it seems to stay married to that display aspect ratio if you don't reload the script. I'm not sure if it works exactly the same way for anamorphic encoding, but if you had a non anamorphic script outputting 640x480 (for example) and edited the resizing to 656x480 without reloading it (just for example) I'm pretty sure MeGUI will go all anamorphic & try to "correct it" to 4:3 by changing the SAR.

Off the top of my head, I can't think of another likely explanation, especially given for your previous test it used SAR 8083:6650 both times.

[sumirecccp]

@sumirecccp

It can take time until attachments get approved, to show an image instantly you can use a image hoster like postimage.

megui is maintained by Zathor.

thank you , edited.

[hello_hello]

thank you for Zathor and tebasuna51 for testing.
The best way to solve this problem I think is to add a "DAR select menu" on the one-click configuration dialog, so we can choose or ignore the DAR manually.

It's very useful in batch VOB converting I think.

The only way for an Output DAR option not to distort the encodes by different amounts would be for MeGUI to make sure they're all cropped to the same aspect ratio.

I had a cunning plan, but it was slightly thwarted by MeGUI in the end. Still workable though.
By somewhat of a coincidence (there's no guarantee the auto-cropping will be the same each time) applying your autocrop settings to your sample manages to give you exactly 4:3, if you assume a generic PAR/SAR of 32:27.

Autocrop defaults to a mod4 width and mod2 height when cropping (I forgot about that till after I finished playing around so didn't change it myself), however to ensure it's 4:3 each time, you should still set the correct aspect ratio, and if you're going to set a cropping aspect ratio, you might as well make it mod2 for some extra resizing accuracy if you resize afterwards.

If the source PAR is 32:27, that'll be:
Autocrop(mode=1, wMultOf=2, threshold=50, samples=10, aspect=1.125)
Otherwise, and it might be more correct, if you use the mpeg4 SAR of 40:33, the aspect will be:
Autocrop(mode=1, wMultOf=2, threshold=50, samples=10, aspect=1.1)

Here's the difference for your sample (without wMultOf=2):
Aspect 1.125 vs Aspect 1.1

https://s3.postimg.org/iumi60hi7/1125.jpg (https://postimg.org/image/iumi60hi7/) https://s3.postimg.org/76sgbgsdb/image.jpg (https://postimg.org/image/76sgbgsdb/)

The cropping/resolution mightn't always be the same, but the display aspect ratio should be.

Follow autocrop with resizing to 4:3 dimensions in your template if you want to resize, as you're doing.
Autocrop(mode=0, wMultOf=2, threshold=50, samples=10, aspect=1.125)
Spline36Resize(640,480)

Create an encoder preset with the "force SAR" option set to 1:1 under the Misc tab for x264, or add --sar 1:1 to the custom command line section for x265 and save the encoder preset as part of your OneClick profile. That fixes the encoding, and it doesn't seem to matter if "keep input resolution" etc are enabled or not, but the muxing.... not so much....

--[Information] [06/05/17 3:42:10 PM] Avisynth input script
---[NoImage] global MeGUI_darx = 16
---[NoImage] global MeGUI_dary = 9
---[NoImage] LoadPlugin("C:\Program Files\MeGUI\tools\dgindex\DGDecode.dll")
---[NoImage] DGDecode_mpeg2source("D:\aseauczn.pgj\VTS_01_PGC_02_1.d2v")
---[NoImage] Autocrop(mode=0,threshold=50,samples=10, aspect=1.1)
---[NoImage] Spline36Resize(640,480)
--[Information] [06/05/17 3:42:10 PM] resolution: 640x480
--[Information] [06/05/17 3:42:10 PM] frame rate: 30000/1001
--[Information] [06/05/17 3:42:10 PM] frames: 1550
--[Information] [06/05/17 3:42:10 PM] aspect ratio: 16:9 (1.778)
--[Information] [06/05/17 3:42:11 PM] custom command line: --sar 1:1
--[Information] [06/05/17 3:42:11 PM] Job command line: "C:\Program Files\MeGUI\tools\x265\avs4x26x.exe" --x26x-binary "C:\Program Files\MeGUI\tools\x265\x86\x265.exe" --preset superfast --sar 1:1 --output "D:\aseauczn.pgj\VTS_01_PGC_02_1_Video.hevc" "D:\aseauczn.pgj\VTS_01_PGC_02_1.avs"
--[Information] [06/05/17 3:42:11 PM] Process started
--[Information] [06/05/17 3:42:11 PM] Standard output stream
---[Information] [06/05/17 3:42:47 PM] avs [info]: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
---[Information] [06/05/17 3:42:47 PM] avs [info]: Video colorspace: YV12
---[Information] [06/05/17 3:42:47 PM] avs [info]: Video resolution: 640x480
---[Information] [06/05/17 3:42:47 PM] avs [info]: Video framerate: 30000/1001
---[Information] [06/05/17 3:42:47 PM] avs [info]: Video framecount: 1550
---[Information] [06/05/17 3:42:47 PM] avs4x26x [info]: "C:\Program Files\MeGUI\tools\x265\x86\x265.exe" - --preset superfast --sar 1:1 --output D:\aseauczn.pgj\VTS_01_PGC_02_1_Video.hevc --frames 1550 --fps 30000/1001 --input-res 640x480 --input-csp i420
--[Warning] [06/05/17 3:42:11 PM] Standard error stream
---[Information] [06/05/17 3:42:11 PM] yuv [info]: 640x480 fps 30000/1001 i420p8 sar 1:1 unknown frame count

Unfortunately it's the muxing that lets the team down.

--[Information] [06/05/17 3:45:43 PM] Job command line: "C:\Program Files\MeGUI\tools\mkvmerge\mkvmerge.exe" -o "D:\VTS_01_PGC_02_1.mkv" --aspect-ratio 0:16/9 --default-duration 0:29.97fps "--compression" "0:none" -d "0" --no-chapters -A -S "D:\aseauczn.pgj\VTS_01_PGC_02_1_Video.hevc" --engage no_cue_duration --engage no_cue_relative_position --ui-language en

I can't think of a reason why MeGUI should specify an aspect ratio when muxing with MKVToolNix. The SAR is always written to the video stream, and when it is, MKVToolNix uses it to set the correct display aspect ratio automatically, so it only seems like potential for something to go wrong.

All is not lost though. Until you've convinced Zathor to remove the aspect ratio from the muxing command line, set MeGUI to not delete temporary files, find the encoded hevc stream, open it with MKVToolNix GUI, click the "start multiplexing button" (add the extracted audio first etc if you wish) and in no time you'll have a 4:3 MKV.

If you want to use anamorphic encoding without any resizing instead and still output 4:3, remove the resizing from your template and add the appropriate SAR to the command line. ie:

Autocrop(mode=0, wMultOf=2, threshold=50, samples=10, aspect=1.125).Spline36Resize(640,480) for --sar 1:1

Autocrop(mode=0, threshold=50, samples=10, aspect=1.125) for --sar 32:27

Autocrop(mode=0, threshold=50, samples=10, aspect=1.1) for --sar 40:33

Whichever you use, you'll just have to mux the output hevc file yourself so MeGUI can't set the wrong MKV aspect ratio, but it should be encoded correctly.

The aspect ratio for cropping is easy to work out once you've picked a source PAR/SAR. I go with mpeg4 or generic PARs as they're easier to remember than ITU, and they can be found under "force SAR" in MeGUI's x264 configuration.
(4 / 3) / (32 / 27) = 1.125
How to set aspect properly (https://forum.doom9.org/showthread.php?p=1058927#post1058927)

[tebasuna51]

The best way to solve this problem I think is to add a "DAR select menu" on the one-click configuration dialog, so we can choose or ignore the DAR manually.

Like I say I never use One-click encode, then I don't know if that can help or not.

But I don't understand for what you check 'Keep Input Resolution (disable crop & resize)' when you seems use a AviSynth Profile than make a crop and a resize:

tfm(order=-1).tdecimate(hybrid=1)
autocrop(mode=0,threshold=50,samples=10)
lanczos4resize(640,480)

What happens if you uncheck 'Keep Input Resolution (disable crop & resize)'? Maybe the Input DAR is ignored.

Aren't they both wrong?
...
When you ran the encodes, did you resave/edit the script and add it to the queue without first reloading it into the Avsiynth script section (was it already loaded), or did you at least usie the "re-open video preview" button?
See the full log's.

First log procedure:
1) Open MeGUI
2) Settings -> Main Configuration -> Use ITU Aspect Ratio NOT CHECKED
3) Load .d2v in Avs Script Creator, encode with detected Input DAR 16:9 (1.77778)
The AR 1.337 is not changed.
4) Again Load .d2v in Avs Script Creator, manually select Input DAR in AviSynth Script creator to ITU 16:9 NTSC (1.823169)
5) New encode, the avs AR 1.370 is changed to 1.337.
6) Close MeGUI

Second log procedure:
1) Open MeGUI
2) Settings -> Main Configuration -> Use ITU Aspect Ratio CHECKED
3) Load .d2v in Avs Script Creator, encode with detected Input DAR ITU 16:9 NTSC (1.823169)
The AR 1.370 is not changed.
4) Again Load .d2v in Avs Script Creator, manually select Input DAR in AviSynth Script creator to DAR 16:9 (1.77778)
5) New encode, the avs AR 1.337 is changed to 1.370.

I think you're at least partly a victim of MeGUI's option for anamorphic aspect ratio fudging, which is 1% by default,...
I know, the question is not related with exact sar's to use, is for what MeGUI change the avs aspect ratio.

[hello_hello]

A couple more muxing thoughts....

I ask, because I discovered x264 is very good a variable frame rate encoding so I've been using TIVTC to create a timecodes file for NTSC sources, then it's simply a matter of adding the timecodes file to the x264 command line. It's surprisingly easy. So much so, it's a wonder no Avisynth GUIs have implemented a VFR mode (that I know of), but once again I can't let MeGUI mux the output because it adds a frame rate to the mkvmerge command line. Does that have a purpose, at least when the encoder is writing the output directly to MKV?

And I think sometimes it adds the frame rate like this --default-duration 0:29.97fps and sometimes in this format --default-duration 0:3000/1001, but I can't remember when exactly.

[Sharc]

I am pretty sure the PAR of the original .vob sample is 32:27.
The source is hard telecined, possibly with broken pattern (I didn't fully check though). Because of the interlaced frames, vertical resizing should be avoided unless proper IVTC is applied.
So my proposed script for an anamorphic 4:3 picture would be (without IVTC):
crop(94,0,-94,0)
spline36resize(710,480) #don't resize vertically
addborders(4,0,6,0) #pad to 720 width

Encode this with --tff --sar 8:9 (=0.8888... generic NTSC for DAR 4:3)

[Zathor]

I located the bug (at least in my side).

Beggining with Settings -> Main Configuration -> Use ITU Aspect Ratio NOT CHECKED
Now detected Input DAR is 16:9 (1.77778)


All correct.
Now manually select Input DAR in AviSynth Script creator to ITU 16:9 NTSC (1.823169)



The avs is correct but the job obey the Main Configuration instead the manual user selection.

Just the same (see previous post) if beggining with Settings -> Main Configuration -> Use ITU Aspect Ratio CHECKED
I just tested it myself and sadly I cannot reproduce it. I did what you wrote and - as not mentioned by you - I did the first AVS, closed the AVS creator, queued the encoding, let it finish, started the AVS creator again (reused existing d2v), created the second AVS, closed the AVS creator, queued the encoding. Both have their correct ARs. No difference between the jobs and the files AR.
EDIT: Bug found - it appears only if the setting "show video preview after avisynth script selection" is unchecked.
EDIT2: fixed

[Zathor]

A couple more muxing thoughts....

I ask, because I discovered x264 is very good a variable frame rate encoding so I've been using TIVTC to create a timecodes file for NTSC sources, then it's simply a matter of adding the timecodes file to the x264 command line. It's surprisingly easy. So much so, it's a wonder no Avisynth GUIs have implemented a VFR mode (that I know of), but once again I can't let MeGUI mux the output because it adds a frame rate to the mkvmerge command line. Does that have a purpose, at least when the encoder is writing the output directly to MKV?

And I think sometimes it adds the frame rate like this --default-duration 0:29.97fps and sometimes in this format --default-duration 0:3000/1001, but I can't remember when exactly.

All these fps/AR settings get applied to the muxers as for some input formats there are/were problems to be detected by the muxers resulting in wrong files. I am not sure if this is still true today. If not I can remove those forced settings at least for the formats/input files we now it works for.
Please keep in mind that we have four muxers and an "unlimited" count of input formats (while only 4 types are encoded by MeGUI, way more can be muxed e.g. into mkv).

[stax76]

All these fps/AR settings get applied to the muxers as for some input formats there are/were problems to be detected by the muxers resulting in wrong files. I am not sure if this is still true today. If not I can remove those forced settings at least for the formats/input files we now it works for.
Please keep in mind that we have four muxers and an "unlimited" count of input formats (while only 4 types are encoded by MeGUI, way more can be muxed e.g. into mkv).

I use MediaInfo to check if the input has fps metadata.


If MediaInfo.GetFrameRate(p.VideoEncoder.OutputPath, 0) = 0 Then
args.Append(" --default-duration 0:" + p.Script.GetFramerate.ToString("f6", CultureInfo.InvariantCulture) + "fps")
End If


MediaInfo code to get the frame rate:


Function GetFrameRate(Optional defaultValue As Double = 25) As Double
Dim num = GetVideo("FrameRate_Num").ToInt
Dim den = GetVideo("FrameRate_Den").ToInt
If num > 0 AndAlso den > 0 Then Return num / den
Dim ret = GetVideo("FrameRate")
If ret = "" Then ret = GetVideo("FrameRate_Original")
If ret = "" Then ret = GetVideo("FrameRate_Nominal")
If ret.IsDouble Then Return ret.ToDouble Else Return defaultValue
End Function


I believe most tools create fps metadata, one tool that don't is VCEEnc because of the VCE SDK.

[Zathor]

I use MediaInfo to check if the input has fps metadata.
I believe most tools create fps metadata, one tool that don't is VCEEnc because of the VCE SDK.
Thanks, yes, MeGUI does it the same way with MediaInfo. However you still do not know if the muxer uses also the media information of the source file. E.g. HEVC was not parsed for some time by the muxers to my knowledge even as it could be added.

[Zathor]

I ask, because I discovered x264 is very good a variable frame rate encoding so I've been using TIVTC to create a timecodes file for NTSC sources, then it's simply a matter of adding the timecodes file to the x264 command line. It's surprisingly easy. So much so, it's a wonder no Avisynth GUIs have implemented a VFR mode (that I know of)
Could you please share more details about that? e.g. sample file(s),...

[hello_hello]

Like I say I never use One-click encode, then I don't know if that can help or not.

But I don't understand for what you check 'Keep Input Resolution (disable crop & resize)' when you seems use a AviSynth Profile than make a crop and a resize:

tfm(order=-1).tdecimate(hybrid=1)
autocrop(mode=0,threshold=50,samples=10)
lanczos4resize(640,480)

What happens if you uncheck 'Keep Input Resolution (disable crop & resize)'? Maybe the Input DAR is ignored.

I don't think the "keep input resolution" option should have anything to do with the aspect ratio directly. It seems to just disable cropping and resizing. Maybe I don't use OneClick enough myself, so I don't understand why it also greys out the InputDAR option.
It'd be like opening a source in the script creator and being able to set a different InputDAR when resizing is enabled, but you're stuck with the InputDAR detected by MeGUI if you disable resizing. The same applies to the anamorphic option. I don't understand why "keep input resolution" greys it out if all it should do is disable auto-cropping and auto-resizing.

I guess ideally OneClick would work the same way as creating a script with the Script Creator, using the InputDAR as the basis for it's calculations according to the script output. I guess that's what it does when OneClick is auto cropping and resizing, but it's oblivious to any changes in resolution or aspect ratio inflicted on the video by an Avisynth profile.

My main motivation for creating this script (https://forum.videohelp.com/threads/382888-CropResizeBorder-script) was to make it easy to crop and resize to a specific output resolution/aspect ratio automatically for batch encoding, pretty much what sumirecccp wants to do with his auto-cropping, I assume, and it works a treat as long as I create individual scripts and load them for batch encoding rather than add it to an Avisynth profile for OneClick.
It be great if a GUI could do the same.... here's a bunch of files I want cropped to exactly 16:9 and resized to 960x540... as opposed to copping varying amounts of back and outputting whatever resolution/aspect ratio happens to remain.

See the full log's.

Yeah, I see what you mean and it appears Zathor's outdone himself and fixed it already. :)

[hello_hello]

Could you please share more details about that? e.g. sample file(s),...

Certainly. I'll wonder off and find some old scripts and return shortly.

Before I go.......

I also don't use OneClick enough to have discovered which settings in the Avisynth profile configuration effect the OneClick encoder. For instance if you create an Avisynth profile with anamorphic encoding enabled and select it as the Avisynth profile for OneClick, but leave anamorphic encoding unchecked in the OneClick configuration, which setting wins? That sort of thing....

Cheers.

[Zathor]

I also don't use OneClick enough to have discovered which settings in the Avisynth profile configuration effect the OneClick encoder. For instance if you create an Avisynth profile with anamorphic encoding enabled and select it as the Avisynth profile for OneClick, but leave anamorphic encoding unchecked in the OneClick configuration, which setting wins? That sort of thing....
Good point! I will modify it in the way that the AVS profile will enable the OneClick anamorphic setting if enabled in the AVS profile. But maybe the best way is to completly remove the anamorphic checkbox and only to use it from within the AVS profile. Any thoughts?

Regarding the "keep input resolution": To be honest the settings of the Display Aspect Ratio and anamorphic get in any case applied if if disabled. I will change that as well yo that you can modify the checkbox / AR selection.

[hello_hello]

Could you please share more details about that? e.g. sample file(s),...

Hopefully this essay won't make it look hard. I'm just being thorough. ;)

When I referred to VFR and TIVTC, I was referring to encoding any hybrid NTSC DVD. A combination of "film" and "video". TIVTC mostly outputs two constant frame rates. 23.976 and 29.970. There's plugins such as Dedup for producing timecodes files and removing as many duplicate frames as possible, but that's all they do.

If you're not fond of TIVTC's de-interlacing, I'm fairly sure you can still create a second de-interlaced clip for it to use.

I'm yet to find a way to IVTC the film parts and de-interlace the video parts to 60fps, although I'm not sure that's a big deal. If a source was predominantly interlaced I'd probably be inclined to de-interlace it all with QTGMC to 60fps and be done with it.

If I'm doing a bunch of encodes, my method is to create two scripts for each encode in advance, the first only with TIVTC for outputting the metrics files (I'll call it script A) and the second with TIVTC and whatever filtering for encoding (I'll call it script B). The trick is to be organised and name all the input/output metrics files in the scripts in logical way, so then it's just a matter of adding "script A" for encode one to the job queue as an analysis pass, "script B" for encode one as a normal encode, "script A" for encode two as an analysis pass, "script B" for encode two and so on...

Once the scripts are created the tedious part is having to open the x264 encoder configuration before adding each encoding script to the queue to change the name of the timecodes file to match the name of the timecodes file in the script.

Analysis and encoding scripts for a single job:

Analysis pass:
TFM(Output="D:\TFM Episode 1.txt")
TDecimate(Mode=4, Hybrid=2, Output="D:\TDecimate Episode 1.txt")

Encoding:
TFM(Input="D:\TFM Episode 1.txt")
TDecimate(Mode=5, Hybrid=2, Input="D:\TDecimate Episode 1.txt", TFMIn="D:\TFM Episode 1.txt", mkvOut="D:\Timecodes Episode 1.txt")

Before adding the second script to the job queue, the following would be added to the custom command line in the x264 encoder configuration:

--tcfile-in "D:\Timecodes Episode 1.txt"

That's pretty much it. None of the output files have to exist, including timecodes file for x264. TIVTC creates it as soon as the encoding script is opened. I always have x264 writing directly to an MKV so I don't know if it can work the same way when outputting raw avc.

The MeGUI "gotcha".....
Mainly due to it's checking of scripts as you add them to the queue. When you add an analysis script to the queue MeGUI does it's checking thing, and TFM and TDecimate spit out their respective metrics files, but only for the first few frames. When you run the analysis pass they're over-written with full versions, however... if the analysis pass has already run and you're silly enough to add the script to the job queue again, or have the audacity to open it an the preview etc, the complete metrics file will be over-written and you have to run the analysis pass again.
That's not a big deal because it's fairly fast. The problem is not realising it's happened before running the encoding pass, which will end up a mess. I'm pretty sure TDecimate has a setting to prevent that, but if memory serves it also prevents the loading of scripts in batch mode the way I described. I'd have to re-check those details.

TIVTC outputs a constant frame rate for Avisynth. I'm fairly sure it uses the average frame rate. Therefore if you leave the keyint settings up to MeGUI, they'll be set according to that frame rate. Personal preference.... I change the GOP calculation setting to fixed and set keyint to 240, or 250, or 300, depending on the mood I'm in.

An alternative is to not give x264 the timecodes file and simply encode at a fixed frame rate and add the timecodes file when muxing, but as x264 is frame rate aware, the resulting bitrate can be a little different for a given CRF value. I've not looked closely for quality differences but I assume x264 distributes the bits differently in VFR mode.

Encoding other VFR sources in VFR mode is a breeze if they're MKVs or something that can be remuxed as MKVs.
Remux, extract the video time codes, add them to the x264 command line and encode.

[hello_hello]

Good point! I will modify it in the way that the AVS profile will enable the OneClick anamorphic setting if enabled in the AVS profile. But maybe the best way is to completly remove the anamorphic checkbox and only to use it from within the AVS profile. Any thoughts?

To be honest 90% of my OneClick usage has been in the last couple of days, but I did find it a little frustrating at times.
By that, I mean MeGUI's encoder configurations have me well trained, so after opening OneClick and changing a setting and closing it, I kept forgetting it'd revert back to the way it was configured by the current OneClick profile. Quite a few times I unintentionally encoded with the wrong encoder configuration, or the wrong Avisynth profile etc, especially as some of those settings aren't visible initially.

Personally I think if the OnceClick configuration was much the same as the encoder configurations.... advanced options under tabs, no configuration within a configuration.... that's what configuring a OneClick profile seems like to me.... but a preset list at the bottom, and MeGUI asking twice if you want to update the profile or save it to scratchpad would give it quite a familiar feel. I know the configuration within the configuration works that way, but it just feels to me like the whole lot should be a single window.

For the Avisynth profile thing... I came up with various ideas but in the end decided they were bad, and part of the problem may be there's too many ways to change settings, so I kept going back to merging OneClick's configuration within a configuration into a single OneClick configuration, and maybe a better way to unite it with the Script Creator's Avisynth Profile Configuration will become more obvious.
For example, at the moment you can open the Avisynth profile configuration from both the OneClick/Advanced Config tab/Avisynth Profile/ Config button and also from the OneClick/Profile Configuration/Avisynth Profile Config button....

I don't know why, but having a Go button rather than a Queue button in the OneClick root configuration window makes me smile....

I still haven't managed to get around to playing with your MeGUI test build. Tomorrow....

[tebasuna51]

EDIT: Bug found - it appears only if the setting "show video preview after avisynth script selection" is unchecked.
EDIT2: fixed
Yes, I have "Show video preview after avisynth script selection" unchecked.

Thanks.

[Zathor]

2726 [OneClick] removed the "Anamorph Output" option in the OneClick profile. Please use the anamorphic encoding options in the AviSynth profile instead.
2725 [Main] fixed wrong AR of a "video encoding" queued job in rare cases (regression of 2610)
2724 [OneClick] cosmetic fix as sometimes even with "don't encode video" some video processing options were not disabled
2723 [OneClick] improved error handling of invalid AviSynth scripts

I still haven't managed to get around to playing with your MeGUI test build. Tomorrow....
Take your time. Btw I upload (at least until the new feature will be merged) always the test/debug builds in parallel to the normal builds.

And thanks for the VFR explanation! Do you have a sample file available?

[sumirecccp]

hi zathor, I test the build 2726 but it will crash when processing one-click profile.
https://preview.ibb.co/dn8wrQ/QQ_20170507022536.jpg

LOG:

Preliminary log file only. During closing of MeGUI the well formed log file will be written.

-[Information] Versions
--[Information] [2017/05/07 2:26:21] MeGUI: 2726
--[Information] [2017/05/07 2:26:21] Operating System: Windows 10 Enterprise x64 (10.0.0.15063)
--[Information] [2017/05/07 2:26:21] .NET Framework: 4.0 (4.0.0.0)
--[Information] [2017/05/07 2:26:21] .NET Framework: 4.7 (4.7.02046)
-[Information] Update detection
--[Information] [2017/05/07 2:26:21] Automatic update is disabled
--[Information] [2017/05/07 2:26:21] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [2017/05/07 2:26:21] Haali Media Splitter: 1.13.138.14 (14-04-2013)
--[Information] [2017/05/07 2:26:21] Haali DSS2: not installed
--[Information] [2017/05/07 2:26:21] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [2017/05/07 2:26:21] MediaInfo: 0.7.95.0 (04-05-2017)
--[Information] [2017/05/07 2:26:21] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [2017/05/07 2:26:21] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [2017/05/07 2:26:21] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [2017/05/07 2:26:21] 7z: 9.20 (18-11-2010)
-[Information] [2017/05/07 2:26:21] Version: 1.0.2721.0
-[Information] [2017/05/07 2:26:21] Date: 29-04-2017
-[Information] [2017/05/07 2:26:21] Interface: 3
--[Information] AviSynth Wrapper
--[Information] [2017/05/07 2:26:21] No package requires an update
-[Information] [2017/05/07 2:26:21] File Version: 2.6.0.5
-[Information] [2017/05/07 2:26:21] Date: 20-02-2015
-[Information] [2017/05/07 2:26:21] Name: Avisynth 2.6
-[Information] [2017/05/07 2:26:22] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
-[Information] [2017/05/07 2:26:22] AviSynth+: false
-[Information] [2017/05/07 2:26:22] MT: true
-[Information] [2017/05/07 2:26:22] Status: inactive
--[Information] AviSynth
-[Information] [2017/05/07 2:26:22] File Version: 0.1
-[Information] [2017/05/07 2:26:22] Date: 16-03-2017
-[Information] [2017/05/07 2:26:22] Name: AviSynth+ 0.1 (r2455, MT, i386)
-[Information] [2017/05/07 2:26:22] Version: AviSynth+ 0.1 (r2455, MT, i386)
-[Information] [2017/05/07 2:26:22] AviSynth+: true
-[Information] [2017/05/07 2:26:22] MT: true
-[Information] [2017/05/07 2:26:22] Status: active
--[Information] AviSynth portable
-[Information] OneClick
--[Information] [2017/05/07 2:27:04] MediaInfo
---[Information] [2017/05/07 2:27:04] File: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB
-[Information] Format: MPEG-PS
-[Information] FormatString: MPEG-PS
-[Information] FileSize: 36626432
-[Information] PlayTime: 00:00:51.718
---[Information] General
-[Information] ID: 224
-[Information] StreamOrder:
-[Information] Width: 720
-[Information] Height: 480
-[Information] FrameCount: 1550
-[Information] FrameRate: 29.970
-[Information] FrameRateOriginal:
-[Information] FrameRateMode:
-[Information] ScanType: Interlaced
-[Information] Codec: MPEG-2V
-[Information] CodecString: MPEG-2 Video
-[Information] Bits Depth: 8
-[Information] Format: MPEG Video
-[Information] AspectRatio: 1.778
-[Information] AspectRatioString: 16:9
-[Information] Delay: 280.633
-[Information] Title:
-[Information] Language:
-[Information] LanguageString:
-[Information] Default:
-[Information] DefaultString:
-[Information] Forced:
-[Information] ForcedString:
---[Information] Video
-[Information] ID: 189-128
-[Information] StreamOrder: 0
-[Information] Format: AC-3
-[Information] FormatProfile:
-[Information] FormatSettingsSBR:
-[Information] FormatSettingsPS:
-[Information] SamplingRate: 48000
-[Information] SamplingRateString: 48.0 kHz
-[Information] Channels: 2
-[Information] ChannelsString: 2 channels
-[Information] ChannelPositionsString2: 2/0/0
-[Information] BitRateMode: CBR
-[Information] Delay: 280.633
-[Information] Title:
-[Information] Language:
-[Information] LanguageString:
-[Information] Default:
-[Information] DefaultString:
-[Information] Forced:
-[Information] ForcedString:
-[Information] [2017/05/07 2:27:04] The language information is not available for this track. The default MeGUI language has been selected.
---[Information] Audio
--[Information] [2017/05/07 2:27:12] Video: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB
--[Information] [2017/05/07 2:27:12] Audio: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB ([80] - AC-3 - 2 channels / 48.0 kHz / Japanese)
-[Information] Log for job1 (idx, VTS_01_PGC_02_1.VOB -> VTS_01_PGC_02_1.d2v)
--[Information] [2017/05/07 2:27:18] Started handling job
--[Information] [2017/05/07 2:27:18] Preprocessing
--[Information] [2017/05/07 2:27:18] Job command line: "E:\D\software\megui\tools\dgindex\dgindex.exe" -SD=< -AIF=<F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB< -OF=<F:\DVD_VOLUME\VIDEO_TS\depvgcfg.azo\VTS_01_PGC_02_1< -FO=0 -exit -hide -OM=2
--[Information] [2017/05/07 2:27:18] Process started
--[Information] [2017/05/07 2:27:18] Standard output stream
--[Information] [2017/05/07 2:27:18] Standard error stream
--[Information] [2017/05/07 2:27:21] Running auto force film
---[Information] [2017/05/07 2:27:21] Film percentage: -1
--[Information] [2017/05/07 2:27:21] Postprocessing
-[Information] [2017/05/07 2:27:21] Successfully deleted F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.log
---[Information] [2017/05/07 2:27:21] Deleting intermediate files
--[Information] [2017/05/07 2:27:21] Job completed
-[Information] Log for job2 (oneclick, VTS_01_PGC_02_1.VOB -> )
--[Information] [2017/05/07 2:27:21] Started handling job
--[Information] [2017/05/07 2:27:21] Preprocessing
--[Information] [2017/05/07 2:27:21] Processing thread started
--[Information] [2017/05/07 2:27:21] Desired size:
--[Information] [2017/05/07 2:27:21] Split size:

[Zathor]

I am not able to reproduce that. Could you please upload your OneClick profile? Export it please with File\Export Presets

[sumirecccp]

I am not able to reproduce that. Could you please upload your OneClick profile? Export it please with File\Export Presets

Oh sorry, I checked the "always use the included avisynth" incorrectly.

2726 will output 640x480,4:3 mp4 when choose INPUT DAR 4:3. but it will only take effect in single file mode.

when use foldermode/multi file mode, it will still output auto-detect 16:9 mp4.

https://image.ibb.co/iOZdo5/QQ_20170507120743.jpg

[Zathor]

Oh sorry, I checked the "always use the included avisynth" incorrectly.
:confused: It should not crash in any case. What have you changed so that it does not crash anymore or what was the reason for your crash?

2726 will output 640x480,4:3 mp4 when choose INPUT DAR 4:3. but it will only take effect in single file mode.
when use foldermode/multi file mode, it will still output auto-detect 16:9 mp4.
That is expected as you cannot choose the AR in the OneClick profile (yet).

[sumirecccp]

Zathor, I did't change anything except "always use the included avisynth" in settings.
after uncheck it, it works well again.

>>I am not able to reproduce that. Could you please upload your OneClick profile? Export it please with File\Export Presets

the preset is as the same as before, I did't change anything

>>That is expected as you cannot choose the AR in the OneClick profile (yet).

Hope you can add that function in future build.

[Zathor]

Zathor, I did't change anything except "always use the included avisynth" in settings.
after uncheck it, it works well again.
So it seems to be then a crash in AviSynth and not in MeGUI. Nevertheless it is strange.

@all: I rewrote the aspect ratio handling a bit. Please test as always. There will be some use cases which I did not had the chance to test.

2631 [OneClick] added aspect ratio selection to the OneClick profile
input aspect ratio can always be selected
if an input aspect ratio will be selected this will be forced
the aspect ratio will not be forced by the muxer if the video track has been encoded
cosmetics
2630 [AutoEncode] do not force the aspect ratio to be written by the muxer as it is available in the video stream
2629 [Muxer] added/improved aspect ratio writing (all muxers except the AVI muxer)
for the M2TS muxer only some input video types are supported
improved logging
2628 [VideoEncoder] forced aspect ratio to be written to the encoding
if not available in the job the avs aspect ratio information will be used
2627 [Worker] priority changes will also be applied to child processes. Feature request #615

[sumirecccp]

>>Zathor
check "always use the included avisynth" in settings will bring a crash: wait for other person's test, I think it should not be the avisynth's ploblem because it crashes at oneclick profile creation step


build 2631:works fine, it will output 640x480x4:3 mp4 at batch mode.
advice: I think there should be a "disable/ignore input DAR" option here,
https://image.ibb.co/ngBB85/QQ_20170508054054.jpg

Like if I have 2 avs, and one I want to output 1712*720 and another one 640x388, etc...

Bugs in Extra IO:
https://image.ibb.co/bPzET5/QQ_20170508055347.jpg
If I have two VOBS, file name like"VTS_01_PGC_02_1.VOB" and "VTS_01_PGC_03_1.VOB", and two cheapter files like "VTS_01_PGC_02 - Chapter Information - OGG.txt" and "VTS_01_PGC_03 - Chapter Information - OGG.txt".
and I want to encode "VTS_01_PGC_03_1.VOB". the one click encoder will auto load the chapter file "VTS_01_PGC_02 - Chapter Information - OGG.txt" ,but not the "VTS_01_PGC_03 - Chapter Information - OGG.txt" .

also there should be a "X" clear button so I could delete the chapter file.

[hello_hello]

Today I realised what it is that bugs me the most about the double confirmation dialogue, aside from the fact there's two of them.

I'm not sure I've lined them up exactly, but it's close enough.
Of course normally they're in the same position vertically on the screen as they appear one after the other.

https://s27.postimg.org/90jvtdon7/confim2.jpg

If you're not careful with cursor placement, after the second popup message replaces the first, clicking "No" can become clicking "Yes" or clicking "No" can become clicking "Cancel", so there's two confirmation dialogues with required reading (I was fine with one but my brain doesn't seem to have enough memory for retaining two) and cursor placement needs to move up to a conscious level where it can be adjusted to compensate for button drift.

Maybe it's just me, but the second or two all that takes feels like hard work. :)

[hello_hello]

sumirecccp's post reminded me of something.

The subtitle section in the script creator is equally stubborn when it comes to removing subtitles from scripts. There's no way to "clear" the subtitle field once they've been added, short of shutting down the script creator and starting again.

I don't think any of the "x" buttons in OneClick or AudoEncode are Woking for me. They seem unable to clear anything.

[Zathor]

>>Zathor
check "always use the included avisynth" in settings will bring a crash: wait for other person's test, I think it should not be the avisynth's ploblem because it crashes at oneclick profile creation step
I do not have that problem at all with the included avisynth build and your profile. I may upload a debug build later for you to test to see where it will crash.


Bugs in Extra IO:
If I have two VOBS, file name like"VTS_01_PGC_02_1.VOB" and "VTS_01_PGC_03_1.VOB", and two cheapter files like "VTS_01_PGC_02 - Chapter Information - OGG.txt" and "VTS_01_PGC_03 - Chapter Information - OGG.txt".
and I want to encode "VTS_01_PGC_03_1.VOB". the one click encoder will auto load the chapter file "VTS_01_PGC_02 - Chapter Information - OGG.txt" ,but not the "VTS_01_PGC_03 - Chapter Information - OGG.txt" .
It should only autoload in the case it has been or will be created by MeGUI. You only have the VOB + TXT in the directory or the whole structure (+ IFOs...).

I don't think any of the "x" buttons in OneClick or AudoEncode are Woking for me. They seem unable to clear anything.
If you (incl. sumirecccp) tell me which X does not work or is missing I will check it.

Today I realised what it is that bugs me the most about the double confirmation dialogue, aside from the fact there's two of them.
Maybe it's just me, but the second or two all that takes feels like hard work. :)
It is not so easy to change as both are needed for some uses cases and only in one specfic use case you see both.

[sumirecccp]

>>I do not have that problem at all with the included avisynth build and your profile.

ok,waiting.

>>It should only autoload in the case it has been or will be created by MeGUI. You only have the VOB + TXT in the directory or the whole structure (+ IFOs...).
only have VOB+txt in the directory, you can copy VTS_01_PGC_02_1.VOB I uploaded before and rename it with VTS_01_PGC_03_1.VOB and test for it.

>>If you (incl. sumirecccp) tell me which X does not work or is missing I will check it.
I mean a button like this:

https://image.ibb.co/cv8BrQ/QQ_20170508145521.jpg
https://image.ibb.co/nDBWrQ/QQ_20170508145631.jpg
https://image.ibb.co/bRpvJ5/QQ_20170508145735.jpg

[Zathor]

>>I do not have that problem at all with the included avisynth build and your profile.
ok,waiting.
Here it is: http://megui.org/megui_debug.zip
EDIT: Extract both files into your MeGUI directory. It should still crash, but the log should show me more information.

[StainlessS]

If you (incl. sumirecccp) tell me which X does not work or is missing I will check it.

Dont know if this is one that HH is talking about, but, 2nd Dialog box in post 5521, little 'x' close dialog icon is disabled (greyed out).

[sumirecccp]

>>zathor


Preliminary log file only. During closing of MeGUI the well formed log file will be written.

-[Information] Versions
--[Information] [2017/05/09 2:06:33] MeGUI: 2732
--[Information] [2017/05/09 2:06:33] Operating System: Windows 10 Enterprise x64 (10.0.0.15063)
--[Information] [2017/05/09 2:06:33] .NET Framework: 4.0 (4.0.0.0)
--[Information] [2017/05/09 2:06:33] .NET Framework: 4.7 (4.7.02046)
-[Information] Update detection
--[Information] [2017/05/09 2:06:33] Automatic update is disabled
--[Information] [2017/05/09 2:06:33] Haali Media Splitter: 1.13.138.14 (14-04-2013)
--[Information] [2017/05/09 2:06:33] Using cached update config and server: http://megui.tmebi.de/test/
--[Information] [2017/05/09 2:06:33] Haali DSS2: not installed
--[Information] [2017/05/09 2:06:33] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
--[Information] [2017/05/09 2:06:33] MediaInfo: 0.7.95.0 (04-05-2017)
--[Information] [2017/05/09 2:06:33] MediaInfoWrapper: 0.7.61.0 (06-01-2013)
--[Information] [2017/05/09 2:06:33] MessageBoxExLib: 1.0.2218.28317 (19-12-2008)
--[Information] [2017/05/09 2:06:33] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
--[Information] [2017/05/09 2:06:33] 7z: 9.20 (18-11-2010)
-[Information] [2017/05/09 2:06:33] Version: 1.0.2721.0
-[Information] [2017/05/09 2:06:33] Date: 29-04-2017
-[Information] [2017/05/09 2:06:33] Interface: 3
--[Information] AviSynth Wrapper
--[Information] [2017/05/09 2:06:34] There is 1 package which can be updated: x265
-[Information] [2017/05/09 2:06:34] File Version: 2.6.0.5
-[Information] [2017/05/09 2:06:34] Date: 20-02-2015
-[Information] [2017/05/09 2:06:34] Name: Avisynth 2.6
-[Information] [2017/05/09 2:06:34] Version: AviSynth 2.60, build:Feb 20 2015 [03:16:45]
-[Information] [2017/05/09 2:06:34] AviSynth+: false
-[Information] [2017/05/09 2:06:34] MT: true
-[Information] [2017/05/09 2:06:34] Status: inactive
--[Information] AviSynth
-[Information] [2017/05/09 2:06:34] File Version: 0.1
-[Information] [2017/05/09 2:06:34] Date: 16-03-2017
-[Information] [2017/05/09 2:06:34] Name: AviSynth+ 0.1 (r2455, MT, i386)
-[Information] [2017/05/09 2:06:34] Version: AviSynth+ 0.1 (r2455, MT, i386)
-[Information] [2017/05/09 2:06:34] AviSynth+: true
-[Information] [2017/05/09 2:06:34] MT: true
-[Information] [2017/05/09 2:06:34] Status: active
--[Information] AviSynth portable
-[Information] OneClick
--[Information] [2017/05/09 2:06:43] MediaInfo
---[Information] [2017/05/09 2:06:43] File: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB
-[Information] Format: MPEG-PS
-[Information] FormatString: MPEG-PS
-[Information] FileSize: 36626432
-[Information] PlayTime: 00:00:51.718
---[Information] General
-[Information] ID: 224
-[Information] StreamOrder:
-[Information] Width: 720
-[Information] Height: 480
-[Information] FrameCount: 1550
-[Information] FrameRate: 29.970
-[Information] FrameRateOriginal:
-[Information] FrameRateMode:
-[Information] ScanType: Interlaced
-[Information] Codec: MPEG-2V
-[Information] CodecString: MPEG-2 Video
-[Information] Bits Depth: 8
-[Information] Format: MPEG Video
-[Information] AspectRatio: 1.778
-[Information] AspectRatioString: 16:9
-[Information] Delay: 280.633
-[Information] Title:
-[Information] Language:
-[Information] LanguageString:
-[Information] Default:
-[Information] DefaultString:
-[Information] Forced:
-[Information] ForcedString:
---[Information] Video
-[Information] ID: 189-128
-[Information] StreamOrder: 0
-[Information] Format: AC-3
-[Information] FormatProfile:
-[Information] FormatSettingsSBR:
-[Information] FormatSettingsPS:
-[Information] SamplingRate: 48000
-[Information] SamplingRateString: 48.0 kHz
-[Information] Channels: 2
-[Information] ChannelsString: 2 channels
-[Information] ChannelPositionsString2: 2/0/0
-[Information] BitRateMode: CBR
-[Information] Delay: 280.633
-[Information] Title:
-[Information] Language:
-[Information] LanguageString:
-[Information] Default:
-[Information] DefaultString:
-[Information] Forced:
-[Information] ForcedString:
-[Information] [2017/05/09 2:06:46] The language information is not available for this track. The default MeGUI language has been selected.
---[Information] Audio
--[Information] [2017/05/09 2:06:53] Video: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB
--[Information] [2017/05/09 2:06:53] Audio: F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB ([80] - AC-3 - 2 channels / 48.0 kHz / Japanese)
-[Information] Log for job3 (idx, VTS_01_PGC_02_1.VOB -> VTS_01_PGC_02_1.d2v)
--[Information] [2017/05/09 2:06:59] Started handling job
--[Information] [2017/05/09 2:06:59] Preprocessing
--[Information] [2017/05/09 2:06:59] Job command line: "E:\D\software\megui\tools\dgindex\dgindex.exe" -SD=< -AIF=<F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.VOB< -OF=<F:\DVD_VOLUME\VIDEO_TS\iziwdfnu.2ow\VTS_01_PGC_02_1< -FO=0 -exit -hide -OM=2
--[Information] [2017/05/09 2:06:59] Process started
--[Information] [2017/05/09 2:06:59] Standard output stream
--[Information] [2017/05/09 2:06:59] Standard error stream
--[Information] [2017/05/09 2:07:06] Running auto force film
---[Information] [2017/05/09 2:07:06] Film percentage: -1
--[Information] [2017/05/09 2:07:06] Postprocessing
-[Information] [2017/05/09 2:07:06] Successfully deleted F:\DVD_VOLUME\VIDEO_TS\VTS_01_PGC_02_1.log
---[Information] [2017/05/09 2:07:06] Deleting intermediate files
--[Information] [2017/05/09 2:07:06] Job completed
-[Information] Log for job4 (oneclick, VTS_01_PGC_02_1.VOB -> )
--[Information] [2017/05/09 2:07:06] Started handling job
--[Information] [2017/05/09 2:07:06] Preprocessing
--[Information] [2017/05/09 2:07:06] Processing thread started
--[Information] [2017/05/09 2:07:06] Desired size:
--[Information] [2017/05/09 2:07:06] Split size:
--[Information] [2017/05/09 2:07:06] DEBUG: 1
-[Information] AviSynth
-[NoImage] LoadPlugin("E:\D\software\megui\tools\dgindex\DGDecode.dll")
-[NoImage] DGDecode_Mpeg2Source("F:\DVD_VOLUME\VIDEO_TS\iziwdfnu.2ow\VTS_01_PGC_02_1.d2v")
-[NoImage] 場所 System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
-[NoImage] 場所 System.Environment.get_StackTrace()
-[NoImage] 場所 MeGUI.AviSynthClip.HandleAviSynthWrapperDLL(Boolean bUnload, String script) 場所 D:\MEGUI\MeGUI_debug\packages\tools\avscreator\AvisynthWrapper.cs:行 633
-[NoImage] 場所 MeGUI.AviSynthClip..ctor(String func, String arg, AviSynthColorspace forceColorspace) 場所 D:\MEGUI\MeGUI_debug\packages\tools\avscreator\AvisynthWrapper.cs:行 542
-[NoImage] 場所 MeGUI.AviSynthScriptEnvironment.ParseScript(String script, AviSynthColorspace forceColorspace) 場所 D:\MEGUI\MeGUI_debug\packages\tools\avscreator\AvisynthWrapper.cs:行 83
-[NoImage] 場所 MeGUI.AvsFile..ctor(String script, Boolean parse) 場所 D:\MEGUI\MeGUI_debug\packages\reader\avs\AvsReader.cs:行 92
-[NoImage] 場所 MeGUI.AvsFile.ParseScript(String scriptBody) 場所 D:\MEGUI\MeGUI_debug\packages\reader\avs\AvsReader.cs:行 84
-[NoImage] 場所 MeGUI.d2vFile..ctor(String fileName) 場所 D:\MEGUI\MeGUI_debug\packages\reader\d2v\d2vReader.cs:行 90
-[NoImage] 場所 MeGUI.OneClickPostProcessing.createAVSFile(String indexFile, String inputFile, Nullable`1 AR, Int32 desiredOutputWidth, LogItem _log, AviSynthSettings avsSettings, Boolean autoDeint, VideoCodecSettings settings, Boolean autoCrop, Boolean keepInputResolution, Boolean useChaptersMarks) 場所 D:\MEGUI\MeGUI_debug\packages\tools\oneclick\OneClickPostProcessing.cs:行 562
-[NoImage] 場所 MeGUI.OneClickPostProcessing.StartPostProcessing() 場所 D:\MEGUI\MeGUI_debug\packages\tools\oneclick\OneClickPostProcessing.cs:行 284
-[NoImage] 場所 System.Threading.ThreadHelper.ThreadStart_Context(Object state)
-[NoImage] 場所 System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
-[NoImage] 場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
-[NoImage] 場所 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
-[NoImage] 場所 System.Threading.ThreadHelper.ThreadStart()
--[Information] [2017/05/09 2:07:06] sessions open: 1, id: 600580




but there're not a directory named D:\MEGUI\MeGUI_debug\packages\tools\avscreator\

[LigH]

Not on your PC. I believe that's the location of Zathor's sources.

[Zathor]

Dont know if this is one that HH is talking about, but, 2nd Dialog box in post 5521, little 'x' close dialog icon is disabled (greyed out).

I assume not, however that second X is also gone as the dialogue in this use case is gone:

2635 [MP4 Muxer] write always aspect ratio information to preserve anamorphic information. Bug #837
2634 [Profile] removed redundant second warning when changing a profile which should be saved to the scratchpad. Feature request #606
2633 [OneClick] added button to clear the working directory path and the chapters file
[AVS Script Creator] added button to clear the subtitle file
[Muxer] added button to clear the chapter file