67 replies to this topic

[kurben]

The channels with the sound jitter, are they using the AAC audio format? Check with yellow button. 

[zeros]

sound jitter, are they using the AAC audio format? Answer: No, but this problem is only in the DVB-T2 in the two local channels. With the problem was all right the procedure for a week with athoik patch, but it came back with sundtek solution. I will post screenshot about the yellow button result tonight.

Edited by zeros, 2 February 2016 - 11:20.

[zeros]

One more difference - with tuner TypeChanged.

Also I will add NimManager different Teams py-files

I don't know how ohter Teams per say, but surely this thing limps with PLi.

Attached Files

•  NimManager-different-Teams-py-files.rar   57.32KB   1 downloads
•  tunerTypeChanged.png   444.19KB   2 downloads

[Dimitrij]

zeros

Add this  NimManager.py in folder /usr/lib/enigma2/python/Components/

[zeros]

Thanks! It on my box and restart is also done. I`m reporting after some testing.

[zeros]

Hi Dimitrij!

I checked what you've changed, and find the only thing in line 158, you swapped the order "DVB-S2", "DVB-S" to "DVB-S", "DVB-S2".
I can tell you that the sound is the same as previous (the sound jitter on DVB-T2 channels there exist, unfortunately).
A timer recording from DVB-S(2) I can't yet say if it is OK with DVB-T and DVB-T2 - it is too early to report! It seems that the worse is not gone in anyway, but I'm not sure that this thing is already OK with that! Yesterday it worked, but has in the past also been that works, although rather rare!

I will try to swap back to

types = [type for type in ["DVB-T2", "DVB-T", "DVB-C", "DVB-S2", "DVB-S", "ATSC"] if check(slot.frontend_id, type)]

to see, if the sound jitter on DVB-T2 channels fade away with that (in order to be sure on that). That worked in my mind a week and on my side everything was fine, but that was not OK for sundtek DVB-C!

If the sound jitter disappears with it off, then I have more ideas...

Attached Files

•  DVB-S2_DVB-S.png   101.93KB   2 downloads

[zeros]

Dimitrij, look at ATV code on NimManager-ATV.py: (line 2095)

except:
   if slot.description.find("Sundtek SkyTV Ultimate III") > -1:
    print"[NimManager] Sundtek SkyTV Ultimate III detected, multiType = False"
    addMultiType = False

I think we should add it too. And probably something more also!

Attached Files

•  except-Sundtek.png   498.6KB   2 downloads

[sundtek]

what does cat /proc/bus/nim_sockets show up?

 

Don't do any detection based on a complete device name.

[zeros]

Hi sundtek!

in my case it gives me:

root@dm7020hd:~# cat /proc/bus/nim_sockets

NIM Socket 0:

        Type: DVB-S2

        Name: BCM4505

        Has_Outputs: no

        Frontend_Device: 0

        I2C_Device: 0

NIM Socket 1:

        Type: DVB-T

        Name: CXD1981

        Has_Outputs: yes

        Mode 0: DVB-C

        Mode 1: DVB-T

        Frontend_Device: 1

        I2C_Device: 2

NIM Socket 2:

        Type: DVB-T

        Name: PCTV 290e

        Has_Outputs: no

        Frontend_Device: 2

root@dm7020hd:~#

I will ask from a friend, how he will see his sundtek stick. If someone comes to the front, please let it know (I do not have at the moment Sundtek Stick, as I use the PCTV 290e.

Edited by zeros, 3 February 2016 - 17:15.

[andy1]

Only DVB S and S2 original tuners are working on my ET10000.

 

DVB C and DVB T2/T original tuners currently shows no signal.

[zeros]

andy1, whether they previously worked for You?

[andy1]

Only DVB S and S2 original tuners are working on my ET10000.

 

DVB C and DVB T2/T original tuners currently shows no signal.

I have reverted back to img.20160127 and all tuners are back to normal and working fine.

[zeros]

I'm currently testing the Dmitrij file, today I have everything working, but it has in the past also been.
This error is sneaky.

[Dimitrij]

I confirm the problem:

Sundtek DVB-T not in NIim list

et8500 login: root
root@et8500:~#  cat /proc/bus/nim_sockets
NIM Socket 0:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 0
        Has_Ouput: yes
        I2C_Device: 0
NIM Socket 1:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 1
        Has_Ouput: yes
        I2C_Device: 1
NIM Socket 2:
        Type: DVB-S2
        Name: AVL6211
        Frontend_Device: 2
        Has_Ouput: yes
        I2C_Device: 2
NIM Socket 3:
        Type: DVB-C
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Mode 2: DVB-T
        Name: Si216x
        Frontend_Device: 3
        Has_Ouput: yes
        I2C_Device: 3
NIM Socket 4:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 4
        Has_Ouput: no
        I2C_Device: 11
NIM Socket 5:
        Type: DVB-S2
        Name: Sundtek DVB-S/S2 (IV) (0/0) (USB)
        Frontend_Device: 5
        Has_Ouput: no
        I2C_Device: 12
root@et8500:~#

[Erik Slagter]

And that is because one of the patches we applied last week?

[Dimitrij]

It should be a thorough investigation.

[andy1]

 

Only DVB S and S2 original tuners are working on my ET10000.

 

DVB C and DVB T2/T original tuners currently shows no signal.

I have reverted back to img.20160127 and all tuners are back to normal and working fine.

 

Info. Pluggable dualtuners on ET10000 that didn't work on img. 20160202 and latest 20160203: Si2169 (DVB-C/T/T2) I haven't tested any img. between january 27 and february 02.

[zeros]

Erik, the problem exist a long time ago, before this patch.
This is IMHO very good offer by Dimitrij post #24 - in my opinion, could give it a try!? So far, here is all well. What do you think?

[zeros]

Hi!
It It seems to me now that it's all right.
On current PLi: (also on all the rest Teams works (openatv, Vix, etc.)
types = [type for type in ["DVB-C", "DVB-T", "DVB-T2", "DVB-S2", "DVB-S", "ATSC"] if eDVBResourceManager.getInstance().frontendIsCompatible(slot.frontend_id, type)]

and on Dimitrij offered Mod.:

types = [type for type in ["DVB-C", "DVB-T", "DVB-T2", "DVB-S", "DVB-S2", "ATSC"] if eDVBResourceManager.getInstance().frontendIsCompatible(slot.frontend_id, type)]

 

Very good, well done!!!

 

Can you explain to me why this sequence is important? If it can, in some cases, cause problems for another user(s). Anyway, I have all right with that Mod.!

[Dimitrij]

so

NIM Socket 3:
        Type: DVB-T2
        Mode 0: DVB-T2
        Mode 1: DVB-C
        Mode 2: DVB-T
        Name: Si216x
        Frontend_Device: 3
        Has_Ouput: yes
        I2C_Device: 3
NIM Socket 4:
        Type: DVB-T
        Name: Sundtek DVB-T (III) (1/0) (USB)
        Frontend_Device: 4
        Has_Ouput: no
        I2C_Device: 11

In this situation the DVB-T can not be deleted:

				if "DVB-T2" in types:
					# DVB-T2 implies DVB-T support
					types.remove("DVB-T")

Edited by Dimitrij, 4 February 2016 - 08:19.