Problem with HDHomeRun DVB-T

#1
Hi,

I like to use ProgDVB with my HDHomeRun DVB-T network tuner:
http://www.silicondust.com/products/models/hdhr3-eu/

It works great with other software, like Windows Media Center, DVBViewer, TSReader, etc.

But, when I try with ProgDVB I have this error: "[{] Device not started!"

This is the content of "BDA.log" (MAC address changed to 11111111):

15:41:15.118 - Start logging...
15:41:15.118 - GetBdaTunerList
15:41:15.119 - tuner Silicondust HDHomeRun Tuner 11111111-0 - -
15:41:15.129 - Silicondust HDHomeRun Tuner 11111111-0 ex:56781 type:Unknow type 0
15:41:15.129 - tuner Silicondust HDHomeRun Tuner 11111111-1 - -
15:41:15.138 - Silicondust HDHomeRun Tuner 11111111-1 ex:56782 type:Unknow type 0
15:41:15.138 - GetInfo 2
15:41:15.138 - CreateExtApi default
15:41:15.139 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-0 56781
15:41:15.139 - exIndex 0
15:41:15.139 - maxfilters 128
15:41:15.139 - caps 200304
15:41:15.139 - PossibleStart 1
15:41:15.140 - CreateExtApi default
15:41:15.140 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-1 56782
15:41:15.140 - exIndex 1
15:41:15.140 - maxfilters 128
15:41:15.141 - caps 200304
15:41:15.141 - PossibleStart 1
15:41:17.049 - GetInfo 2
15:41:17.049 - CreateExtApi default
15:41:17.049 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-0 56781
15:41:17.049 - exIndex 0
15:41:17.050 - maxfilters 128
15:41:17.050 - caps 200304
15:41:17.050 - PossibleStart 1
15:41:17.050 - CreateModule 56781
15:41:17.050 - CBDAManager
15:41:17.050 - BDAManager::Start 56781
15:41:17.050 - index 0
15:41:17.050 - CreateExtApi default
15:41:17.050 - BuildGraph
15:41:17.054 - LoadNetworkProvider DVB-S
15:41:17.062 - GetTunerSpace DVB-S
15:41:17.062 - CTuneRequestSwitchManager::SetDefaultTunerRequst apply err Error in put tuner request
15:41:17.062 - Error in default request!
15:41:17.062 - Connecting NetworkProvider -> Silicondust HDHomeRun Tuner 11111111-0 ... ERROR!!!
15:41:17.063 - LoadNetworkProvider DVB-C
15:41:17.066 - GetTunerSpace DVB-C
15:41:17.067 - CTuneRequestSwitchManager::SetDefaultTunerRequst apply err Error in put tuner request
15:41:17.067 - Error in default request!
15:41:17.067 - Connecting NetworkProvider -> Silicondust HDHomeRun Tuner 11111111-0 ... ERROR!!!
15:41:17.067 - LoadNetworkProvider DVB-T
15:41:17.071 - GetTunerSpace DVB-T
15:41:17.071 - BW: 0
15:41:17.071 - Connecting NetworkProvider -> Silicondust HDHomeRun Tuner 11111111-0 ... ERROR!!!
15:41:17.071 - LoadNetworkProvider ATSC
15:41:17.074 - GetTunerSpace ATSC
15:41:17.075 - Connecting NetworkProvider -> Silicondust HDHomeRun Tuner 11111111-0 ... ERROR!!!
15:41:17.075 - !!!BuildGraph error Cannot connect network provider

15:41:17.075 - TearDownGraph OK
15:41:17.305 - ~CBDAManager
15:41:17.305 - PowerOff
15:41:17.305 - Stop
15:41:41.413 - GetInfo 2
15:41:41.413 - CreateExtApi default
15:41:41.414 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-0 56781
15:41:41.414 - exIndex 0
15:41:41.414 - maxfilters 128
15:41:41.414 - caps 200304
15:41:41.414 - PossibleStart 1
15:41:41.414 - CreateExtApi default
15:41:41.415 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-1 56782
15:41:41.415 - exIndex 1
15:41:41.415 - maxfilters 128
15:41:41.415 - caps 200304
15:41:41.415 - PossibleStart 1
15:41:45.420 - GetInfo 2
15:41:45.420 - CreateExtApi default
15:41:45.421 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-0 56781
15:41:45.421 - exIndex 0
15:41:45.421 - maxfilters 128
15:41:45.421 - caps 200304
15:41:45.421 - PossibleStart 1
15:41:45.421 - CreateExtApi default
15:41:45.422 - GetModuleInfo {BDA} Silicondust HDHomeRun Tuner 11111111-1 56782
15:41:45.422 - exIndex 1
15:41:45.422 - maxfilters 128
15:41:45.422 - caps 200304
15:41:45.422 - PossibleStart 1

