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, 26 Jun 2025 00:07:30 -0700
Message-ID: <CAMM0M5_xC3opwRsR6Jnac357ohtfMk4FwR9tv0_1H16ihRryMQ@mail.gmail.com> (raw)
In-Reply-To: <GV1P250MB073746E19C327380D69383968F7AA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
Hi Andreas,
On Wed, Jun 25, 2025 at 5:42 PM Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
>
> Pavel Roslyy:
> > [...]
> >
> > +#define OFFSET(x) offsetof(USMDemuxContext, x)
> > +#define FLAGS AV_OPT_FLAG_AUDIO_PARAM | AV_OPT_FLAG_DECODING_PARAM
> > +static const AVOption usm_options[] = {
> > + { "hca_lowkey",
> > + "Low key used for handling CRI HCA streams", OFFSET(hca_keyl),
> > + AV_OPT_TYPE_INT64, {.i64=0}, .min = 0, .max = UINT32_MAX, .flags = FLAGS, },
> > + { "hca_highkey",
> > + "High key used for handling CRI HCA streams", OFFSET(hca_keyh),
> > + AV_OPT_TYPE_INT64, {.i64=0}, .min = 0, .max = UINT32_MAX, .flags = FLAGS, },
>
> Why are these two options instead of one? The HCA decoder also treats it
> as 64bit value.
I copied these options from libavformat/hca.c, and I'm not sure why that file
splits it, but I assume it would be best to keep the options the same across
both demuxers. And since hca.c works I figured it's best not to try to fix
it.
I'm open to any suggestions on the matter.
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".
prev parent reply other threads:[~2025-06-26 7:07 UTC|newest]
Thread overview: 7+ 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 0:42 ` Andreas Rheinhardt
2025-06-26 7:07 ` Pavel Roslyy [this message]
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=CAMM0M5_xC3opwRsR6Jnac357ohtfMk4FwR9tv0_1H16ihRryMQ@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