11 May
2015
11 May
'15
9:25 a.m.
I'm thinking about something similar to seti@home
distributed computing model.
You drive your encoding on your own computer, your footage stay local, but you send away
some frames to encoding servers and receive back encoded images in
return.
It's exactly the way how DCP-o-Matic seems to work on a LAN, but extended to the
whole internet. This way, no need for fast transfert speeds, the number of
encoding servers can speed up your encoding jobs.
I think that hosting at home, behind my DSL modem, a Rapsberry Pi encoding server will
not cost me much in watts and bandswith. In return, if I can use 10s
or 100s of encoding servers when I need it, that's a good deal...
No matter how you do it, you still need to send the source video frame out
to a client and receive the encoded data back. Unless you can do that
quicker than encoding the frame locally, there is no point in doing it
remotely. It doesn't scale well, either, as if you are using 100 encoding
servers you would need the bandwidth to transfer data to and from them
all. seti@home and similar things work because they need a lot of CPU but
work on small data blocks.
Regards,
Carl