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 <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/vvcdec: fix seeking for open GOP
Date: Sat, 3 Feb 2024 09:21:26 -0300
Message-ID: <b505bccd-fc08-4cd1-8fb3-dd48521a2b2f@gmail.com> (raw)
In-Reply-To: <CAFXK13dwxDZfK=xhUcdoo8gazK0oNACV9N2sWtJ9cck3JoPwpQ@mail.gmail.com>

On 2/3/2024 9:17 AM, Nuo Mi wrote:
> On Sat, Feb 3, 2024 at 7:54 PM James Almer <jamrial@gmail.com> wrote:
> 
>> On 2/3/2024 7:34 AM, Nuo Mi wrote:
>>> how to reproduce:
>>> wget https://media.xiph.org/video/derf/y4m/students_cif.y4m
>>> vvencapp --input students_cif.y4m --preset faster --output students.266
>>> MP4Box -add students.266:fps=30000/1001:par=12:11 -new students.mp4
>>
>> Can't you do this with ffmpeg? mp4 muxing support was added recently,
>> and we have a parser to find frame boundaries from raw bitstreams.
>>
>> Yes, we can
> ffmpeg -i students.266 -c:v copy students.mp4
> But the reporter used the mp4box
> see:  https://github.com/ffvvc/FFmpeg/issues/190#issuecomment-1924169765

That's ok, just wanted to know why not use ffmpeg for this. If it 
couldn't remux the file, then that'd be something we should fix.
_______________________________________________
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:[~2024-02-03 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 10:34 Nuo Mi
2024-02-03 11:54 ` James Almer
2024-02-03 12:17   ` Nuo Mi
2024-02-03 12:21     ` James Almer [this message]
2024-02-03 13:19       ` Nuo Mi
2024-02-05 14:16 ` Nuo Mi

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=b505bccd-fc08-4cd1-8fb3-dd48521a2b2f@gmail.com \
    --to=jamrial@gmail.com \
    --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