#nvenc — Public Fediverse posts

Comment on this video (which us not shown on my Fedi instance, yay federation!)

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#h265 #av1 #svtav1 #nvidia #nvenc #intelarc

boredsquirrel @[email protected] · 2026-03-12 · 03:44 UTC

Comment on this video (which us not shown on my Fedi instance, yay federation!)

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#h265 #av1 #svtav1 #nvidia #nvenc #intelarc

boredsquirrel @[email protected] · 2026-03-12 · 03:44 UTC

Comment on this video (which us not shown on my Fedi instance, yay federation!)

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

#h265 #av1 #svtav1 #nvidia #nvenc #intelarc

boredsquirrel @[email protected] · 2026-03-12 · 03:44 UTC

Comment on this video (which us not shown on my Fedi instance, yay federation!)

I cannot believe that that GPU is not usable for video work. That is what GPUs are made for!

Poorly, there are a few caveats:
- there are always more DEcoders supported than ENcoders. I guess not being able to play a video (it would play but be less efficiently decoded on the CPU) is worse than being bound to #h265 instead of #av1 for recording.
- thus it makes sense that GPUs generally work flawlessly for gaming, as that is just displaying videos (or rendering content, which is kinda different, no idea why video codecs are more difficult than rendering methods)
- for every video format out there exists an encoder. If you use software rendering (on the CPU), you can use ANYTHING. Like encode to modern (and free!) AV1 using #svtav1 on any old CPU.
- if you want to encode videos on a GPU, you need drivers, but also a different encoder. On #NVIDIA you use #NVENC (NVidia ENCoder), for example nvenc_x265 for h265/HEVC videos. On #IntelArc (and afaik AMD GPUs), you use the #QSV (quick sync video) library which builds on top of #VAAPI, which is open source. So you can encode to AV1 using qsv_av1 for example.

What encoders are supported depends on the GPU a lot. Intel Arc seems to have supported the free, efficient and future-proof AV1 codec the earliest, but also the older free codecs VP9 and VP8 (also used in webm), like in a GPU I recently bought used. My older NVIDIA GPU only supports H265, which is proprietary and often less efficient than AV1 (not always, video codecs are black magic).

As OBS can use your GPU for video capture (encoding), the issue is purely in software support.

I only have experience with #ffmpeg for re-encoding videos, but that is also in many video editing tools. Try if you can get them somehow.

