Hi!

Chris wrote:

> What tools do you use to examine the stream?

I wrote my own tools. In particular, one that splits a TS into its
components. And then I usually use hexdump to examine the bits.

> Where is a good place to start to learn to interpret them?

There's a lot of information on http://www.le-hacker.org/dvd.html

>>But: some receivers/recorders don't write the tables to disk, so you
>>have to guess. This is what dvbcut currently does, but it guesses wrong
>>if the audio frames aren't aligned. Converting the transport stream to a
>>program stream may help, but only if the converter re-packages the audio
>>track (the program I use doesn't, and dvbcut -batch won't work either,
>>for obvious reasons).
>>
> 
> I use WebScheduler to capture. It has an option to capture all PIDs
> belonging to a program.

That option - if found elsewhere - does not necessarily include the SI
tables that are broadcast. In fact, the standard says that so-called
"partial transport streams" (i.e. recordings of a program) shall contain
modified and/or special tables. I haven't yet seen a hard- or software
that conforms to this clause, however. But there are several that only
store the audio and video streams, but no SI tables. I'm using one of
them (dvbd) myself.

I think we should follow two paths here: Use the tables if they are
present, and keep guessing along if they are not. I already wrote some
simple table-parsing code (for another program) that might be suitable.

Stay tuned,
-- 
Michael "Tired" Riepe <[EMAIL PROTECTED]>
X-Tired: Each morning I get up I die a little

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
DVBCUT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dvbcut-user

Reply via email to