Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza kaydolun.

Oturum aç

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza giriş yapın.

Şifremi hatırlamıyorum

Şifreni mi unuttun? Lütfen e-mail adresinizi giriniz. Bir bağlantı alacaksınız ve e-posta yoluyla yeni bir şifre oluşturacaksınız.

3 ve kadim dostu 1 olan sj'yi rakamla giriniz. ( 31 )

Üzgünüz, Flood yazma yetkiniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Please briefly explain why you feel this user should be reported.

hw accelerated x265 encoding

Since my children were born, I have shot many terabytes of 4k video footage in various bitrates. Lowest one being 100Mb/s. I would like to compress all of the raw clips into h.265 to save some space (tens of terabytes). However, on my CPUs, this would take years.

Can anybody recommend a hw accelerator for this purpose? Must work in gnu/linux and preferably be sub 500 Euro. I had a Xilinx Alveo U30 on loan from a friend but that card costs around 2 grand.

I also tried this with a GPU (nvenc) but that lowers the quality significantly so I would prefer not to use this approach.

UPDATE: since this has turned into a nvidia/quicksync this and that, I’d like to emphasize that I am looking for dedicated h265 accelerator card recommendations (whether it be asic or fpga based).

Benzer Yazılar

Yorum eklemek için giriş yapmalısınız.

