Re-Encode Advice?

Rodrigo_de_Mendoza@lemmy.dbzer0.com to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 32 points –

After a recent data loss, I'm reconsidering various CODECs before re-encoding my re-pirated "loot". I'm looking to maintain a good balance between quality and file size as my previous files were HUGE. I've read about x264, h264, h265 & vp9 for video and it's between AAC or AC-3 for audio. I'm looking for long-term and broad device compatibility. Also, I'll be using FFBatch front-end for ffmpeg for re-encoding. So, fellow pirates, what are your libraries coded in? Any helpful input would be greatly appreciated.

22

You are viewing a single comment

I see what you mean about the other CODECs like VP9 and AV1. The future looks good for them but for a Plex library not so much. I tried converting a single ~20 minute TV episode and it took about ~16mins for AOM-AV1 and VP9 was somewhat over an hour or so. But, H265 zips right along in ~5 mins or less an ep with not as much strain on the CPU. Probably be going down the H265/AAC route. Thanks for the data & information. It's helped very much!

That will be down to your GPU having hardware acceleration for certain codecs and not others, because a pure CPU encode of those codecs on anything but an Epyc or other ball tot he wall top end CPU is going to take hours.

My Radeon 470 had Kronos Open CL but I think some of my system drivers have gone crazy because the option to use it has disappeared. I'm really considering a new build even though my system's only 3.5 yrs old.