All Black Output with New Avisynth?

[markums2k]

Just grabbed the latest version of AVISYNTH.

I am using the optimal script as-is with a d2v as the video source. So everything appears to be working. No errors. TMPGEnc even spends a good 2 minutes judging the field order (I'm sure you're all familiar with the progress bar). But when there's NO ACTUAL VIDEO.

It's all black. I don't understand. Anyone else experience this problem? I even tried commenting all the filters and unnecessary plug-ins out. Even a 'vanilla' AVS script does the same thing: black video. If I encode directly from the d2v file, it works fine.

Any ideas? Could it be an incompatiblity with my version of DVD2AVI or TMPGEnc or something? Everything worked fine until I installed the new AVISYNTH to use the new optimal script. Dammit!

Any help would be most appreciated. Thanks guys...

[kwag]

Load your script in Vdub, and see if it displays an error.

-kwag

[markums2k]

Thanks for the super fast reply, Kwag.

Same result in Vdub. No errors, just black video. It's the exact length of the actual clip, seems like it should work... it's just all black.

Right now, everything in the script is commented out except the plug-in load for 'MPEG2Dec3.dll' and 'Mpeg2Source' for the clip itself.

[kwag]

Can you play it in WMP If you can't, then it's a CODEC related issue

-kwag

[vhelp]

hi markums2k..

It's still black cause.. let me guess.. you installed AVIsynth v2.52.. and you
lost your ability to frameserve w/ video ?? or similar ??

It's a lot of hit n miss, till you nail it

