Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Tristan Matthews <tmatth@videolan.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/rtpdec_opus: Set duration field on Opus AVPacket
Date: Tue, 20 May 2025 14:04:35 -0400
Message-ID: <CAN8HRD=V9A6O34n9qYW-W-MFFJ_s-K0-EuDbnkmoJB3zt8-2oQ@mail.gmail.com> (raw)
In-Reply-To: <639ff2d7-ca15-4952-a6ee-420f7a2f4b56@app.fastmail.com>

Hi,

On Mon, May 19, 2025 at 8:17 PM Jonathan Baudanza <jon@jonb.org> wrote:
>
> Does anyone have feedback on this?
>
> Here are some steps to reproduce the current issue:
>
> # Start broadcasting
> ffmpeg -re -i input.opus -c:a copy -f rtp -sdp_file stream.sdp  rtp://127.0.0.1:9000
>
> # Start recording (in another terminal)
> ffmpeg -protocol_whitelist file,udp,rtp -i stream.sdp -y -c:a copy output.opus
>
> # Observe that output.opus pts starts at -960
> ffprobe -show_entries packet=pts,duration output.opus | head

This LGTM, I can confirm that the pts now starts from 0 as opposed to
-960 for ogg/opus files (and no change for e.g., mkv files).

Best,
Tristan
_______________________________________________
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-05-20 18:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-12  3:11 Jonathan Baudanza
2025-05-20  0:16 ` Jonathan Baudanza
2025-05-20 18:04   ` Tristan Matthews [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-12  2:19 [FFmpeg-devel] [PATCH] libavformat/rtpdec_opus " Jonathan Baudanza
2025-05-12  2:29 ` softworkz .

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='CAN8HRD=V9A6O34n9qYW-W-MFFJ_s-K0-EuDbnkmoJB3zt8-2oQ@mail.gmail.com' \
    --to=tmatth@videolan.org \
    --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