Bug 391116

Summary: kaffeine doesn't find some transponders on Astr 19.2E
Product: [Applications] kaffeine Reporter: peter9999
Component: generalAssignee: Bulat <ainnatul5202>
Status: REPORTED ---    
Severity: normal CC: ainnatul5202, kartografixer, peter9999
Priority: NOR    
Version First Reported In: 2.0.14   
Target Milestone: ---   
Platform: Android   
OS: ChromeOS   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Debug info presented ba caffeine in the diagnostic window

Description peter9999 2018-02-26 18:21:30 UTC
Created attachment 111025 [details]
Debug info presented ba caffeine in the diagnostic window

kaffeine finds only some transponders on Astra 19.3E.  For example the stations on 10744 Mhz (Phoenix, arte, tagesschau24, all SD) are omitted. Many other channels are ok. The DVB-Card /Skystar2) is ok, runs in an Windows environment in same machine. Manual entry of the channels isn't possible, because the Audio-PID-field is not editable. Same Problem with version 2.0.14.

The diagnostic window of kaffeine is in the appeded file
Comment 1 Mauro Carvalho Chehab 2018-02-27 03:15:47 UTC
(In reply to peter9999 from comment #0)
> Created attachment 111025 [details]
> Debug info presented ba caffeine in the diagnostic window
> 
> kaffeine finds only some transponders on Astra 19.3E.  For example the
> stations on 10744 Mhz (Phoenix, arte, tagesschau24, all SD) are omitted.
> Many other channels are ok. The DVB-Card /Skystar2) is ok, runs in an
> Windows environment in same machine. Manual entry of the channels isn't
> possible, because the Audio-PID-field is not editable. Same Problem with
> version 2.0.14.
> 
> The diagnostic window of kaffeine is in the appeded file

Did you try to enable "Other NIT" options at Kaffeine scan popup window?
It takes more time to parse channels, but it should find the other channels.
Comment 2 peter9999 2018-02-27 09:28:54 UTC
   Yes, tried this also, but no success either.


   Am 27.02.2018 um 04:15 schrieb Mauro Carvalho Chehab:

     https://bugs.kde.org/show_bug.cgi?id=391116          
     --- Comment #1 from Mauro Carvalho Chehab      <mchehab+kde@kernel.org> [1]      ---
     (In reply to peter9999 from comment #0)

       Created attachment 111025 [details]
       Debug info presented ba caffeine in the diagnostic window
       
       kaffeine finds only some transponders on Astra 19.3E.  For example the
       stations on 10744 Mhz (Phoenix, arte, tagesschau24, all SD) are omitted.
       Many other channels are ok. The DVB-Card /Skystar2) is ok, runs in an
       Windows environment in same machine. Manual entry of the channels isn't
       possible, because the Audio-PID-field is not editable. Same Problem with
       version 2.0.14.
       
       The diagnostic window of kaffeine is in the appeded file     

     Did you try to enable "Other NIT" options at Kaffeine scan popup window?
     It takes more time to parse channels, but it should find the other channels.
   

   


   1. mailto:mchehab+kde@kernel.org
