bug-vcdimager
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[VCDImager Bugs/Devel] [VCDImager] Problem with RC3 (fwd)


From: Herbert Valerio Riedel
Subject: [VCDImager Bugs/Devel] [VCDImager] Problem with RC3 (fwd)
Date: Sun, 13 May 2001 14:29:06 +0200 (CEST)

...so here we have a potential bug report ... :-/

it's related to vcd_mpeg_stream.c...

-- 
Herbert Valerio Riedel      /     Finger address@hidden for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748  5F65 4981 E064 883F 4142
---------- Forwarded message ----------
Date: Sun, 13 May 2001 08:09:23 -0400
From: Karl Heinz Kremer <address@hidden>
Reply-To: address@hidden
To: address@hidden
Subject: [VCDImager] Problem with RC3

I can encode a MPEG1 file that I created using the latest version of
the lavtools (1.4pre1) with VCDImager 0.5.9beta2 but not with the
i0.6.2rc3 version. With RC3 I end up with an error:

**ERROR: scanning error 0x000001b9 2324

Here is the complete output of the program:

address@hidden:/data1 > vcdimager -v -l "Test with  new VCDImager" test.mpg
--DEBUG: initializing libvcd 0.6.2rc3 [linux-gnu/i386]
   INFO: scanning mpeg track #0 for scanpoints...
--DEBUG: pos != len (2321 != 2324)
[ ... this line gets repeated ... ]
--DEBUG: pos != len (2321 != 2324)
**ERROR: scanning error 0x000001b9 2324

Here is the output of the old version with the same parameters:

address@hidden:/data1 > vcdimager.old -v -l "Test with  old VCDImager" test.mpg
   INFO: scanning mpeg track #0 for scanpoints...
--DEBUG: mpeg scan: type 6 @186496
--DEBUG: track# 0's estimated playtime: 2483.67 seconds
--DEBUG: iso9660: highest alloced sector is 265 (using 300 as isosize)
   INFO: writing track 1 (ISO9660)...
   INFO: writing track 2, MPEG1, NTSC (352x240/30fps)...
++ WARN: Program end marker seen at packet 186496 -- before actual end of stream
--DEBUG: MPEG packet statistics: 155795 video, 30549 audio, 152 null, 0 unknown
finished ok, image created with 187022 sectors (439875744 bytes)

What does the warning mean that the old version prints?

Thanks,

Karl Heinz




reply via email to

[Prev in Thread] Current Thread [Next in Thread]