vdub error in gknot

jjaomni · 26th April 2003, 18:31

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 · 27th April 2003, 07:51

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 · 28th April 2003, 09:31

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 · 28th April 2003, 23:29

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 · 28th April 2003, 23:52

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:

Code:

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

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

TelemachusMH

Rocks · 29th April 2003, 00:03

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

.

TelemachusMH · 29th April 2003, 00:18

Glad to hear it.

TelemachusMH

ruanova · 29th April 2003, 09:24

Thanks TelemachusMH....

jjaomni · 4th May 2003, 23:37

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

can't remember what the value was either

jjaomni · 22nd May 2003, 07:07

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

TelemachusMH · 22nd May 2003, 19:14

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 · 9th June 2003, 00:24

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 · 9th June 2003, 10:07

If you try to open it and you get that error you probably need the Panasonic DV codec.
If you can open it, goto File/File Information and post what is there.

TelemachusMH

Angelus · 13th June 2003, 18:32

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 · 13th June 2003, 18:38

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 · 13th June 2003, 18:40

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

Angelus · 13th June 2003, 19:51

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 · 13th June 2003, 19:53

Quote:

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 · 13th June 2003, 23:13

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 · 17th June 2003, 04:45

Quote:

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

26th April 2003, 18:31	#1 \| Link
jjaomni Registered User Join Date: Mar 2002 Posts: 43	vdub error in gknot 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? Last edited by jjaomni; 26th April 2003 at 19:13.

27th April 2003, 07:51	#2 \| Link
Rocks Registered User Join Date: Nov 2002 Posts: 6	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? Last edited by Rocks; 28th April 2003 at 00:47.

28th April 2003, 23:29	#4 \| Link
Rocks Registered User Join Date: Nov 2002 Posts: 6	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? Last edited by Rocks; 28th April 2003 at 23:35.

28th April 2003, 23:52	#5 \| Link
TelemachusMH Just a kid at heart Join Date: Oct 2001 Location: Wouldn't you like to know ;-) Posts: 272	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: Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32\VIDC.YV12 Change the value there to "xvid.dll" or "divx.dll". TelemachusMH

29th April 2003, 00:03	#6 \| Link
Rocks Registered User Join Date: Nov 2002 Posts: 6	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.

28th April 2003, 09:31	#3 \| Link
ruanova Registered User Join Date: Mar 2003 Location: Santiago de Compostela (Spain) Posts: 27	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...

29th April 2003, 00:18	#7 \| Link
TelemachusMH Just a kid at heart Join Date: Oct 2001 Location: Wouldn't you like to know ;-) Posts: 272	Glad to hear it. TelemachusMH

29th April 2003, 09:24	#8 \| Link
ruanova Registered User Join Date: Mar 2003 Location: Santiago de Compostela (Spain) Posts: 27	Thanks TelemachusMH....

4th May 2003, 23:37	#9 \| Link
jjaomni Registered User Join Date: Mar 2002 Posts: 43	well that worked. is how does that get set wrong? can't remember what the value was either Last edited by jjaomni; 4th May 2003 at 23:53.

22nd May 2003, 07:07	#10 \| Link
jjaomni Registered User Join Date: Mar 2002 Posts: 43	xl_yv12.dll is the value it was. what set that up to give me such a headache

22nd May 2003, 19:14	#11 \| Link
TelemachusMH Just a kid at heart Join Date: Oct 2001 Location: Wouldn't you like to know ;-) Posts: 272	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

9th June 2003, 00:24	#12 \| Link
Angelus Registered User Join Date: Apr 2003 Posts: 511	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.

9th June 2003, 10:07	#13 \| Link
TelemachusMH Just a kid at heart Join Date: Oct 2001 Location: Wouldn't you like to know ;-) Posts: 272	If you try to open it and you get that error you probably need the Panasonic DV codec. If you can open it, goto File/File Information and post what is there. TelemachusMH

13th June 2003, 18:32	#14 \| Link
Angelus Registered User Join Date: Apr 2003 Posts: 511	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!

13th June 2003, 18:38	#15 \| Link
Angelus Registered User Join Date: Apr 2003 Posts: 511	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?

13th June 2003, 18:40	#16 \| Link
len0x I'm afraid we've to stop Join Date: Mar 2003 Location: Amongst mad people Posts: 5,402	@Angelus if you're using 2.5.x then mpeg2dec3.dll should be used if 2.0.8 then just mpeg2dec.dll... __________________ Gordian Knot Family: Gordian Knot: website, download Auto Gordian Knot: Website and download, tutorial, FAQ

13th June 2003, 19:51	#17 \| Link
Angelus Registered User Join Date: Apr 2003 Posts: 511	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.

13th June 2003, 23:13	#19 \| Link
Angelus Registered User Join Date: Apr 2003 Posts: 511	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.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode