Query: stream_type
OS: debian
Section: 1
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
STREAM_TYPE(1) User Commands STREAM_TYPE(1)NAMEstream_type - attempt to determine if an input stream is TS, PS, or ESSYNOPSISstream_type [switches] <infile>DESCRIPTIONTS tools version 1.11, stream_type built Nov 11 2008 17:15:48 Attempt to determine if an input stream is Transport Stream, Program Stream, or Elementary Stream, and if the latter, if it is H.262 or H.264 (i.e., MPEG-2 or MPEG-4/AVC respectively). The mechanisms used are fairly crude, assuming that: - data is byte aligned - for TS, the first byte in the file will be the start of a NAL unit, and PAT/PMT packets will be findable - for PS, the first packet starts immediately at the start of the file, and is a pack header - if the first 1000 packets could be H.262 *or* H.264, then the data is assumed to be H.264 (the program doesn't try to determine sensible sequences of H.262/H.264 packets, so this is a reasonable way of guessing) It is quite possible that data which is not relevant will be misidentified The program exit value is: * 10 if it detects Transport Stream, * 11 if it detects Program Stream, * 12 if it detects Elementary Stream containing H.262 (MPEG-2), * 14 if it detects Elementary Stream containing H.264 (MPEG-4/AVC), * 5 if it looks like it might be PES, * 9 if it really cannot decide, or * 0 if some error occurred Files: <infile> is the file to analyse Switches: -verbose, -v Output more detailed information about how it is making its decision -quiet, -q Only output error messages TS tools version 1.11, stream_type built Nov 11 2008 17:15:48 Attempt to determine if an input stream is Transport Stream, Program Stream, or Elementary Stream, and if the latter, if it is H.262 or H.264 (i.e., MPEG-2 or MPEG-4/AVC respectively). The mechanisms used are fairly crude, assuming that: - data is byte aligned - for TS, the first byte in the file will be the start of a NAL unit, and PAT/PMT packets will be findable - for PS, the first packet starts immediately at the start of the file, and is a pack header - if the first 1000 packets could be H.262 *or* H.264, then the data is assumed to be H.264 (the program doesn't try to determine sensible sequences of H.262/H.264 packets, so this is a reasonable way of guessing) It is quite possible that data which is not relevant will be misidentified The program exit value is: * 10 if it detects Transport Stream, * 11 if it detects Program Stream, * 12 if it detects Elementary Stream containing H.262 (MPEG-2), * 14 if it detects Elementary Stream containing H.264 (MPEG-4/AVC), * 5 if it looks like it might be PES, * 9 if it really cannot decide, or * 0 if some error occurred Files: <infile> is the file to analyse Switches: -verbose, -v Output more detailed information about how it is making its decision -quiet, -q Only output error messagesSEE ALSOThe full documentation for stream_type is maintained as a Texinfo manual. Please check http://tstools.berlios.de for more information. stream_type 1.11 November 2008 STREAM_TYPE(1)
Related Man Pages |
---|
esreport(1) - debian |
ps2ts(1) - debian |
ts_packet_insert(1) - debian |
stream(3o) - debian |
mojo::ioloop::stream(3pm) - debian |
Similar Topics in the Unix Linux Community |
---|
ts2mpa 0.1 (Default branch) |
MPGEDIT 0.74beta1 (Default branch) |
Video Encoder 264 does not install, problem with LD flags |
echo "$$date" |
File manipulation via awk |