Log in

View Full Version : Divx5enc + could not open log file for reading


X-Nemesis
6th February 2003, 08:31
The error I get is:

00:00:04 Error File "tmp\divxenc.avi" not found

And then I get this error:

Cannot start video compression, the source image format is not acceptable (error code -2)

This is when trying to do a compressibility test...

I did search on this and couldn't find anything helpful.

jonny
6th February 2003, 11:47
Please post:

.avs file
entire log file
divx5enc you are using, avisynth version ecc...


Cannot start video compression, the source image format is not acceptable (error code -2)


It seems there are problems in your .avs file (perhaps resolution?)

X-Nemesis
6th February 2003, 17:47
I think I figured out the problem...my crops were at odd values (0,59...) and avisynth2.5 or yuv12 needs even numbers doesn't it?

Where abouts is the logfile stored anyways? Is a new one made up for each encode or is there a permanent one which covers all encodes processed?

Thanks for replying..and also thanks for such a great tool!!

Does divx5enc deal with credits as gknot does...automatically I mean or do I need to set it up in gknot first and then load seperate avs into divx5enc?

jonny
6th February 2003, 23:03
I think I figured out the problem...my crops were at odd values (0,59...) and avisynth2.5 or yuv12 needs even numbers doesn't it?

http://forum.doom9.org/showthread.php?s=&threadid=42708
(tnx hakko504!)


Where abouts is the logfile stored anyways? Is a new one made up for each encode or is there a permanent one which covers all encodes processed?

In "jobs503\jobs.log"
Cover all the encodes (you can reset it in the job list menu).


Does divx5enc deal with credits as gknot does...automatically I mean or do I need to set it up in gknot first and then load seperate avs into divx5enc?

Yes, for now you have to encode credits separately.
I'm planning to add a nice credits support (this means that the comp.test will calculate the size of the credits, bitrate gain and comp.test value for only the movie part... but you'll have to wait a bit for this :))

X-Nemesis
6th February 2003, 23:59
well...I just did another compressibility test with new avs (13 days) and got this error message...

Predicted size is 0

LoadPlugin("g:\PROGRA~1\GORDIA~1\mpeg2dec3.dll")
mpeg2source("D:\Vobs\13 Days.d2v")
trim(0,199814)
crop(0,6,718,464)
mergechroma(blur(1.3))
LanczosResize(704,368

hakko504
7th February 2003, 08:13
You're missing a close paranthesis at the end of the resize.

And a note about the thread jonny linked to: the restrictions I mentioned were not enforced by older versions of AviSynth. Sh0dan added this restriction quite recently, so users of the regular 2.07 won't get an error message. Only the official 2.5 beta have this restriction of the released AviSynth versions. I think the restriction does exist in the 2.0 branch of the CVS, so future releases of that branch will most likely have it too.

AviSynth 2.07+ page is here (http://cultact-server.novi.dk/kpo/avisynth/avs_cvs.html) and the AviSynth 2.5 alpha page is here (http://cultact-server.novi.dk/kpo/avisynth/avisynth_alpha.html)

bullfrog
7th February 2003, 13:40
Originally posted by jonny

Yes, for now you have to encode credits separately.
I'm planning to add a nice credits support (this means that the comp.test will calculate the size of the credits, bitrate gain and comp.test value for only the movie part... but you'll have to wait a bit for this :))

I also wait the new version with credits support.:)

Thanks