MeGUI: bug reports and feature requests [Archive] - Page 108

kuchikirukia

30th April 2017, 03:42

I have an encode in progress so I can't restart it, but after flipping it it isn't showing up in the log, and still getting 56MB/s.

-[Information] Log for job4 (idx, 8_track1_eng.mpg -> 8_track1_eng.d2v)
--[Information] [4/29/2017 10:37:18 PM] Started handling job
--[Information] [4/29/2017 10:37:18 PM] Preprocessing
--[Information] [4/29/2017 10:37:18 PM] Job command line: "C:\Program Files (x86)\MeGUI\tools\dgindex\dgindex.exe" -SD=< -AIF=<D:\Video\8_track1_eng.mpg< -OF=<D:\Video\8_track1_eng< -FO=0 -exit -hide -OM=0
--[Information] [4/29/2017 10:37:18 PM] Process started
--[Information] [4/29/2017 10:37:18 PM] Standard output stream
--[Information] [4/29/2017 10:37:18 PM] Standard error stream
--[Information] [4/29/2017 10:37:43 PM] Postprocessing
---[Information] [4/29/2017 10:37:43 PM] Deleting intermediate files
----[Information] [4/29/2017 10:37:43 PM] Successfully deleted D:\Video\8_track1_eng.log
--[Information] [4/29/2017 10:37:43 PM] Job completed

E: and on restart, still the same.

raymondjpg

30th April 2017, 07:17

The latest version 2722 of MeGUI is outputting MKV files with only limited metadata for the video stream when opened with MediaInfo. Demuxing the output from MeGUI with MKVExtract GUI2 and remuxing with MKVToolNix GUI restores full video stream information when opened with MediaInfo.

It is as if MeGUI has intervened somehow with an mkvmerge command line switch to limit metadata. Is this so, and if so is there somewhere in the options to restore full video stream information in MKV output? Or is this a bug with the latest version 2722 of MeGUI?

sneaker_ger

30th April 2017, 07:29

raymondjpg

30th April 2017, 08:01

Zathor

30th April 2017, 09:12

Are you using x265 and is MeGUI using mkvmerge 11.0.0? There is a bug in mkvmerge 11.0.0 "stable" that can corrupt HEVC headers. Replace mkvmerge 11.0.0 stable with the latest pre-build (https://mkvtoolnix.download/windows/pre/).

Thanks for the hint, I reverted to 10.0 for the moment.

I have an encode in progress so I can't restart it, but after flipping it it isn't showing up in the log, and still getting 56MB/s.
Could you please upload a full log? I need also the version chapter and the mediainfo.

hello_hello

30th April 2017, 09:30

MeGUI still seems to be using an outdated version of FluxSmooth (version 1.1a rather than 1.1b).
http://avisynth.nl/index.php/FluxSmooth

Zathor

30th April 2017, 14:02

MeGUI still seems to be using an outdated version of FluxSmooth (version 1.1a rather than 1.1b).
http://avisynth.nl/index.php/FluxSmooth
Thanks, updated - also TIVTC: https://github.com/pinterf/TIVTC/releases

kuchikirukia

30th April 2017, 19:58

[Information] Log
-[Information] Versions
--[Information] [4/30/2017 2:54:58 PM] MeGUI: 2715
--[Information] [4/30/2017 2:54:58 PM] Operating System: Windows 10 Home x64 (10.0.0.14393)
--[Information] [4/30/2017 2:54:58 PM] .NET Framework: 4.0 (4.0.0.0)
--[Information] [4/30/2017 2:54:58 PM] .NET Framework: 4.6.x (4.6.01586)
--[Information] [4/30/2017 2:54:58 PM] AviSynth: 2.6.0.5 (20-02-2015) (active)
--[Information] [4/30/2017 2:54:58 PM] AviSynth portable: 2.6.0.6 (30-04-2017) (inactive)
--[Information] [4/30/2017 2:54:58 PM] AvisynthWrapper: (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] Haali Media Splitter: 1.13.138.14 (14-04-2013)
--[Information] [4/30/2017 2:54:58 PM] Haali DSS2: (14-04-2013)
--[Information] [4/30/2017 2:54:58 PM] ICSharpCode.SharpZipLib: 0.85.5.452 (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] MediaInfo: 0.7.94.0 (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] MediaInfoWrapper: 0.7.61.0 (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] MessageBoxExLib: 1.0.2218.28317 (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] SevenZipSharp: 0.64.3890.29348 (30-04-2017)
--[Information] [4/30/2017 2:54:58 PM] 7z: 9.20 (30-04-2017)
-[Information] Update detection
--[Information] [4/30/2017 2:54:58 PM] Automatic update is disabled
--[Information] [4/30/2017 2:54:58 PM] Using cached update config and server: http://megui.org/auto/stable/
--[Information] [4/30/2017 2:54:58 PM] No package requires an update
-[Information] FileIndexer
--[Information] [4/30/2017 2:55:15 PM] MediaInfo
---[Information] [4/30/2017 2:55:15 PM] File: D:\Video\9_track1_eng.mpg
---[Information] General
----[Information] Format: MPEG Video
----[Information] FormatString: MPEG Video
----[Information] FileSize: 1701505334
----[Information] PlayTime:
---[Information] Video
----[Information] ID:
----[Information] StreamOrder:
----[Information] Width: 720
----[Information] Height: 480
----[Information] FrameCount:
----[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.333
----[Information] AspectRatioString: 4:3
----[Information] Delay:
----[Information] Title:
----[Information] Language:
----[Information] LanguageString:
----[Information] Default:
----[Information] DefaultString:
----[Information] Forced:
----[Information] ForcedString:
-[Information] Log for job15 (idx, 9_track1_eng.mpg -> 9_track1_eng.d2v)
--[Information] [4/30/2017 2:55:25 PM] Started handling job
--[Information] [4/30/2017 2:55:25 PM] Preprocessing
--[Information] [4/30/2017 2:55:25 PM] Job command line: "C:\Program Files (x86)\MeGUI\tools\dgindex\dgindex.exe" -SD=< -AIF=<D:\Video\9_track1_eng.mpg< -OF=<D:\Video\9_track1_eng< -FO=0 -exit -hide -OM=0
--[Information] [4/30/2017 2:55:25 PM] Process started
--[Information] [4/30/2017 2:55:25 PM] Standard output stream
--[Information] [4/30/2017 2:55:25 PM] Standard error stream
--[Information] [4/30/2017 2:55:53 PM] Postprocessing
---[Information] [4/30/2017 2:55:53 PM] Deleting intermediate files
----[Information] [4/30/2017 2:55:53 PM] Successfully deleted D:\Video\9_track1_eng.log
--[Information] [4/30/2017 2:55:53 PM] Job completed

kuchikirukia

30th April 2017, 21:08

I figured it out. MeGUI sets DGIndex to run in low priority. Even without CPU and disk in use it still slows waaaaaaaaaaaaaaay down compared to Normal.
This doesn't affect LSMASH or ffindex.

-When I set DGindex GUI to Low priority through Task Manager, the Base Priority and Dynamic Priority change, but I/O stays at normal and it indexes at full speed.
-When MeGUI is doing the indexing, DGIndex.exe's I/O priority is Low by default.
It does appear to be the I/O priority killing it since reading from RAM MeGUI indexes at 30% CPU util on Low. (same percentage as Normal priority).

Oh, and why is MeGUI pinging 127.0.0.1 when it indexes with LSMASH?

sumirecccp

1st May 2017, 04:09

>>Zathor, yes, i'm using one click encoder, to encode (or batch encode) some 16:9 VOBS. I want use avisynth profile to cut the blackborder, and output 640x480 mp4.

and when I drag the file to one-click encoder, the "display aspect autio" will auto become 16:9(when the "keep input resolution" is in gray), and it will output an 640x480,16:9 mp4.

my avisynth is like this:

<input>
<deinterlace>
LoadPlugin("E:\D\software\megui\tools\avisynth_plugin\TIVTC.dll")
#tfm(order=-1).tdecimate(mode=1,hybrid=1)
tfm(order=-1).tdecimate(hybrid=1)
<crop>
autocrop(mode=0,threshold=50,samples=10)
<resize>
lanczos4resize(640,480)
<denoise>

hello_hello

1st May 2017, 12:09

sumirecccp,
Seems like MeGUI is trying to save you from yourself. You can't just resize a 16:9 picture to 4:3 dimensions without squishing it. You need to crop a fair bit of picture from each side so what's left is 4:3, or resize it to 4:3 dimensions and set a 16:9 aspect ratio (as it seems MeGUI is doing).

Assuming it's a 16:9 NTSC DVD and there's no top and bottom cropping required, to get to 4:3 you need to do this, rather than just resize:
Crop(90,0,-90,0)
lanczos4resize(640,480)

Or if you're using autocrop.dll rather than MeGUI's auto-cropping, set the appropriate aspect ratio so it crops to 4:3. You'd need to do it like this (I'm pretty sure) to compensate for the fact the DVD doesn't have square pixels, then resize it to 4:3 dimensions:

autocrop(mode=0,threshold=50,samples=10,aspect=1.125)
lanczos4resize(640,480)

OneClick may still change the display aspect ratio (I'm not sure how OneClick works as I don't use it), but try it without OneClick first to see what happens.

Or (shameless plug) try this script (https://forum.videohelp.com/threads/382888-CropResizeBorder-script). It uses autocrop.dll to do the cropping, but hopefully it'll crop and resize with less aspect error than using autocrop.dll on it's own, as above.

tebasuna51

1st May 2017, 12:48

BUG:auto-detect display aspect ratio will still take effect even choosing the "keep input resolution" option, and "display aspect ratio" is in gray.

I use one 720x480 DVD VOB source, and use avisynth profile to crop the borders, and resize to 640x480, (keep input resolution is in check and display aspect ratio is in gray),but it will still produce a wrong ratio, 16:9.

when check off the "keep input resolution" ,and modify the display aspect ratio to 4:3, then check on "keep input resolution", it will be correct 4:3.
>>Zathor, yes, i'm using one click encoder, to encode (or batch encode) some 16:9 VOBS. I want use avisynth profile to cut the blackborder, and output 640x480 mp4.

and when I drag the file to one-click encoder, the "display aspect autio" will auto become 16:9(when the "keep input resolution" is in gray), and it will output an 640x480,16:9 mp4.

my avisynth is like this:

I'm not a 'One Click Encoder' mode user, but I have some questions (maybe a full log of the encode can clarify the problem)

- If your input is "16:9 VOBS", your output must be 16:9 even if your output is 640x480 pixels (here help the full log to see what hapens). A 640x480,16:9 mp4 can be correct.

- Seems there are some problem with "keep input resolution" and your AviSynth profile "640x480 auto 50 td" (the template than you show?). Both are incompatible.

BTW my recomendation for recode DVD input with x264 or x265 is use 'Autocrop' and 'Anamoph output' without Resize.

sumirecccp

1st May 2017, 14:56

hello_hello, tebasuna51, I tried your solutions but none works, it still output 640x480,16:9 mp4. the "display aspect autio" will still effect even when it's gray.

but I'm very sure build 2624 will output 640x480,4:3 mp4.

you may download 2624 at https://sourceforge.net/projects/megui/files/megui-stable/

and I uploaded the example vob here:
https://mega.nz/#!5sgDQIyQ!w9x-gq8IM3c9PpPilAXGv093P42A5psdw_EPM7X1hZ4

Zathor

1st May 2017, 22:13

I figured it out. MeGUI sets DGIndex to run in low priority. Even without CPU and disk in use it still slows waaaaaaaaaaaaaaay down compared to Normal.
This doesn't affect LSMASH or ffindex.

When "idle" priority is selected it will also set I/O priority to idle so this is correct.

Oh, and why is MeGUI pinging 127.0.0.1 when it indexes with LSMASH?
I had to cheat a bit and needed a running process for the job progress while the index is performed in a MeGUI thread without process.

>>Zathor, yes, i'm using one click encoder, to encode (or batch encode) some 16:9 VOBS. I want use avisynth profile to cut the blackborder, and output 640x480 mp4.

and when I drag the file to one-click encoder, the "display aspect autio" will auto become 16:9(when the "keep input resolution" is in gray), and it will output an 640x480,16:9 mp4.

my avisynth is like this:

<input>
<deinterlace>
LoadPlugin("E:\D\software\megui\tools\avisynth_plugin\TIVTC.dll")
#tfm(order=-1).tdecimate(mode=1,hybrid=1)
tfm(order=-1).tdecimate(hybrid=1)
<crop>
autocrop(mode=0,threshold=50,samples=10)
<resize>
lanczos4resize(640,480)
<denoise>

I still do not get what you try to do and may miss some information. Is it possible that you upload beside the sample the log file and also all your profiles (select "file\export presets" in MeGUI)? Also MeGUI may have problems as you select that no cropping should be performed and you do have an autocrop in your script. Therefore all AR calculations may be off. Why do you not use the MeGUI crop function?

sumirecccp

2nd May 2017, 06:30

>>Zathor, I'm not very sure why you can't understand my meaning.

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

and your request logs & profiles here:
https://mega.nz/#!Iw4FVLpA!1kF1Xit5K5-JJSg9qYXk3gXbL4tOwO6LEkN7uhgcrLs https://mega.nz/#!dsoW3LIZ!6jBRnIydO4dvD8JdrFYn2RrQgg0_6gLMrM7TwJbvq8c

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

hello_hello

2nd May 2017, 20:00

Zathor,

If you'd care to play follow the links and update YadifMod2, apparently there's a newer version than the one MeGUI is using, although unfortunately if you check the newer dll's properties it shows it's version 0.0.2, when apparently it's actually version 0.2. MeGUI is currently using version 0.0.4, I believe.

The newer version was built by real.finder from the source at github and can be found here:
https://forum.doom9.org/showpost.php?p=1798117&postcount=36
Here's real.finder explaining the story:
https://forum.doom9.org/showthread.php?p=1805827#post1805827
https://forum.doom9.org/showthread.php?p=1805931#post1805931
And here's the updated changelog/readme:
https://github.com/chikuzen/yadifmod2/blob/7156fbe5b5327ee61d7d8abb419f277bc1a4edf4/avisynth/readme.md#changelog

Cheers.

LigH

3rd May 2017, 09:15

Is it possible to change the order of preference of source filters in the File Indexer (e.g. always FFMS2 over L-SMASH Source)?

Also asked in the VideoHelp forum (https://forum.videohelp.com/threads/383449-FFVideoSource-vs-LWLibavVideoSource) by someone else...

hello_hello

3rd May 2017, 10:45

LigH,
What type of files are you indexing? Multiple types, or something in particular? For me, when opening MKV sources at least, the indexer defaults to L-Smash.

Edit, sorry I misread your post. I thought you were saying it's currently defaulting to ffms2, not that you want it to.

I'd like MeGUI to remember the last indexer I selected for a particular file type (rather than set a default) so if I used ffms2 to index an MKV last, it'd default to ffms2 for the next MKV I index etc. Same for the option to demux audio. I'd reeeeeaaaaaallllly love it if MeGUI remembered the last choice there.

hello_hello

3rd May 2017, 11:03

Zathor,

One day when you're bored, could a little change be made to the OneClick encoder configuration?

When you open an audio/video encoder configuration, the list of encoder presets is down the bottom, so if you have "show advanced settings enabled" (x264 configuration) you can switch tabs and the selected preset stays at the bottom of the configuration window. That way you can select a preset no matter which tab is selected, and the settings naturally change accordingly.

For some reason the OneClick profile list is glued to the first tab. I know there's only a couple of tabs in the OneClick encoder configuration, but still, it'd make life easier if it was tab independent too. Long post short.... could the "show advanced settings" drop down list swap places with the OneClick Profile drop down list?

Cheers.

PS when you edit an encoder preset and just wish it to be saved to scratchpad, is it really necessary for MeGUI to ask twice if you want to update the preset or save the changes to scrachpad. The old system of simply clicking yes to update the preset, or no to have the changes saved to scratchpad, was better IMHO. Less annoying, at least....

kalehrl

3rd May 2017, 11:19

Previously, I was able to copy the contents of an avisynth script created by MeGUI in AvsPmod to preview the script and make further adjustments.
Now, when I click the preview button, it complains no matter what source filter I choose:

http://i65.tinypic.com/qn41ok.jpg

Groucho2004

3rd May 2017, 11:35

hello_hello

3rd May 2017, 12:15

If Lsmash is working fine for MeGUI maybe try coping msvcr120.dll (or whichever version it is) from the MeGUI\tools\lsmash folder into the AvsPmod folder, or if you haven't, try rebooting. I occasionally have a bunch of encodes running in the queue, and suddenly all new jobs fail with an error because a plugin won't load. It usually happens the other way around for me.... a script won't open with MeGUI but it will with another program, however a reboot fixes it. Or try re-installing the correct flavour of the Microsoft Visual C++ Redistributable.

http://avisynth.nl/index.php/LSMASHSource

Or try opening the script another way. MPC-HC or VirtualDub etc.
What happens if you open the existing script with AvsPmod, rather than copying the contents to create a new one?

MeGUI recently switched to Avisynth+ (development update server). Which version do you have installed and what's the whole script? I shouldn't matter, but maybe there's something going on there if MeGUI is using it's own portable Avisynth, which obviously AvsPmod won't be.

Groucho2004

3rd May 2017, 12:57

hello_hello

3rd May 2017, 13:21

So if he's running 32 bit MeGUI and Lsmash is working when he loads a script in MeGUI, what's the cause?

Groucho2004

3rd May 2017, 13:27

So if he's running 32 bit MeGUI and Lsmash is working when he loads a script in MeGUI, what's the cause?He creates the script in megui and tries to load/preview it in Avspmod. At least that's how I interpret his post. I don't know what megui does with plugin paths so Avspmod might load plugins from a different directory.

LigH

3rd May 2017, 13:29

When running the script inside MeGUI, MeGUI will possibly use its own AviSynth environment with own plugins.

AvsPmod runs outside MeGUI and will use a system-wide AviSynth installation with default plugin locations. So it's quite probable that one has to make all plugins working in MeGUI also work outside of it.

Groucho2004

3rd May 2017, 13:30

hello_hello

3rd May 2017, 13:33

Yeah but I'd assume he has 32 bit Avisynth installed, and he's using 32 bit MeGUI, so everything should be 32 bit, but maybe that's not the case and he switched to 64 bit MeGUI (although he didn't mention it). I guess we'll have to wait and see. I thought x64 MeGUI was still kind of experimental, but maybe more people are using it now.

hello_hello

3rd May 2017, 14:39

My turn for some MeGUI torture. :)

The folder containing ffms2.dll at the top, MPC-HC happily opening the script in question (which MeGUI created) at the bottom, and MeGUI having a hissy in the middle. MeGUI and MPC-HC both using the "installed" Avisynth. Anyone know what error=0x8 means?

Fortunately no reboot required this time. Just shutting down and restarting MeGUI. Computers.....

https://s11.postimg.org/6v54g36bn/megui_unable.gif

Groucho2004

3rd May 2017, 15:15

tebasuna51

3rd May 2017, 15:16

... tebasuna51, I tried your solutions but none works, it still output 640x480,16:9 mp4.

My solution implies don't Resize, if your output is 640x480 is not my solution.

I encode this sample with:
- Auto detected display aspect ratio -> Input DAR: ITU 16:9 NTSC (1.823169)
- Clever anamorphic...: Encode non-mod16
- Autocrop (without resize)

-[Information] Log for job25 (video, VTS_01_PGC_02_1.avs -> VTS_01_PGC_02_1.264)
...
--[Information] [03/05/2017 14:14:59] Avisynth input script
---[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] [03/05/2017 14:15:00] resolution: 532x472
--[Information] [03/05/2017 14:15:00] aspect ratio: 137:100 (1.370)
--[Information] [03/05/2017 14:15:00] Job command line: ... --sar 8083:6650 ...
And I obtain a output DAR 646x472

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)
-[Information] Log for job27 (video, VTS_01_PGC_02_1.avs -> VTS_01_PGC_02_1.264)
...
--[Information] [03/05/2017 14:29:23] Avisynth input script
---[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] [03/05/2017 14:29:24] resolution: 532x472
--[Information] [03/05/2017 14:29:24] aspect ratio (avs): 131:98 (1.337)
--[Information] [03/05/2017 14:29:24] aspect ratio (job): 137:100 (1.370)
--[Information] [03/05/2017 14:29:24] Job command line: ... --sar 8083:6650 ...
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

