Interesting feature, but how often is that needed? O
I never had such issue ever in my life.
Is it something that can happen on such filesystems? Then I guess ext4 is far superior (/s).
Jokes aside, that extra space with raid5 if by far more tangible and statistically sound than the bit flipping fearmonger.
Which never happened to me so far.
Frankly, if a pixel of a photo or a piece of a scene of a movie is corrupted, I will just never know, and never even notice. Nor a corrupted bit in a text note would be critical.
I cannot think of any unreplaceable file of mine that would actually suffer from bit rot issue.
Good point on the expansion. But o am not too bothered about it, as I have always done by moving data around. Takes a while, but leaves you with a set of disks with the old data still there, and it saved my ass a few times in the past. Now I should be fine with good backups, but you never know.
There is no real need for GPU, since its not ideal to use GPU for storage. GPU transcoding is better suited for streaming, and it has lower quality than CPU transcoding.
Anyway, just enable it by setting the proper ffmpeg flags as stated in the readme and there you go.
IMU, GPU encoding is for streaming: it aims at fast, not so great, output quality without CPU usage. Exactly what you are getting.
Don't use GPU encoding for storage... CPU encoding is much better.
Edit: since its aimed at streaming, GPU encoding only needs to achieve real time performance, no need to go any faster. CPU encoding instead can go as fast as your cores can push.
The hdd spin on once every night for backup, then off after a bit by the timeout.
That should not be a critical issue.