Page 13 of 70 FirstFirst ... 311121314152363 ... LastLast
Results 181 to 195 of 1041

Thread: MUX'ing, VSplit, and MPG2 files.

  1. #181
    Join Date
    Jan 2002
    Posts
    4,809
    Originally posted by FreydNot
    Code:
    33333 -> old Vid ByteCount = 2E 33 94 to 30  F F0
    33333 -> new Vid ByteCount = 23 44 10 to 25 20 9C
    33333 -> NOT ALIGNED on the Video... It is an OOB chunk!
    Found an OOB packet... The Audio Diff is: 00:00:00.036
    It is in sequence... Everything is fine...
    Crap. Ok. Remember the 20 50 40 I have mentioned at times. This is a reset in the byte counter of the TyStream file to 23 44 10. This is the first time I have seen this. But then there have been 2 new ones tonight. But that is why I release the pre-test version. To see if these would keep cropping up.


    Code:
    ### The Vid Body is off! 23 44 18 -> 30  F F8  diff == 0xFFF33420 (-838624)
    This is the same reset value again. Just not in a position in the chunk to cause the rest of the error/debug messages.

    --jdiner

  2. #182
    Join Date
    Sep 2002
    Posts
    2

    Question

    Hi,

    New to the forum but wondered if I could help test from the UK TIVO perspective. I tried out the new version but on WinXP it GPF's on every ty I have tried. An example of the output with /V on is shown below. Of course it may be me in which case flame away! but if it isn't I am happy to help try fixes or provide more info. I can FTP the file (or a part of it if someone tells me how and where to split it). The example is small about 131MB so I could ftpit as is on cable. Thanks for all the great work.

    X:\newshows>vsplit13a -V test2.ty hmm.m2v hmm.m2a
    Processing 'test2.ty': (10 chunks per tick)

    checkNumRecs: Number of Records: 18165 (f5 46 7a bd)
    Startup: Found a bad chunk in the first Analysis-10. Skipping until there are 10 good ones.

    checkNumRecs: Number of Records: 92 (5c 0 16 80)

    checkNumRecs: Number of Records: 95 (5f 0 ff ff)

    checkNumRecs: Number of Records: 93 (5d 0 2 80)

    checkNumRecs: Number of Records: 96 (60 0 3 80)

    checkNumRecs: Number of Records: 96 (60 0 3 80)

    checkNumRecs: Number of Records: 76 (4c 0 22 80)

    checkNumRecs: Number of Records: 95 (5f 0 ff ff)

    checkNumRecs: Number of Records: 107 (6b 0 7 80)

    checkNumRecs: Number of Records: 81 (51 0 b 80)

    checkNumRecs: Number of Records: 97 (61 0 ff ff)
    Read the first 10 chunk's for analysis...
    Detected Tivo Type: Standalone
    Detected Audio Stream Type: MPEG Layer II
    We found the SEQ header start!
    ***** Setting first Video PTS to: 00:00:01.402
    Final standardAudioSize = 880
    Final standardFrameLength = 864
    Final standardAudioDiff = 3240 or 00:00:00.036
    First Video PTS: 00:00:01.402


    last 4 = 0 0 0 0 -- first 4 = 5c 0 16 80

    X:\newshows>

  3. #183
    Join Date
    Feb 2002
    Posts
    54
    ### The Vid Body is off! 20 50 50 -> 31 B4 50 diff == 0xFFEE9C00 (-1139712)

    ### The Vid Body is off! 6A 66 B4 -> 6A 66 A4 diff == 0x10 (16)

    ### The Vid Body is off! 5D A3 60 -> 5D A3 50 diff == 0x10 (16)

    ### The Vid Body is off! 5C D7 50 -> 5C D7 40 diff == 0x10 (16)

    ### The Vid Body is off! 63 A6 18 -> 63 A6 8 diff == 0x10 (16)

    ### The Vid Body is off! 5C 30 64 -> 6D 94 64 diff == 0xFFEE9C00 (-1139712)

    You want clips of any of these? BTW, PM me the specific FTP you want these uploaded to.

    I'm going to try to PM you the entire log file from my 26 tests, and you can point out any particular chunks you want.

  4. #184
    Join Date
    Mar 2002
    Posts
    290
    Originally posted by Kythorn
    Here's the most amusing log output I've seen in a while.
    Note: this spans 3 FSIDs, but is reported as 0m in TyTool.
    I've watched this entire episode in the past...
    The only time I've seen this is when I'm replaying a stored video from disk while running Tytool. If I put the Dtivo back on live TV, then I get proper file sizes. I assume DTivo somehow locks it's database file while you're viewing it the same way that it locks it while recording it.

    Do you ever get the "0M" from anything else?

  5. #185
    Join Date
    Feb 2002
    Posts
    54
    Originally posted by rd001

    The only time I've seen this is when I'm replaying a stored video from disk while running Tytool. If I put the Dtivo back on live TV, then I get proper file sizes. I assume DTivo somehow locks it's database file while you're viewing it the same way that it locks it while recording it.

    Do you ever get the "0M" from anything else?
    Tivo isn't playing anything. Tuner 1 -> channel 0. Tuner 2 -> Channel 1. (both videoless channels)

    Just fired up tytool and refreshed, it's still 0 megs. And no, I've never seen this before.

  6. #186
    Join Date
    Jan 2002
    Posts
    4,809
    Originally posted by Kythorn


    Tivo isn't playing anything. Tuner 1 -> channel 0. Tuner 2 -> Channel 1. (both videoless channels)

    Just fired up tytool and refreshed, it's still 0 megs. And no, I've never seen this before.
    I have seen this before. If it was being played and was stopped at some point in the middle of the show. I.e. "resume playing option" the size is oftern reported a 0... I don't know why. But the size records that come back from the MFS DB in the tivo don't report anything... I.e. not just wrong I actually get back 0's...

    --jdiner

  7. #187
    Join Date
    Jan 2002
    Posts
    4,809
    Ok. Well. Something things are just not right still. But I have a new test version pretty much ready to roll. I am just running some big tests of it here before I post it.

    So everyone get ready to run things again...

    --jdiner

  8. #188
    Join Date
    Jan 2002
    Posts
    4,809
    Ok. A few more things have been cleaned up and trapped out now.

    Please run this one through again. What I most need people to look for at this point are the ### and $$$ flags. These are part of the lineup checking code in the new byte counting stuff. They show up when things are off. For now with this release ignore the rest of the messages.

    They should never show up... But do on occassion for some unknown reason in the audio. I have seen 3 of them in 50 test clips. If you find a file with them please drop me a quick email at:

    joshua@best.com

    A PM or a post here might be easier but I would like to archive everything a touch more permanently.

    --jdiner

  9. #189
    Join Date
    Jan 2002
    Posts
    4,809
    Anyone having problems with the temporal references had any luck with the 13a release and getting rid of them?

    --jdiner

  10. #190
    Join Date
    Jun 2002
    Location
    Silicon Valley, CA
    Posts
    199
    I've tried it with two streams that were problematic before.
    One stream previously had the temporal references problem, and it still does.

    The other previously had no audio (though it plays OK on TiVo)
    and it shows an absolute slew of errors.

    Overall, I saw no improvement over the previous version.

    I think I've already submitted samples of these streams,
    but can do so again if it helps.
    SVR 2000 running 3.0 with 1x160Gb and Lifetime Sub
    SAT-T60 running 3.1 with 1x250Gb and Turbonet over 802.11

  11. #191
    Join Date
    Jun 2002
    Location
    Silicon Valley, CA
    Posts
    199
    Here's the output from vsplit13b
    Maestro complains of temporal distortion 4% into the m2v file


    Processing 'grobags.ty': (10 chunks per tick)
    Detected Tivo Type: DTivo
    Detected Audio Stream Type: MPEG Layer II
    Final standardAudioSize = 588
    Final standardFrameLength = 576
    Final standardAudioDiff = 2160 or 00:00:00.024
    First Video PTS: 00:01:55.392
    .....$$$ The Aud Body is off! 33 AD 70 -> 33 A9 5C diff == 0x414 (1044)
    .... 100......... 200......... 300......... 400......... 500
    ......... 600........55555 -> old Aud ByteCount = 33 F4 28 to 34 F AC
    55555 -> new Aud ByteCount = 34 14 C to 34 2D 40
    55555 -> NOT ALIGNED on the Audio... It is an OOB chunk!
    We got one that is just to far away!
    getBoth: old Vid ByteCount = 28 5D E8 to 2A 3E 44
    getBoth: old Aud ByteCount = 33 F4 28 to 34 F AC
    Found an OOB packet... The Audio Diff is: 00:00:00.288
    Is it in sequence??? It is OFF by exactly 12.000000 frames.
    It is in the right range. Let's see if it lines up.
    It is in sequence. Starting back up after the 'hole'...
    . 700......... 800......... 900.........

    [then everything OK until]

    8000
    ......... 8100.........

    33333 -> old Vid ByteCount = 2D 73 D0 to 2F 5C CC
    33333 -> new Vid ByteCount = 28 FC 70 to 2A E2 7C
    33333 -> NOT ALIGNED on the Video... It is an OOB chunk!
    55555 -> old Aud ByteCount = 32 35 B8 to 32 4A 5C
    55555 -> new Aud ByteCount = 32 C4 F4 to 32 DB E4
    55555 -> NOT ALIGNED on the Audio... It is an OOB chunk!

    77777 -> Yep. We are out of here! Neither lined up!


    Found an OOB packet... The Video Diff is: 01:22:09.609
    getBoth: old Vid ByteCount = 2D 73 D0 to 2F 5C CC
    -1x4: We are NOT aligned on the Video... It is an OOB chunk!
    We got one that is just to far away!
    getBoth: old Vid ByteCount = 2D 73 D0 to 2F 5C CC
    getBoth: old Aud ByteCount = 32 35 B8 to 32 4A 5C
    Found an OOB packet... The Audio Diff is: 01:22:09.498
    Is it in sequence??? It is OFF by exactly 205395.750000 frames.
    Nope... Not in sequence... Skipping it...

    8200.........

    [then everything OK until]

    .........15000
    ...

    33333 -> old Vid ByteCount = 24 A0 AC to 26 7C E8
    33333 -> new Vid ByteCount = 28 93 20 to 2A 65 50
    33333 -> NOT ALIGNED on the Video... It is an OOB chunk!
    55555 -> old Aud ByteCount = 33 FE 58 to 34 1E 74
    55555 -> new Aud ByteCount = 32 F9 5C to 33 22 A4
    55555 -> NOT ALIGNED on the Audio... It is an OOB chunk!

    77777 -> Yep. We are out of here! Neither lined up!


    Found an OOB packet... The Video Diff is: 00:37:02.885
    getBoth: old Vid ByteCount = 24 A0 AC to 26 7C E8
    -1x4: We are NOT aligned on the Video... It is an OOB chunk!
    We got one that is just to far away!
    getBoth: old Vid ByteCount = 24 A0 AC to 26 7C E8
    getBoth: old Aud ByteCount = 33 FE 58 to 34 1E 74
    Found an OOB packet... The Audio Diff is: 00:37:02.926
    Is it in sequence??? It is OFF by exactly 92621.916667 frames.
    Nope... Not in sequence... Skipping it...

    ......15100.........15200.........15300.........15400.........15500
    .........15600.........

    33333 -> old Vid ByteCount = 2F 65 DC to 31 4E 88
    33333 -> new Vid ByteCount = 26 9 78 to 27 DA 0
    33333 -> NOT ALIGNED on the Video... It is an OOB chunk!
    55555 -> old Aud ByteCount = 32 A2 68 to 32 B7 C
    55555 -> new Aud ByteCount = 34 F 10 to 31 BD D4
    55555 -> NOT ALIGNED on the Audio... It is an OOB chunk!

    77777 -> Yep. We are out of here! Neither lined up!


    Found an OOB packet... The Video Diff is: 00:41:29.122
    getBoth: old Vid ByteCount = 2F 65 DC to 31 4E 88
    -1x4: We are NOT aligned on the Video... It is an OOB chunk!
    We got one that is just to far away!
    getBoth: old Vid ByteCount = 2F 65 DC to 31 4E 88
    getBoth: old Aud ByteCount = 32 A2 68 to 32 B7 C
    Found an OOB packet... The Audio Diff is: 00:41:29.557
    Is it in sequence??? It is OFF by exactly 103731.541667 frames.
    Nope... Not in sequence... Skipping it...

    15700...

    A/V Sync Offset: 4ms (i.e. plays 4ms early!)
    SVR 2000 running 3.0 with 1x160Gb and Lifetime Sub
    SAT-T60 running 3.1 with 1x250Gb and Turbonet over 802.11

  12. #192
    Join Date
    May 2002
    Posts
    134

    Sounds good

    Sound good to me - I live on a lake, so we'll water-ski and drink beer all day, edit and setup batches for the computers to process in the evening, and then let the puter's work on the next-day's batches. Not a bad way to spend September in Florida!

    Originally posted by rc3105
    wooly:

    I'm working on editing utils so I can chop the commercials out of my b5 episodes and archive them to dvd. I should head over there in my RV, camp out and make a set of mcgyvers for jdiner and a set of b5's for us.




    --
    Riley


    *jdiner, what type of standalone player do you have?

  13. #193
    Join Date
    Feb 2002
    Posts
    54
    Ran through the same 26 streams with 3 more thrown in for good measure.

    Overall same results, as far as I could see, the new code and the old code agreed.

    The 7 occurences I previously had of ### The Vid Body is off! did not occur in 13b.

    No better luck with the clip that vsplit just completely disintegrates on though. I'll make and upload as many clips as you like, just tell me which ones, and where to put them. Bandwidth on my side is not an issue.

    If you can't put the location here, PM me or shoot an email, I'll toss the ones you requested so far and any additional ones up tomorrow.

  14. #194
    Join Date
    Feb 2002
    Posts
    54
    Originally posted by jdiner


    Wow. That disintegrated nicely. I would like a copy of that one. Actually just the piece where it is on and then gets off so badly.

    Use the TyFileSplit program to grab just that section. Please start 40 or so chunks before it fails, and then go 100-150 chunks in length from that point. That will great a file of roughly 20-30 meg in size. Hopefully you have a decent network link and can upload it to me.

    --jdiner
    This is kind of interesting.

    I did what you said, and split off from did tyfilesplit from 8000 for 150 blocks. Ran vsplit on it for the hell of it... processed fine.

    Got curious, and split off from 8000 to the end of the file, then ran vsplit on it again.

    The errors don't start until another solid 2000 chunks in, and they're completely different errors.

    I tossed a mail to you of this log file as well.

    This is not due to vsplit13b, the except for some ### vid body's that didn't happen in 13b, 13a and 13b's output is identical - if I start at the beginning and run all the way through.

    Let me know if you want a different or additional range of chunks.

  15. #195
    Join Date
    Jan 2002
    Posts
    4,809
    Kythorn, check your PMs...

    --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
  •