kalehrl

3rd May 2017, 18:45

He creates the script in megui and tries to load/preview it in Avspmod. At least that's how I interpret his post. I don't know what megui does with plugin paths so Avspmod might load plugins from a different directory.
That's what I've been trying to do.
One thing you could try:
Run AVSMeter with the switch "-avsinfo". See if that throws any errors.
This is the output:
PS C:\Users\kaleh\Desktop\AVSMeter254> .\avsmeter -avsinfo

AVSMeter 2.5.4 (x86) - Copyright (c) 2012-2017, Groucho2004

VersionString: AviSynth 2.60, build:Mar 31 2015 [16:38:54]
VersionNumber: 2.60
File version: 2.6.0.6
Interface Version: 6
Multi-threading support: No
Avisynth.dll location: C:\WINDOWS\SysWOW64\avisynth.dll
Avisynth.dll time stamp: 2015-03-31, 06:40:58 (UTC)
PluginDir2_5 (HKLM, x86): C:\Program Files (x86)\AviSynth\plugins

[CPP 2.5 / 32 Bit plugins]
C:\Program Files (x86)\AviSynth\plugins\FFT3dGPU.dll [0.8.2.0]
C:\Program Files (x86)\AviSynth\plugins\mvtools2.dll [2.6.0.5]

