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


Ignore:
Timestamp:
Sep 8, 2017, 10:53:47 AM (3 years ago)
Author:
Psychonaut
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #6602, comment 2

    initial v1  
    1 I disagree that the issue is invalid, as the behaviour is at odds with what is written in the manual (which says that -metadata is used "to set metadata", not "to set metadata other than the encoder label").  If this is the intended behaviour, then the bug here is with the documentation, which should be updated.  From doing some web searches, I see I'm not the only one who has been confused by this behaviour: https://stackoverflow.com/questions/22120041/prevent-libavformat-ffmpeg-from-adding-encoder-tag-to-output-help-strippin
     1I disagree that the issue is invalid, as the behaviour is at odds with what is written in the manual (which says that `-metadata` is used "to set metadata", not "to set metadata other than the encoder label").  If this is the intended behaviour, then the bug here is with the documentation, which should be updated.  From doing some web searches, I see I'm not the only one who has been confused by this behaviour: https://stackoverflow.com/questions/22120041/prevent-libavformat-ffmpeg-from-adding-encoder-tag-to-output-help-strippin
    22
    33Incidentally, I don't think that this ''should'' be the intended behaviour.  Consider the command line in my original report, which uses `-acodec copy` on an audio file. Since FFmpeg is not changing the stream here, does it really make sense for it to add or replace the existing encoder label with its own?  This sort of thing could hinder troubleshooting when FFmpeg is used to post-process files produced by another encoder.