Re: [FFmpeg-devel] [PATCH 2/2] avformat/tee: fix multiple bsfs in tee

2025-06-26 Thread Marvin Scholz
On 25 Jun 2025, at 11:56, Nicolas George wrote: > Marvin Scholz (HE12025-06-25): >> Since 155508c6e925f4f2f5e77087a7e1925b3de735ff specifying multiple >> bsfs for different streams was broken: >> >> "[bsfs/a=h264_metadata:bsfs/v=h264_metadata]out.mp4|..." >> >> This incorrectly only parsed the

Re: [FFmpeg-devel] [PATCH 2/2] avformat/tee: fix multiple bsfs in tee

2025-06-25 Thread Nicolas George
Marvin Scholz (HE12025-06-25): > Since 155508c6e925f4f2f5e77087a7e1925b3de735ff specifying multiple > bsfs for different streams was broken: > > "[bsfs/a=h264_metadata:bsfs/v=h264_metadata]out.mp4|..." > > This incorrectly only parsed the first bsfs specification. The reason > for this is that th

[FFmpeg-devel] [PATCH 2/2] avformat/tee: fix multiple bsfs in tee

2025-06-24 Thread Marvin Scholz
Since 155508c6e925f4f2f5e77087a7e1925b3de735ff specifying multiple bsfs for different streams was broken: "[bsfs/a=h264_metadata:bsfs/v=h264_metadata]out.mp4|..." This incorrectly only parsed the first bsfs specification. The reason for this is that the dictionary is modified in the iterator, hen