[CPP 2.6 / 32 Bit plugins]
C:\Program Files (x86)\AviSynth\plugins\DirectShowSource.dll [2.6.0.3]
C:\Program Files (x86)\AviSynth\plugins\KNLMeansCL.dll
C:\Program Files (x86)\AviSynth\plugins\masktools2.dll [2.1.0.0]
C:\Program Files (x86)\AviSynth\plugins\nnedi3.dll [0.9.4.20]
C:\Program Files (x86)\AviSynth\plugins\RgTools.dll
C:\Program Files (x86)\AviSynth\plugins\TCPDeliver.dll [2.6.0.7]
PS C:\Users\kaleh\Desktop\AVSMeter254>
If Lsmash is working fine for MeGUI maybe try coping msvcr120.dll (or whichever version it is) from the MeGUI\tools\lsmash folder into the AvsPmod folder, or if you haven't, try rebooting. I occasionally have a bunch of encodes running in the queue, and suddenly all new jobs fail with an error because a plugin won't load. It usually happens the other way around for me.... a script won't open with MeGUI but it will with another program, however a reboot fixes it. Or try re-installing the correct flavour of the Microsoft Visual C++ Redistributable.

http://avisynth.nl/index.php/LSMASHSource

Or try opening the script another way. MPC-HC or VirtualDub etc.
What happens if you open the existing script with AvsPmod, rather than copying the contents to create a new one?

