vdub error in gknot

[jjaomni]

videosourceavi error: the sourceimage format is not acceptable. (error code -2)

won't encode the video
is this a know problem

how do you use mpeg2dec3.dll in vdub?

[Rocks]

I get the same error from VDubMod when started from Gknot 0.28. "Videosourceavi error: the sourceimage format is not acceptable. (error code -2)".

The problem seems to only show up in Gknot whenever I try to encode or do a compressibility check. I am able to open the .avs file that GKnot creates within VDubMod itself and start compression with out any problems.

I have tried using Divx 5.04, 5.05, and I've reinstalled gknot several times and even deleted the registry keys manually but I have still not been able to get it to work.
Is this a know problem with Gknot?

[ruanova]

I got the same problem. I'm solved switching between AVS versions (2.5.1 to 2.0.7) with AvisynthSwitcher ....

But I don't know what's the problem...

[Rocks]

Thanks for the tip ruanova. I switched to AviSynth 2.0.8 and turned off the use of mpeg2dec3.dll and everything seems to work fine now.

But I wanted to find out what the problem might be because I want to use AviSynth 2.5.1 because it is supposed to be faster than the older ones so I did some tests. I tried to use Nic's YV12 MpegDecoder.dll (http://nic.dnsalias.com/MPEGDecoder.html) instead of mpeg2dec3.dll to see if that might be the problem but I still got the old "Videosourceavi error: the sourceimage format is not acceptable. (error code -2)". I tried AviSynth 2.5.0, 2.5.1, and the 2.5.1 build that comes with Gknot but the same error pops up.

So my conclusion is that there is some problem with Gknot and AviSynth 2.5.x on many peoples systems.

Len0x, TheWef, do you know what's going on? Anybody else?

[TelemachusMH]

It sounds to me that you don't have a YV12 vfw interface. If you install Xvid or Divx 5 you will have the interface. However, that may not fix it. Try setting this registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\VIDC.YV12

Change the value there to "xvid.dll" or "divx.dll".

TelemachusMH

[Rocks]

Thanks, TelemachusMH!

That did the trick. I did have XviD and Divx 5.0.5 installed but when I set that registry value to "divx.dll" it magically fixed my problems:D.

[TelemachusMH]

:D Glad to hear it.

TelemachusMH

[ruanova]

Thanks TelemachusMH....

[jjaomni]

well that worked. is how does that get set wrong?


can't remember what the value was either

[jjaomni]

xl_yv12.dll is the value it was. what set that up to give me such a headache

[TelemachusMH]

Anything could have changed that value really. On my system it defaults to the ATI YV12 dll, because I have a tv tunner card, and when I install the software for it, it changes that value. It could have been changed by tv software, or a video player you installed, or a video editor you installed, I really don't know.

TelemachusMH

[Angelus]

This somewhat relates to what has been posted in the other threads. I captured video from my DV camcorder and tried to use VDub or VDubMod to deinterlace and compress the video file but got the error: source image format is not acceptable. When I was doing this, the video was in "Full Processing Mode" and just out of curiosity i changed it to direct stream copy and it encoded. I don't know if any of this makes sense, but perhaps it pertains to GK too.

[TelemachusMH]

If you try to open it and you get that error you probably need the Panasonic DV codec (http://forum.doom9.org/attachment.php?s=&postid=265418).
If you can open it, goto File/File Information and post what is there.

TelemachusMH

[Angelus]

Hi I'm using Gordian Knot 0.28.4 beta with the Rippack 0.28.4 and the codec pack 1.2. I just started to encode "old school" today and its giving me the source image format is not acceptable error code -2. The registry has that value in it but it still gives me the error. Does any1 else have this problem or now how to fix it? I even used that avisynthswitcher and switched to avisynth 2.0.7 and turned off the use of mpeg2dec3.dll. Please help!

[Angelus]

I'm encoding it now but all I did was switch it to avisynth 2.5 and instead of just encoding the "movie" part i am encoding the "movie and credits" together. And so far its working so wat is going on?

[len0x]

if you're using 2.5.x then mpeg2dec3.dll should be used
if 2.0.8 then just mpeg2dec.dll...

[Angelus]

yes i know. I tried both versions of avisynth and got the same error. Just when i encoded the whole movie with the credits did it start to work.

[len0x]

Originally posted by Angelus
Just when i encoded the whole movie with the credits did it start
to work.

makes no sense to me, but whatever works for you :)

