Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FEATURE] Cut a video (-ss) with timings non-aligned on keyframes, with minimal re-encoding
Date: Mon, 21 Jul 2025 20:39:38 +0200
Message-ID: <20250721183938.GA29660@pb2> (raw)
In-Reply-To: <15da76f4-4209-4996-9db1-bc3f96a55a0e@mtasv.net>


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

Hi

On Sun, Jul 20, 2025 at 09:54:09PM +0000, basj@gget.it wrote:
> Hi,
> 
> Out of curiosity, has there been any progress since 1 year about this topic?
> 
> Really, millions of CPU-hours are probably wasted to reencode already-perfectly-encoded content, just for cutting purposes. For example, is there a way to cut a AVI or MKV H264 video with a specific starting point and specific length, with minimal re-encoding?
> 
> When using: "ffmpeg -ss 120 -t 60 -i input.mp4 -c copy output.mp4",

> the result is often choppy or non-smooth in the first seconds,

clean patch welcome


> because the cut point doesn't necessarily coincide with a keyframe, at least on some players.
> 
> We could reencode just the beginning until the next keyframe, and then use copy codec for the rest of the video, and then concatenate, but nobody does this, it's unnecessarily complex (and I'm not even sure it works).

theres some recent talk about edit lists, maybe what you describe is
another use case of proper edit list rendering


> 
> 20 Aug 2024, 22:34, michael@niedermayer.cc wrote:
> 
> > Such signalling can be added to existing containers with little effort.
> > Iam also happy to help to add it to nut
> 
> Can you explain with a little bit more details how it would work? Thanks in advance!

Its a year since that mail you reply to, but
IIRC that just refered to that any data you want to attach you can attach in
nut. To frames, to streams, to any timespans and so on.

thx

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

Breaking DRM is a little like attempting to break through a door even
though the window is wide open and the only thing in the house is a bunch
of things you dont want and which you would get tomorrow for free anyway

[-- 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".

  reply	other threads:[~2025-07-21 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-20 21:54 basj
2025-07-21 18:39 ` Michael Niedermayer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-14 10:05 basj
2024-08-14 11:42 ` Zhao Zhili
2024-08-13  7:35 basj
2024-08-13  8:55 ` Timo Rothenpieler
2024-08-05 19:45 basj

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=20250721183938.GA29660@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /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