From: Richard A. <ri...@ys...> - 2007-05-01 19:13:05
|
On Tue, 2007-05-01 at 18:05 +1000, xi...@za... wrote: > There is the possibility of separate RTP streams per program (different > ip and/or port number). The frontend tuning, and delivery of RTP, > is all controlled by the server. You tell the server what you want and > where you want it sent. Some is done directly from lirc configs, > the rest from browser scripts (I have created a non-MythTV pvr > using standard browser technology, and single dvb server app). > > When you change channel (same or different transponder) the first > thing the server always sends is a new PAT (artificially created so as to > contain only a single program number). This causes demux_ts to reset > itself and start looking for fresh PMT so as to determine correct > audio and video pids (given the application of my patch to fix > a major bug in demux_ts.c). > > All of the channel picking is independent of xine. > > Xine isn't using lirc, so irxevent does some of the work, and irexec > does the rest. > > Of course there is limited osd, but I am thinking of inserting > appropriate subtitles into the stream as some stage. > > Any complexity in all of this is taken care of during installation. > When running all you do is click on buttons on your remote control. I think you've missed the point - I'm driving xine via a telent front-end linked against xine-lib. So currently I can do everything (from playing stored videos to switching channels) through one TCP socket without touching lirc or anything else. The telnet comands come from a custom database back-end which holds the schedules of what is to be shown and feeds them out at the right time. So for me having everything (including channel switches) accessible from the xine-lib api just makes creating systems based on xine-lib much easier than having two applications, two APIs and needing to link them together. I suspect many set-top box creators would like to do the same. Richard |