From: Desmond Liu via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Desmond Liu <desmond.liu@netint.ca>
Subject: [FFmpeg-devel] Re: [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders
Date: Wed, 27 Aug 2025 23:19:11 +0000
Message-ID: <YT2PR01MB66732436DDF007F3F34B5954FE38A@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJgjuozwGTKwO_t2K7exsHT_Fe1SkaN_+iO7mFo9Uz0vzAQyZg@mail.gmail.com>
Hi Pavel,
> I've cloned the netint ffmpeg fork from
> https://github.com/netintsteven/NI_FF_upstream/tree/upstream
> - looks like it was last updated on June 30th, 2025 -- about 2 months
> behind ffmpeg master
> - libavcodec/nicodec.h includes ni_device_api.h, so
> https://github.com/NETINT-Technologies/netint_libxcoder is a prerequisite
> ... that probably should be mentioned in the ffmpeg fork README.md
A lot of ffmpeg functionality is achieved through external libraries and
header files (e.g. qsv, vulkan, vmaf just to name a few).
There does not seem to be any centralized document in the ffmpeg repo
on where to find external libraries. The README.md file in the ffmpeg
repo doesn't seem appropriate.
If you could point to a place, I'd be happy to make the change.
Regards,
Desmond Liu
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-08-27 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 17:41 [FFmpeg-devel] " Desmond Liu
2025-07-17 20:19 ` Pavel Koshevoy
2025-07-18 0:57 ` Desmond Liu
2025-07-18 2:59 ` Pavel Koshevoy
2025-07-22 21:26 ` Desmond Liu
2025-08-26 21:47 ` [FFmpeg-devel] " Pavel Koshevoy via ffmpeg-devel
2025-08-27 16:45 ` Pavel Koshevoy via ffmpeg-devel
2025-08-27 23:32 ` Desmond Liu via ffmpeg-devel
2025-08-27 23:19 ` Desmond Liu via ffmpeg-devel [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=YT2PR01MB66732436DDF007F3F34B5954FE38A@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM \
--to=ffmpeg-devel@ffmpeg.org \
--cc=desmond.liu@netint.ca \
/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