Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] 7.0 release
@ 2024-04-03 22:57 Michael Niedermayer
  2024-04-04  5:27 ` Jean-Baptiste Kempf
  2024-04-04  7:12 ` Anton Khirnov
  0 siblings, 2 replies; 9+ messages in thread
From: Michael Niedermayer @ 2024-04-03 22:57 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 617 bytes --]

Hi

I will try to make the 7.0 release from the release branch in the next 48h
(with some luck but easy possible it will get delayed)
i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
ATM there is one. Given that 7.0 is behind shedule it seems better to
fix them for 7.0.1. But iam happy to wait if people want that one fixed
before.

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The bravest are surely those who have the clearest vision
of what is before them, glory and danger alike, and yet
notwithstanding go out to meet it. -- Thucydides

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-03 22:57 [FFmpeg-devel] 7.0 release Michael Niedermayer
@ 2024-04-04  5:27 ` Jean-Baptiste Kempf
  2024-04-04  7:12 ` Anton Khirnov
  1 sibling, 0 replies; 9+ messages in thread
From: Jean-Baptiste Kempf @ 2024-04-04  5:27 UTC (permalink / raw)
  To: ffmpeg-devel

Hello,

On Thu, 4 Apr 2024, at 00:57, Michael Niedermayer wrote:
> I will try to make the 7.0 release from the release branch in the next 48h
> (with some luck but easy possible it will get delayed)

Please consider pulling in the Changelog modifications I suggested on the mailing list and on IRC, since this is pretty trivial.

jbk

-- 
Jean-Baptiste Kempf -  President
+33 672 704 734
https://jbkempf.com/
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-03 22:57 [FFmpeg-devel] 7.0 release Michael Niedermayer
  2024-04-04  5:27 ` Jean-Baptiste Kempf
@ 2024-04-04  7:12 ` Anton Khirnov
  2024-04-04 11:47   ` Michael Niedermayer
  1 sibling, 1 reply; 9+ messages in thread
From: Anton Khirnov @ 2024-04-04  7:12 UTC (permalink / raw)
  To: FFmpeg development discussions and patches

Quoting Michael Niedermayer (2024-04-04 00:57:39)
> Hi
> 
> I will try to make the 7.0 release from the release branch in the next 48h
> (with some luck but easy possible it will get delayed)
> i will not try to fix any issues marked as blocking 7.0 on trac, IIRC

IMO people are overly eager to mark everything as 'blocking'. Not every
bug and not every regression should be blocking, otherwise nothing ever
gets finished.

-- 
Anton Khirnov
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04  7:12 ` Anton Khirnov
@ 2024-04-04 11:47   ` Michael Niedermayer
  2024-04-04 11:50     ` James Almer
  0 siblings, 1 reply; 9+ messages in thread
From: Michael Niedermayer @ 2024-04-04 11:47 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 2155 bytes --]

On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2024-04-04 00:57:39)
> > Hi
> > 
> > I will try to make the 7.0 release from the release branch in the next 48h
> > (with some luck but easy possible it will get delayed)
> > i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
> 
> IMO people are overly eager to mark everything as 'blocking'.

No, thats not true, very few bugs are marked as blocking, we have 2837
open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
blocking maximum at any time over the last weeks


> Not every
> bug ... should be blocking,

true


> and not every regression

IMO, every regression should by default be blocking. Adding regressions
is not ok. And adding and releasing with regressions should not be the
default mode of operation.

It should be
1. Mark every regression as blocking
2. Make an effort to fix the bugs you caused and help others to fix theirs
3. If some individual bug is too difficult to fix, make a concious decission
   to move that specific bugs blocking tag to the next release
4. If teh release gets delayed too much, its possible to release with the
   regressions, because "no release" can be worse


> otherwise nothing ever
> gets finished.

Lets look at the facts
we have 151 open/new bugs marked as regressions, 3 of them are less than
8 months old.
That means 2 things

