I noticed that at speeds around 50MB/s Tixati seems to max out the thread it's running on. Maybe this is due to hash checking? I have a 6900k @ 4.3Ghz so going pretty fast but it would be faster if more cores/threads could be used for hash checking of the pieces.

I'd like to add that if Your proposition would be implemented, the devs should also take care to not read from any single physical drive in multiple threads, even if logical partitions are different.

IOW tixati will need to distinguish that, say, C: and D: are on the same HDD platters, while E: is not, so it is safe to hash from E: and D: simultaneously in multiple threads, but concurrent hashing from C: and D: should not be possible by default, and should resort to single thread in latter case (if IO-bound and not CPU-bound, that is).

This whole affair might also need to be implemented by using separate threads for reading, buffering, hashing, and passing events regarding two.