Changes between Version 8 and Version 9 of Ticket #4947, comment 2


Ignore:
Timestamp:
Jan 30, 2016, 1:39:14 PM (5 years ago)
Author:
wader8
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4947, comment 2

    v8 v9  
    33In practise the issue arises when a ffmpeg parameter is mistakenly used in the place where an avcodec parameter should be used, however, it also applies to any invalid characters that the avcodecs do not recognize, so techincally it has nothing to do with ffmpeg's own parameters, nor with avcodec's parameters, but I believe it does have to do with ffmpeg error level system in some fashion, as the codec most probably isn't running the whole console application. However I may be wrong on this, it has to be analyzed to determine the correct component this ticket applies to.
    44
    5 In x265 codec the message for an invalid parameter is simply "'''''unknown parameter'''''", however in the case of the x264 codec it is clearly labeled as an "error" by the original developers and the message reads "'''''error parsing option'''''", however neither are treated as actual errors by FFMPEG core and are treated as if they were a warning and so the process continues with default param values, which in a real situation may not be practical as the user who is originally trying to define such custom values for these params which have to be manually written, may want to have them customized to his/her precise liking, so the continuation of the encoding/decoding process may not be in any benefit in such cases.
    6 The user may go AFK or think that everything is okay as the warning may not be seen if the console output is greater because the console window auto-scrolls away from these warnings which usually are at the very beginning. The user may come back later or later realize only to find out the results are not to his liking, and would have to redo the whole process, losing time and effort.
     5In x265 codec the message for an invalid parameter is simply "'''''unknown parameter'''''", however in the case of the x264 codec it is clearly labeled as an "error" by the original developers and the message reads "'''''error parsing option'''''", however neither are treated as actual errors by FFMPEG core and are treated as if they were a warning and so the process continues with default param values, which in a real situation may not be practical as the user who is originally trying to define such custom values for these params, which have to be manually written, may want to have them customized to his/her precise liking, so the continuation of the encoding/decoding process may not be in any benefit in such cases.
     6The user may go AFK or think that everything is okay, as the warning may not be seen if the console output is greater because the console window auto-scrolls away from these warnings which usually are at the very beginning. The user may only later realize the results are not to his liking, and would have to redo the whole process, losing time and effort.
    77
    88Treating these avcodec messages as global ffmpeg errors (which stop all operations) instead of warnings would fix this issue instantly and avoid any time being lost and furthermore would avoid confusion with less experienced users, which has been noticed in various help&support channels. This fix will therefore also lessen the amount of beginner-level support inquiries and free up time from bigger issues as this is a very simple one.