MeGUI recently switched to Avisynth+ (development update server). Which version do you have installed and what's the whole script? I shouldn't matter, but maybe there's something going on there if MeGUI is using it's own portable Avisynth, which obviously AvsPmod won't be.
None of this worked - copying the files into avspmod, rebooting. MPC HC throws the same error. I believe I have the 32bit version of MeGUI.

Taurus

3rd May 2017, 19:40

Did you shorten the avsinfo log?
LSMASHSource.dll is missing in the "normal" plugin dir...
If MeGui is looking in it's own plugin folder, make sure all required plugins are available.
Or make a "repair" update within Megui's updater.
Right click in options/update on LSMASHSource. Choose "force reinstall", press update...
Is there a mark in Extra Configuration / "always use the inluded avisynth"?
I dont use the build-in avisynth routines,
so please let us know what's your gameplay :D

kalehrl

3rd May 2017, 19:50

LSMASHSource.dll is missing from the plugins dir but in the script it is loaded from the megui folder.
I tried the "repair" option but it didn't fix the problem.
"always use the inluded avisynth" isn't marked.
Megui is using the system avisynth according to its log:
--[Information] AviSynth Wrapper
---[Information] [3.5.2017. 20.47.09] Version: 1.0.2721.0
---[Information] [3.5.2017. 20.47.09] Date: 29-04-2017
---[Information] [3.5.2017. 20.47.09] Interface: 3
--[Information] AviSynth
---[Information] [3.5.2017. 20.47.09] File Version: 2.6.1.0
---[Information] [3.5.2017. 20.47.09] Date: 17-05-2016
---[Information] [3.5.2017. 20.47.09] Name: Avisynth 2.6
---[Information] [3.5.2017. 20.47.09] Version: AviSynth 2.61, build:May 17 2016 [16:06:18] VC2008Exp
---[Information] [3.5.2017. 20.47.09] AviSynth+: false
---[Information] [3.5.2017. 20.47.09] MT: false
---[Information] [3.5.2017. 20.47.09] Status: active
--[Information] AviSynth portable
---[Information] [3.5.2017. 20.47.09] File Version: 0.1
---[Information] [3.5.2017. 20.47.09] Date: 16-03-2017
---[Information] [3.5.2017. 20.47.09] Name: AviSynth+ 0.1 (r2455, MT, i386)
---[Information] [3.5.2017. 20.47.09] Status: inactive
In the meantime I downloaded the latest avisynth alpha and installed it.

