PDA

View Full Version : Video Resizing issue


grpprod
12th February 2006, 20:28
Hi all,

I try to process my video with the latest VirtualDub 1.6.12, but when I try to save it as DivX, it gives me the following error:

"Video compression error. The source image format is not acceptable"

If I disable "Do not prompt with errors and warnings" inside DivX's config, The error transforms to:

"Invalid width, please check your crop settings"

Here are some notes:

1. The video is captured with the native PAL resolution, ie 768 X 576. If I try to capture it with the 720 X 576 resolution, no problem occurs!

2. As a workaround, I have tried to apply the resize filter to make it 720x576 after capturing at 768x576. This also seems to work fine! The thing is that I do not wish to make my resolution smaller .

Any help would be mostly appreciated.

setarip_old
14th February 2006, 06:56
Hi!

This MAY be pertinent to the difficulty you're having. This is part of a quote I saw at a FAQ somewhere on the 'net:

"Capturing at 768x576 (which is only available using VirtualDub's "Set custom video format" dialog), works quite well, however."

grpprod
28th February 2006, 17:10
Thanks for the reply.

Capturing is not performed by VirtualDub. I use it only for post-processing. It seems very strange, since DivX appears to have the following limitations:

Width must be a multiple of 4
Height must be a multiple of 2

Isn't it obvious that 768 is a multiple of 4, and 576 is a multiple of 2? :stupid:

communist
28th February 2006, 17:24
Please take a look at forum rule 8
8) No cross posting. Post your message once, to the appropriate forum and nowhere else or it will be locked or deleted without warning.

As for your problem: I think its a problem with DivX. Is it set to any profile for DivX players? Because AFAIK 720*576 is the highest resolution the SD profiles allow. Try changing to unconstrained profile (or whatever it is named) in DivX config window.

grpprod
5th March 2006, 18:16
Sorry about breaking the forum rules, won't happen again, for this I now :readrule:

Thanks for the suggestion, indeed this has solved the problem!