home.social
Sign in Create account

#qsv — Public Fediverse posts

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

  1. boredsquirrel @[email protected] ·

    @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

    #h265 #av1 #svtav1 #nvidia #nvenc #intelarc
  2. Mika @[email protected] ·

    Done this with the #AMD 5600G's iGPU, now testing #Jellyfin hardware transcoding with my #Intel #ArcA380 GPU - one question though, is it normal for CPU usage to be rather high at least in the early parts of streaming (while transcoding), even with hardware transcoding?

    I'm just trying to figure out if it is actually hardware transcoding - I'm assuming it is, bcos on the admin dashboard I'm seeing that it's transcoding as AV1 and I'm sure my Ryzen 7 1700 would not be able to do/handle that, esp considering that I'm testing with 4 streams playing concurrently? but the CPU usage is rather high the first minute or two or more from when the stream starts, it does lower down afterwards - the video playback is perfectly fine, no stuttering or anything like that.

    My method of passthrough is the same as I did with the 5600G, that is a simple passthrough to the     #LXC container, then to the #Docker container running Jellyfin. I don't think I noticed this high CPU usage when testing the 5600G, and the only minor configuration difference between the two was I'd used #VAAPI with the 5600G and disabled #AV1 encoding (since idt it supports it), while on the Arc A380 GPU I'm using Intel's #QSV and have enabled AV1 encoding.

    Am I correct to assume that hardware transcoding is indeed working? Cos again, I'm quite certain my Ryzen 7 1700 would definitely NOT be able to handle this lol esp since I only give the LXC container 2 cores.

    #amd #jellyfin #intel #arca380 #lxc #docker
  3. Cahiers Pédagogiques @[email protected] ·

    Souvent, les enseignantes et enseignants ne se sentent pas compétents, (in)formés, ou en sécurité pour aborder en classe les controverses de l’actualité: vaccination, climat et transitions énergétiques, identité sexuelle, consommation de viande, etc. Ces questions divisent et mobilisent. Comment faire, sans se mettre en danger ni délaisser les apprentissages disciplinaires?
    #débat #vaccins #SVT #QSV #histoiregeographie #controverses
    ⏬
    cahiers-pedagogiques.com/forme

    #debat #vaccins #svt #qsv #histoiregeographie #controverses