All that is really needed is the .DLL, though I'm not sure why it was tied to
an install app. The installation step (somewhere in it's process) is what
causes a previous setup to no longer work in most cases, w/ frameserving.

You'll have to hunt and peck at your setup, till you get it working again. I
spend almost two weeks figuring it all out. Anyways..

If vdub does not respond, and you're crashing a lot (or not) you have to
may have to re-shut down the PROXY services, by going into vdub's
AVIPROXY folder, and activating the two .reg files. And, you'll probably have ta do this a number of times, till your setup works again.
-- -- -- FIG A. -- -- --

Also, you have to "Uninstall handler" and re-install it.
-- -- -- FIG B. -- -- --

You'll probably have to go through Fig A and Fig B a number of times, till
it works again. This is what I went through (and then some) till I got it to
work. Actually, it took some time before I realize that I had to perform
these steps. Seems, no one knew about these steps till I found them out
on my own. Now, its YOUR turn hehe..

Good luck (and patiance)
-vhelp

[markums2k]

vhelp, your suggestions look like they may lead to a solution, but it's very hard to understand...

I haven't really had any problems with crashes or anything. I will poke around Vdub and try to find the things you mentioned.

Kwag, the AVS file does NOT play correctly in WMP (Windows Media Player, right?). Shows only black video, just like all the other applications. I don't think it's a codec issue, but you know a lot more than I do. How do I resolve a codec issue, if that is the case? Is there a recommended package in the download section?

EDIT: vhelp I understand the post now and will try those two steps. Fingers crossed...

[markums2k]

Okay, I can't find anything resembling AVIPROXY folders in Vdub. So that idea is out the window. And remember, I can still load regular AVI files in Vdub, no problem. I haven't lost complete frame serving capability.

The only thing that is not working as it should is AVS files, and they WERE working until I installed AVISYNTH 2.5.2 earlier this afternoon. Very odd...

I've tried to find a similar problem on this and other boards, but so far haven't seen anything. So it seems isolated to my system. I'm not terribly surprised at my bad luck...

[kwag]

Try creating your .d2v again, but with DVD2AVI version 1.77.3

-kwag

[vhelp]

Hi markums2k..

I'm glad you're making some form of head-way.

However...
When you last installed vdub, did you Extract ALL the files in one gulp into
a directory "manuallly", or did you use the [Extract To] button, to
let winzip properly install in cronolagical order, including it to re-create the
subdirecties under it's main folder ??
I know it sound a bit crazy, but if you missed this proper instalation procedure,
then what you have is ALL the file basically DUMPED into one sub folder.

IF that's the case, then you wont find AVIPROXY folder. But, what you will
find, are the files you need to activate and de-activate etc - the headacke
part

There's a readme.txt file in their that describes this a bit. But, its
sort of confusing...

Quote:

-------------------
The AVIFile handler included with VirtualDub 1.3b is capable
of running in Proxy mode -- that is, you can install it as the
*default* handler for AVI files, and it will work with signposts
that are renamed to the AVI extension. This means that
applications which previously failed with the AVIFile handler
because of the .VDR extension can now be used, provided that
the .VDR files are renamed to the .AVI extension.

This support is very experimental, so try at your own risk.

To try the AVIFile proxy support, first use auxsetup.exe to
install AVIFile frameserver support, then use the REGEDIT tool
to install the proxyon.reg file. Use the proxyoff.reg file
to disable it.

The proxy support will be invisible to most programs, but some
programs do not like the proxy handler and will no longer work
if it is installed; you will have to disable the proxy for
these programs. These applications were tested:

Ligos LSX-MPEG Encoder 3.0: works
Panasonic MPEG Encoder 2.30: works most of the time
XingMPEG Encoder 2.20: fails (must deinstall proxy)
-------------------

As to Bold, "and some installers will DISABLE the proxy support".
That was left out.

The two files you need are to activate/de-activate (back and forth, till your
frameserving of .AVS and .d2v files work again) are:
* 1 - proxyon.reg
* 2 - proxyoff.reg
* 3 - AuxSetup.exe <--- don't forget this one too.

Its VERY tricky. But, sooner or late, it will work again. Its VERY frustrating,
and will cause you to loose your mind at some point.
What I've done was Reboot my system after performing each steps 1-3.
Its very fussy. But, once you get it working, my advice is try not to have
another AVIsynth update "install". Instead, just get your hands on the
latest .DLL file. That's all you really need. There's already an update, but
sh0dan said that it was going to stay as v2.52 till its stable enough
for a v2.53 change. Just note the "date" on the .DLL to keep track of it.
And, never go throw out any of these .DLL's either

Good luck.
-vhelp

[markums2k]

Thanks so much, vhelp, for elaborating. I'm going to post this, and then prepare to read over all that info...

FYI for whoever is watching, updated my version of DVD2AVI. Went from 1.76 to 1.77.3. Then made a new d2v project. Made sure to point to the new d2v file in the script... no change. No progress. Still getting black video in TMPGEnc, WMP, and Vdub.

Okay, now back to vhelp's post...

[markums2k]

Ok, I've done this about 4 times so far...

1. reg on
2. reg off
3. uninstall handler
4. re-install handler
5. reboot PC

No progress so far (each time, attempted to play new AVS file in TMPG, WMP and Vdub). Still getting the black video. If that's the wrong sequence, say so.

I'm going to try it some more, but not before I get some sleep.

As regards Vdub and the missing folder, turns out that all I had 'installed' were the P4 optimized files (consisting of a single exe and two other files). Oddly enough, it was working fine up until this fiasco. So I went and got the REAL files for Vdub and installed them properly, then copied the P4 files as directed. Long story short, I now have the aviproxy folder and the auxsetup.exe.

Should I try restarting after each individual step? Any further suggestions? Should I be adding parameters to GripCrop to get this to work right? I just had it commented out all along, since I didn't require any resizing. Might be a shot in the dark... I have no knowledge of gripfit features, prior to switching to the optimal script.

[markums2k]

Oh, BTW, I'm not using Movie Stacker. All changes to the code have been made in windows notepad. Does that matter? Just thought I'd mention it.

[Wilbert]

Assuming you installed DivX5 or a recent XviD binary, this is your problem:

http://www.avisynth.org/index.php?pa...AviSynth#q1.23

[sh0dan]

@markums2k: In vdub - what codec is show in File/File Information?

[markums2k]

Thanks for replying, sh0dan. In Vdub under file info, when I have the AVS file loaded, it says the 'Decompressor' is: Pinnacle Systems MPEG Codec.

[markums2k]

BINGO. Problem is solved.

Wilbert, you are the man. I didn't have that VIDC.YV12 string in the registry, so I added it, and made 'divx.dll' the value.

And everything is back to normal. FYI, DIVX also shows as the decompressor in Vdub now. Thanks so much, guys!

[vhelp]

hay markums2k..

Great news.

I thought you were frameserving dvd2avi project files ??
Well, at least you got it working agin I took the plung and re-installed
v2.52 back on my 2nd pc, and woudn't you know it, LOL, I'm back to where
I was last time, no frameserve support, and BLACK video - xcept, that
I'm not using divX and I don't even have it installed on it

I'm glad you got it all working out now. Irividurchy
Now, have fun.
-vhelp

[Nforcer]

I've silently watching from the side lines, I don't know much about how everything works but all I know is I tried the registry fix and no I don't have the black screen either. Thanks so much

[markums2k]

Yeah, vhelp... it's the weirdest thing. I WAS working with d2v files. What that has to do with DIVX, I'll never know.

I must say, I'm very pleased with the output of the optimal script. All I have to do now is read up on gripfit usage... weeeeee

Thanks again, guys.