MeGUI: bug reports and feature requests

[hello_hello]

Could you please try these two builds?
http://megui.org/debug.7z

fix: may fix the change intended with 2863
force: force portable avisynth (will not try to detect system installed one)

Fix: Exactly the same. Even when encoding, Avisynth 2.6 is used.

Force: The portable Avisynth+ is used and the log file says Avisynth is not installed.

I have no idea why having Avisynth 2.6 installed should make a difference, but the problem seems to be MeGUI is failing to copy Avisynth.dll to the MeGUI folder. The same for devil.dll. I'm pretty sure it's just those two dlls. If either are in the MeGUI folder, the "fix" version deletes them when it runs (if the installed Avisynth is 2.6).

For the "force" version, the dlls are copied to the MeGUI folder. All the required runtime files are in the MeGUI folder either way. Actually, when the "installed" Avisynth is used they were removed by a previous MeGUI, but currently they always remain in the MeGUI folder. I don't know if that's by design.

The log file for the "fix" version says avisynth.dll is in the MeGUI folder, but it's not.

--[Warning] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] File Version: 2.6.0.6
----[Information] File Date: 31-03-2015
----[Information] File Name: Avisynth 2.6
----[Information] File Path: c:\windows\system32\avisynth.dll
----[Information] AviSynth Version: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
----[Information] AviSynth+: false
----[Information] AviSynth MT: false
----[Information] AviSynth Status: active
---[Warning] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\megui\avisynth.dll
----[Warning] AviSynth Status: inactive - portable AviSynth build cannot be used. The loaded DLL is: c:\windows\system32\avisynth.dll
-[Information] Update detection
--[Information] [25/06/18 2:20:17 AM] Connected to server: http://megui.tmebi.de/test/
--[Information] [25/06/18 2:20:17 AM] No package requires an update

I'm pretty sure this is different to the problem I originally reported because I'm sure a few versions ago MeGUI was copying Avisynth.dll to the MeGUI folder, but it wasn't using it, so something there must have changed recently. Hopefully the problem now is simply the absence of Avisynth.dll