[Angelus]

Well it didn't work for me but virtualdub mod actually came up and began encoding this time when i encoded both the movie and the credits together. It seems when i start encoding, the credits complete fine and when it starts to encode the movie, I get an error:

"exception unknown software exception (0xe0070001) occured in the application at location 0x77e73887"

Any body have any thoughts? I already did a reinstall once to no avail.

[Polarbear]

Originally posted by Angelus
Well it didn't work for me but virtualdub mod actually came up and began encoding this time when i encoded both the movie and the credits together. It seems when i start encoding, the credits complete fine and when it starts to encode the movie, I get an error:

"exception unknown software exception (0xe0070001) occured in the application at location 0x77e73887"

Any body have any thoughts? I already did a reinstall once to no avail.

I have the similar problem and seems like many people are having the similar problem.

http://forum.doom9.org/showthread.php?s=&threadid=55039
As of now, my only guess is what is being suggested in the previous thread which is errors in the ripped .vob files, eventhough I did not see any errors during the ripping phase.

-Polarbear

[Angelus]

Yeah i had that problem b4 with the bad rips and I re-ripped them again and still got the error message. So unless I got 2 bad rips one after the other, I dunno what is wrong...

[Polarbear]

After reading through other threads from other forums and other topics, I am fairly certain it has something to do with the source. It seems to be that a certain frame(s) within the source that has error, and that can be error / glitch in the original source, such as DVD itself. The filters themselves seem to not able to 'ignore' slight glitches / errors, so causing the crash.

-Polarbear

[SKD_Tech]

Also another way to get around it is open up your AVS file before VirtualDub can get to it and at the top you should see the name of the troublesome .dll . it says "mpeg2dec3.dll" change it to "mpeg2dec.dll" Hey it fixed it for me!

[Angelus]

I think PolarBear is right. I finally watched the status of VDubMod when I was encoding it and it got stuck on frame # 4597 or something like that so it does have something to do with the source. Is there any way you can skip frames while encoding or is there any other type of filter i could use that would let this error slide? :D I also tried using the mpeg2dec.dll instead of the mpeg2dec3.dll and that didn't have an effect at all.

[Polarbear]

Not to beat this horse to death, but VERY VERY VERY weird issue here which complicates the situation.

I tried every method I can get my hands on, including different filters, different versions of almost every component of Gknot, essentially short of re-ripping or reformatting the drive. Nothing works.

Here is the twist.

I have another computer, let's call this (A), networked on local network to the computer, let's call it (B), which has the source and has the encoding issues. I set up drives on (B) to be network drives and basically allow (A) to have access to those drives. The encoding is essentially done on comp (A) but simply have comp (A) access the source video on comp (B). One can then have the encoded video reside on (A) or (B).

Guess what? The encoding from (A) of the video source on (B) went without a problem at all. ALL of the previously problematic video sources on (B) were encoded by (A) perfectly.

I have a 3rd computer on the same local network and it was able to do the exact same thing as comp (A), producing the same, error-free final encodings from the problematic sources on (B).

All of the previous conjectures on the reasons for such errors seem to be wrong. It is a very weird problem obviously. I am tempted to format the harddrive partition where the OS resides on comp (B) and reinstall the OS + GK packages and see if the same problems still occur for the problematic video sources or the problems will simply go away, but that seems a bit time consuming and for now, I found a work-around solution for myself, at least.

I hope someone with expert experience in GK development can shed some light on this problem, and if further details of setup are necessary, will be glad to provide them.

-Polarbear

[Angelus]

