Changes between Version 3 and Version 4 of Ticket #5931, comment 4


Ignore:
Timestamp:
Jun 30, 2018, 4:12:52 AM (12 months ago)
Author:
keymapper
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5931, comment 4

    v3 v4  
    1 Why was this set to 'wontfix'? If there are any further infos/details needed to get this fixed I'd be happy to provide. I have been running into this issue a bunch recently on the latest build (ffmpeg-20180619-a990184) and it is a pretty nasty bug, making features that are 95% complete basically useless due to unreliability/inaccuracy. PNGs end up with anywhere from 1 to 20 empty pixels on the right and there's no way to know which empty pixels are due to the bug and which are due to actual silence in the input audio. Does anyone know any way to work around this bug, like if there is some magic number for the .png dimensions that makes ffmpeg happy, or some way to calculate how many of the blank pixels are erroneous (is it a function of the length of the audio)?
     1Why was this set to 'wontfix'? If there are any further infos/details needed to get this fixed I'd be happy to provide. I have been running into this issue a bunch recently on the latest build (ffmpeg-20180619-a990184) and it is a pretty nasty bug, making features that are 95% complete basically useless due to unreliability/inaccuracy. PNGs end up with anywhere from 1 to 300+ empty pixels on the right and there's no way to know which empty pixels are due to the bug and which are due to actual silence in the input audio. Does anyone know any way to work around this bug, like if there is some magic number for the .png dimensions that makes ffmpeg happy, or some way to calculate how many of the blank pixels are erroneous (is it a function of the length of the audio)?