16 Yorumları

  1. my 3070 encode speed is around 3.4~3.7x for camera’s 4K 60Mb/s but only around 1.7x for other downloaded content. (no idea what make the diff)

    (and depends on your needs, I can change the setting to boost encoding speed to around 6x and sometimes don’t tell the diff)

    don’t forget the read speed from your drive. it’s another bottleneck

  2. For the infocon.org project I encode / transcode everything to H265 / HEVC using Nvidia GPU GTX 1660 (Inexpensive)

    The big difference is this current generation supports much more than the previous one in hardware. For example I now can do up to 5 B frames, look ahead, and P frames, 10 bit main, etc. The result is about 20-25% smaller than the previous HEVC GPU encoded files. So you can bump up quality and stay the same size or save disk space.

    The people saying HW GPU encoding is terrible are talking older generations with default settings. I’d also suggest switch audio over to Opus when you transcode, that saves a lot of space as well.

  3. If you’re looking for an ASIC-based solution and not a GPU, I highly recommend cards based on encoder chips from Socionext. They produced great results for H.265.

    I had the opportunity to test one of these demo cards and it was very good, albeit with a slightly clunky interface.


  4. The best quality PC hardware encoder is currently found in nVidia Turing (7th gen) cards (or newer), which gives you 10-bit H.265 with B frame support. I have not tested Alveo cards.

    This matrix tells you what your card supports:

    I stopped using Handbrake a few years ago and moved to StaxRip, which gives you a lot more control.

    This will sound counter-intuitive, but H.26x encoding at 10 bit instead of 8 bit gives you better quality output for the same target bit-rate. This is true even for 8 bit source material. 10-bit playback with H.265 is supported pretty much everywhere, but be careful with H.264; some devices and software won’t play 10 bit encodings back. You’ll get 10 bit encodings from nVidia nvEnc and Intel QuickSync, but AMD were still 8-bit only, last time I checked a couple of years ago. QuickSync lost quality with some scene transitions or large motion vectors, compared to nVidia

    I have had mixed-to-poor results from encoding at a fixed bit-rate because you get blocky artefacts as soon as there is a lot of fine detail moving in complex ways. Choosing a constant QP (I=20, P=24, B=28) gives you something that’s 1/5 to 1/10th the size and is pretty hard to complain about. If you have lots of film grain that is throwing out blocky artefacts, you can: apply a temporal denoising filter (very slow), downscale the image by 10% (very fast) or drop the QP to I=18, P=21, B=24. Every time you drop QP by 6, the file size doubles. You’d have to really pixel peep to see artefacts if you keep all QP settings under 22. There’s not much to gain below QP16 and it’s supposed to be lossless at QP6.

  5. Renting a server is your most economical option and also the least work and risk. No need to take on another uni-tasking asset for any period of time.

  6. Look into M1 Macs

    Not sure on the details, but re-encoding movies into x265 in Handbrake is double as fast on my M1 Macbook Pro than my Ryzen 7 3700X

  7. You really want to use a software encoder like x264, x265, or /r/av1 There are also high quality commercial software encoders.

    The problem with hardware encoders is that they typically only use the baseline profiles for encoding. They do not employ all the tricks available in the codec specification to get the best visual fidelity for the bit rate.

    As such, using a CPU with lots of vector math extensions like AVX2 and/or AVX-512 are a good idea. Any intel Core iX-4000 series or newer support AVX2. They are dirt cheap used and reasonably energy efficient.

    You mentioned an FPGA. It is a forgone conclusion services like youtube are using advanced hardware accelerated encoders that are probably implemented in FPGAs or possibly an custom chip, but good luck getting access to them directly.

  8. You could consider encoding to H264 on a ‘slow’ handbrake preset. Sure it’s not as compressible as h265, but it is much faster. You could reduce bitrates to 20-30Mb/s for 4k and still get great quality. Given your *lowest* bitrate is 100Mb/s, you could save a lot of space fairly quickly.

    Also, how the hell have you shot so many TBs? Are you shooting in RedRAW? lol

  9. Broadcom are supposed to be producing these m.2 cards but I’ve not found much info

    Broadcom Valkyrie

    The driver was added to mainline earlier this year. I assume the price is in line with the xilinx

    macbook m1 is another option

  10. Dang, I was going to recommend NAVI GPU, with 2.5x transcode speed improvement over 12-core 4.4GHz @ 100% utilization… People here are throwing out 10x and 15x estimates? I do not know how this is possible?

    I assume you want to keep the footage helix4k resolution?

    My RX 580 8GB + video toolbox + Handbrake only uses about 8% of my CPU, with no heat or wear issues… it could definitely run 24/7 – I find the transcoded files (x265->H264) to be indistinguishable from the originals. Only transcoded for “smart” TV compatibility (and Plex Server). Plex does the on-the-fly transcode beautifully, but completely ignores all subtitles (except PGS for some strange reason). I need the subtitles, so this is the only method. An entire 90 minute movie done in 19 min, so it is 5x realtime.

    PS. I am talking out my a*s, with the current graphics card pricing woes, you may have issues even finding a card? Some of the cheaper/easier options may be best. ie: Intel/Quick Sync/VAAPI???

  11. Intel quick sync

    Nvidia nvenc

    Amd VCE

    Those are the three options you have.

    All of them were built to prioritize speed, power and silicon efficiency. Not to be the best quality at lowest bitrate.

  12. CPU encoding will provide best results. Just get a used office PC that is a couple years old. You can let it run 24/7.

  13. Don’t hardware accelerate this. Hardware accelerated encoding is always worse than software encoding.

  14. I got a 1050ti (can go into small systems, has no external power requirement either, draws all power from pci bus) off ebay for cheap (well, what passes for cheap these days) and use FFMPEG compiled with CUDA support on ubuntu and I get pretty good results using gpu encoding. Speed improvements depend on source material, but I get anywhere from 3x-15x real time encoding.

    I can’t tell the difference between raw/gpu encoded with correct settings. but I’m not some superhuman video flaw detector either. I mean, if you use shitty settings you get shitty results, but ffmpeg has been around for forever, there are plenty of guides to tweak it for best results. What I don’t know is if ffmpeg+cuda support just uses nvenc or if it just adds GPU support for libx265. I pretty much followed this guide and then tweaked my ffmpeg settings a bunch. [https://docs.nvidia.com/video-technologies/video-codec-sdk/ffmpeg-with-nvidia-gpu/](https://docs.nvidia.com/video-technologies/video-codec-sdk/ffmpeg-with-nvidia-gpu/) They go into a fairly detailed discussion about quality settings as well. I followed their recommendations, did some trial/error stuff on my own and I’m pretty satisfied with the results.

  15. >I also tried this with a GPU (nvenc) but that lowers the quality significantly so I would prefer not to use this approach.

    At what setting? And what generation?

  16. Which generation of Nvenc did you try? The last and current gen is pretty good. Quicksync since 7th gen should also be a decent option.