Now mpeg-2 transport streams are meant for streaming and thats why we're now working on streaming mpeg-2 transport streams.
Multiple audio streams/subtitles can indeed be streamed as well to the client.Newbie question. mpeg-2 transport streams can handle the same extra content of a mpeg2 stream, namely multi audio tracks, subtitles and etc, so user can view this content over the client?
This question has already been answered.but I've just read that MyBlaster will not be supported in the first version for control of an external STB - please; say it ain't so..
donate a card that is able to receive such a broadcast and the developers can start to code the support
Exactly what i mean, at this moment almost all broadcasts are in mpeg-2The Football world cup was broadcasted in MPEG4/H.264 in Sweden in the Boxer DVB-T network last summer.
for dvb-s2 you will need a new card;-)So you don't need a special card you just need to support a demuxer(?) that can do MPEG4.
This "magic packed" would be called WOL (Wake On Lan)
Genreally speaking a server is running 24/7. Maybe such a "Wake On Lan" feature will be added in the future. but this is not planed at the moment.
there are much more importand other things on the ToDo list now.
Real time comskip would be nice, but unfortunaly i never got comskip to work 100% for my tv channels. It either misses ads or even worse, cuts out parts of a program Anyway, when plugin structure is in place we could add real-time comskip
My Server:Well I did some calculating just now and according to the current electricity prices (SEK 1.22/kwH incl taxes) and a 200W average power consumption the yearly electricity cost for running a server 24/7 would run up to 293$US.
you should know that setting upo WOL functionality is not as easy as enabling one setting in most cases.For example as an implementation you could propably put the same suspend/hibernate/resume functionality in the server and then to make it always be on when any client is on you could have clients send WOL/magic packets to the server on startup/resume of the client. On shutdown I guess you'd have to send a customized message to the server signing off the current client and then the server can check if it has other clients and current recordings and if not suspend/hibernate.
you will need either a mainboard with onboard NIC which is supports WOL or a additional NIC-PCI card which supports WOL, then you may have to connect the NIC with the mainboard with one cable that is never bundled with the NIC........I have never used WOL so I imagined it to be: enabling it in bios and possibly allowing some traffic in the servers firewall and at worst also changing some setting in the networking prefs. Sure too advanced for an average user but many tasks in conjunction with an HTPC is.
which means ~ $9,- each month.Edit: Recalculated on infinityloops idle power consumption. About 110$US per year.