1. we have hundreads of old regressions (some maybe even arent reported)
that are not getting fixed. Thats an issue and more attention should be
brought to them.

2. we have 3 regressions that are new, I do think we can and should
handle fixing new regressions.

and 3. we arent really blocking the release, the blocking tag is flexible
and very easy to change to the next release. But it gives things more vissibility

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Into a blind darkness they enter who follow after the Ignorance,
they as if into a greater darkness enter who devote themselves
to the Knowledge alone. -- Isha Upanishad

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04 11:47   ` Michael Niedermayer
@ 2024-04-04 11:50     ` James Almer
  2024-04-04 12:29       ` Michael Niedermayer
  2024-04-04 12:46       ` Michael Niedermayer
  0 siblings, 2 replies; 9+ messages in thread
From: James Almer @ 2024-04-04 11:50 UTC (permalink / raw)
  To: ffmpeg-devel

On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
> On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
>> Quoting Michael Niedermayer (2024-04-04 00:57:39)
>>> Hi
>>>
>>> I will try to make the 7.0 release from the release branch in the next 48h
>>> (with some luck but easy possible it will get delayed)
>>> i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
>>
>> IMO people are overly eager to mark everything as 'blocking'.
> 
> No, thats not true, very few bugs are marked as blocking, we have 2837
> open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
> blocking maximum at any time over the last weeks

The bug marked as blocking has no available sample, and the commit you 
say generated the regression just moved a failure path around, so how 
can it change the reported aspect ratio of the input?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04 11:50     ` James Almer
@ 2024-04-04 12:29       ` Michael Niedermayer
  2024-04-04 12:51         ` James Almer
  2024-04-04 12:46       ` Michael Niedermayer
  1 sibling, 1 reply; 9+ messages in thread
From: Michael Niedermayer @ 2024-04-04 12:29 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]

On Thu, Apr 04, 2024 at 08:50:12AM -0300, James Almer wrote:
> On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
> > On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2024-04-04 00:57:39)
> > > > Hi
> > > > 
> > > > I will try to make the 7.0 release from the release branch in the next 48h
> > > > (with some luck but easy possible it will get delayed)
> > > > i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
> > > 
> > > IMO people are overly eager to mark everything as 'blocking'.
> > 
> > No, thats not true, very few bugs are marked as blocking, we have 2837
> > open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
> > blocking maximum at any time over the last weeks
> 
> The bug marked as blocking has no available sample, and the commit you say

https://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket4161/

I dont understand why google hasnt indexed (or finding that) though

My testcase:
-i VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpg -bitexact -vcodec libx264 -an -vsync cfr file-16:9.ts


> generated the regression just moved a failure path around, so how can it
> change the reported aspect ratio of the input?

I have not investigated it, I just see that there are various circular features
in the video that are not circular anymore

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Asymptotically faster algorithms should always be preferred if you have
asymptotical amounts of data

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04 11:50     ` James Almer
  2024-04-04 12:29       ` Michael Niedermayer
@ 2024-04-04 12:46       ` Michael Niedermayer
  1 sibling, 0 replies; 9+ messages in thread
From: Michael Niedermayer @ 2024-04-04 12:46 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 1472 bytes --]

On Thu, Apr 04, 2024 at 08:50:12AM -0300, James Almer wrote:
> On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
> > On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2024-04-04 00:57:39)
> > > > Hi
> > > > 
> > > > I will try to make the 7.0 release from the release branch in the next 48h
> > > > (with some luck but easy possible it will get delayed)
> > > > i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
> > > 
> > > IMO people are overly eager to mark everything as 'blocking'.
> > 
> > No, thats not true, very few bugs are marked as blocking, we have 2837
> > open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
> > blocking maximum at any time over the last weeks
> 
> The bug marked as blocking has no available sample, and the commit you say
> generated the regression just moved a failure path around, so how can it
> change the reported aspect ratio of the input?

Its the wrong commit, its the next commit 924a6f3cc7788e2d258348b1547a49805091ea2d

    fftools/ffmpeg_dec: override video SAR with AVCodecParameters value

    Rather than access the AVStream one.

    This is a step towards decoupling Decoder and InputStream.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04 12:29       ` Michael Niedermayer
