VD2 crash 'mlcy' codec related - how to debug/fix

[stormy1777]

I'm by far not a "power user", just doing basic muxing of MOV/MP4 + MP3 audio.

Just now, launched a new VD2/43073 opened video + added mp3, cut start/end, adjusted frame rate and audio sync, then pressed F7/save, I think at that point, got a "crash" notice, so saved the file (attached), it says something about:

Crash reason: Unhandled Microsoft C++ Exception

Crash context:
An exception occurred in module 'KERNELBASE'...

...while opening video codec with FOURCC "mlcy" (compchoose.cpp:527)...

...while enumerating video codecs (compchoose.cpp:514).


Using gspot, got a list of known/installed codecs, and MLCY is not in that list (see screenshot)...

I don't recall ever installing it specifically, but maybe the MeGUI update pulled it, in any event, found the installer here:

http://www.linek.sk/mlc/

and it does offer un/install option...

Is that really the "solution", or maybe it is something more related to VD2?

It only happened once thus far, but i've had other crashes which i just dismissed over the past few weeks, going forward I'll save these and try to figure the root cause...

any thoughts welcomed, otherwise i've relaunched and all is working fine.

Too bad I'm not using Projects b/c then edits would not be lost in a crash event.. maybe that is an enhancement, that VD2 will SAVE the current project (despite the crash? is that possible??).

Stormy.

[clsid]

You can remove it by deleting the "vidc.mlcy" value from this Registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

[shekh]

It is good idea to uninstall all codecs you don't know / care about.
There is project autosave before "running operation". Codec selection dialog is not specifically guarded. If you do some lengthy edits, try to get used for ctrl+s thing.
Saving something after the crash is not that bad idea but there is chance to hit secondary crash because the entire process state is "damaged".

[stormy1777]

Thanks clsid sounds like you're speaking directly out of the Registry, hope it's nice and warm there - thanks for that key location! removed it; waiting for the next crash :) :)

My "project" tend to be (very) short-lived, so never gotten into saving/project files I'll try to change that habit :) When I did AVI it was very simple/fast, a bit of a "learning curve" with MP4 so taking a bit longer than normal..

Best-effort-auto-save (esp. if project is not already saved) after crash will definitely be a big time-saver in some cases :)

Stormy

[StainlessS]

Its a good habit to hit CTRL/S in nearly every app, I do it usually without thinking, probably about every four or five minutes,
in C++ compiler, Text Editor, Word processor, basically everything.

Its also a pretty good habit to hit CTRL/A (select all) and then CTRL/C (copy to ClipBoard), every now and then when preparing post for forum, just in case,
I still do get clobbered every now and then, things sometimes go wrong and for some reason I dont always remember to copy to clipboard when
creating a post (CTRL/S is for me automatic, but CTRL/A + CTRL/C is not automatic).

EDIT: In VDub2 Avisynth script editor(Tools Menu), F5 is Save and reload Script (stay at current frame), whereas F7 is save and reload new (to frame 0).
Also, in VD2 Script editor, CTRL/S also works, and I also do that automatically every few minutes.

[stormy1777]

EDIT: In VDub2 Avisynth script editor(Tools Menu), F5 is Save and reload Script (stay at current frame), whereas F7 is save and reload new (to frame 0).


Wonderful, never used that editor before, pls note the F7 works only for "AVI" scripts, if u have a MOV/MKV/MP4 you get:

---------------------------
File open error
---------------------------
AVI Import Filter error: (Unknown) (80040154)
---------------------------
OK
---------------------------

which is expected I suppose :) that's probably from the days that VD was AVI only/mostly :)

[shekh]

This makes no sense. Avisynth is "fake AVI" from the point of view of VD, no matter what files it operates on (it is avisynth business to deal with MOV/MKV).
If you have this error it means avisynth is not installed or has some unresolved dependencies and cant load.

[hello_hello]

I don't recall ever installing it specifically, but maybe the MeGUI update pulled it, in any event, found the installer here:

