Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] SW's Patchsets Overview
Date: Mon, 14 Apr 2025 15:44:53 +0000
Message-ID: <BN0P223MB035863999F16ADBD0C269D57BAB32@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB0365066DF0B56E60A0E2C4E9BAAF2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

Hello,


this is a follow-up to the list of patches I had posted recently.

From those, I would like to push the following by the end of the week:


avformat/hls demuxer: Add WebVTT subtitle support

GitHub:    https://github.com/ffstaging/FFmpeg/pull/53
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=13981


avcodec/dvbsubdec: Fix conditions for fallback to default resolution

GitHub:    https://github.com/ffstaging/FFmpeg/pull/57/files
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14038
Note:      Pathwork builds were all broken at that time


avformat/dump: Print stream start offsets for input streams

GitHub:    https://github.com/ffstaging/FFmpeg/pull/58
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14039


Improve HWDeviceContext logging

GitHub:    https://github.com/ffstaging/FFmpeg/pull/61
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14206


=> Please let me know about any objections or when you need more time 
   to look at any of them.


------------------

These are on-hold:



avformat/id3v2: Support null-separated multi-value properties

GitHub:    https://github.com/ffstaging/FFmpeg/pull/54
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14046

=> Waiting for response from Michael as he has a patch in the same area


avutil/log: Add log flag to control printing of memory addresses

GitHub:    https://github.com/ffstaging/FFmpeg/pull/59
Patchwork: https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=14094

=> I think it would be good to put this up for a vote. Not the patch per-se
   but the question of what should be the default. Even though this is 
   nothing like an important architectural decision, it still affects what
   we all are seeing when running FFmpeg CLI, so it should be backed by 
   a majority (which will also get me out of the line 😊)


Thanks,
sw
_______________________________________________
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".

  parent reply	other threads:[~2025-04-14 15:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  1:07 softworkz .
2025-04-02 19:45 ` Marton Balint
2025-04-02 20:18   ` softworkz .
2025-04-06 21:04     ` Marton Balint
2025-04-06 21:12       ` softworkz .
2025-04-08 22:24         ` Michael Niedermayer
2025-04-08 22:45           ` softworkz .
2025-04-12  1:43             ` Michael Niedermayer
2025-04-07  9:14       ` Nicolas George
2025-04-07  9:47         ` softworkz .
2025-04-08 22:53         ` Marton Balint
2025-04-08 23:31           ` softworkz .
2025-04-09  8:33           ` Nicolas George
2025-04-14 15:44 ` softworkz . [this message]
2025-04-18  5:58   ` 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=BN0P223MB035863999F16ADBD0C269D57BAB32@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.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