@ 2024-04-04 12:51         ` James Almer
  2024-04-04 16:39           ` Michael Niedermayer
  0 siblings, 1 reply; 9+ messages in thread
From: James Almer @ 2024-04-04 12:51 UTC (permalink / raw)
  To: ffmpeg-devel

On 4/4/2024 9:29 AM, Michael Niedermayer wrote:
> On Thu, Apr 04, 2024 at 08:50:12AM -0300, James Almer wrote:
>> On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
>>> On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
>>>> Quoting Michael Niedermayer (2024-04-04 00:57:39)
>>>>> Hi
>>>>>
>>>>> I will try to make the 7.0 release from the release branch in the next 48h
>>>>> (with some luck but easy possible it will get delayed)
>>>>> i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
>>>>
>>>> IMO people are overly eager to mark everything as 'blocking'.
>>>
>>> No, thats not true, very few bugs are marked as blocking, we have 2837
>>> open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
>>> blocking maximum at any time over the last weeks
>>
>> The bug marked as blocking has no available sample, and the commit you say
> 
> https://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket4161/
> 
> I dont understand why google hasnt indexed (or finding that) though
> 
> My testcase:
> -i VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpg -bitexact -vcodec libx264 -an -vsync cfr file-16:9.ts
> 
> 
>> generated the regression just moved a failure path around, so how can it
>> change the reported aspect ratio of the input?
> 
> I have not investigated it, I just see that there are various circular features
> in the video that are not circular anymore

I can't find a difference between 6.1 and master:

> $ ffmpeg-6.1 -i VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpeg -bitexact -vcodec libx264 -an -vsync cfr -nostats -y file-16-9_6.1.ts
> ffmpeg version n6.1.1-20240112 Copyright (c) 2000-2023 the FFmpeg developers
>   built with gcc 13.2.0 (crosstool-NG 1.25.0.232_c175b21)
>   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libvpl --enable-openal --enable-lib
 opencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra-version=20240112
