Re: [FFmpeg-devel] Matroska and output_ts_offset

2022-08-29 Thread Andreas Rheinhardt
Peter Zebühr: >> On 29 Aug 2022, at 16:37, Andreas Rheinhardt >> wrote: >> >> The Matroska muxer is buggy wrt. to the ts_offset relating to codec >> delay. You can see it in lines 1839-1841 which are commented out. >> Commenting them out happened in commit >> 82e4f39883932c1b1e5c7792a1be12dec6ab6

Re: [FFmpeg-devel] Matroska and output_ts_offset

2022-08-29 Thread Peter Zebühr
> On 29 Aug 2022, at 16:37, Andreas Rheinhardt > wrote: > > The Matroska muxer is buggy wrt. to the ts_offset relating to codec > delay. You can see it in lines 1839-1841 which are commented out. > Commenting them out happened in commit > 82e4f39883932c1b1e5c7792a1be12dec6ab603d, merging the lib

Re: [FFmpeg-devel] Matroska and output_ts_offset

2022-08-29 Thread Andreas Rheinhardt
Peter Zebühr: > Hello, > > I noticed the other day that if I try to mux opus in webm with a timestamp > offset set I don't get the expected timestamps out on my packets. Example: > > ffmpeg -f lavfi -i "sine=frequency=1000:duration=60" -output_ts_offset > 200ms -c:a libopus sine_200ms_off

[FFmpeg-devel] Matroska and output_ts_offset

2022-08-29 Thread Peter Zebühr
Hello, I noticed the other day that if I try to mux opus in webm with a timestamp offset set I don't get the expected timestamps out on my packets. Example: ffmpeg -f lavfi -i "sine=frequency=1000:duration=60" -output_ts_offset 200ms -c:a libopus sine_200ms_offset.webm Now if I inspect