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


Ignore:
Timestamp:
Jan 29, 2019, 10:41:03 PM (8 years ago)
Author:
barsnick

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #7695, comment 2

    initial v1  
    77On the other hand, the report is correct in so far that it does not seem possible to give ffmpeg command line options meant for e.g. protocols triggered "underneath". I.e. ffmpeg launches with a file protocol input which promotes to hls, but this in turn may trigger http protocol segments, yet ffmpeg will refuse to accept http protocol options on the command line.
    88
    9 Some ''muxers'' have ways of achieving this: The `tee` muxer has a special syntax, the `segment` muxer has "`-segment_format_options`", the `dash` muxer has "`-format_options`", the fifo muxer has "`-format_opts`". I don't see this for the `hls` demuxer (which is used in this example) though. The `hls` demuxer ''does'' expose some http protocol options via its own proxy options ("`-http_persistent`", "`-http_multiple`"), but "`-headers`" does not belong to those.
     9Some ''muxers'' have ways of achieving this: The `tee` muxer has a special syntax, the `segment` muxer has "`-segment_format_options`", the `dash` muxer has "`-format_options`", the `fifo` muxer has "`-format_opts`". I don't see this for the `hls` demuxer (which is used in this example) though. The `hls` demuxer ''does'' expose some http protocol options via its own proxy options ("`-http_persistent`", "`-http_multiple`"), but "`-headers`" does not belong to those.
    1010
    1111So, this may actually be a feature request...