Changes between Initial Version and Version 1 of Ticket #4588, comment 2


Ignore:
Timestamp:
Jun 3, 2015, 12:24:42 AM (4 years ago)
Author:
wolfgang
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4588, comment 2

    initial v1  
    11As far as I understand it, "SMPTE 302m" embeds some kind of non-MPEG-codec into the MPEG-TS, using a private stream. So the problem occurs, as soon as the {{{avformat_find_stream_info()}}} finds, that the stream already has some codec id assigned.
    22
    3 Would it be a valid course of action, if the ffmpeg command line tool reassigned all private streams ({{{AVMEDIA_DATA}}}, {{{AV_CODEC_ID_BIN_DATA}}}) to be of unknown content ({{{AVMEDIA_UNKNOWN}}}, {{{AV_CODEC_ID_NONE}}}), and reset the {{{AVStream::probe}}} value, to indicate, that the stream should be tested for a usable codec?
     3Would it be a valid course of action, if the ffmpeg command line tool reassigned all private streams ({{{AVMEDIA_TYPE_DATA}}}, {{{AV_CODEC_ID_BIN_DATA}}}) to be of unknown content ({{{AVMEDIA_TYPE_UNKNOWN}}}, {{{AV_CODEC_ID_NONE}}}), and reset the {{{AVStream::request_probe}}} value, to indicate, that the stream should be tested for a usable codec?
    44
    55That way, users of libavformat would be dignified with correct stream identification for MPEG-TS and users of the ffmpeg tool could still use their "SMPTE 302m" files.