And transcoding means playing a video file rather than just sending it over a network?
It means decoding it and then re-encoding it, usually on-the-fly
You may need to do this for several reasons
- the device you want to stream to cannot play the file in it's current form
- the network (eg wifi) can't sustain the bitrate required to play the file in it's current form
For instance, suppose you have a movie on your server in 1080p VC1 with TrueHD audio in a .M2TS container and you want to play that on your iPad.
AFAIK, the iPad doesn't support M2TS files, VC1 video or TrueHD audio, and it's not unfeasible that wifi might struggle to meet the sustained bitrate required anyway.
In such a case, you'd either have to transcode the file offline and store a seperate copy for playback on the ipad (could get tedious and disk space hungry if you have a lot of movies) or else transcode it on-the-fly.
If you choose the latter, you need a pretty beefy CPU - depending on what you are transcoding from and to, you may find that a dual core may not cut it!
A faster cpu must make parity disk creation faster though.
With modern CPUs, and typical home servers, probably not - the performance limiters are elsewhere in the system (usually the disks and/or controllers/IO busses).
Try it yourself - download a copy of DisParity -
disParity
and try it with some test folders.
There's no install, and you just delete the folders later