No channels detected ("Failed to create IDVBCLocator"?)

[sharpeagle]

Hi, I get the following in the logs:

Code:

2023-10-08 17:47:01.799    [DEBUG][4]    Tuning:
<tuning>
  <type>DVB-C</type>
  <locator>
    <frequency>738000</frequency>
    <bandwidth>8</bandwidth>
    <symbol_rate>6950</symbol_rate>
    <modulation>QAM256</modulation>
  </locator>
</tuning>

2023-10-08 17:47:01.799    [DEBUG][4]    StartStream(): c:\temp\test.ts
2023-10-08 17:47:01.799    [DEBUG][4]    DigitalRecorderDVBC::Tune()
2023-10-08 17:47:01.799    [ERROR][4]    Failed to create IDVBCLocator

It is a Windows 11 install, the tuner is an USB made by some taiwanese company called Astrometa.
Now, I'm not sure if the tuner got broken or not, but what I can see is that after a fresh reboot, the native DVB software is able to scan and detect, then display streams. Then, after playing around together with NPVR and again de DVB tool, nothing is displayed anymore in the DVB player.
If I unplug and plug in again the dongle, DVB tool is functional again. But I've never had any luck with NPRV detecting channels even after fresh reboot....
Any thoughts? Thanks a lot!

LE
here is the devices.log contents also:

Code:

[...startup]
2023-10-08 17:32:59.970    [DEBUG][1]    Doing device discovery
2023-10-08 17:33:00.000    [DEBUG][1]    About to detect digital tuners
2023-10-08 17:33:00.005    [DEBUG][1]     - 'ASTROMETA DTV Filter'
2023-10-08 17:33:00.010    [DEBUG][1]    About to check standards supported by 'ASTROMETA DTV Filter'
2023-10-08 17:33:00.010    [DEBUG][1]    Found IBDA_Topology

2023-10-08 17:33:00.010    [DEBUG][1]     - KSNODE_BDA_RF_TUNER         

2023-10-08 17:33:00.010    [DEBUG][1]     - KSNODE_BDA_COFDM_DEMODULATOR

2023-10-08 17:33:00.010    [DEBUG][1]    Done
2023-10-08 17:33:00.010    [DEBUG][1]    Forcing DVB-C for 'ASTROMETA DTV Filter'
2023-10-08 17:33:00.010    [DEBUG][1]    Setting up device for:
2023-10-08 17:33:00.010    [DEBUG][1]    About to check for HDPVR/Colossus/Siena tuners.
2023-10-08 17:33:00.023    [DEBUG][1]    About to check for analog tuners
2023-10-08 17:33:00.026    [DEBUG][1]    FindFilterByName failed to locate filter: MainConcept (HCW) MPEG Multiplexer-Plus
2023-10-08 17:33:00.026    [DEBUG][1]    MainConcept mux not present. Disabling analog support.

[mvallevand]

That's a BDA error in the first snippet. Make sure you have the proper BDA drivers for DVB-C they show two PIDS there. Their TV player might also be locking the device.

Sometimes Astrometa devices use RealTek tuners which are known to have problems with BDA.

Martin

[sharpeagle]

That's a BDA error in the first snippet.  Make sure you have the proper BDA drivers for DVB-C they show two PIDS there.  Their TV player might also be locking the device.

Sometimes Astrometa devices use RealTek tuners which are known to have problems with BDA.

Martin

Thanks, indeed, it is a RealTek under the hood....
The embedded tv player is not running, so it may be the a driver issue. Strange thing is that the native player works fine.
I've used the tuner in the past, it was W7 or WS2012, with a previous driver version. 
What I will try is to spawn a W7 VM with the old drivers and pass the USB to it. Then have a NPVR instance there, to see how it goes.
I tried pushing the old driver in W11 but it complained about driver signing (hash), although I disabled signing via bcdedit (nointegritychecks->Yes). I've even copied the old driver in system32/drivers after the new signed one got installed (disabled it first)....
I'll get back after my little experiment.

[sharpeagle]

One more thing:
I see in the logs that it uses the path c:\temp...
Now, this c:\temp is a symbolic link to a temp folder in a RAM drive. I thought at some point that this may be the issue, so I stopped NPVR service, renamed C:\Users\Public\NPVR-Data folder, changed the TEMP/TMP environment variable from c:\temp to c:\templocal, rebooted the devices...and it still uses c:\temp as the TEMP folder.
From where exactly does NPVR gets this variable?
Shall I reinstall it? Is this "c:\temp" stored somewhere else and not in Public folder?
Or "c:\temp" is used by default and it's a simple coincidence with my setup?

[mvallevand]

I only recall temp used for the installer and some Direct Show logging, so I am not sure what folders you are talking about, you need to upload the zipped logs I guess. The temp in the devicehost files is bogus I think.

Martin

[sub]

What is it putting in c:\temp?

[sharpeagle]

What is it putting in c:\temp?

2023-10-08 17:47:01.799    [DEBUG][4]    StartStream(): c:\temp\test.ts
2023-10-08 17:47:01.799    [DEBUG][4]    DigitalRecorderDVBC::Tune()

See the 1st post with the logs.

[mvallevand]

You only posted snippets but as I posted I think the DeviceHostWindows lines might be bogus.

Martin

[sub]

It doesn't need that c:\temp\test.ts file. It doesn't matter if you don't have a c:\temp directory, and it'll continue fine without it.

2023-10-08 17:47:01.799 [ERROR][4] Failed to create IDVBCLocator

I'd suggest trying this - stop the NextPVR service. Start a command prompt with 'run as administrator', and change directory to the c:\program files\nextpvr directory, then try manually running NextPVRServer.exe and doing the scan. I'm hoping you'll then have the required IDVBCLocator settings in the registry. After this, reboot.