I can see that XBMC still opens a new RTSP session for every channel that is being set. This results in an expensive reopening of the tuner at the server for every channel change.
In case of the DVBViewer Recording Service, a tuner is always opened with a SETUP message and closed with a TEARDOWN message, which is done for each channel change in case of XBMC. Depending on the DVB card(s) being used and whether a CI-CAM is involved or not, this can take several seconds. Some DVB cards even re-init the CAM on a tuner open, which takes ~5-10s.
I suggest reading the SAT>IP specs (page 24 ff.) on how the RTSP control messages should be adapted for a delivery system like DVB. Switching the channel only requires a PLAY with the different parameters, no expensive TEARDOWN+SETUP:
I don't really know the design of XBMC, how it triggers the PVR Add-On or who actually does what. But I assume that it is heavily file based and that there is no clear indication of when a (tuner) session may start and end?
In case of the DVBViewer Recording Service, a tuner is always opened with a SETUP message and closed with a TEARDOWN message, which is done for each channel change in case of XBMC. Depending on the DVB card(s) being used and whether a CI-CAM is involved or not, this can take several seconds. Some DVB cards even re-init the CAM on a tuner open, which takes ~5-10s.
I suggest reading the SAT>IP specs (page 24 ff.) on how the RTSP control messages should be adapted for a delivery system like DVB. Switching the channel only requires a PLAY with the different parameters, no expensive TEARDOWN+SETUP:
I don't really know the design of XBMC, how it triggers the PVR Add-On or who actually does what. But I assume that it is heavily file based and that there is no clear indication of when a (tuner) session may start and end?
