I posted a while back about exposing a firewire AVHDD disc player/recorder subunit as a PVR backend.
Well, I have studied the several of the existing PVR source implementations and have coded up myself a PVR backend & client to interface with XBMC, but I have a couple questions which I am not clear on. The existing add-on wiki pages seem to describe a scripted addon, not a compiled c++ add on?
BTW - I have only been looking at the PVR source code for a couple of days and at this point dont really understand the XBMC code base / architecture.
Here are several questions:
1. PVR Setup: I need to attempt to fetch a persisted GUID for the firewire device to use, and if either the PVR has not ever been setup or the persisted GUID no longer is on the 1394 network, I need to programatically present to the user a list of device GUID's currently on the network to choose from. Do I need to overwrite the settings.xml file and somehow force a reload?
2. PVR_STREAM_PROPERTIES: presumably XBMC assumes there is only 1 stream at a time, either live TV or a recorded transport stream, so the stream_properties would apply to whichever is currently in use? What specification does unsigned int iCodecType / iCodecId refer to?
3. Channel Scanning: Can someone describe the use of DialogChannelScan() & CallMenuHook()
4. In Progress Recordings: The GetRecordings method fetches a list of recordings from the backend. How does XBMC keep track of continuously changing values of in-progress recordings such as the iDuration member?
5. Are there instructions for compiling and packaging a PVR add on seperate from the rest of XBMC (for OSX)?
I would like to compile my add on and install using my existing installation and avoid compiling the entire code base of XBMC from scratch if at all possible.
Well, I have studied the several of the existing PVR source implementations and have coded up myself a PVR backend & client to interface with XBMC, but I have a couple questions which I am not clear on. The existing add-on wiki pages seem to describe a scripted addon, not a compiled c++ add on?
BTW - I have only been looking at the PVR source code for a couple of days and at this point dont really understand the XBMC code base / architecture.
Here are several questions:
1. PVR Setup: I need to attempt to fetch a persisted GUID for the firewire device to use, and if either the PVR has not ever been setup or the persisted GUID no longer is on the 1394 network, I need to programatically present to the user a list of device GUID's currently on the network to choose from. Do I need to overwrite the settings.xml file and somehow force a reload?
2. PVR_STREAM_PROPERTIES: presumably XBMC assumes there is only 1 stream at a time, either live TV or a recorded transport stream, so the stream_properties would apply to whichever is currently in use? What specification does unsigned int iCodecType / iCodecId refer to?
3. Channel Scanning: Can someone describe the use of DialogChannelScan() & CallMenuHook()
4. In Progress Recordings: The GetRecordings method fetches a list of recordings from the backend. How does XBMC keep track of continuously changing values of in-progress recordings such as the iDuration member?
5. Are there instructions for compiling and packaging a PVR add on seperate from the rest of XBMC (for OSX)?
I would like to compile my add on and install using my existing installation and avoid compiling the entire code base of XBMC from scratch if at all possible.