>   libavutil      58. 29.100 / 58. 29.100
>   libavcodec     60. 31.102 / 60. 31.102
>   libavformat    60. 16.100 / 60. 16.100
>   libavdevice    60.  3.100 / 60.  3.100
>   libavfilter     9. 12.100 /  9. 12.100
>   libswscale      7.  5.100 /  7.  5.100
>   libswresample   4. 12.100 /  4. 12.100
>   libpostproc    57.  3.100 / 57.  3.100
> -vsync is deprecated. Use -fps_mode
> Input #0, mpeg, from 'VR_MOVIE_GuyMartinsSpitfireBcast169 qsf lappyAspectNoChnge_extract.mpeg':
>   Duration: 00:00:09.02, start: 0.200000, bitrate: 9119 kb/s
>   Stream #0:0[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, top first), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
>     Side data:
>       cpb: bitrate max/min/avg: 9263200/0/0 buffer size: 1835008 vbv_delay: N/A
>   Stream #0:1[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 384 kb/s
> Stream mapping:
>   Stream #0:0 -> #0:0 (mpeg2video (native) -> h264 (libx264))
> Press [q] to stop, [?] for help
> [libx264 @ 000001c5022c7000] using SAR=16/15
> [libx264 @ 000001c5022c7000] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
> [libx264 @ 000001c5022c7000] profile High, level 3.0, 4:2:0, 8-bit
> Output #0, mpegts, to 'file-16-9_6.1.ts':
>   Stream #0:0: Video: h264, yuv420p(tv, top coded first (swapped)), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 25 fps, 90k tbn
>     Metadata:
>       encoder         : Lavc libx264
>     Side data:
>       cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
> [out#0/mpegts @ 000001c502242000] video:1144kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 7.177651%
> frame=  225 fps=0.0 q=-1.0 Lsize=    1226kB time=00:00:08.88 bitrate=1131.0kbits/s dup=3 drop=0 speed=18.4x
> 
> $ ./ffmpeg -i VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpeg -bitexact -vcodec libx264 -an -vsync cfr -nostats -y file-16-9_master.ts
> ffmpeg version N-114652-g7895d1860f Copyright (c) 2000-2024 the FFmpeg developers
>   built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
>   configuration: --enable-gpl --enable-nonfree --enable-libvorbis --enable-libaom --enable-libdav1d --enable-libfdk-aac --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libwebp --enable-librav1e --enable-libzimg --enable-libx264 --enable-libx265 --enable-libsvtav1 --disable-avx512 --cpu=alderlake --extra-cflags='-D_WIN32_WINNT=0xA00' --cc='ccache cc' --samples=../samples --prefix=/mingw64
>   libavutil      59. 12.100 / 59. 12.100
>   libavcodec     61.  5.100 / 61.  5.100
>   libavformat    61.  3.100 / 61.  3.100
>   libavdevice    61.  2.100 / 61.  2.100
>   libavfilter    10.  2.100 / 10.  2.100
>   libswscale      8.  2.100 /  8.  2.100
>   libswresample   5.  2.100 /  5.  2.100
>   libpostproc    58.  2.100 / 58.  2.100
> -vsync is deprecated. Use -fps_mode
> Input #0, mpeg, from 'VR_MOVIE_GuyMartinsSpitfireBcast169 qsf lappyAspectNoChnge_extract.mpeg':
>   Duration: 00:00:09.02, start: 0.200000, bitrate: 9119 kb/s
>   Stream #0:0[0x1e0]: Video: mpeg2video (Main), yuv420p(tv, top first), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
>       Side data:
>         cpb: bitrate max/min/avg: 9263200/0/0 buffer size: 1835008 vbv_delay: N/A
>   Stream #0:1[0x80]: Audio: ac3, 48000 Hz, stereo, fltp, 384 kb/s
> Stream mapping:
>   Stream #0:0 -> #0:0 (mpeg2video (native) -> h264 (libx264))
> Press [q] to stop, [?] for help
> [libx264 @ 00000236b3705520] using SAR=16/15
> [libx264 @ 00000236b3705520] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
> [libx264 @ 00000236b3705520] profile High, level 3.0, 4:2:0, 8-bit
> Output #0, mpegts, to 'file-16-9_master.ts':
>   Stream #0:0: Video: h264, yuv420p(tv, top coded first (swapped)), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 25 fps, 90k tbn
>       Metadata:
>         encoder         : Lavc libx264
>       Side data:
>         cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: N/A
> [vf#0:0 @ 00000236b3830300] Reconfiguring filter graph because video parameters changed to yuv420p(tv, bt470bg), 720x576
> [out#0/mpegts @ 00000236b35507c0] video:1144KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: 7.192419%
> frame=  225 fps=0.0 q=-1.0 Lsize=    1226KiB time=00:00:08.92 bitrate=1126.1kbits/s dup=3 drop=0 speed=19.8x
> 
> $ ffmpeg-6.1 -i file-16-9_6.1.ts -nostats -f md5 -
> ffmpeg version n6.1.1-20240112 Copyright (c) 2000-2023 the FFmpeg developers
>   built with gcc 13.2.0 (crosstool-NG 1.25.0.232_c175b21)
>   configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-w64-mingw32- --arch=x86_64 --target-os=mingw32 --enable-gpl --enable-version3 --disable-debug --disable-w32threads --enable-pthreads --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libharfbuzz --enable-libvorbis --enable-opencl --disable-libpulse --enable-libvmaf --disable-libxcb --disable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-chromaprint --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libkvazaar --enable-libaribcaption --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-librist --enable-libssh --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libvpl --enable-openal --enable-lib
 opencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --enable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --disable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags= --extra-libs=-lgomp --extra-version=20240112
>   libavutil      58. 29.100 / 58. 29.100
>   libavcodec     60. 31.102 / 60. 31.102
>   libavformat    60. 16.100 / 60. 16.100
>   libavdevice    60.  3.100 / 60.  3.100
>   libavfilter     9. 12.100 /  9. 12.100
>   libswscale      7.  5.100 /  7.  5.100
>   libswresample   4. 12.100 /  4. 12.100
>   libpostproc    57.  3.100 / 57.  3.100
> Input #0, mpegts, from 'file-16-9_6.1.ts':
>   Duration: 00:00:09.00, start: 1.480000, bitrate: 1115 kb/s
>   Program 1
>     Metadata:
>       service_name    : Service01
>       service_provider: FFmpeg
>   Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
> Stream mapping:
>   Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
> Press [q] to stop, [?] for help
> Output #0, md5, to 'pipe:':
>   Metadata:
>     encoder         : Lavf60.16.100
>   Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p(progressive), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 124416 kb/s, 25 fps, 25 tbn
>     Metadata:
>       encoder         : Lavc60.31.102 rawvideo
> MD5=84e38ecdb51a230cdded5247f096c6bf
> [out#0/md5 @ 0000022538ce3700] video:136688kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
> frame=  225 fps=0.0 q=-0.0 Lsize=       0kB time=00:00:08.96 bitrate=   0.0kbits/s speed=54.4x
> 
> $ ./ffmpeg -i file-16-9_master.ts -nostats -f md5 -
> ffmpeg version N-114652-g7895d1860f Copyright (c) 2000-2024 the FFmpeg developers
>   built with gcc 13.2.0 (Rev5, Built by MSYS2 project)
>   configuration: --enable-gpl --enable-nonfree --enable-libvorbis --enable-libaom --enable-libdav1d --enable-libfdk-aac --enable-libmp3lame --enable-libopus --enable-libvpx --enable-libwebp --enable-librav1e --enable-libzimg --enable-libx264 --enable-libx265 --enable-libsvtav1 --disable-avx512 --cpu=alderlake --extra-cflags='-D_WIN32_WINNT=0xA00' --cc='ccache cc' --samples=../samples --prefix=/mingw64
>   libavutil      59. 12.100 / 59. 12.100
>   libavcodec     61.  5.100 / 61.  5.100
>   libavformat    61.  3.100 / 61.  3.100
>   libavdevice    61.  2.100 / 61.  2.100
>   libavfilter    10.  2.100 / 10.  2.100
>   libswscale      8.  2.100 /  8.  2.100
>   libswresample   5.  2.100 /  5.  2.100
>   libpostproc    58.  2.100 / 58.  2.100
> Input #0, mpegts, from 'file-16-9_master.ts':
>   Duration: 00:00:09.00, start: 1.480000, bitrate: 1116 kb/s
>   Program 1
>     Metadata:
>       service_name    : Service01
>       service_provider: FFmpeg
>   Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
> Stream mapping:
>   Stream #0:0 -> #0:0 (h264 (native) -> rawvideo (native))
> Press [q] to stop, [?] for help
> Output #0, md5, to 'pipe:':
>   Metadata:
>     encoder         : Lavf61.3.100
>   Stream #0:0: Video: rawvideo (I420 / 0x30323449), yuv420p(progressive), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 124416 kb/s, 25 fps, 25 tbn
>       Metadata:
>         encoder         : Lavc61.5.100 rawvideo
> MD5=84e38ecdb51a230cdded5247f096c6bf
> [out#0/md5 @ 00000289cc23eee0] video:136688KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
> frame=  225 fps=0.0 q=-0.0 Lsize=       0KiB time=00:00:09.00 bitrate=   0.0kbits/s speed=  55x

Am i doing something wrong?
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: [FFmpeg-devel] 7.0 release
  2024-04-04 12:51         ` James Almer
@ 2024-04-04 16:39           ` Michael Niedermayer
  0 siblings, 0 replies; 9+ messages in thread
From: Michael Niedermayer @ 2024-04-04 16:39 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 3694 bytes --]

On Thu, Apr 04, 2024 at 09:51:50AM -0300, James Almer wrote:
> On 4/4/2024 9:29 AM, Michael Niedermayer wrote:
> > On Thu, Apr 04, 2024 at 08:50:12AM -0300, James Almer wrote:
> > > On 4/4/2024 8:47 AM, Michael Niedermayer wrote:
> > > > On Thu, Apr 04, 2024 at 09:12:04AM +0200, Anton Khirnov wrote:
> > > > > Quoting Michael Niedermayer (2024-04-04 00:57:39)
> > > > > > Hi
> > > > > > 
> > > > > > I will try to make the 7.0 release from the release branch in the next 48h
> > > > > > (with some luck but easy possible it will get delayed)
> > > > > > i will not try to fix any issues marked as blocking 7.0 on trac, IIRC
> > > > > 
> > > > > IMO people are overly eager to mark everything as 'blocking'.
> > > > 
> > > > No, thats not true, very few bugs are marked as blocking, we have 2837
> > > > open/new bugs and 1 marked as blocking. And we had maybe 2-3 marked as
> > > > blocking maximum at any time over the last weeks
> > > 
> > > The bug marked as blocking has no available sample, and the commit you say
> > 
> > https://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket4161/
> > 
> > I dont understand why google hasnt indexed (or finding that) though
> > 
> > My testcase:
> > -i VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpg -bitexact -vcodec libx264 -an -vsync cfr file-16:9.ts
> > 
> > 
> > > generated the regression just moved a failure path around, so how can it
> > > change the reported aspect ratio of the input?
> > 
> > I have not investigated it, I just see that there are various circular features
> > in the video that are not circular anymore
> 
> I can't find a difference between 6.1 and master:
[...]
> Am i doing something wrong?

This bug is cursed, be carefull

git checkout  924a6f3cc7788e2d258348b1547a49805091ea2d^
make -j32
./ffmpeg -i ~/tickets/4161/VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpg -bitexact -vcodec libx264 -an -vsync cfr file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts

git checkout  924a6f3cc7788e2d258348b1547a49805091ea2d
make -j32
./ffmpeg -i ~/tickets/4161/VR_MOVIE_GuyMartinsSpitfireBcast169\ qsf\ lappyAspectNoChnge_extract.mpg -bitexact -vcodec libx264 -an -vsync cfr file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts

ls -alF file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts
-rw-r----- 1 michael michael 1255652 Apr  4 18:32 'file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts'
-rw-r----- 1 michael michael 1255652 Apr  4 18:33  file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts

md5sum  file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts
9ec90b2497787f7d5d76aa1d34cde7eb  file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts
4361f0f20181c39a3a9b3a7f35619520  file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts

now if i play these with ffplay

./ffplay file-169-924a6f3cc7788e2d258348b1547a49805091ea2d.ts
./ffplay file-169-924a6f3cc7788e2d258348b1547a49805091ea2d^.ts

and one of these simply has the wrong aspect ratio
i never looked at anything else but i now also see in the ffplay output

Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 720x576 [SAR 16:15 DAR 4:3], 25 fps, 25 tbr, 90k tbn
vs.
Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(progressive), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 90k tbn

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Asymptotically faster algorithms should always be preferred if you have
asymptotical amounts of data

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2024-04-04 16:40 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-03 22:57 [FFmpeg-devel] 7.0 release Michael Niedermayer
2024-04-04  5:27 ` Jean-Baptiste Kempf
2024-04-04  7:12 ` Anton Khirnov
2024-04-04 11:47   ` Michael Niedermayer
2024-04-04 11:50     ` James Almer
2024-04-04 12:29       ` Michael Niedermayer
2024-04-04 12:51         ` James Almer
2024-04-04 16:39           ` Michael Niedermayer
2024-04-04 12:46       ` Michael Niedermayer

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git