Update EPG stops after 6 frequencies!?

[DrWG]

[attachment=undefined][attachment=undefined]Hello!
 
I have a problem with nextpvr on my Raspberry Pi 4, 2 MB RA, OS: Raspian.
Installed with nextpvr-helper. Should be the newest version.
Tuner USB-Stick: Hauppauge WinTV SoloHD
EPG Source: DVB/ATSC EPG
Installation is generally running fine: recording, playing, connection to web client, connections to Kodi …
Sufficient resources: RAM, CPU, OS/Programs on SD-Card, Recording Directory and Recording Buffer at external NAS (Windows Server)  
But if I start Update EPG it stops after 6 frequencies.
After that recording is no longer possible.
Restart of nextpvr-service or unplugging the tuner stick does not help. After restart of the Raspberry, recording and/or start of EPG update again is possible (but stops again after 6 frequencies).
If I delete some channels and start Update EPG at other frequencies it also stops after 6 frequencies.
Empty EPG database does not help.
Database npvr.db3 has ca. 12000 EPG entries (3,5 MB). The database could be opened with SQLite, looks o.K.
Same version on my windows server is running fine. EPG database should have ca. 45 MB.
I have added log files (device-adapter0: middle part deleted to match 2 MB).
Hope someone has an idea.

[Graham]

I have added log files.

The NextPVR forum includes a test to make sure that everyone is sitting up and paying attention ...  

Attachments larger than 2 Meg are silently ignored and do not attach.

[mvallevand]

Don't attached logs attached the zipped logs you get from the web app.

Martin

[DrWG]

Zipped logs attached.

[sub]

If you hit 'update epg' and leave it on the screen, what do you see when it stops?

[DrWG]

It counts down from 60 to 1 second at the last scanned frequency (in my case 122 MHz), then it stops and does not change to the next frequency. 
If I delete some channels, it stops at some other frequency, but again the 6th one.

[DrWG]

EPG data are scanned with different parameters in the Windows and Linux version.
Especially SID is always 100000 in the Windows version.
Could that be a reason for my EPG update problems?

Linux

<tuning>
<type>DVB-C</type>
<name>Das Erste HD</name>
<locator>
<conf>330000000OFF</conf>
</locator>
<service_id>11100</service_id>
<service_type>27</service_type>
</tuning>

Windows

<tuning>
<type>DVB-C</type>
<locator>
<frequency>330000</frequency>
<bandwidth>8</bandwidth>
<symbol_rate>6900</symbol_rate>
<modulation>QAM256</modulation>
</locator>
<service_id>100000</service_id>
<tsid>1051</tsid>
<onid>41985</onid>
<service_type>25</service_type>
<provider>ARD</provider>
</tuning>

[mvallevand]

The Windows (BDA) and Linux (dvbv5) logic for scanning are completely different.

Martin

[Rockthisparty]

Did you solve the problem? Just posted a rather similar problem and then found this post / thread.

[DrWG]

Yes, I have solved the problem: I have changed to Tvheadend.
I would emphasize this step for everyone!