The device is DVB-T/C and the tunning space selected in the config is DVB-T. So, please, can you provide a fix?
Thank you!

Re: Problem with HDHomeRun DVB-T

#3
Prog wrote:same?

viewtopic.php?f=2&t=8845
Hi,

I readed all the other post, and it's not related at all! The Setup of the HDHomeRun software has the Tuner option for select the Surce Type (Digital Antena=DVB-T or Digital Cable=DVB-C), so the problem isn't the tunning space.

Moreover, when I try to enable the device an ERROR Window appears, with the message "[{] Device not started!". Then I can't configure anything of the device driver (options button disabled).

Perhaps the problem is on BDA Demulator type. I found this document: https://www.silicondust.com/hdhomerun/h ... opment.pdf
In section "II.Windows BDA Drivers" it explains the implementation of the BDA driver.
At some page in the document it says:
Many third party BDA applications continue to use the older “Microsoft XXXX Network Provider”
components for compatibility with XP. This has the advantage of supporting XP, but the
disadvantage of not being able to programatically detect if an ATSC tuner supports US-QAM.

Unfortunately the conflicting combinations mean that it is not possible for a driver to publish one
set of features. To solve this problem the HDHomeRun BDA driver will auto-detect which network
provider(s) are part of the graph and use this detection to select which demodulator nodes to
publish.

It is recommended that an application attempt to use the universal “Microsoft Network Provider”
component, and only use the “Microsoft XXX Network Provider” components if the universal
component fails to instantiate.
I hope soon ProgDVB will be compatible with HDHR DVB-T/C.

Re: Problem with HDHomeRun DVB-T

#5
Prog wrote:Is it work if selected only one device?
Hi Prog,

I only select one device! And when I select the device the error window appears. The log file is after these steps:

1) Open ProgDVB
2) Go Device Options
3) Enable one HDHR device (error window)
4) Close ProgDVB

As I understand from the documentation you are using the BDA Interface with XP compatibility, but the recomendation is first try the most recent BDA Interface, and if fails then try the XP Interface. Can be this the problem?

Re: Problem with HDHomeRun DVB-T

#8
Hi,

Perhaps this helps:

I try to execute GraphEdit and I instantiate filter "Silicondust HDHomeRun Tuner 11111111-0". Then I instantiate two modules "Microsoft DVBT Network Provider" and "Microsoft Network Provider". The first one REFUSES to connect to input0 pin of HDHR Tuner0 filter; but second CONNECTS without problems.

So, are you using old XP interfaces for BDA tuners, or the new one?

Re: Problem with HDHomeRun DVB-T

#10
Prog wrote:I am not sure about new API because many years no any problems with BDA parts. But single tuner DVB C/T devices like ASTROMETA is not typical for ProgDVB. Because 2 tuners = 2 different tuner filters.
Sure! In GraphEdit I see TWO different tuners! But one for each tuner, no one for each tuner space (i.e. no one DVB-T and one DVB-C for each tuner). The problem ins't the dual tuner, the problem is the multiple tuner space support. If you read the documentation the "old" BDA API ins't compatible with some devices. The solution is use the new "Microsoft Network Provider" that is agnostic about the tuner space. Moreover, old API is DEPRECATED by Microsoft, see https://msdn.microsoft.com/en-us/librar ... s.85).aspx

I hope you can use this new API as it will be easy for you!
Cheers!

Re: Problem with HDHomeRun DVB-T

#11
Hi Prog,

After more tests with GraphEdit I do this:

1) Open GraphEdit.
2) Instantiate filter "Microsoft DVBT Network Provider"
3) Instantiate filter "Silicondut HDHomeRun Tuner 11111111-0"
4) Connect "Antenna Out" pin to "Input0" pin

And it works! So the problem can be the dynamic change of the tuner space incorporated in the filter. The logs show that you first try DVB-S, then DVB-C, then DVB-T and finally ATSC. So, please, can you try to use only one network provider and disable autoconfig? Or provide the option to change the order of tests (if first try DVB-T I feel the driver will initialize without troubles).

I don't know where is the problem, but I feel is not very complex to fix. It's possible to generate more verbose BDA logs?

Re: Problem with HDHomeRun DVB-T

#13
Prog wrote:You can try rename device name to "xxxx - DVB-T" for force DVB-T using.
Hi Prog,

Where I can rename it? In ProgDVB all options are disabled... I only see "{BDA} Silicondust HDHomeRun Tuner" and "{BDA} Silicondust HDHomeRun Tuner" and only enable/disable checkbox is available.

Please, help me to enable this device! :cry:

Re: Problem with HDHomeRun DVB-T

#15
Prog wrote:I am mean on driver level (in inf file or registry)
Sorry? The name of the driver is defined by the manufacturer, no?
I can't found how to change the name in the Windows registry. :(

Please, can you provide more debug level or force tunning? I can send to you any logs generated by ProgDVB
:roll:
cron