MeGUI is totally portable. It doesn't install any "system" codecs.
The one exception is the Haali Media Splitter (https://haali.su/mkv/), but that's not a codec as such and it's possibly not installed by default. I think it's only required by MeGUI's for some DirectShow decoding, but I can't remember exactly, and I installed the splitter myself anyway.

Programs don't always display the AVisynth error message. MeGUI sometimes just tells you it can't open a script. To see the error I open the script with MPC-HC or AvsPmod, both of which would require Avisynth to be installed (as opposed to MeGUI's portable version of Avisynth).

[StainlessS]

Wonderful, never used that editor before, pls note the F7 works only for "AVI" scripts, if u have a MOV/MKV/MP4 you get:


I presume that you mean that you are trying to use the script editor when you have directly loaded some non AVS media (not via Avisynth script). The script editor edits your already existing and VD2 loaded script only.
F5, or F7, refresh/reload avs script, has no script to refresh/reload if it aint already got one.

EDIT: You may (have not actually tried this), be able to open script editor in newly opened VD2, write a valid script, and
CTRl/S (save, if not already created then will open Save As dialog box), and once saved, then you should be able to F5/F7.
If it dont work as above, then do say something.

EDIT:
Tried with simple script below, no problem at all (CTRL/S saved as Testing.avs, then F5 or F7 works just fine).

ColorBars

[stormy1777]

I'm not sure how to reproduce, i was using an AVI in the script editor, then switched to an MP4 source, and it produced that error, however, cannot reproduce it, so, ignoring that for time being, yeah, script editor is GREAT/integrated tool, was totally not aware of it.. and writing script from scratch worked too. I'll keep an eye next time, maybe one day I'll install a webcam on the monitor for such cases :) :) like that nifty "Textarea Cache" addon that saved me ONCE already, and caused me to BRAVELY press SUBMIT without any second thought or ctrl-a/c ever to cross my mind :) :)

WOOO... I can fly..... oppps... waittttttttttttttttttttttttt.... I'm faaaaaalllllllllllllllllllinnnnnnnnnnnnnnnnnnnnnggggggggggggg :) :)

[hello_hello]

I mentioned it in another thread, but the VD script editor doesn't automatically add the avs extension to the file name when you save a script you've created from scratch. If you don't add it yourself, it results in the "AVI Import Filter error: (Unknown) (80040154)" error.

There also seems to be no way to resave a script with a new name after it's been saved for the first time. That's an annoyance for when you want to save two versions of a script. I don't know if it's a limitation due to the way the script editor and VD interact, but if not, it'd be nice to have a "Save As" option to save a copy of a script with a new name.

While I'm here, as I've only been using the script editor for a few minutes now, could somebody explain what the options under "Edit/Script Handling" do? I haven't been able to find any info on that.

Cheers.

[stormy1777]

If you don't add it yourself, it results in the "AVI Import Filter error: (Unknown) (80040154)" error.


very possibly what took place... I'm now installing a web-cam to monitor my every move :)

[StainlessS]

While I'm here, as I've only been using the script editor for a few minutes now, could somebody explain what the options under "Edit/Script Handling" do? I haven't been able to find any info on that.


Works the same way as VDubMod, eg, make some edits (cut out adverts/commercials), press CTRL/I (in script editor, insert trimset), and it inserts the avisynth Trim(...) + Trim(...) etc, I am Mobile at the moments, hope I aint got summick wrong here.

EDIT: On 2nd thoughts, methinks I got that wrong, "Script Handling" was I think a bit baffling to me too.

[shekh]

> what the options under "Edit/Script Handling" do?

The editor uses different features according to script type. I remember these effects: with avisynth it enables code highlight and some code suggestions. With vapoursynth it enabled python code highlight.
The procedures like "insert range" change their meaning and syntax.

[StainlessS]

> what the options under "Edit/Script Handling" do?

The editor uses different features according to script type. I remember these effects: with avisynth it enables code highlight and some code suggestions. With vapoursynth it enabled python code highlight.
The procedures like "insert range" change their meaning and syntax.

And it presumably automatically changes with loaded script type, so in most cases needs no user attention.

EDIT: Needs no answer.