2013-05-13, 08:20
Phew - good news.... I don't have a firstborn yet ;-)
BTW - I am not sure where you are, or which way you chose to proceed in regards to LiveTv. But you were discussing two options earlier in the thread... One was to read the DirectX stream directly to the screen. That would allow for fast channels switching but restrict it to local playback (if you could figure it out) and the other was the more traditional/distributed server/client version, which, in the current way XBMC uses ffmpeg, requires the dreaded pre-buffering (slow channel switches).
I was thinking, that if you could manage to get the "local" Directx approach working, why not implement both with an option to configure the individual Client? So if it is local, you use Directx and get the benefits of fast channel changes and if it is remote, you get the benefits of a distributed setup?
Personally, I am running everything locally with hard wires to connect my kitchen and bedroom to the same video output. So I would greatly benefit from the local version. But in the future, I am planning to invest in some more tuners, and then the distributed setup would be interesting for me, I would love to keep a local fast channel switch in my living room, and the slow distributed way for my kitchen and bedroom.
Makes sense?
I know it's a bit more coding work - but just stating the case, that one does not neccesarily have to exclude the other - and both options have merit :-)
BTW - I am not sure where you are, or which way you chose to proceed in regards to LiveTv. But you were discussing two options earlier in the thread... One was to read the DirectX stream directly to the screen. That would allow for fast channels switching but restrict it to local playback (if you could figure it out) and the other was the more traditional/distributed server/client version, which, in the current way XBMC uses ffmpeg, requires the dreaded pre-buffering (slow channel switches).
I was thinking, that if you could manage to get the "local" Directx approach working, why not implement both with an option to configure the individual Client? So if it is local, you use Directx and get the benefits of fast channel changes and if it is remote, you get the benefits of a distributed setup?
Personally, I am running everything locally with hard wires to connect my kitchen and bedroom to the same video output. So I would greatly benefit from the local version. But in the future, I am planning to invest in some more tuners, and then the distributed setup would be interesting for me, I would love to keep a local fast channel switch in my living room, and the slow distributed way for my kitchen and bedroom.
Makes sense?
I know it's a bit more coding work - but just stating the case, that one does not neccesarily have to exclude the other - and both options have merit :-)