I'm hoping to breathe some new life into this thread. I still haven't been able to encode the movie because it keeps getting stuck on various frames while in VDubMod. It there any type of filter in VDubMod that allows you to drop a problematic frame or frames so that I would be able to encode? Thanks

[Master]

Hi everybody,

I still have the error code-2 problem after 1st pass even though I added the regestry entry. It worked fine for 2 or 3 movies but came back to haunt me, now.
Does anybody have another idea how to solve the problem?

Thanx.

[len0x]

The best solution is to contact avisynth developers or Nic with a sample of VOB file containing problematic frames...

[Polarbear]

For those who were helpful enough and remembered my problem, I believe I found the solution, and it ended up being a hardware one.

The problem came about ever since I replaced my harddrive. Through LOTS of testing and hardware swapping, the IDE cable connecting the harddrive was the culprit. The old cable, while worked great with my previous ATA-100 HD seem to be having a lot of problems with the newer ATA-133 HD's. I replaced the IDE cable with the one that came with the new HD, also ATA-100, and two things were immediate:

1) The transfer rate / seek time, HD performance all shot up to close to what the specs for the harddrive is at. (I ran HD testing utility.) Previously, it was VERY VERY slow, and actually was the cause for those weird random system reboots.

2) Encodings are all working perfectly now and no more random reboots.

It is very weird as to how the IDE cable turned out to be the culprit, considering it was working fine with my previous ATA-100 HD for a good year and half.

Thanx again all of you guys,
Cheers,

-Polarbear

[billou2k]

I think i went through all the threads I could and tried all the solutions i found but I still have this problem
I ve installed avisynth 2 instead of avisynth 2.5 recreated d2v and avisynth file to handle the previous version
but I still have the problem using the divx kauehi pro codec
(all the others codecs are fine with me)
Then i tried the registery trick but the key reported before on this thread doesnt exist on my system ( the closest one would be VIDC.YUY2 set on msyuv.dll)
If I create the VIDC.YV12 with xvid.dll as a value, the problem is still there (the only difference is that in the "select video compression" dialog I got xvid mpeg4 codec appearing twice with one showing a fourcc set to yv12)

is it a problem related with kauehi or there is really something misconfigured on my system... I think I tried everythin I could... Please tell me if i forgot something!
thanks

PS I experienced the same problems with Kauehi and Manihi

[Angelus]

My guess is to steer clear of those types of codecs; they aren't official releases from Divx and they have proven to be buggy. So if I were you, I'd just stay with 5.05

[billou2k]

Usually I dont like giving up on a problem of that sort...
but I believe this time you are right!:D
I ll test their beta codec when they make it work properly

[hektor]

I've got the solution to the problem!!!! It was caused by TV Tuner drivers. If anyone got WIN98SE please edit your c:\windows\system.ini file and in [drivers32] section add line : VIDC.YV12=DivX.dll
after all other drivers. Of course solution to the problem in XP was explained earlier. Sorry for my english. Hope this help. :D

[jjaomni]

i think what is going on is that ffdshow is adding it's own codec into that registry setting. since i have had to remove ffdshow due to stability issues in explorer for some reason and had to change that vaule back to divx.dll a few times now on this install of xp.

[sinesurfr]

Hi,

I only get this error when GKnot tries to do the second pass, so I manually opened up vdubmod and opened the avs there trying to fix it to no avail. I also tried the registry tweak as well as changing the script dll by deleting the 3 in line 7 LoadPlugin("C:\PROGRA~1\GORDIA~1\mpeg2dec3.dll"), which only made the avs unopenable. I also tried uninstalling and reinstalling gknot. It worked fine for my other movies. I don't know why this one doesn't work. Thanks.

[len0x]

oh good to know about ini file!

[FSB-SPY]

Adding the line for divx.dll did not do anything... still fails on second pass. How can I remedy this...?

[FSB-SPY]

