Hi,
I am QA testing the latest HDHomeRun drivers for use with MediaPortal 1.0.0 RC1.
Regarding the CaptureCardDefinitions file...
1) The file references an old HDHomeRun uBDA driver that was discontinued 2 years ago.
The entry for HDHomeRun uBDA should be removed.
2) The "Microsoft XXXX Network Provider" components have been deprecated by MS. MS recommend using the "Microsoft Network Provider" component instead. MP seems to work correctly either way, but for future compatibility should probably use the "Microsoft Network Provider" component for all tuners.
3) The HDHomeRun driver instance friendly name includes the Device ID and Tuner index of the tuner.
Each HDHomeRun has 2 tuners and most HDHomeRun owners have 1-2 units (ie 2 to 4 tuners). 6 or 8 tuners is also not uncommon.
The tuners are often used in a mixture of OTA and QAM so it is important that the user can tell the tuners apart.
We need a way to do a partial wildcard match to identify the tuner/filter components.
The current instructions are rather nasty, requiring the user to hand-edit the CaptureCardDefinitions file:
HDHomeRun MediaPortal Instructions
Nick
I am QA testing the latest HDHomeRun drivers for use with MediaPortal 1.0.0 RC1.
Regarding the CaptureCardDefinitions file...
1) The file references an old HDHomeRun uBDA driver that was discontinued 2 years ago.
The entry for HDHomeRun uBDA should be removed.
2) The "Microsoft XXXX Network Provider" components have been deprecated by MS. MS recommend using the "Microsoft Network Provider" component instead. MP seems to work correctly either way, but for future compatibility should probably use the "Microsoft Network Provider" component for all tuners.
3) The HDHomeRun driver instance friendly name includes the Device ID and Tuner index of the tuner.
Each HDHomeRun has 2 tuners and most HDHomeRun owners have 1-2 units (ie 2 to 4 tuners). 6 or 8 tuners is also not uncommon.
The tuners are often used in a mixture of OTA and QAM so it is important that the user can tell the tuners apart.
We need a way to do a partial wildcard match to identify the tuner/filter components.
The current instructions are rather nasty, requiring the user to hand-edit the CaptureCardDefinitions file:
HDHomeRun MediaPortal Instructions
Nick