Log in

View Full Version : 4:3 interlaced DV & Procoder


Mtz
24th January 2004, 15:38
I have a DV source PAL 720x576 and I'm trying to convert with DVD2SVCD and Procoder to DVD.
I read the problems form here (http://forum.doom9.org/showthread.php?s=&threadid=64085) but, not resolved my problem.
The resulting mpeg have black borders added and the final size is 720x576. In D2S the setting was 4:3.
I opened the AviSynth_Script_file.avs in VirtualDub and have correct aspect ratio (4:3) with no borders. Also, AviSynth_Script_file_avs-vfapi.avi is correct.

But when I open the Procoder_Project_file.pcp in Canopus after the encoding, at the "Aspect Ratio" tab, the settings are:
Source Video Aspect Ratio
Preset: User Defined
Video Size: 720:576
Source video aspect ratio: 20:11
Source Pixel Aspect Ratio
Preset: VCD PAL 16:9
Source pixel aspect ratio: 16:11

If I change the settings in bold for DVD at 4:3 and encoding again, the result is correct, with no borders added.
Canopus Procoder Version 1.50.22.0

Mtz
28th January 2004, 16:38
Looks like nobody have this problem.
Can D2S developers confirm if that is a bug with Canopus Procoder Version 1.50.22.0?
Why put Procoder that black borders on my 720x576 movie?

Mtz
6th February 2004, 17:09
Originally posted by Mtz
Can D2S developers confirm if that is a bug with Canopus Procoder Version 1.50.22.0?

Or maybe the beta-testers.

If that is a bug, I hope that it will not be in the next 1.2.2 version. I don't want answer to my problem, just:
BUG or not BUG. :confused:

ralphthedog
7th February 2004, 01:53
I seem to remember Procoder 1.35(?) working OK.......but I have been using CCE 2.67 for pretty much everything lately.

Procoder hasn't been supported for as long as the other encoders, maybe there's a few permutations of settings that throws things askew a bit.

There is definitely a DVD2SVCD bug in the CVD resolution setting where borders get added when they shouldn't, but you can easily remove them from the avisynth script by editing it before encoding (button on the frameserver tab).

There definitely isn't an incorrect addborders line added to your avisynth script?

Mtz
7th February 2004, 13:57
The avisynth script is ok. I loaded it in VirtualDub and the settings are correct as I said.
For DV material I want to use Procoder. With CCE and TMPGenc there are no problems with the same source.

DDogg
23rd March 2004, 19:13
Looking at the readme (http://212.88.77.140/readme.txt) I don't think Procoder 1.5.x was even supported in 1.2.1 build 3? Anyway, d2s says he thinks this has been resolved in the beta test version not yet released.

Mtz
24th March 2004, 00:41
:(
Two months of waiting for an simple and good answer.
Thanks, DDogg!