[VCDImager Bugs/Devel] problems with vcdimager 0.7.x

[kgrimes]

I'm not sure if this is a bug or not, but I'm getting an assertion 
when attempting to use either vcdimager.exe or vcdxbuild.exe to 
create a bin/cue image of a mpeg2 file that I have.  The mpeg2 was 
encoded with tmpeg1.2a, and was muxed with bbmpeg 1.24 as a SVCD.  
Vcdimager v 0.6.2 works fine with the mpeg, however both 0.7.7 and 
0.7.9 give an assertion about the user data length not being 14.  
This has happened with every mpeg that I have tried, so either I am 
doing something VERY wrong or there is a legitimate bug.  Let me 
know if you need the stack dump file or any sample mpegs to 
reproduce the problem, as I can make those available if needed.

[c:\dl\vcdimager]vcdimager -c c:\foo.cue -b c:\foo.bin -t svcd 
h:foo1.mpg
++ WARN: initializing libvcd 0.7.9 [cygwin/i686]
++ WARN:
++ WARN:  this is the UNSTABLE development branch!
++ WARN:  use only if you know what you are doing
++ WARN:  see http://www.hvrlab.org/~hvr/vcdimager/ for more 
information
++ WARN:
   INFO: scanning mpeg sequence item #0 for scanpoints...
!ASSERT: file vcd_mpeg.c: line 329 (_parse_user_data): assertion 
failed: (usdi->len == 14)
      0 [sig] vcdimager 1176 open_stackdumpfile: Dumping stack 
trace to VCDIMAGER.EXE.stackdump