Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: [FFmpeg-devel] Re: [FFmpeg-cvslog] [ffmpeg] branch master updated. 3d96d83a0a avformat/rawdec: set framerate in codec parameters
Date: Wed, 3 Dec 2025 20:32:48 -0300
Message-ID: <2fca9282-b95c-4c2c-9e36-574292f5b60a@gmail.com> (raw)
In-Reply-To: <aS5erpNIfBemCHK1@neo>


[-- Attachment #1.1.1: Type: text/plain, Size: 2080 bytes --]

On 12/2/2025 12:36 AM, Michael Niedermayer via ffmpeg-devel wrote:
> Hi Gavin
> 
> this patch breaks decoding a video with a single image:
> 
> this works and creates our single image video
> ./ffmpeg -i lena.pnm /tmp/file.m2v
> 
> this fails after the patch:
> ./ffmpeg -i /tmp/file.m2v /tmp/file.jpg -y
> 
> [image2 @ 0x60dca024f140] Cannot write more than one file with the same name. Are you missing the -update option or a sequence pattern?
> [vost#0:0/mjpeg @ 0x60dca024f3c0] Error submitting a packet to the muxer: Invalid argument
>      Last message repeated 1 times
> [out#0/image2 @ 0x60dca024f040] Error muxing a packet
> [out#0/image2 @ 0x60dca024f040] Task finished with error code: -22 (Invalid argument)
> [out#0/image2 @ 0x60dca024f040] Terminating thread with return code -22 (Invalid argument)
> [out#0/image2 @ 0x60dca024f040] video:375KiB audio:0KiB subtitle:0KiB other streams:0KiB global headers:0KiB muxing overhead: unknown
> frame=    2 fps=0.0 q=5.0 Lsize=N/A time=00:00:00.04 bitrate=N/A dup=1 drop=0 speed=0.455x elapsed=0:00:00.08
> Conversion failed!
> 
> This also breaks:
> ./ffmpeg -i https://trac.ffmpeg.org/raw-attachment/ticket/3923/frame16.h264 test.jpg
> 
> rawdec has a user parameter called framerate which is set to 25 by default.
> If your input is not 25, obviously then it should not be set to 25.
> 
> Your change does not achive a fallback of 25 if it cannot be determined,
> as clearly shown in the example above where our single frame is turned into
> 2 frames, clearly showing there is a new inconsistancy.
> 
> I suggest to revert this patch (to avoid creating more bugs by a rushed attempt to
> fix this) and attempt to fix your file by setting the user framerate parameter correctly
> 
> Independant of this, making it autodetect would be cool, yes, i agree
> but i think we need more time, testing and no regressions

As the committer, I'm ok reverting it if it introduces regressions, but 
we should work towards having this fixed considering many of the fate 
changes were correct.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

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

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-12-03 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251128005559.1126A690194@ffbox0-bg.ffmpeg.org>
2025-12-02  3:36 ` Michael Niedermayer via ffmpeg-devel
2025-12-03 23:32   ` James Almer via ffmpeg-devel [this message]
     [not found] <20251126095910.2B49E68EB72@ffbox0-bg.ffmpeg.org>
2025-12-02  2:28 ` [FFmpeg-devel] Re: [FFmpeg-cvslog] [ffmpeg] branch master updated. 92f2f9ea5c avcodec/d3d12va_encode: D3D12 AV1 encoding support Michael Niedermayer via ffmpeg-devel
2025-12-02 12:07   ` Nicolas George via ffmpeg-devel
2025-12-03 23:13     ` Michael Niedermayer via ffmpeg-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2fca9282-b95c-4c2c-9e36-574292f5b60a@gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=jamrial@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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