ShaneZ
26th April 2003, 19:18
Well, I ran into this problem after installing Avisynth 2.51 so I figured I would share with the group because I have seen some other errors close to the one I encountered.
A few days ago I installed AVS 2.51. After looking at some user comments I decided to downgrade back to AVS 2.07 because of compatibility issues. After the downgrade, DC4U started acting erraticallly. It would do some pgc's fine, but on some it would give me a Bad Data error. Yesterday I reinstalled AVS 2.51 and everything works fine again, luckily.
Not much of a bug report, but maybe it can help someone. So if you upgraded to AVS 2.51 and went back to 2.0x and are getting some strange errors this could be a large part of your problem.
Shane
A few days ago I installed AVS 2.51. After looking at some user comments I decided to downgrade back to AVS 2.07 because of compatibility issues. After the downgrade, DC4U started acting erraticallly. It would do some pgc's fine, but on some it would give me a Bad Data error. Yesterday I reinstalled AVS 2.51 and everything works fine again, luckily.
Not much of a bug report, but maybe it can help someone. So if you upgraded to AVS 2.51 and went back to 2.0x and are getting some strange errors this could be a large part of your problem.
Shane