From: Robert S. <rob...@gm...> - 2003-05-01 12:11:09
|
From: "John Adcock" <Jo...@ad...> > I'm not quite as pessimistic as Robert on what's there but I agree > with the overall sentiment that there is a lot of work to do. The problem with Microsoft's (actually Intel's) BDA TIF is that it has no means of caching anything at all - every time you turn it on _or even change the multiplex_, it first has to receive all the necessary DVB SI tables before it can tune in to any service - and that can take up to 30 seconds. 30 seconds to switch the station is not bearable, IMHO. And AFAIK there is absolutely nothing you can do about it, as there is no means to pass it the full information it needs - it will only take the tables from the live data stream, and no way other. There is a way to switch almost instantly between services on the same multiplex, but that's all you can achieve. I suppose you'd be fine if you have only one multiplex in your area ;) Another thing is the Network Provider, which IMHO has an architectural problem: It can (AFAIK) tune only into exactly _one_ service at a time. Unfortunately, Teletext is always a _separate_ service, and not a component of a TV service. Thus, you could only either have TV and no Teletext, or Teletext and no TV. Stupid, eh? Same goes for data services (TCP/IP over DVB), but that one is even uglier: For TCP/IP over DVB, one would desire to have it _always_ receive TCP/IP data, as a "background app", regardless whether the TV app is currently running or not. I suppose the only solution to that would be to have those two be the one and same application, i.e. the TV app should be able to "silently" run in the background receiving IP data... I think one would have to implement a completely new Network Provider, possibly even with a new interface, that allows tuning into several services on the same multiplex at once. At least 3 simultaneous services should be possible: TV, Teletext and IP. Regards, -- Robert Schlabbach e-mail: rob...@gm... Berlin, Germany |