Dear cracknme, I have tried, see attachment.
It was manually scanned only 546MHz contained multi plp channels.


Thank you.

There are no error(s) at all, so it should work normally.

Prog , the card support the standard 'KSPROPERTY_BDA_PLP_NUMBER' to set PLPId, is it set by any chance to '-1 ...

Hello evgenc,

Can you try the attached file(s), I want to check if any SelPLP/GetPLP function return any error(s). You can test with the Manual Scan, no need for a full Normal Scan.

Dear crackname, sorry to mislead you... At Manual scanning - all needed channels was detected since module ver. June 30.

Then Prog asked me to check autoscanning mode (Normal scan). So, since June 30 I have checked only autoscanning mode with new modules, all above logs are for autoscanning mode ...

additions:

1) if scan with delay then the same result as without delay ...

2) just find now, maybe it will helps you - when use manual scanning for PLP>0, the icon of #02 channel has "$" symbol...
Maybe the autoscanning mode detect it as pay TV channel and not shows it at scan results?!


So ...

Hello evgenc,

According to the logs , everything should work perfectly. Try the new module, and the PreRelease that Prog suggested.

Also try the new attached module, I think this would be the final working one.

From the log:
"H810::AfterChange(...): freq:546000, symb:8000000, PLPId=0" -> The ...

Hello evgenc,

Strange, the card detect 'DVB-T2' (in the log), but keeps returning weird PLPNum:
- H810::AfterChangeChannel PLPId=0, DVB-T2
- H810::GetPLP -> PLPNum=2
- H810::AfterChangeChannel PLPId=1, DVB-T2
- H810::AfterChangeChannel PLPId=0, DVB-T2
- H810::GetPLP -> PLPNum=0
- H810 ...

Strange, there is a PLPNum of '3' in the log that should not be returned by the card at all.

Try the attached new file, it will reset PLPId to 0 when there is no need for PLP.

evgenc,

Can you try the attached module, Just to test if we should set PLP before or after setting the Frequency/Transponder in hope to fix PLP on normal scan

Hello evgenc,

Glad you sorted the problem.

I forwarded the module to @Prog, he will probably release a new version soon.

Good luck

Hello evgenc,

1) Figured it could probably not work, that's why I posted the June 30 one.
2) Glad it work. I can't decide if an error occurred in the module or ProgDVB without checking the Log files.

You can add channels from manual scan, by scanning for available PLPs and select each PLP and do a ...

evgenc wrote: ↑

Sun Jun 30, 2019 6:07 pm

OK, crackname, it will be more convinient for you to communicate in English...

Yes, my fault, I used the file from your x64 folder, not x32...

Will make deep tests tomorrow...

Ok, good luck

Hello evgenc,

It's ok, I will use a translator, and I'll try to help as much as I can.

The module is not loaded at all, it should generate "BDA_AverMedia.txt" in logs directory, but it's not in the attached "log.rar".

You should copy the file in the folder "x32" because you are using the 32bits ...

Hello @evgenc

Can you try the attached module (backup the original one), then report if it work.

The shutdown can be disabled on the configuration Options > Controls > Bind Keys. Just look for Power Off in "Remote control key" column, and change the key.

Thank! This helped to disable this feature.

Yes, I also want to understand. And why does the remote control continue to work (with the ...

crackname
I tested the remote control, now it seems that all the keys are working. But there is some strange glitch in general, you have to press several times, so that the key would work. I checked on my native software again, where the key works right away, and ProgDVB here you have to press ...