Functions that would be useful:

• Implement two backend commands: QUERY_RECORDING_DEVICES, QUERY_RECORDING_DEVICE
  • QUERY_RECORDING_DEVICES should take no parameters and return all audio and video recording devices visible to that host, be they configured or not. QUERY_RECORDING_DEVICE should take either a cardid or a videodevice and return information on that device.
  • The device information should be of the following form:

    <config>
      <device cardtype="" [videodevice=""] [audiodevice=""] [cardid=""]
              device_name="" driver_name="" status="accessible|inaccessible" >
        <input name="Television" sourceid="" />
        <probedinput name="Television" />
        <probedinput name="Composite" />
        <probedinput name="S-Video" />
        <programinfo> <!-- xml for the current recording (if there is one) --> </programinfo>
        <programinfo> <!-- xml for the next recording (if there is one) --> </programinfo>
      </device>
    </config>
    

• The cardtype is the info that is in the capturecard.cardtype column, or would be there if inserted into the DB. The videodevice, audiodevice and cardid are similarly correspond to the columns of those names in the capturecard table. The device_name and driver_name correspond to probed info and are not in the DB. The status would necessarily be accessible for a probed card, but if the card is defined in the database for that host but can not be accessed for recording it should be flagged as inaccessible. While neither audiodevice for videodevice alone is required, at least one of the two should be defined.

• The input tags describe inputs defined in the DB for the card, there would be none of these for a probed card and hopefully at least one for each card defined in the DB for that host. The probedinput tags describe each of the inputs available on the card, one or more of these may correspond to input tags.

• The programinfo tags describe any in-progress or soon to be in progress recordings on the hardware. This is to allow the user to decide whether to reconfigure a card or not when doing so may cause a recording to be lost.

• Each recording device should only be listed once per QUERY_RECORDING_DEVICES result. This means no two entries should have an identical videodevice or audiodevice entry, and in some cases (HDHomeRun) a more extensive comparison is required as there are multiple ways to define the device (i.e. by IP or unique id).