Changes between Version 2 and Version 3 of Ticket #9307
- Timestamp:
- Jun 28, 2021, 4:21:41 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #9307
- Property Summary Seeking to the start of some files produces noise spike → Decoding of Opus audio with missing packets produces produces noise spike
-
Ticket #9307 – Description
v2 v3 1 1 Summary of the bug: 2 With some files, seeking to the start produces a noise spike. 2 OLD: With some files, seeking to the start produces a noise spike. 3 4 UPDATED: Output levels from Opus decoding can vary greatly if some packets at the start are missing, either because they weren't included in the stream or because ffplay seeks to a video keyframe that comes after those packets. 5 3 6 4 7 In the past, I found this was the case with a slight change in volume when encoding audio. So, for example, the filter "volume=0.8734" would produce a 'bugged' file that would cause this noise spike, while "volume=0.8733" would not. I waited to report it until I could use a more recent version of ffmpeg and ffplay.