Groucho2004

3rd May 2017, 21:40

@kalehrl
Are you by any chance using the 64 bit version of Avspmod? That would provoke the same error message.

LouieChuckyMerry

4th May 2017, 02:25

PS when you edit an encoder preset and just wish it to be saved to scratchpad, is it really necessary for MeGUI to ask twice if you want to update the preset or save the changes to scrachpad. The old system of simply clicking yes to update the preset, or no to have the changes saved to scratchpad, was better IMHO. Less annoying, at least....

+1. That's been in the back of my head for a couple-three months now, thanks for the prod ;) .

hello_hello

4th May 2017, 10:47

kalehrl,
Have you tried copying the lsmash dll to the installed Avisynth plugin folder? As long as it's the same version MeGUI uses, duplicating plugins like that shouldn't do any harm (I have quite a few of MeGUI's plugins copied to the "installed" Avisynth plugin folder).

Theoretically it should still produce the same error, but with LSmash in the auto-loading plugins directory, you can delete the LSmash loadplugin line from the script so it's not still being loaded from the MeGUI plugins folder and if it auto-loads okay, problem solved, well..... problem worked around, maybe..... it'd still be nice to know why it's happening. You could do the same with any other plugins that've stopped working with Avspmod, if there's others.

hello_hello

4th May 2017, 11:17

Same advice as above (post #5457).

Also: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

Interesting. According to that, I must have run out of memory.

Which I kind of have been. Normally while MeGUI is running an encode I can create and preview another script, but lately with any CPU intensive filtering in the script (QTGMC, RMLogo etc) if I try to play/preview the script it only gets through a few frames and then MeGUI has a hissy, complaining about being out of memory. Then it disables the "improve AVS opening" option for the current session, which I'm fairly certain never achieves anything when there's a problem, so I have to go into options and enable it again. I must have done that 20 times in the last few days. Automatically disabling the "improve AVS opening" option every time there's a light shower within a hundred miles is sooooooooo annoying. At least for me.

Anyhow, I wasn't doing anything I don't normally do. When the error started there weren't any encodes running at all. Given simply restarting MeGUI fixed the problem I assume MeGUI must be holding onto memory unnecessarily, or something to that effect. If it was a plugin using lots of memory, shouldn't it be freed when the encoding finishes? I'll have to start keeping an eye on memory usage to see what's happening.

Maybe I need to have a cleanup. It's been at least four years since I installed XP and created an image, and I've not been to Windows Update since, or defragged any of the drives, or done any sort of maintenance, and this PC runs 24/7. It might be time for a reset. VirtualDubMod seems to think so. It started complaining a week ago when I open it, then it works normally anyway. OpenCL.dll is in the same place it's always been. Computers.....

https://s27.postimg.org/d86two7pv/VDM.gif

Groucho2004

4th May 2017, 11:45

Do you need two versions of masktools2? It appears you have two versions from the info you posted.Where are you seeing that?

hello_hello

4th May 2017, 12:21

Where are you seeing that?

Whoops. My Bad. He has MVTools2 and MaskTools2. I misread it.

hello_hello

4th May 2017, 12:53

Here's a quote from a post in the VideoHelp forum yesterday. Seems it's the same problem kalehrl is having.
If midts quoted the error message correctly it's a different one this time. https://forum.videohelp.com/threads/383449-FFVideoSource-vs-LWLibavVideoSource#post2484868

I tried with both 32/64 versions of VirtualDub 1.10.4 and I get avisynth open failure: loadplugin: unable to load ffms2.dll (or lsmashsource.dll) error=0xc1 with x32 and same errors with x64 build.

Odd..... could a Windows Update have broken something?

kalehrl, I can't remember.... which flavour of Windows are you using? I'm just wondering if maybe that's something you have in common. midts is using Win10 x64.

Groucho2004

4th May 2017, 13:05

Computers.....Don't blame computers, in 95% of the cases it's PEBCAC. :D

LigH

4th May 2017, 13:22

Microsoft Windows - System Error Codes (https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx)

ERROR_BAD_EXE_FORMAT
193 (0xC1)

%1 is not a valid Win32 application

Possibly because it's a Win64 DLL.

So it's quite probable that each version of the script loads each wrong DLL version.

I hope that AVSMeter64.exe -avsinfo -l and AVSMeter64.exe script.avs tells us more.

hello_hello

4th May 2017, 13:22

Don't blame computers, in 95% of the cases it's PEBCAC. :D

I don't know.... I'm pretty sure computers are quite vindictive. Or maybe it's built into Windows. My latest example...

My USB3 hard drive, which has disconnected and reconnected intermittently since the day I put a USB3 card in this PC (USB2 is fine) is now working reliably and no longer disconnecting. That's either because I replaced the mouse, or it's one of those bizarre coincidences computers enjoy inflicting on users to mess with their heads and send them down the wrong problem solving path. Who'd have guessed? The mouse was working fine until a couple of weeks ago.
https://forum.videohelp.com/threads/383456-USB3-drive-not-disconnecting-any-more

hello_hello

4th May 2017, 13:43

Microsoft Windows - System Error Codes (https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx)

Possibly because it's a Win64 DLL.

kalehrl says he's 32 bit everywhere (Avisynth, MeGUI etc), unless there's a 64 bit Avspmod?

I'm sure I've seen that error message before, when there's been a missing dependency, or MeGUI is having a hissy. I know that's not what it means, but I'm still sure I've seen it.

I was under the impression Avisynth plays some type of error message lotto, and due to the law of averages it'll be the correct error message a certain percentage of the time. :)

Does Avisynth "standard" have identical error messages to Avisynth+? Are they the same error message for every flavour of Windows?
I ask, because when I deliberately replaced ffms2 with a 64 bit version and loaded it in a script (XP, AVISynth standard), this is the error message I was offered (when I didn't specifically load ffms2 in the script because it was in the plugins folder, the error message was "there's no such function as.....")

https://s28.postimg.org/f2y6uc46l/error.gif

kalehrl

4th May 2017, 14:41

@kalehrl
Are you by any chance using the 64 bit version of Avspmod? That would provoke the same error message.
The about says Windows X86-64 so it should be 32bit. There is no 64bit version to download.
kalehrl,
Have you tried copying the lsmash dll to the installed Avisynth plugin folder? As long as it's the same version MeGUI uses, duplicating plugins like that shouldn't do any harm (I have quite a few of MeGUI's plugins copied to the "installed" Avisynth plugin folder).

Theoretically it should still produce the same error, but with LSmash in the auto-loading plugins directory, you can delete the LSmash loadplugin line from the script so it's not still being loaded from the MeGUI plugins folder and if it auto-loads okay, problem solved, well..... problem worked around, maybe..... it'd still be nice to know why it's happening. You could do the same with any other plugins that've stopped working with Avspmod, if there's others.
I copied it but it throws the same error. I tried erasing the complete line and also using the path to it in avisynth folder but the error is the same.
Here's a quote from a post in the VideoHelp forum yesterday. Seems it's the same problem kalehrl is having.
If midts quoted the error message correctly it's a different one this time. https://forum.videohelp.com/threads/383449-FFVideoSource-vs-LWLibavVideoSource#post2484868

Odd..... could a Windows Update have broken something?

kalehrl, I can't remember.... which flavour of Windows are you using? I'm just wondering if maybe that's something you have in common. midts is using Win10 x64.
I'm using Windows 10 Pro 64bit updated recently to Redstone 2.