home.social

#nvenc — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #nvenc, aggregated by home.social.

  1. Рабочий стол в LXC-контейнере: детективная история о протоколах, тупиках и самописном Wayland-композиторе

    Домашний облачный рабочий стол и гейминг в контейнере, с общим GPU. Готового решения не было — пришлось пройти четыре тупика и написать свой Wayland-композитор. Читать исследование

    habr.com/ru/articles/1045602/

    #Proxmox #LXC #проброс_gpu #wayland #moonlight #sunshine #Gamescope #steam_deck #облачный_гейминг #nvenc

  2. Рабочий стол в LXC-контейнере: детективная история о протоколах, тупиках и самописном Wayland-композиторе

    Домашний облачный рабочий стол и гейминг в контейнере, с общим GPU. Готового решения не было — пришлось пройти четыре тупика и написать свой Wayland-композитор. Читать исследование

    habr.com/ru/articles/1045602/

    #Proxmox #LXC #проброс_gpu #wayland #moonlight #sunshine #Gamescope #steam_deck #облачный_гейминг #nvenc

  3. Рабочий стол в LXC-контейнере: детективная история о протоколах, тупиках и самописном Wayland-композиторе

    Домашний облачный рабочий стол и гейминг в контейнере, с общим GPU. Готового решения не было — пришлось пройти четыре тупика и написать свой Wayland-композитор. Читать исследование

    habr.com/ru/articles/1045602/

    #Proxmox #LXC #проброс_gpu #wayland #moonlight #sunshine #Gamescope #steam_deck #облачный_гейминг #nvenc

  4. Возможости современных моделей в разработке кода: кейс автоматического решения сложной проблемы

    Кейс полностью автономного траблшутинга нетривиальной системной проблемы с неработоспособностью NVENC в Docker-контейнера на Jetson Orin NX с помощью Claude Opus 4.6, как пример выхода больших языковых моделей за пределы квалификации middle-grade инженера. Около 40 минут заняло расследование проблемы, по мотивам которого, я попросил сеть написать статью, которую и предлагаю вашему вниманию как пример того, на что я мог потратить целый день, а большинство middle-grade инженеров бы не справилось вообще. Весь траблшутинг и статья сделаны в полностью автоматическом режиме без участия человека.

    habr.com/ru/articles/1014276/

    #nvidia #nvenc #gstreamer #video_encoding #troubleshooting #ai

  5. Возможости современных моделей в разработке кода: кейс автоматического решения сложной проблемы

    Кейс полностью автономного траблшутинга нетривиальной системной проблемы с неработоспособностью NVENC в Docker-контейнера на Jetson Orin NX с помощью Claude Opus 4.6, как пример выхода больших языковых моделей за пределы квалификации middle-grade инженера. Около 40 минут заняло расследование проблемы, по мотивам которого, я попросил сеть написать статью, которую и предлагаю вашему вниманию как пример того, на что я мог потратить целый день, а большинство middle-grade инженеров бы не справилось вообще. Весь траблшутинг и статья сделаны в полностью автоматическом режиме без участия человека.

    habr.com/ru/articles/1014276/

    #nvidia #nvenc #gstreamer #video_encoding #troubleshooting #ai

  6. Возможости современных моделей в разработке кода: кейс автоматического решения сложной проблемы

    Кейс полностью автономного траблшутинга нетривиальной системной проблемы с неработоспособностью NVENC в Docker-контейнера на Jetson Orin NX с помощью Claude Opus 4.6, как пример выхода больших языковых моделей за пределы квалификации middle-grade инженера. Около 40 минут заняло расследование проблемы, по мотивам которого, я попросил сеть написать статью, которую и предлагаю вашему вниманию как пример того, на что я мог потратить целый день, а большинство middle-grade инженеров бы не справилось вообще. Весь траблшутинг и статья сделаны в полностью автоматическом режиме без участия человека.

    habr.com/ru/articles/1014276/

    #nvidia #nvenc #gstreamer #video_encoding #troubleshooting #ai

  7. @niccolove @niccolo_ve

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

    tube.kockatoo.org/w/63cGWTvhzq

    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.

    #MicrosoftSurface #KDENlive #Shotcut #VideoEditing

  8. @niccolove @niccolo_ve

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

    tube.kockatoo.org/w/63cGWTvhzq

    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.

    #MicrosoftSurface #KDENlive #Shotcut #VideoEditing

  9. @niccolove @niccolo_ve

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

    tube.kockatoo.org/w/63cGWTvhzq

    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.

    #MicrosoftSurface #KDENlive #Shotcut #VideoEditing

  10. @niccolove @niccolo_ve

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

    tube.kockatoo.org/w/63cGWTvhzq

    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.

    #MicrosoftSurface #KDENlive #Shotcut #VideoEditing

  11. 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.

    crazy.macer.life/moving-to-fre

  12. 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.

    crazy.macer.life/moving-to-fre

  13. 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.

    crazy.macer.life/moving-to-fre

  14. 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.

    crazy.macer.life/moving-to-fre

  15. 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.

    crazy.macer.life/moving-to-fre

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

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

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

    habr.com/ru/articles/895076/

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

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

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

    habr.com/ru/articles/895076/

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

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

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

    habr.com/ru/articles/895076/

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

  24. 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 ]

  25. 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 ]

  26. 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 ]

  27. 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 ]

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

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

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

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

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

  33. 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.

  34. 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.

  35. 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.

  36. 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.

  37. 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.

  38. 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.

  39. 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.

  40. 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.

  41. 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.

  42. 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.

  43. 🎞️ 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

    obsproject.com/download#linux

    #OBS #Linux #NVENC

  44. 🎞️ 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

    obsproject.com/download#linux

    #OBS #Linux #NVENC

  45. 🎞️ 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

    obsproject.com/download#linux

    #OBS #Linux #NVENC