From memory, LouieChuckyMerry is using a 64 bit version of Windows. Maybe MeGUI is behaving differently on 32 bit Windows. Or XP..... :(

Thank you!

[hello_hello]

Zathor,

I tried the "fix" version of MeGUI after manually copying avisynth.dll & devil.dll to the MeGUI folder while MeGUI was running, so it couldn't delete them, but it still used the installed Avisynth 2.6 for both previewing and encoding.

Is that expected behavior? Should MeGUI simply use the dll in the MeGUI folder if it's present, regardless of the setting in Options? From what you posted previously I assumed the avisynth wrapper would first look for Avisynth.dll in the MeGUI folder and use it if it's found there.

PS, If I'm the only one with this problem maybe it's time to give up. I can always swap Avisynth.dll in the system32 folder if I want to use Avisynth+ for some reason.

Cheers.

[Zathor]

The process during startup is:
- delete avisynth.dll if found in the MeGUI folder
- run a avs script to check if a system installed avisynth is found (+ log output)
- if no, no suitable version or if "always use portable" is checked, the avisynth.dll will be copied to the MeGUI root folder (from tools\avs)
- run a avs script to check if this portable avisynth can be used (+ log output)
- if the portable version cannot be used, delete the avisynth.dll from MeGUI root

So if you do not find it there, it has already been deleted.

Did the "force" version work or not? It does not do the steps with the system avisynth. Could you post a log of that?

What happens if you copy the tools\avs avisynth.dll and devil.dll to e.g. x264 folder and start the encode? Is it then using it?
EDIT: the avisynth.dll in an encoder folder cannot be influenced at all by MeGUI. So either it does work or not. During program start I can do a few changes for the detection and usage e.g. in AVS Creator, but not for the encoders. There the encoder has to call the proper dllbased on the search rules. Therefore it would be good to know e.g. when you run the x264.exe (without MeGUI) on a command line if the avisynth.dll in that folder will be used or not.

[hello_hello]

It still seems to me that MeGUI is failing to copy Avisynth.dll to the MeGUI folder when Avisynth 2.6 is installed, for some inexplicable reason.

Did the "force" version work or not? It does not do the steps with the system avisynth. Could you post a log of that?

Yes it did. The log file really only says the same as I did in my earlier post, but here it is:

[Information] AviSynth Information
-[Information] AviSynth Wrapper
--[Information] Version: 1.0.2847.0
--[Information] Date: 06-05-2018
--[Information] Interface: 3
-[Information] AviSynth
--[Information] AviSynth Status: not installed
-[Information] AviSynth portable
--[Information] File Version: 0.1
--[Information] File Date: 28-03-2018
--[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
--[Information] File Path: c:\megui\avisynth.dll
--[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
--[Information] AviSynth+: true
--[Information] AviSynth MT: true
--[Information] AviSynth Status: active

What happens if you copy the tools\avs avisynth.dll and devil.dll to e.g. x264 folder and start the encode? Is it then using it?

"Fix" deletes them from the x264 folder when it runs, but if I start "fix" and then manually copy the dlls to the x264 folder, it previews scripts with Avisynth 2.6 and encodes them with Avisynth+.

For "Force" it's the other way round. If I run "force" and then delete Avisynth.dll and devil.dll from the x264 folder, MeGUI still previews scripts using Avisynth+ but it encodes them with Avisynth 2.6.

EDIT: the avisynth.dll in an encoder folder cannot be influenced at all by MeGUI. So either it does work or not. During program start I can do a few changes for the detection and usage e.g. in AVS Creator, but not for the encoders. There the encoder has to call the proper dllbased on the search rules. Therefore it would be good to know e.g. when you run the x264.exe (without MeGUI) on a command line if the avisynth.dll in that folder will be used or not.

With the dlls in the x264 folder, I used the same command line as MeGUI via a command prompt and the script encoded successfully with Avisynth+.

"C:\MeGUI\tools\x264\x264.exe" --keyint 240 --sar 1:1 --frames 240 --output "D:\version.mkv" "D:\version.avs"

Full disclosure: Each time I started an encode via the command line I had to dismiss the following message before the encode would start, but it always ran successfully. I have seen the same message on a few occasions when starting MeGUI (I'm pretty sure it pops up as an MeGUI.exe message and not an x264 message), but it only happens occasionally. I've never seen the error when starting an encode with MeGUI or mention of it in the log file. The same error popped up when encoding via the command line with both Avisynth 2.6 and Avisynth+.

Cheers.

https://s15.postimg.cc/ugngeoxyz/x264_opencl.gif

PS After all that testing, the error message popped up just now when I restarted MeGUI. It looks like this:

https://s15.postimg.cc/z04adkfej/Me_GUI_opencl.gif

[Zathor]

So bottom line is that only MeGUI itself has the problem. It seems that when using first the system installed AviSynth it cannot switch back to portable one. The encoders are always fine. Is that summary correct?
I will change it in the way that if "always use portable" is ticked I will not do any checks with the system installed one (same as "forced" version).
There will be still the issue if "always use portable" is not ticked and the system installed one cannot be used (outdated).

EDIT: regarding the opencl.dll error - it seems your graphics driver does not support it.

[hello_hello]

So bottom line is that only MeGUI itself has the problem. It seems that when using first the system installed AviSynth it cannot switch back to portable one. The encoders are always fine. Is that summary correct?

That's correct.
I'd still be interested to know if anyone else running 32 bit Windows has the same problem, or if it's just me.

EDIT: regarding the opencl.dll error - it seems your graphics driver does not support it.

I guess it's unrelated then. I'm still using graphics drivers from 2013, because there were two driver updates that made a mess so I stopped updating them (I'm not a gamer so driver updates don't do much for me). I probably should look at updating the drivers now to see if it fixes that problem.

Thanks for your help.

[LouieChuckyMerry]

The fix in 2863 was intended for the issue LouieChuckyMerry had. He conformed that it was working when "show debug information" was enabled so I have enabled that now by default for that part. However I noticed that I changed it a bit and I do not know if it therefore still works as expected

I checked Version 2865. "Log debug information" needs to be ticked for the log to indicate AviSynth+ true, otherwise the log shows false.

[Groucho2004]

--[Information] MeGUI: 2860 x86
--[Information] Update Check: development update server
-[Information] Operating System: Windows 7 Premium x64 SP1 (6.1.65536.7601)
...
-[Information] File Version: 2.6.0.5
-[Information] File Date: 20-02-2015
-[Information] File Name: Avisynth 2.6
-[Information] File Path: c:\windows\system32\avisynth.dll

A 32 bit avisynth.dll must be in SysWoW64 on a 64 bit OS, not Sytem32. My guess is that it's in the right place but megui can't properly detect the SysWoW64 directory.

[LigH]

Because MeGUI x86 is a 32 bit process, a 64 bit Windows will have mapped SysWoW64 as fake "system32"; only a 64 bit process can actually see SysWoW64.

[Groucho2004]

only a 64 bit process can actually see SysWoW64.
:confused::confused::confused:

I spent quite a bit of time to determine the "real" SysWoW64 directory in my programs without getting Windows file redirection involved.

If you're interested, here is the code I use nowadays:
BOOL GetSysWoW64Directory(string &s_syswow64dir, string &s_errormsg)
{
s_syswow64dir = "";
s_errormsg = "";

HMODULE hKernel32 = GetModuleHandle("kernel32.dll");
if (hKernel32 == NULL)
{
s_errormsg = "Cannot obtain module handle to kernel32.dll";
return FALSE;
}

BOOL bIs64BitProcess = FALSE;
BOOL bIsWoW64Process = FALSE;

if (sizeof(void*) == 8) // Test 64 on 64
bIs64BitProcess = TRUE;
else // Test WOW64
{
BOOL bWoW64Process = FALSE;
typedef BOOL (WINAPI *LPFN_ISWOW64PROCESS) (HANDLE, PBOOL);
LPFN_ISWOW64PROCESS fnIsWow64Process = (LPFN_ISWOW64PROCESS)GetProcAddress(hKernel32, "IsWow64Process");
if (fnIsWow64Process != NULL)
fnIsWow64Process(GetCurrentProcess(), &bWoW64Process);
if (bWoW64Process)
bIsWoW64Process = TRUE;
}

if ((bIs64BitProcess) || (bIsWoW64Process))
{
char szSysWOW64Directory[MAX_PATH];
typedef UINT (WINAPI *LPFN_GETSYSTEMWOW64DIRECTORY)(LPTSTR, UINT);
LPFN_GETSYSTEMWOW64DIRECTORY getSystemWow64Directory = (LPFN_GETSYSTEMWOW64DIRECTORY)GetProcAddress(hKernel32, "GetSystemWow64DirectoryA");

if (getSystemWow64Directory(szSysWOW64Directory, sizeof(szSysWOW64Directory)) > 3)
s_syswow64dir.assign(szSysWOW64Directory);
}
else
{
s_errormsg = "Not running on 64 Bit OS";
return FALSE;
}

return TRUE;
}

[LigH]

And this code works when you compile it as 32 bit application? Interesting. But also quite complex, I doubt many "leisure time programmers" will know all the involved system functions. It may not even be necessary.

I mean ... in general, most applications only need access to the system DLL's in the directory matching their own bitness. If you have a 32 bit application, simply use "system32" and trust in Windows mapping it to SysWoW64 if it is a 64 bit Windows. The application may not even need to know that the mapping happened at all. It is not interested in DLL's of the opposite bitness, anyway.

For MeGUI specifically, the main reason to report the path is to tell apart "the system directory" from "the application directory". When MeGUI x86, as a 32 bit process, tries to copy from "the system directory", Windows will ensure that "the 32 bit system directory" will be accessed (no choice in a 32 bit Windows, and mapped SysWoW64 in a 64 bit Windows). The reported directory may be not "physically" correct from the scope of a 64 bit system, but virtually correct from the scope of a 32 bit application running in a "Windows on Windows64" subsystem. Scope matters.

[Groucho2004]

And this code works when you compile it as 32 bit application?Works in 32 and 64 bit programs on 32 and 64 bit OS.

The reported directory may be not "physically" correct from the scope of a 64 bit system, but virtually correct from the scope of a 32 bit application running in a "Windows on Windows64" subsystem. Scope matters.I like to know the real directory, not a "virtual" one.

The whole reason why I wrote this function is because the Win32 API file/folder redirection functions do not work consistently across Windows versions and I needed something reliable.

[LigH]

Alright. Zathor will know whether this is relevant and useful for MeGUI.

The access error reported by hello_hello appears to be somewhat dependent on the last used AviSynth installer. So I wonder if there is e.g. a file sharing mode issue due to the avisynth.dll being used by additional processes (and may it just be a Windows Explorer file type hook or similar) when the legacy AviSynth 2.6 installer was used... that seems to be a quite specific issue, not much related to just detecting the location of the system path in either scope.

[Zathor]

Thanks, Groucho2004, for the code. I know that the shown path is not correct because of redirection, however that is the path which is shown when I check for running modules and their path. To see if it is the same as when using the portable one this is sufficient and not worth additional efforts. I may change my mind in the future :)

[hello_hello]

Zather,
thanks for the hard work! All is good now.

-[Information] Versions
--[Information] MeGUI: 2867 x86
--[Information] Update Check: development update server
--[Information] System Information
---[Information] Operating System: Windows XP Professional x86 SP3 (5.1.196608.2600)
---[Information] .NET Framework: 4.0 (4.0.30319)
---[Information] Redistributables
----[Information] Microsoft Visual C++ 2010 x86: 10.0.40219
----[Information] Microsoft Visual C++ 2013 x86: 12.0.30501
----[Information] Microsoft Visual C++ 2017 x86: 14.13.26020
---[Information] DPI: 100% (96/96)
---[Information] Monitor 1
----[Information] Resolution: 1152x864
----[Information] Primary Screen: True
---[Information] Monitor 2
----[Information] Resolution: 1920x1080
----[Information] Primary Screen: False
--[Information] Component Information
---[Information] Haali Media Splitter: 1.11.96.14 (03-03-2011)
---[Information] Haali DSS2: (03-03-2011)
---[Information] ICSharpCode.SharpZipLib: 0.85.5.452 (07-08-2008)
---[Information] MediaInfo: 18.05.0.0 (08-05-2018)
---[Information] SevenZipSharp: 0.64.3890.29348 (02-01-2011)
---[Information] 7z: 9.20 (18-11-2010)
--[Information] AviSynth Information
---[Information] AviSynth Wrapper
----[Information] Version: 1.0.2847.0
----[Information] Date: 06-05-2018
----[Information] Interface: 3
---[Information] AviSynth
----[Information] AviSynth Status: ignored as portable build is forced
---[Information] AviSynth portable
----[Information] File Version: 0.1
----[Information] File Date: 28-03-2018
----[Information] File Name: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] File Path: c:\program files\megui\avisynth.dll
----[Information] AviSynth Version: AviSynth+ 0.1 (r2664, MT, i386)
----[Information] AviSynth+: true
----[Information] AviSynth MT: true
----[Information] AviSynth Status: active

[imsrk48]

Hey Dear MeGui's Developers
Please add option for burn subtitles on video in mkv file like handbrake

Sent from my P4 using Tapatalk

[LigH]

It already exists in the "AVS Script Creator" tool ("Filters" tab), because to "burn in" subtitles (make them video content), they have to be processed by an AviSynth plugin.

[Forteen88]

MeGUI 2836 says that x264 L4.1 is "--vbv-bufsize 78125 --vbv-maxrate 62500", while x264 says that L4.1 is "--vbv-bufsize 62500 --vbv-maxrate 50000". So which is the correct H264 L4.1?

Example when using MeGUI:
---[Warning] [02/10/2015 09:48:29] x264 [warning]: VBV bitrate (62500) > level limit (50000)
---[Warning] [02/10/2015 09:48:30] x264 [warning]: VBV buffer (78125) > level limit (62500)

EDIT: OK then I understand, I had MeGUI set on High Profile, not Main Profile. Thanks tebasuna51!

[tebasuna51]

From https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC

Level 4.1 max video coding layer kbit/s (Baseline, Extended and Main Profiles) = 50000
The maximum bit rate for High Profile is 1.25 times that of the Base/Extended/Main Profiles -> 62500

Change the 'AVC Profile' from 'High' to 'Main' in MeGUI x264 config dialog and you obtain:
--vbv-bufsize 62500 --vbv-maxrate 50000

You can let --vbv-bufsize 78125 --vbv-maxrate 62500 if you know than your player support Level 4.1 High Profile.

Or change to --vbv-bufsize 62500 --vbv-maxrate 50000
if you want make your encode more compatible with players.

You can low until: --level 4.0 --vbv-bufsize 25000 --vbv-maxrate 20000
for DivX Plus HD certified players (some TV's or standalone players)
It is your choice.

[DS2902]

After upgrading to 2867, it stopped running
https://i.imgur.com/1G4nYvU.png

[LigH]

That russian message part apparently means: "Entry point not found"...

[THEAST]

After upgrading to 2867, it stopped running
https://i.imgur.com/1G4nYvU.png

I have the same issue. I randomly got the same error even before the latest update when trying to create new AVS scripts using both MeGUI x86 and x64, but since the last update, the x64 version does not even open anymore. However, the x86 version seems to work fine using the latest update.

Edit: I just tried again, now the x64 version also works. I have not touched anything or even rebooted my machine since a few hours ago when it didn't work.

Edit 2: MeGUI x64 does not work again after rebooting my machine.

[DS2902]

Edit 2: MeGUI x64 does not work again after rebooting my machine.
I have it now does not depend on the reboot. It can start on the first try, or maybe with the twentieth.

[Zetti]

#Zathor

Is it possible you will add ffdcaenc to MeGUI??

https://forum.doom9.org/showthread.php?t=170952

[imsrk48]

It already exists in the "AVS Script Creator" tool ("Filters" tab), because to "burn in" subtitles (make them video content), they have to be processed by an AviSynth plugin.i know I'm talking about burn subtitles in mkv file

Sent from my P4 using Tapatalk

[LigH]

Why is the MKV container relevant here?

If you want to "burn" the subtitles into the video stream, then the container doesn't matter.

If you want to multiplex the subtitles into an MKV container, then they will not become part of the video stream.

Either or. Decide.
_

Or do you mean subtitles already multiplexed in your MKV source file, so you don't mean the target container?

To process them with MeGUI, you may have to extract them from the MKV. I don't know if any of the subtitle filters for AviSynth accept an MKV container as source, that would be surprising to me.

Rendering the source with DirectShow, only to have the subtitles rendered over the video, should not be your preference: DirectShowSource can be unreliable, there is a reason why MeGUI disabled it by default.

[tebasuna51]

Is it possible you will add ffdcaenc to MeGUI??

Is it possible but I don't know if it is useful.

I'm not sure if a DTS 1536 Kb/s make by ffdcaenc is better than an AC3 640 Kb/s make by ffmpeg, more compatible and 42% of size.

BTW you can use BeHappy (https://forum.doom9.org/showthread.php?t=104686) to use ffdcaenc with AviSynth support.

EDIT: seems there are also some incompatibility with hardware players
https://forum.doom9.org/showthread.php?p=1845723#post1845723

[imsrk48]

Why is the MKV container relevant here?

If you want to "burn" the subtitles into the video stream, then the container doesn't matter.

If you want to multiplex the subtitles into an MKV container, then they will not become part of the video stream.

Either or. Decide.
_

Or do you mean subtitles already multiplexed in your MKV source file, so you don't mean the target container?

To process them with MeGUI, you may have to extract them from the MKV. I don't know if any of the subtitle filters for AviSynth accept an MKV container as source, that would be surprising to me.

Rendering the source with DirectShow, only to have the subtitles rendered over the video, should not be your preference: DirectShowSource can be unreliable, there is a reason why MeGUI disabled it by default.I'm adding Custom sub file but it's only burn in mp4 not in mkv are you checked it.

i tried in handbrake.
handbrake can hardcode subs on mkv also but MeGui only hardcode subs on mp4

so if MeGui can hardcode subs in mkv container than please tell how.

[LigH]

I told you: if you mean "burning in" as "rendering into the video content", then use the "AVS Script Creator". When you see subtitles in the preview window of MeGUI, then the subtitles are part of the video stream, and then it doesn't matter anymore into which container you multiplex the video containing the subtitles as pixels.

But if you only use the multiplexer to add a subtitle stream without encoding a new video, then this does not mean "burning in". And if the subtitles appear in MP4 but not in MKV, we need many more technical details to know, e.g. an extended (not just a simple) MediaInfo analysis of both results. Then we need to compare both if a subtitle stream is contained at all, and whether it is flagged as "default" or "forced" (if not, you may have to enable the display of the subtitle stream in your video player).

[imsrk48]

I told you: if you mean "burning in" as "rendering into the video content", then use the "AVS Script Creator". When you see subtitles in the preview window of MeGUI, then the subtitles are part of the video stream, and then it doesn't matter anymore into which container you multiplex the video containing the subtitles as pixels.

But if you only use the multiplexer to add a subtitle stream without encoding a new video, then this does not mean "burning in". And if the subtitles appear in MP4 but not in MKV, we need many more technical details to know, e.g. an extended (not just a simple) MediaInfo analysis of both results. Then we need to compare both if a subtitle stream is contained at all, and whether it is flagged as "default" or "forced" (if not, you may have to enable the display of the subtitle stream in your video player).I'm also using AVS script creator but when I'm use mkv container than Subtitles is only added as softsub not hardcode.

Sent from my P4 using Tapatalk

[LigH]

I'll leave explaining this "feature" to Zathor or any other person who ever did that...

[imsrk48]

@Zathor sir when I'm Encoding .ts into mkv then audio was mismatched so please fix this problem & add subtitle hardcode also with mkv container.

Sent from my P4 using Tapatalk

[LigH]

Asynchronity between video and audio from TransportStream sources may be caused by cut GOPs. You should always pre-clean TS sources before converting them.

[kalehrl]

HD Stream Extractor fixes the asynchronity between video and audio from TransportStream sources.

[imsrk48]

Asynchronity between video and audio from TransportStream sources may be caused by cut GOPs. You should always pre-clean TS sources before converting them.Thanks LigH Sir

Sent from my P4 using Tapatalk

[imsrk48]

HD Stream Extractor fixes the asynchronity between video and audio from TransportStream sources.Thanks a lot

Sent from my P4 using Tapatalk

[Gser]

@Zathor sir when I'm Encoding .ts into mkv then audio was mismatched so please fix this problem & add subtitle hardcode also with mkv container.

Sent from my P4 using Tapatalk
Hardcoding subtitles and containers have nothing to do with each other. Avisynth script creator faithfully adds subtitles using textsub to an avisynth script.

[kuchikirukia]

I have a set of MKVs with a 6 channel DTS-MA track 1 and a 2 channel AAC as track 2. When attempting to encode using the front-panel audio encoder, it will randomly decide to encode the AAC track, giving "[Warning] [7/3/2018 9:37:27 PM] Channel count mismatch! The input file is reporting 6 channels and the AviSynth script is reporting 2 channels." The avisynth script says 6 channels detected in positions 3/2/0.1.

Would this be an LSMASH bug, since its default is to select the first detected audio track, but it looks like it may be switching between detection and serving?

[tebasuna51]

@kuchikirukia
Please add the log file.
Seems a MediaInfo-AviSynth conflict. And don't help this info:
...the AviSynth script is reporting 2 channels." The avisynth script says 6 channels detected in positions 3/2/0.1."

A workaround is extract the desired track with the tool HD Stream Extractor.

[leon]

@Zathor

Could you set "FFMSIndex" as the default indexer for WMV files?
I don't know if it's just me, but LSMASH always fails on WMVs.

[LigH]

If you read the last pages of the FFMS2 and L-SMASH Source threads, you will see it's not just you.

[leon]

Yeah, thanks.
FFMS2 is getting the job done right now for me, but it occasionally can't decode the very last frame.

[imsrk48]

How can i select multi tracks in avs script creator method for Encoding multi audio mkv

Sent from my P4 using Tapatalk

[imsrk48]

how to hardcode a .ass subtitle into mkv container using avs script creator any solution or this?

[kuchikirukia]

@kuchikirukia
Please add the log file.
Seems a MediaInfo-AviSynth conflict.

[Warning] Log for job392 (audio, 00003-002.mkv -> 00003-002.m4a)
-[Information] [7/4/2018 2:37:18 PM] Started handling job
-[Information] [7/4/2018 2:37:18 PM] Preprocessing
-[Warning] [7/4/2018 2:37:18 PM] MediaInfo
--[Information] [7/4/2018 2:37:18 PM] File: F:\Video\BDMV\STREAM\00003-002.mkv
--[Information] General
---[Information] Format: Matroska
---[Information] FormatString: Matroska
---[Information] FileSize: 6267504073
---[Information] PlayTime: 00:21:57.324
---[Information] Attachments: Benguiat_Bk_BT_Bold.ttf / Benguiat_Bk_BT_Bold_Italic.ttf / AGCrownStyle.ttf / Benguiat.ttf / Europe.ttf
--[Information] Video
---[Information] ID: 1
---[Information] StreamOrder: 0
---[Information] Width: 1920
---[Information] Height: 1080
---[Information] FrameCount: 31584
---[Information] FrameRate: 23.976
---[Information] FrameRateOriginal:
---[Information] FrameRateMode: CFR
---[Information] ScanType: Progressive
---[Information] Codec: V_MPEG4/ISO/AVC
---[Information] CodecString: AVC
---[Information] Bits Depth: 8
---[Information] Format: AVC
---[Information] AspectRatio: 1.778
---[Information] AspectRatioString: 16:9
---[Information] Delay: 0
---[Information] Title:
---[Information] Language:
---[Information] LanguageString:
---[Information] Default: Yes
---[Information] DefaultString: Yes
---[Information] Forced: No
---[Information] ForcedString: No
--[Information] Audio
---[Information] ID: 2
---[Information] StreamOrder: 1
---[Information] Format: DTS
---[Information] FormatProfile: MA / Core
---[Information] FormatSettingsSBR:
---[Information] FormatSettingsPS:
---[Information] Muxing Mode:
---[Information] SamplingRate: 48000
---[Information] SamplingRateString: 48.0 kHz
---[Information] Channels: 6
---[Information] ChannelsString: 6 channels
---[Information] ChannelPositionsString2: 3/2/0.1
---[Information] BitRateMode: VBR / CBR
---[Information] Delay: 1
---[Information] Title:
---[Information] Language: ja
---[Information] LanguageString: Japanese
---[Information] Default: Yes
---[Information] DefaultString: Yes
---[Information] Forced: No
---[Information] ForcedString: No
--[Information] Audio
---[Information] ID: 3
---[Information] StreamOrder: 2
---[Information] Format: AAC
---[Information] FormatProfile: LC
---[Information] FormatSettingsSBR: No (Explicit)
---[Information] FormatSettingsPS:
---[Information] Muxing Mode:
---[Information] SamplingRate: 48000
---[Information] SamplingRateString: 48.0 kHz
---[Information] Channels: 2
---[Information] ChannelsString: 2 channels
---[Information] ChannelPositionsString2: 2/0/0
---[Information] BitRateMode:
---[Information] Delay: 0
---[Information] Title: Track 1 English 2.0
---[Information] Language: en
---[Information] LanguageString: English
---[Information] Default: No
---[Information] DefaultString: No
---[Information] Forced: No
---[Information] ForcedString: No
--[Information] Text
---[Information] ID: 4
---[Information] StreamOrder: 3
---[Information] Codec: S_TEXT/ASS
---[Information] CodecString: ASS
---[Information] Delay:
---[Information] Title: Subtitle Track 2 English
---[Information] Language: en
---[Information] LanguageString: English
---[Information] Default: Yes
---[Information] DefaultString: Yes
---[Information] Forced: No
---[Information] ForcedString: No
--[Warning] Text
---[Information] ID: 5
---[Information] StreamOrder: 4
---[Information] Codec: S_TEXT/ASS
---[Information] CodecString: ASS
---[Information] Delay:
---[Information] Title: Subtitle Track 1 Signs And Songs
---[Information] Language: zxx
---[Information] LanguageString: zxx
---[Information] Default: No
---[Information] DefaultString: No
---[Information] Forced: No
---[Information] ForcedString: No
---[Warning] [7/4/2018 2:37:19 PM] The language information "zxx/zxx" is unknown. The default MeGUI language has been selected instead.
--[Information] Chapters
---[Information] 00:00:00.000: :Chapter 02 Part 1
---[Information] 00:09:16.556: :Chapter 03 Part 2
---[Information] 00:20:11.210: :Chapter 04 End Theme
---[Information] 00:21:26.285: :Chapter 05 Next Episode Preview
-[Information] [7/4/2018 2:37:19 PM] Trying to open the file with LWLibavAudioSource()
-[Information] [7/4/2018 2:38:01 PM] Successfully opened the file with LWLibavAudioSource()
-[Warning] [7/4/2018 2:38:02 PM] Channel count mismatch! The input file is reporting 6 channels and the AviSynth script is reporting 2 channels
-[Information] [7/4/2018 2:38:03 PM] AviSynth script
--[NoImage] ClearAutoloadDirs()
--[NoImage] AddAutoloadDir("C:\Program Files (x86)\MeGUI\tools\avs\plugins")
--[NoImage] LoadPlugin("C:\Program Files (x86)\MeGUI\tools\lsmash\LSMASHSource.dll")
--[NoImage] LWLibavAudioSource("F:\Video\BDMV\STREAM\00003-002.mkv")
--[NoImage] # detected channels: 6
--[NoImage] # detected channel positions: 3/2/0.1
--[NoImage] return last
-[Information] [7/4/2018 2:38:03 PM] Command line used: --ignorelength --threading -v 1280 --no-delay - -o "{0}"
-[Information] [7/4/2018 2:38:03 PM] AviSynth script environment opened
-[Information] [7/4/2018 2:38:04 PM] Script loaded
-[Information] [7/4/2018 2:38:04 PM] Output Decoder
--[Information] [7/4/2018 2:38:04 PM] Channels: 2
--[Information] [7/4/2018 2:38:04 PM] Bits per sample: 32
--[Information] [7/4/2018 2:38:04 PM] Sample rate: 48000
-[Information] [7/4/2018 2:38:04 PM] Job command line: C:\Program Files (x86)\MeGUI\tools\qaac\qaac.exe --ignorelength --threading -v 1280 --no-delay - -o "F:\Video\BDMV\STREAM\00003-002.m4a"
-[Information] [7/4/2018 2:38:04 PM] Process started
-[Information] [7/4/2018 2:38:04 PM] Standard output stream
-[Information] [7/4/2018 2:38:04 PM] Standard error stream
--[Information] [7/4/2018 2:38:04 PM] qaac 2.67, CoreAudioToolbox 7.10.9.0
--[Information] [7/4/2018 2:38:04 PM] 00003-002.m4a
--[Information] [7/4/2018 2:38:04 PM] AAC-LC Encoder, CVBR 320kbps, Quality 96
--[Information] [7/4/2018 2:38:28 PM] 63210496/-1 samples processed in 0:23.515
--[Information] [7/4/2018 2:38:28 PM] Overall bitrate: 329.164kbps
--[Information] [7/4/2018 2:38:28 PM] Optimizing...29%
--[Information] [7/4/2018 2:38:28 PM] Optimizing...56%
--[Information] [7/4/2018 2:38:28 PM] Optimizing...98%
--[Information] [7/4/2018 2:38:28 PM] Optimizing...done
-[Information] [7/4/2018 2:38:28 PM] MediaInfo
--[Information] [7/4/2018 2:38:28 PM] File: F:\Video\BDMV\STREAM\00003-002.m4a
--[Information] General
---[Information] Format: MPEG-4
---[Information] FormatString: MPEG-4
---[Information] FileSize: 54443454
---[Information] PlayTime: 00:21:56.885
--[Information] Audio
---[Information] ID: 1
---[Information] StreamOrder: 0
---[Information] Format: AAC
---[Information] FormatProfile: LC
---[Information] FormatSettingsSBR:
---[Information] FormatSettingsPS:
---[Information] Muxing Mode:
---[Information] SamplingRate: 48000
---[Information] SamplingRateString: 48.0 kHz
---[Information] Channels: 2
---[Information] ChannelsString: 2 channels
---[Information] ChannelPositionsString2: 2/0/0
---[Information] BitRateMode: VBR
---[Information] Delay:
---[Information] Title:
---[Information] Language:
---[Information] LanguageString:
---[Information] Default:
---[Information] DefaultString:
---[Information] Forced:
---[Information] ForcedString:
---[Information] [7/4/2018 2:38:28 PM] The language information is not available for this track. The default MeGUI language has been selected.
-[Information] [7/4/2018 2:38:28 PM] Postprocessing
--[Information] [7/4/2018 2:38:28 PM] Deleting intermediate files
---[Information] [7/4/2018 2:38:28 PM] Successfully deleted F:\Video\BDMV\STREAM\00003-002.mkv.lwi
-[Information] [7/4/2018 2:38:28 PM] Job completed



Encoding from an avisynth script with just the LWLibavAudioSource line comes back with no errors but it's still 2 channels, and shows detected 2 channels in the log's avisynth script instead of 6 like before.
Adding stream_index=1 encodes the DTS-MA track.

So it indicates a problem with LSMASH's default -1 for stream_index (pick the first audio track), no?

[LigH]

how to hardcode a .ass subtitle into mkv container using avs script creator any solution or this?

Again, and again, and again:

You "hardcode" subtitles into the contained video stream, using the AVS Script Creator. Not into a container. If you see the subtitles in the preview window of MeGUI, they will also be contained in your newly encoded video. Even if you first create a raw video stream without any container; it doesn't matter.

ASS is a text script just like SRT. And the AVS Script Creator provides several different text subtitle filters, some of them supporting ASS better than others. Test it using the preview window of MeGUI before encoding.

[tebasuna51]

@kuchikirukia
To avoid a mistake between tracks the 00003-002.m4a is english or japanese?

If it is japanese seems there are a confl¡ct between MediaInfo-AviSynth.

The BDMV\STREAM\00003-002.mkv is a mix of m2ts?
In BD's is possible have a m2ts intro 5.1 and after m2ts only 2.0.


maybe the DTS-MA is

[hello_hello]

How can i select multi tracks in avs script creator method for Encoding multi audio mkv

Use the File Indexer under the Tools menu to extract the audio (or create scripts if it can't be extracted) and they'll be loaded into the audio section.

[Gser]

Again, and again, and again:

You "hardcode" subtitles into the contained video stream, using the AVS Script Creator. Not into a container. If you see the subtitles in the preview window of MeGUI, they will also be contained in your newly encoded video. Even if you first create a raw video stream without any container; it doesn't matter.

ASS is a text script just like SRT. And the AVS Script Creator provides several different text subtitle filters, some of them supporting ASS better than others. Test it using the preview window of MeGUI before encoding.

I swear all of his posts have been like this. It's like he doesn't even bother finding out anything about video encoding himself, comes here to be given out everything on a silver platter and then throws the platter out the window.

[Zetti]

Is it possible but I don't know if it is useful.

I'm not sure if a DTS 1536 Kb/s make by ffdcaenc is better than an AC3 640 Kb/s make by ffmpeg, more compatible and 42% of size.

BTW you can use BeHappy (https://forum.doom9.org/showthread.php?t=104686) to use ffdcaenc with AviSynth support.

EDIT: seems there are also some incompatibility with hardware players
https://forum.doom9.org/showthread.php?p=1845723#post1845723
I will try it.