Extending the bittorrent protocol, to make it possible to specify the audio/video codec for example h.264 and share the load of reencoding. When you get a torrent packet from the initial seeder, you are to re-encode, if you get a packet from someone else, it will already be reencoded.
Recognised Problems: MD5/SHA packet checking will be problematic, initial seeder will also have to receive the re-encoded video and replace the original upon completion
- Set of know codecs combinations
- shared work load on reencoding video,
Sounds neat, but to convert a 40min show only takes an hour or two, and this seems like something bittorrent has little to do with. Also its probably impossible to verify the resulting encoded video because there is no way to say "you did it wrong" unless you were to compare each frame with room for error and waste CPU time. This idea would be better suited as a distributed computing program that happens to use Bittorrent.
This is outside the scope of bittorrent. Bittorrent is a low-layer data distribution protocol like ftp or http that does not concern itself with what is actually distributed.
And re-encoding is not considered a common-use scenario. The need to distribute the load over many many clients is even less common.