progdvb.com

Crackname,
I have test it and it was find also one channel with PLP2, but did not find second channel with PLP1.
Logs and picture are attached.

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.

Попробуйту нормальный сканер с дополнительной задержкой в настройках сканера. Вподь до 2 секунд

Guys,
no positive result, special channels not deteced and not added to channel list.
In attachment is two logs, one is without transponder delay, secon - with delay 2000 ms.

Prog, насчет установки задержки после установки транспондера: Величина задержки после закрытия программы и вновь ее открытия, сбрасывается на ноль... Видимо, так задумано?

не самая часто используемая настройка. Может и глюк.

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::AfterChangeChannel PLPId=0, DVB-T2
- H810::GetPLP -> PLPNum=0

Please try the new module in the attachment; I modified the way we get PLPNum from the card using what AverTV use. Hope it'll work.

Yes, crackname, there is some positive movement now!
Your first module version have no result, but your second version (new) have find one additional channel #07 (PLP2), and did not find second channel (PLP1)...

Logs are in attachments.

В старой версии задержки сканирования не только не сохранялись но и не работали. См пререлиз.

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 first call to lock the transponder with 3 PLPs
"H810::GetPLP -> PLPNum=3, PLPId=0" -> Got the correct PLPs Count and Scanned PLP-0
"H810::AfterChange(...): freq:546000, symb:8000000, PLPId=1" -> The second call to lock the transponder with 3 PLPs using PLP-1 and Scanned PLP-1 (You got no Channel here, try adding delay to scan)
"H810::AfterChange(...): freq:546000, symb:8000000, PLPId=2" -> The third call to lock the transponder with 3 PLPs using PLP-2 and Scanned PLP-2 (You got 'Россия 24')

crackname, I have install final ProgDVB v. 7.28.2 now. After that I have add your final module (03-07-2019).
As before the autoscanning mode has find only one PLP>0 channel (#07) and showed it at scan results with other PLP0 channels and add it to channel list with other PLP0 channels...

Logs are attached.

By the way, I have checked the logs now, and find that while scanning the program has detected also the PLP1 channel (#02), but did not showed it at scan results and did not add it to channel list...

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?!

evgenc wrote: ↑

Wed Jul 03, 2019 6:44 pm

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, in Manual Scan everything work, but not in Normal Scan ?

Did the previous module find the PLP 2 Channel ?

Try the new module, I do a reset of PLP to '-1' before setting the new one every time we do transponder lock. And we do a delay of 4 Milliseconds after changing PLP.

If it still doesn't work, I will forward the Code to Prog, so he can add some Delay in the module that would probably fix it.

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 only.

In attachnment is log for autoscanning with module 03-07-2019 new. As before channel #02 not detects... If use manual scan then channel #02 will be detects as well.
So, do you need logs for manual scan?

evgenc wrote: ↑

Wed Jul 03, 2019 7:39 pm

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 only.

In attachnment is log for autoscanning with module 03-07-2019 new. As before channel #02 not detects... If use manual scan then channel #02 will be detects as well.
So, do you need logs for manual scan?

No need for the logs of manual scan, I just wanted to know if all the channels are found with the manual scan. So the problem in the Normal scan is probably from ProgDVB handling of the scan.

The "BDA_AverMedia.txt" log contain the correct data for the PLPs, so I think it's as Prog said before to increase the scan Delay.

I will forward the code of the module to Prog, so he can modify it and if he want, post the modified module here for test.

Задержка должна работать в сегодняшем пререлизе. В более старых - не работает.