Grrrr... :P This happened right after I upgraded to the new GKnot. :( Was fine before... so what changed? Somebody please help..

[stormy1777]

quick, let me write it before I forget !!!

I have two computers on one everything works perfect!! gknot, divx5, xvid, everything.. on the other I upgraded to latest gknot 0.28 and then this error started poping up:

"Unable to start video compression error: bad format (-2)"

ok, so like a good girl I read *all* the threads.. and try all the *tricks*, including the registry (mine was already set right).. hmm.. then I narrow it down and notice it has *nothing* to do with gKnot (in my case).. I can reproduce this error with a proper avi file and virtualdub.. all I do is select divx5 as compression and hit save as.. boom error comes.. Ok.. that's a nice small test case.. At this point I figure it's something with divx5.. I try older nandub and other mods and one of them says, "can't open logfile for reading" or something like that.. hmm.. I say, why log?? I just want to save as AVI.. hah.. then I say, it must be doing 2 passes.. so.. I go to knot and at the divx encoding control panel, just before you press "add job to encoding" I press the divx5 codec settings on "first pass" and I see that in the dialog that pops up it says "Multipass, nth pass" or "1-pass" I changed that to "Multipass, 1st pass", then click on the "nth pass" and verify it's "Multipass, nth pass"..

now hit add job, and it works like a champ.. well at least the first job is still running.. it's something to do with the defaults of divx...

then I seem to vaguly recall that the guide for Gknot says to invoke vbub/nandub once before doing anything to accept agreement (which I did) and also to go in the "options" and press these two keys..

anyways, it's working here.. not some mystic hardware issue or video display adapter, just the settings of the divx5 multipass compression..

curious to know if this thread is still alive and if this helps anyone.

enjoy.

[niann]

I was helping a friend set up GK and noticed the same thing, I had to set the options for Divx and XviD by hand the first time using either codec, after that it worked like a charm.

[Jafco]

Originally posted by stormy1777
quick, let me write it before I forget !!!

<snip>

I go to knot and at the divx encoding control panel, just before you press "add job to encoding" I press the divx5 codec settings on "first pass" and I see that in the dialog that pops up it says "Multipass, nth pass" or "1-pass" I changed that to "Multipass, 1st pass", then click on the "nth pass" and verify it's "Multipass, nth pass"..

now hit add job, and it works like a champ..

That was EXACTLY IT! Thanks!

[jjaomni]

glad to know this thread is still alive and kicking. i recently got back into divx after being with xvid for so long with out any issues and no wthe files names have changed so much not usre if the registery change still work since i dont have the same file in the registery that i was changeing it from. but i am again getting the same error

[tomos]

same here, tried the reg fix but no diff. i'm tried to convert hd mpeg-2 TS and it works on some, but not others. no idea why this is happening tbh

[stormy1777]

registy? what registry? just do what is said 3 posts above, my quote.. otherwise be more specific as to exact error u r getting. good luck.

[tomos]

the error is:
"Unable to start video compression error: bad format (-2)"

i am using hdtv files via avs files in vdub mod. it worked fine but now no matter what i cant get rid of this error.
i am using the helium divx codec

tried checking the settings but nothing so far :(

[jjaomni]

my issues is with auto gknot and useing divx. when i get this error. every thing works in gknot with divx and xvid and xvid still works in gknot.

[ntden]

I uninstall all codecs, remove keys vidc.xxx from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32
Reinstall all codecs exclude ffdshow. All worked now.

[Biggs]

My system has broken down as well :(

I am also getting this error message and the registry edit mentioned has not fixed the situation. I am using AGK 2.27 with all bundled software installed, so VirtualDub is 1.5.4.1.

I did have xvid installed and every time i started a job something was changing the registry string to xvid. I uninstalled xvid so now the string does not change but the job still fails anyway.

I have also tried the latest version of GK (0.35.0) and again i get as far as VirtualDub only this time the error reads "Video compression error: An unknown error occured (may be corrupt data). (error code -100)" I have tried the multipass fix also mentioned above but this hasnt solved the issue.

Does anyone have any ideas?
Many thanks

[jjaomni]

i found it was the web cam that i had that was installing it's own file in that spot.

[Biggs]

dont have anything like that installed