Comment 3 Mauro Carvalho Chehab 2018-02-27 12:24:33 UTC
(In reply to peter9999 from comment #0)
> The diagnostic window of kaffeine is in the appeded file

Hmm...
    frequency: 10758,50 MHz is out of LNBf range

It means that either the LNBf you selected is not right or that you hit a bug at libdvbv5.

Please check if your LNBf is properly set. If so, what libdvbv5/v4l-utils are you using? I recommend using the latest upstream version (1.14.2), but, if you're using an older version, you need at least version 1.12.3, as several issues at LNBf settings were backported to it.
Comment 4 Mauro Carvalho Chehab 2018-02-27 12:26:27 UTC
(In reply to Mauro Carvalho Chehab from comment #3)
> (In reply to peter9999 from comment #0)
> > The diagnostic window of kaffeine is in the appeded file
> 
> Hmm...
>     frequency: 10758,50 MHz is out of LNBf range
> 
> It means that either the LNBf you selected is not right or that you hit a
> bug at libdvbv5.
> 
> Please check if your LNBf is properly set. If so, what libdvbv5/v4l-utils
> are you using? I recommend using the latest upstream version (1.14.2), 

I meant to say latest stable upstream version (1.14.2):

https://git.linuxtv.org/v4l-utils.git/log/?h=stable-1.14

> but,
> if you're using an older version, you need at least version 1.12.3, as
> several issues at LNBf settings were backported to it.
Comment 5 peter9999 2018-02-27 20:23:38 UTC
The LNB is ok. I use version 1.12.5-1 of lidvbv5.
Comment 6 Mauro Carvalho Chehab 2018-02-28 10:08:39 UTC
(In reply to peter9999 from comment #5)
> The LNB is ok. I use version 1.12.5-1 of lidvbv5.

I'll try to reproduce the bug here with my RF generator. Could you attach the settings you're using for your DVB settings here? It is located at:

    ~/.local/share/kaffeine/config.dvb

From your logs, it is missing channels at 10758,50 MHz, 10788,00 MHz and  10743,75 MHz. Any other transponders are missing?
Comment 7 Mauro Carvalho Chehab 2018-02-28 10:14:16 UTC
(In reply to Mauro Carvalho Chehab from comment #6)
> (In reply to peter9999 from comment #5)
> > The LNB is ok. I use version 1.12.5-1 of lidvbv5.
> 
> I'll try to reproduce the bug here with my RF generator. Could you attach
> the settings you're using for your DVB settings here? It is located at:
> 
>     ~/.local/share/kaffeine/config.dvb
> 
> From your logs, it is missing channels at 10758,50 MHz, 10788,00 MHz and 
> 10743,75 MHz. Any other transponders are missing?

Also, what LNBf are you using? For Astra 1E, you can't use the Universal one, as it doesn't support Astra frequency ranges. You need to setup it to either EXTENDED or ENHANCED. The EXTENDED LNBf is a variant of Universal LNBfs, designed to also support the Astra 1E ranges.
Comment 8 peter9999 2018-02-28 10:55:31 UTC
   The LNB works fine. I am sure, because it works with all the
   frequencies in our home. And I use the same DVB-card in the same
   computer in an Windows7-Environment with the DVBViewer without any
   problem.


   [device]
   deviceId=P13d0210313d02103
   frontendName=ST STV0299 DVB-S
   configCount=1
   [config]
   type=1
   name=Astra-19.2E
   scanSource=Astra-19.2E
   timeout=1500
   higherVoltage=1
   configuration=0
   lnbNumber=0
   lnb=UNIVERSAL
   latitude=24
   longitude=0


   Am 28.02.2018 um 11:14 schrieb Mauro Carvalho Chehab:

     https://bugs.kde.org/show_bug.cgi?id=391116          
     --- Comment #7 from Mauro Carvalho Chehab      <mchehab+kde@kernel.org> [1]      ---
     (In reply to Mauro Carvalho Chehab from comment #6)

       (In reply to peter9999 from comment #5)         

         The LNB is ok. I use version 1.12.5-1 of lidvbv5.       

       I'll try to reproduce the bug here with my RF generator. Could you attach
       the settings you're using for your DVB settings here? It is located at:
       
           ~/.local/share/kaffeine/config.dvb
       
       From your logs, it is missing channels at 10758,50 MHz, 10788,00 MHz and 
       10743,75 MHz. Any other transponders are missing?     

     Also, what LNBf are you using? For Astra 1E, you can't use the Universal one,
     as it doesn't support Astra frequency ranges. You need to setup it to either
     EXTENDED or ENHANCED. The EXTENDED LNBf is a variant of Universal LNBfs,
     designed to also support the Astra 1E ranges.
   

   


   1. mailto:mchehab+kde@kernel.org
Comment 9 Mauro Carvalho Chehab 2018-02-28 11:35:37 UTC
(In reply to peter9999 from comment #8)

>    lnb=UNIVERSAL

That is the problem. The frequency range for UNIVERSAL LNBf is:

	Universal, Europe
	Freqs     : 10800 to 11800 MHz, LO: 9750 MHz
	Freqs     : 11600 to 12700 MHz, LO: 10600 MHz

With corresponds to the older Universal LNBfs, with don't support frequency ranges between 10.7 to 10.8GHz, and whose max frequency is 12.7GHz.

The frequency range for EXTENDED is:

EXTENDED
	Astra 1E, European Universal Ku (extended)
	Freqs     : 10700 to 11700 MHz, LO: 9750 MHz
	Freqs     : 11700 to 12750 MHz, LO: 10600 MHz

It has an extra 100 MHz range at low frequencies, between 10.7GHz and 10.8GHz, and an extra 50 MHz range at high frequencies, between 12.7GHz and 12.75 GHz.

If you change your LNBf to Extended, Kaffeine should be able to get the other transponders.
Comment 10 peter9999 2018-02-28 13:47:35 UTC
   That was the problem! Works now perfect, thank you!

   Why can´t I change the channels data manually? It is not possible,
   because the Audio-PID field is greyed out. An in the json-database
   there is an undocumented "blob"-field. Tried some modifications, but
   it didn´t work.


   Am 28.02.2018 um 12:35 schrieb Mauro Carvalho Chehab:

     https://bugs.kde.org/show_bug.cgi?id=391116          
     --- Comment #9 from Mauro Carvalho Chehab      <mchehab+kde@kernel.org> [1]      ---
     (In reply to peter9999 from comment #8)


          lnb=UNIVERSAL     

     That is the problem. The frequency range for UNIVERSAL LNBf is:
     
             Universal, Europe
             Freqs     : 10800 to 11800 MHz, LO: 9750 MHz
             Freqs     : 11600 to 12700 MHz, LO: 10600 MHz
     
     With corresponds to the older Universal LNBfs, with don't support frequency
     ranges between 10.7 to 10.8GHz, and whose max frequency is 12.7GHz.
     
     The frequency range for EXTENDED is:
     
     EXTENDED
             Astra 1E, European Universal Ku (extended)
             Freqs     : 10700 to 11700 MHz, LO: 9750 MHz
             Freqs     : 11700 to 12750 MHz, LO: 10600 MHz
     
     It has an extra 100 MHz range at low frequencies, between 10.7GHz and 10.8GHz,
     and an extra 50 MHz range at high frequencies, between 12.7GHz and 12.75 GHz.
     
     If you change your LNBf to Extended, Kaffeine should be able to get the other
     transponders.
   

   


   1. mailto:mchehab+kde@kernel.org
Comment 11 kartografixer 2018-08-20 19:09:07 UTC
I did what Mauro suggested and, yes, there were more transponders.

BUT:

(1.) The list still isn't complete, e. g. there only ten radio stations as before.

(2.) I can hear no sound from the radio stations, or it has many interruptions.

I am especially interested in the german public radio stations as NDR, MDR, WDR, BR, HR and so on.
Comment 12 Mauro Carvalho Chehab 2019-05-03 20:06:41 UTC
*** Bug 398075 has been marked as a duplicate of this bug. ***
Comment 13 Mauro Carvalho Chehab 2019-05-03 20:07:17 UTC
Could you please test with Kaffeine 2.0.17? I found a bug there with could be affecting channel scanning:

https://cgit.kde.org/kaffeine.git/commit/?id=7960208dad913d331ffdd6a129bfdc935337a4e5