Results 1 to 2 of 2

Thread: TyTool Errors: SVCD and Second Time Run

  1. #1
    Join Date
    May 2003
    Posts
    95

    TyTool Errors: SVCD and Second Time Run

    I detailed some of this in this thread... http://www.dealdatabase.com/forum/sh...threadid=25248

    The file was recorded on a DTivo S2 (DVR-7000/17) running 3.1.0 Monte-ied from 3.1.U5, transferred to PC using TyTools7rx and MIPS compiled tserver_mfs6, edited and muxed (SVCD and transcoded to 44.1 @ 192).

    Here is the log of the error from VCDEasy:

    mpeg scan: pack header code (0x000001ba) expected, but 0x000001b9 found (buflen = 4)
    ...PEM (program end marker) found instead of pack header; should be in last 4 bytes of pack
    bad packet at packet #337704 (stream byte offset 784824096) -- remaining 4 bytes of stream will be ignored


    Complete log:

    [Internal Xml Generation]
    Internally computed XML generated successfully: "I:\temp\videocd.xml"

    [VCDxBuild.exe]
    GNU VCDImager 0.7.12
    initializing libvcd 0.7.12 [cygwin/i686]

    this is the UNSTABLE development branch!
    use only if you know what you are doing
    see http://www.hvrlab.org/~hvr/vcdimager/ for more information

    changed volume number to 1
    changed volume count to 1
    changed restriction number to 0
    changing 'next volume use sequence 2' to 0
    changing 'next volume use lid 2' to 0
    changed volume label to `HIGH_3_11'
    changed publisher id to `VCDEASY_V1152'
    changing 'update scan offsets' to 1
    changing 'relaxed aps' to 0
    adding pbc (Selection-000/2)
    adding pbc (Selection-001/2)
    adding pbc (Selection-002/2)
    adding pbc (Selection-003/2)
    adding pbc (Selection-004/2)
    adding pbc (Selection-005/2)
    adding pbc (Selection-end/3)
    sequence count 1
    adding sequence #0, I:\captured\Highlander-Vendetta.ty.mpg
    unknown user data tag id 0x06 encountered (not a problem, most likely caused by a specific MPEG encoder)
    mpeg scan: pack header code (0x000001ba) expected, but 0x000001b9 found (buflen = 4)
    ...PEM (program end marker) found instead of pack header; should be in last 4 bytes of pack
    bad packet at packet #337704 (stream byte offset 784824096) -- remaining 4 bytes of stream will be ignored
    Next time, let VCDEasy analyse the MPEG files to have this warning before...

    pts start offset 0.266933 (max pts = 2654.777922)
    playing time 2654.510989
    mpeg stream contained no scan information (user) data
    scanning mpeg sequence item #0 for scanpoints...
    already scanned... not rescanning
    pbc: psd size 440 (extended psd 0)
    iso9660: highest alloced sector is 232 (using 300 as isosize)
    requested entry point (id=Chapter-0001-02) at 474.257000, closest possible entry point at 474.256833
    requested entry point (id=Chapter-0001-03) at 868.768000, closest possible entry point at 868.768000
    requested entry point (id=Chapter-0001-04) at 1620.736000, closest possible entry point at 1620.735611
    requested entry point (id=Chapter-0001-05) at 2078.343000, closest possible entry point at 2078.342822
    requested entry point (id=Chapter-0001-06) at 2475.256000, closest possible entry point at 2475.256056
    generated image (338304 sectors [75:10.54]) may not fit on 74min CDRs (333000 sectors)
    OGT streams available: 0 0 0 0
    writing track 1 (ISO9660)...
    'update scan offsets' option enabled for the following tracks!
    writing track 2, MPEG2, NTSC 2/3 D-1 (480x480/30fps), audio[0]: l2/44.1kHz/192kbps/stereo ...
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    mpeg: some marker is not set...
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    non-MPEG1 audio stream header seen
    MPEG packet statistics: 309955 video, 27749 audio, 0 zero, 0 ogt, 0 unknown
    writting post-gap ('leadout pregap')...
    finished ok, image created with 338304 sectors [75:10.54]


    It seems like it is at the end of the file... Is this something that needs to be fixed?

    I also noticed that often when running tserver_mfs6 after having run once and ctrl-c exited, a crc mismatch is generated the second time it is run. If you reboot, it is fine. Is this another issue? Might just be for the MIPS compile...


    Thanks,
    Homer Out

  2. #2
    Join Date
    Jan 2002
    Posts
    4,809
    Sorry. i missed this last time. I don't often check the rest of the thread.

    That 00 00 01 b9 is a legal thing. It is the end-of-stream pack header. It is only 4-bytes long. I am not certain why it is being complained about by that tool.

    I suppose I could remove it but it is better left in place.

    --jdiner

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •