From: Pavel Roslyy <roslypav-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] libavformat/usmdec: add support for HCA stream decryption
Date: Thu, 3 Jul 2025 15:28:32 -0700
Message-ID: <CAMM0M59BjmOUWLQATwPRD00uRcYE3bpF=OqrO_E3khQPYmP=Hg@mail.gmail.com> (raw)
In-Reply-To: <20250627213246.GH29660@pb2>
Hello,
After experimenting, I think it would be a better idea to move the hca_*
options into libavcodec/hcadec.c rather than duplicating them into the usm
demuxer. Before I try to submit patches that do this I have some questions.
1) I plan on removing the hca_* options from libavformat/hca.c and placing
them into libavcodec/hcadec.c. Am I correct in assuming that this would be
considered an API deprecation and would require doing deprecation guards in
libavformat/hca.c?
2) If considered an API deprecation, would it make sense to consolidate
hca_lowkey and hca_highkey into a single hca_key option that takes 16 bits of
hexadecimal string (like most other decryption key options) rather than
keeping the options as integer hca_highkey / hca_lowkey in
libavcodec/hcadec.c?
Regards,
Pavel Roslyy
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-03 22:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 6:19 Pavel Roslyy
2025-06-24 6:25 ` Pavel Roslyy
2025-06-25 22:12 ` Michael Niedermayer
2025-06-25 22:40 ` Michael Niedermayer
2025-06-26 7:04 ` Pavel Roslyy
2025-06-26 21:08 ` Michael Niedermayer
2025-06-27 19:20 ` Pavel Roslyy
2025-06-27 21:32 ` Michael Niedermayer
2025-07-03 22:28 ` Pavel Roslyy [this message]
2025-07-04 1:40 ` Michael Niedermayer
2025-06-26 0:42 ` Andreas Rheinhardt
2025-06-26 7:07 ` Pavel Roslyy
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='CAMM0M59BjmOUWLQATwPRD00uRcYE3bpF=OqrO_E3khQPYmP=Hg@mail.gmail.com' \
--to=roslypav-at-gmail.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