[VCDImager Bugs/Devel] SVCDs created with vcdimager 0.7.9 crash WinDVD 2.6

[Oliver Wagner]

Hi,

I think this particular problem was reported before, but I've not seen
any follow-up except the suggestion to try vcdimager 0.7.x. I'm also
inclined to think that this is actually a bug in WinDVD, but a) we
can't be sure :), and b) if it is, it might be interesting to either
note this fact to other vcdimager users and/or add a workaround to vcdimager.

I've created a SVCD image with vcdimager 0.7.9:

vcdimager -t svcd -c file_cd1.cue -b file_cd1.bin -l "VOLUME_CD1"
--info-album-id="VOLUME" --volume-count=3 --volume-number=1
--add-dir=SEGMENT -p -v --update-scan-offsets input.mpg cd2.mpg

"input.mpg" is created with CCE 2.50 demo and multiplexed with bbmpeg
1.24beta18, with NO user scan data added, cd2.mpg is a short file
created with tmpgenc from a still frame (actual stream at 25fps and
everything).

Playing the disk in WinDVD 2.6 (actually, the WinDVD OEM version which
came with my gfx card, "LeadTek WinDVD") causes the following strange
effects:

 - after starting, WinDVD shows the first track to be "Chapter 6"

 - in the navigation menu, it offers "Chapter 1", "Chapter 2" and
 "Chapter 3" for selection; it also offers Chapter 4-6, but those
 menu items are grayed ouot

 - the slider in the WinDVD main window which is used for
 forward/rewinding the mpeg stream doesn't have simple ticks, but a
 complete black bar (it LOOKS as if the number of ticks is so high
 that no space is inserted anymore)

 - any attempt to fast forward or rewind will cause a long hangup,
   and eventually an AV from WinDVD

I-Author and Nero "mastered" SVCDs work more or less flawlessly with
WinDVD, including seeking.

I don't really have enough knowledge about SVCD format for much more
than a guess, put is it possible that vcdimager creates "too many"
scanpoints for WinDVD to cope? Is there some known difference in the
way how I-Author and vcdimager do place scanpoints? Are there other
notable difference in the PBC structure?

Olli