From: Tudor Zaharia <tudor@swisstch.com>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Consulting enquiry: H264 nvenc for libwebrtc
Date: Thu, 4 Aug 2022 12:22:08 +0000
Message-ID: <DB6PR0902MB2053F85CB33C27972F9FBA41DF9F9@DB6PR0902MB2053.eurprd09.prod.outlook.com> (raw)
Dear FFmpeg development community,
My name is Tudor Zaharia and I am sending this message after reading this page: https://ffmpeg.org/consulting.html
For a project that I am implementing, I would like to have H264 hardware encoding capabilities in libwebrtc through Nvidia's nvenc. My understading is that libwebrtc is already using FFmpeg for hardware decoding, but not for encoding. From what I know, the code that uses the OpenH264 encoder should be adapted to use the nvenc encoder (already contained in libwebrtc's source through FFmpeg). I am only interested in a solution that works on Linux, which I believe is a CUDA implementation of the encoder. I believe such implementations do exist - since some browsers have it, but I guess due to licensing issues, I couldn't find any.
Is this in your area of expertise and would have an interest in implementing it?
If yes, can you give me a price and time estimate? If you already have knowledge of an existing implementation that you can directly provide me for a fee, all the better.
Best regards,
Tudor Zaharia
_______________________________________________
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 reply other threads:[~2022-08-04 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 12:22 Tudor Zaharia [this message]
2022-08-04 12:25 ` Tudor Zaharia
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=DB6PR0902MB2053F85CB33C27972F9FBA41DF9F9@DB6PR0902MB2053.eurprd09.prod.outlook.com \
--to=tudor@swisstch.com \
--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