For NVIDIA I needed the latest proprietary drivers (#NixOS makes this extremely easy, can recommend) and ffmpeg, nvenc worked out of the box.

For intel Arc I used the regular drivers included in the kernel, but after adding the QSV runtime to my "hardware.graphics.extraPackages" I needed to recompile the entire kernel. Using a #longterm kernel (currently 6.18) makes this more viable... longterm XD.

https://crazy.macer.life/moving-to-freebsd-jails-bhyve-part-7-jellyfin-in-a-jail-with-hw-transcoding/

#videoediting #shotcut #kdenlive #microsoftsurface #longterm #nixos

Macer @[email protected] · 2025-12-26 · 21:50 UTC

can someone please help me with #jellyfin and #freebsd and #nvenc ? I managed to finally get ffmpeg working but i can't seem to find a way to get jellyfin for freebsd to call nv-sglrun in order to run ffmpeg. i have tried all types of ways to do it but it's almost as though it's hard coded into jellyfin to use the ffmpeg bin and only the ffmpeg bin.

#jellyfin #freebsd #nvenc

Mika @[email protected] · 2025-04-19 · 05:34 UTC

TIL #AMD has #GPU (s) that have no hardware encoding capabilities whatsoever, i.e. their #RX6400. Yikes? Be careful when buying GPUs from AMD, I suppose.

It's one thing when people compare AMD GPUs with #NVIDIA's saying AMD's encoding prowess is inferior vs something like #NVENC, but to literally be unable to hardware transcode H264, HEVC, etc. as a modern GPU is insanely hilarious seeing that it's something even ancient GPUs and even iGPUs are capable of.

AMD CPUs? Solid, my last #Intel CPU was literally 7th gen - have gone through at least ~5 CPU upgrades since then. AMD GPUs? Stayed away from them and will continue to do so, even as a #Linux user. NVIDIA GPUs have been perfectly fine for me on #X11 before, and is perfectly usable (+ continually improving) on #Wayland now - Intel Arc GPUs are also affordable and perfect for my #homelab/servers.

🔗 https://github.com/GPUOpen-LibrariesAndSDKs/AMF/wiki/GPU-and-APU-HW-Features-and-Support#amd-gpu-multimedia-hardware-features

#amd #rx6400 #nvidia #nvenc #intel #linux

Habr @[email protected] · 2025-03-27 · 16:22 UTC

Как улучшить качество аниме до 4K без ИИ: руководство по использованию HVENC и Anime4K

Любимые аниме из детства выглядят размыто на современных 4K-экранах? Есть решение! Узнайте, как апскейлить видео до 4K с помощью FFmpeg , шейдера Anime4K и аппаратного ускорения NVIDIA . Без сложных ИИ — только простые шаги и доступные инструменты. Читайте статью и вдохните новую жизнь в свои сериалы!

#апскейл #4k #аниме #ffmpeg #libplacebo #Anime4K #nvidia #CUVID #nvenc

#nvenc #cuvid #nvidia #anime4k #libplacebo #ffmpeg

Habr @[email protected] · 2025-03-27 · 16:22 UTC

Как улучшить качество аниме до 4K без ИИ: руководство по использованию HVENC и Anime4K

Любимые аниме из детства выглядят размыто на современных 4K-экранах? Есть решение! Узнайте, как апскейлить видео до 4K с помощью FFmpeg , шейдера Anime4K и аппаратного ускорения NVIDIA . Без сложных ИИ — только простые шаги и доступные инструменты. Читайте статью и вдохните новую жизнь в свои сериалы!

#апскейл #4k #аниме #ffmpeg #libplacebo #Anime4K #nvidia #CUVID #nvenc

#nvenc #cuvid #nvidia #anime4k #libplacebo #ffmpeg

Habr @[email protected] · 2025-03-27 · 16:22 UTC

Как улучшить качество аниме до 4K без ИИ: руководство по использованию HVENC и Anime4K

Любимые аниме из детства выглядят размыто на современных 4K-экранах? Есть решение! Узнайте, как апскейлить видео до 4K с помощью FFmpeg , шейдера Anime4K и аппаратного ускорения NVIDIA . Без сложных ИИ — только простые шаги и доступные инструменты. Читайте статью и вдохните новую жизнь в свои сериалы!

#апскейл #4k #аниме #ffmpeg #libplacebo #Anime4K #nvidia #CUVID #nvenc

#nvenc #cuvid #nvidia #anime4k #libplacebo #ffmpeg

Habr @[email protected] · 2025-03-27 · 16:22 UTC

Как улучшить качество аниме до 4K без ИИ: руководство по использованию HVENC и Anime4K

Любимые аниме из детства выглядят размыто на современных 4K-экранах? Есть решение! Узнайте, как апскейлить видео до 4K с помощью FFmpeg , шейдера Anime4K и аппаратного ускорения NVIDIA . Без сложных ИИ — только простые шаги и доступные инструменты. Читайте статью и вдохните новую жизнь в свои сериалы!

#апскейл #4k #аниме #ffmpeg #libplacebo #Anime4K #nvidia #CUVID #nvenc

#апскейл #4k #аниме #ffmpeg #libplacebo #anime4k

:nfld_tri: 🇨🇦 CowMan 🇪🇺 🇺🇦 🇲🇽 @[email protected] · 2025-01-19 · 18:35 UTC

Bah. Looks like have hit the limits of the P400’s NVENC transcoder; hit rates below 1.00x for first time... it's put in a few years.

The P400 RAM usage is about 1 gb with 4 streams, but 100% on encode/decode. The P400 has 1 Pascal (6th gen) nvenc block and 2gb RAM.

Have an Arc A380 coming in now.

A380 should be able to handle quite a bit more, has two MFX engines (quicksync) & 6gb RAM.

Time will tell.

[ #P400 #A380 #nvenc #qsv #IntelArc #transcoding ]

#p400 #a380 #nvenc #qsv #intelarc #transcoding

Stefano Zacchiroli @[email protected] · 2024-12-08 · 13:09 UTC

TIL about #Nvidia #NVENC and its support in Handbrake: https://handbrake.fr/docs/en/latest/technical/video-nvenc.html . Possibly the first time I'm actually happy about having an Nvidia graphics card on my Linux laptop.

#nvidia #nvenc

Bob Dendry has moved! @[email protected] · 2024-08-30 · 11:44 UTC

Question is how will the whole recording/editing workflow go on Linux. The main sticking point for me had been the lack of #NVENC AV1 support in #OBS which is obviously now not a problem.

#DavinciResolve is a wildcard. I know it doesn't support mp4 and/or AAC audio in Linux but I've tried my best to adapt my workflow so that isn't an issue anymore (using .mkv with PCM), so I'm *hoping* everything will be fine, but we'll need to see how it turns out.

#nvenc #obs #davinciresolve

Bob Dendry has moved! @[email protected] · 2024-08-30 · 11:36 UTC

On a whim today I decided to give #Linux a go again on my main rig.

Can I just say that the #Fedora #Bluefin makes the process of installing, configuring and using Linux infinitely easier if you don't want or need to do large amounts of manual configuration of your install - it just works (the #Nvidia specific image is a big plus as well).

Even got #NVENC #AV1 working on #OBS with a minimal amount of fuss (haven't tested it out yet though).

Next stop is getting my GoXLR fully working.

#linux #fedora #bluefin #nvidia #nvenc #av1

Krutonium:// @[email protected] · 2024-08-18 · 13:00 UTC

Hey #Nvidia I want to use #nvenc on the #open driver. Please fix.

#nvidia #nvenc #open

Linux ✅ @[email protected] · 2024-07-21 · 10:21 UTC

🎞️ OBS Studio for Linux getting some vital last pieces reaching on par with Windows (in news recently to cause havoc worldwide again) :afire:

Many creators have stated they'll switch to Linux altogether when OBS features match. That time is nearing 🙂

◉30.2 comes with native NVENC AV1 encoding on Linux
◉Before a copy was used for encoding (cost of performance)
◉Before - OBS copied VRAM to RAM to VRAM to RAM every frame
◉Now: just VRAM to RAM once

►https://obsproject.com/download#linux

#OBS #Linux #NVENC

#obs #linux #nvenc

Marcus "MajorLinux" Summers @[email protected] · 2024-07-14 · 14:00 UTC

Going to make sure I update this.

OBS Studio 30.2 is out now with native NVENC encode for Linux, shared texture support

https://www.gamingonlinux.com/2024/07/obs-studio-302-is-out-now-with-native-nvenc-encode-for-linux/

#OBS #OBSStudio #Linux #NVENC #Windows #Mac #Streaming #Tech #Update #ContentCreation

#obs #obsstudio #linux #nvenc #windows #mac

Mika @[email protected] · 2024-01-28 · 12:26 UTC

Made this post a while back about #gaming (and related things) on #Linux compared to #Windows. TLDR; gaming performance has been fine, with some minor quirks (at least on #NVIDIA) such as #games performing better somehow without #DLSS than with (which is fine by me) - the only "issue" had to do with #recording/#streaming while also running a #game.

I did some further digging and honestly, I don't think there's much issue/performance hit with gaming while recording on #OBS, using NVIDIA #NVENC. I haven't really done proper testing, but it honestly has been fine. My games hit 144FPS, or close at 1440p Max settings pretty easily w my 3080 Ti. I record them by simply adding a "Window Capture" scene and selecting the appropriate #game window, that's it. People recommended "obs-vkcapture" on my last post, and that's been nice too - with that plugin, you only need a single "Game Capture" scene on OBS, and add a launch param to the game's properties on #Steam. Once you launch the game, OBS will immediately be "hooked" to the game and ready to record. People mentioned that doing it this way should prolly be more performant/efficient, but from my limited testing, both ways seem fine.

One thing I forgot to mention though was #Voicemeeter. Voicemeeter's a really freaking neat audio tool on Windows that allowed you to essentially have a virtual audio interface. It does plenty of things, but what I and most people use it for is to split several application audio into separate audio tracks i.e. #Discord is on one audio track, #Firefox on another, #Spotify on another, and so on. This was essential as it allowed me to record my games while being on a Discord call, or have #YouTube playing and not have any audio but the game's to be included in the recording using OBS.

I did a quick search and found a plugin called "obs-pipewire-audio-capture" that solved this need. If your distro is already using #Pipewire for audio (which I think most/all distro do for the past few years), enabling this plugin is as easy as installing the plugin by downloading it from their #GitHub repo and adding it to OBS's plugins folder. After a restart, you can now add multiple audio tracks as scenes to OBS for each application i.e. Spotify, Discord, Games, etc. and enable/disable any of these tracks accordingly for your recording.

All in all, no issues at all recording while gaming/anything. My only issue now has to do with streaming games to friends while gaming i.e. through Discord. Discord does not yet support this (with audio) on Linux, but there's a custom Discord client that's able to do this called "discord-screenaudio" though with a sizeable performance hit if you're going to be streaming anything intensive such as games - anything else (that isn't intensive) like #Plex, #Netflix, etc. has been (mostly) perfectly fine.

Discord surprised us last year by claiming/maintaining the Discord #Flatpak on #Flathub, PLEASE surprise us again by giving us STREAMING WITH AUDIO.

RE: https://sakurajima.social/notes/9o2j4pgvra

#gaming #linux #windows #nvidia #games #dlss

Alonely0 🦀 🇪🇺 @[email protected] · 2024-01-28 · 02:25 UTC

On Linux, getting FFmpeg with NVENC to compile and then actually work is completely impossible. The consequences are the attached image.

#ffmpeg #linux #nvidia #nvenc

Nagaram @[email protected] · 2023-12-10 · 16:41 UTC

Anyone have any thoughts on the #intel #arc A380 versus a #Nvidia #GTX 1630 for #jellyfin encoding? I'm going to pass it through to a VM in Proxmox and I'm a little worried about Arc and it's weird Resizable Bar requirement.

Both are cheap and I'm torn between #nvenc and #av1.

Both is the answer my heart says since they're kinda cheap. But my desire to be a bit more frugal says one for now.

#homelab #server

#intel #arc #nvidia #gtx #jellyfin #nvenc

Tao of Mac @[email protected] · 2023-12-03 · 19:26 UTC

Notes on H.265 Hardware Encoding

I’m starting to run low on disk space on my NAS, with Time Machine and VM snapshots taking up almost half of it. So I decided to do some cleanups, and after moving some non-critical stuff to my old NAS (which I use as offline storage) I started looking at my video folder.(...)

#encoding #nvenc #hardware #videotoolbox #video #handbrake #h.265 #nvidia #transcoding #applesilicon

#encoding #nvenc #hardware #videotoolbox #video #handbrake

Tao of Mac @[email protected] · 2023-12-03 · 19:26 UTC

Notes on H.265 Hardware Encoding

I’m starting to run low on disk space on my NAS, with Time Machine and VM snapshots taking up almost half of it. So I decided to do some cleanups, and after moving some non-critical stuff to my old NAS (which I use as offline storage) I started looking at my video folder.(...)

#encoding #nvenc #hardware #videotoolbox #video #handbrake #h.265 #nvidia #transcoding #applesilicon

#encoding #nvenc #hardware #videotoolbox #video #handbrake

Tao of Mac @[email protected] · 2023-12-03 · 19:26 UTC

Notes on H.265 Hardware Encoding

I’m starting to run low on disk space on my NAS, with Time Machine and VM snapshots taking up almost half of it. So I decided to do some cleanups, and after moving some non-critical stuff to my old NAS (which I use as offline storage) I started looking at my video folder.(...)

#encoding #nvenc #hardware #videotoolbox #video #handbrake #h.265 #nvidia #transcoding #applesilicon

#encoding #nvenc #hardware #videotoolbox #video #handbrake

Tao of Mac @[email protected] · 2023-12-03 · 19:26 UTC

Notes on H.265 Hardware Encoding

I’m starting to run low on disk space on my NAS, with Time Machine and VM snapshots taking up almost half of it. So I decided to do some cleanups, and after moving some non-critical stuff to my old NAS (which I use as offline storage) I started looking at my video folder.(...)

#encoding #nvenc #hardware #videotoolbox #video #handbrake #h.265 #nvidia #transcoding #applesilicon