[VCDImager Bugs/Devel] re: VCDimager autopadding issue?

[David Bartel]

I've recently  been trying to use VCDimager to create bin/cue's of NTSC
SVCD stream files encoding using Tsunami Encoder (TMPGEnc). For some
reason all the other people I talk to who use both Tsunami and VCDimager
don't have problems, so I would assume the problem lies with me, however
I have one problem. I'm using an exact profile downloaded from doom9.net
and following their SVCD guide. The outputted file plays fine, looks
great, and in every way appears to be perfectly compliant with the NTSC
SVCD standard. When I try running this file through VCDimager however,
it ALWAYS autopads it, and I go from a 49 minute (755MB) SVCD to a
bin/cue with an 83-87 minute data track, which of course I cannot burn.
I even tried turning on bitrate padding in Tsunami, but the same result
occurred when using VCDimager. This problem I have duplicated using
every version of VCDimager 6.2 and newer. 6.1 says:

WARN: track # 0 not a multiple of 2324 bytes
WARN: could not determine mpeg format -- assuming it is ok nevertheless
INFO: scanning mpeg track #0 for scanpoints...
ERROR: invalid mpeg packet found at packet# 1 -- please fix this mpeg
file!

I'm at my wit's end here, as yours appears to be the only program that
serves this purpose, and I appear to be the only one having this
problem, yet I'm using identical settings and program versions as other
people, who have no problems. If you have any suggestions I would
greatly appreciate them.

Oh yes, I suppose I should say I'm using the win32 builds.

FractalD.