318 replies to this topic

[athoik]

Tuners that support dvb-t and dvb-c (delsys) should be able to switch to t or c mode, as long as the manufacturer has kernel >= 3.3 and doesn't rely on type switch using proc.

Eg. VU+ although it has kernel with delsys it still uses proc to switch type on their tuners.

Anyway it would be nice to know what box is used and what tuner.

I have some USB tuners, need time to check..

[Abu Baniaz]

Receiver: Duo 4K
USB tuner: Xbox One Digital TV Tuner

https://www.linuxtv.org/wiki/index.php/Xbox_One_Digital_TV_Tuner

It is a hybrid tuner. One connection. Only one mode at a time.

Really sorry for confusion and incorrect details. The tuner is working fine with the multi-tuner commits. I had to install drivers in particular order.
dvb-usb-mn8847x then
dvb-usb-dib0700

Less than £10 for a hybrid DVB-T2/DVB-C tuner.

This is thread is about the multi-tuner commits, so I will start another thread for the USB tuner. Once again, apologies for the incorrect details.

[zeros]

In my case I tested thoroughly different variants.

Triple: 2 x DVB-S2 / S2X, 1x C/T2

First connector (marked LNB1)

Second connector (marked LNB2)

Third connector (marked RF)

 

The current situation in my case:

I can configure one C/T2, C/T2 can be only on Third connector (marked RF). I tried to place signal also to First connector and Second connector (with a special adapter-connector), but it won't work, as was expected.

When I put the DVB-T2 signal into Third connector, I can configure like two separate tuners - under Tuner A or Tuner B.

The same thing for First connector (marked LNB1) - I can configure it under Setup Tuner A or Setup Tuner B. When I put my Sat cable into First connector (marked LNB1), I need to describe it under Tuner A.

 

OK, in my opinion I need this kind of configuration situations for my Triple tuner:

Setup Tuner A:

Tuner type: disabled or DVB-S2 or DVB-S2+DVB-T2 or DVB-S2+DVB-C or DVB-T2 or DVB-C

Setup Tuner B:

Tuner type: disabled or DVB-S2 or DVB-S2+DVB-T2 or DVB-S2+DVB-C or DVB-T2 or DVB-C

 

Is it possible to describe such a terrible thing, what do you mean? 

At the moment I can describe nicely only one DVB-S2 and one DVB-C/T2 Or DVB-S2 and DVB-S2 or DVB-C/T2 and DVB-C/T2 (pointless)

And yes, I can't test DVB-C, because I don't have it.

And I made one more test with two DVB-S2. I configured Tuner A: as DVB-S2 and Tuner B: as DVB-S2 - then the two DVB-S2 works but no DVB-C/T2 then

Is my order a big job? (I'm afraid so)

It probably needs then also check for Si2169C and Si2169D? (Like a special Triple tuners)

Attached Files

•  Tuner-A-DVB-S2.png   409.37KB   3 downloads
•  Tuner-B-DVB-S2.png   275.5KB   3 downloads

[littlesat]

As far I know a Si tuner is hardswitchable

[zeros]

I'll give you more details just in case-
If I configure so:
Setup Tuner A: DVB-S2
Setup Tuner B: DVB-S2
(I cand do so at the moment with your last changes)

And the “real Sat signal” is connected to
First connector (marked LNB1)
(secont connector let stay empty, it means Tuner B not connected)
Then I have picture on TV.

Now I swapped “real Sat signal” is connected to
Second connector (marked LNB2)
and first remains empty.
Then I had no picture on TV. It means it try to get sigal from first input.

I made more test so, that configured then Tuner A disabled
And picture came to TV.

So I assume that this part works fine, only identification or detection is missing.
And you're probably right.

[Taykun345]

Receiver: Duo 4K
USB tuner: Xbox One Digital TV Tuner

https://www.linuxtv.org/wiki/index.php/Xbox_One_Digital_TV_Tuner

It is a hybrid tuner. One connection. Only one mode at a time.

Really sorry for confusion and incorrect details. The tuner is working fine with the multi-tuner commits. I had to install drivers in particular order.
dvb-usb-mn8847x then
dvb-usb-dib0700

Less than £10 for a hybrid DVB-T2/DVB-C tuner.

This is thread is about the multi-tuner commits, so I will start another thread for the USB tuner. Once again, apologies for the incorrect details.

 

 

Nice suggestion, didnt know that it exists. Also cheap as chips. Does it work stable? I dont need it now (i have sundtek in my drawer - dont use it anymore) but information might be useful for others. You need newer kernel?

[WTE]

Receiver: Duo 4K
USB tuner: Xbox One Digital TV Tuner

https://www.linuxtv.org/wiki/index.php/Xbox_One_Digital_TV_Tuner

It is a hybrid tuner. One connection. Only one mode at a time.

Really sorry for confusion and incorrect details. The tuner is working fine with the multi-tuner commits. I had to install drivers in particular order.
dvb-usb-mn8847x then
dvb-usb-dib0700

Less than £10 for a hybrid DVB-T2/DVB-C tuner.

This is thread is about the multi-tuner commits, so I will start another thread for the USB tuner. Once again, apologies for the incorrect details.

 

 

This tuner is not support in Openpli and you need => Kernel 4.16

Backport drivers aren't available in vuplus BSP layer.

 

So it cannot work in Openpli image.

[zeros]

For one Triple tuner such config options:

Tuner A: DVB-S2
Tuner B: DVB-S2

Tuner A: DVB-S2
Tuner B: DVB-T2

Tuner A: DVB-C
Tuner B: DVB-T2

Tuner A: DVB-S2+DVB-C
Tuner B: DVB-S2+DVB-T2

Tuner A: DVB-S2+DVB-T2
Tuner B: disabled

Tuner A: disabled
Tuner B: disabled

Tuner A: disabled
Tuner B: DVB-S2+DVB-T2

Tuner A: DVB-S2+DVB-T2
Tuner B: DVB-S2+DVB-T2

Tuner A: DVB-S2+DVB-T2
Tuner B: DVB-S2+DVB-C

Etc. For disabled staff

[littlesat]

+ is not there.... for hotswitchable tuners you can enable dub-t/c/s or atsc...

[zeros]

That configuration work OK at the moment:
—
Tuner A: DVB-S2
Tuner B: DVB-S2

Tuner A: DVB-S2
Tuner B: DVB-T2

Tuner A: DVB-C
Tuner B: DVB-T2

Tuner A: disabled
Tuner B: disabled

Tuner A: DVB-T2
Tuner B: DVB-T2

Tuner A: DVB-C
Tuner B: DVB-S2

Tuner A: DVB-S2
Tuner B: disabled

Tuner A: disabled
Tuner B: DVB-S2

Tuner A: DVB-C
Tuner B: DVB-C

—
When I configure
Tuner A: DVB-S2
Tuner B: DVB-S2

They work OK, but I can’t configure and therefor use Third Input DVB-T2/C.

I think it needs also opportunity Tuner A: DVB-S2+DVB-C or
Tuner A: DVB-S2+DVB-T2
And the same for Tuner B.

Then my Triple is more correct and NB! better described as on the original dmm image. Is it very difficult to add something like that for testing?

Edited by zeros, 10 March 2019 - 21:13.

[zeros]

I made this test today with my one Triple tuner, I never tried it before:
Tuner A: DVB-T2
Tuner B: DVB-T2
And the “real DVB-T signal” is connected to Third connector (marked RF).
Only one DVB-T cable is connected.

And I can make a whole two separate MUX on different frequencies to put recording. Frankly, I was surprised. What do you call it?

I'm pretty sure it can do at once also this:
Tuner A: DVB-T2
Tuner B: DVB-C

If one cable exists both.

Attached Files

•  1D5A8553-BD66-41D0-8E75-0F14BCC7403F.jpeg   121.84KB   5 downloads
•  D09D736B-173D-4143-BDCE-581A7055A5B4.jpeg   84.02KB   4 downloads

[zeros]

And I may try that kind of changes, but I'm afraid it needs more then. Just the topic can also be left from my side.

Attached Files

•  DVB-S2_DVB-T2.png   466.94KB   3 downloads

[littlesat]

I'm afraid you missed something. As far I'm informed the DMM920 (which we do not support) is not an hotswitchable tuner... If it is a hotswitchable tuner you need to 'patch' NimManager.py so it is recognized as hotswitchable tuner... then everything should do what you wanted...

[zeros]

Thank you, I'll try.
This part is where I have to change, right?
You don't have to bother your head, I'll keep thinking.
Yes, the Triple it's a little special and I don't know exactly myself, how it is right, but currently some part from it remains unused.

Attached Files

•  multi_type.png   421.29KB   3 downloads

[athoik]

I suggest this change:
 

diff --git a/lib/python/Components/NimManager.py b/lib/python/Components/NimManager.py
index 26319e8..8884ea3 100644
--- a/lib/python/Components/NimManager.py
+++ b/lib/python/Components/NimManager.py
@@ -517,7 +517,7 @@ class NIM(object):
                                types.remove("DVB-S")
                        if len(types) > 1:
                                self.multi_type = {}
-                               self.hotswitchable = self.description.upper().startswith("AVL")
+                               self.hotswitchable = not os.path.exists("/proc/stb/frontend/%d/mode" % self.frontend_id)
                                for type in types:
                                        self.multi_type[str(types.index(type))] = type

If the proc for changing mode doesn't exist, then tuner should be considered as hotswitchable.

Please note that even tuner with DVB-T/C should also obey to this rule. So if you have a DVB-T / DVB-C (cable) combiner (and frequencies do not overlap) it should work just fine!

Edited by athoik, 12 March 2019 - 18:53.

[littlesat]

I fully agree... please puah!

[athoik]

pushed: https://github.com/O...a6639ebf49a07ee

[littlesat]

Thanks!... I hope we now finally finished it this was a relive large project... and thanks for helping! Especially for the cpp stuff...

Edited by littlesat, 12 March 2019 - 20:06.

[athoik]

There might be some places where fine-tune might need, especially once branched on next RC and more people start testing it.

On Satconfig.py I think we should first check for howswitchable and then for multitype.

                                if x.isMultiType():
                                        text = "%s: (%s)\n%s" % (_("Switchable tuner types"), ','.join(x.getMultiTypeList().values()), text)
                                elif  x.isHotSwitchable():
                                        text = "%s: (%s)\n%s" % (_("Hotswitchable tuner"), ','.join(x.getMultiTypeList().values()), text)

[zeros]

I added it manually (your change) into the code (and well done 

First it seems me OK, but need more deep testing. But yes, OK, I think!

Attached Files

•  Hotswitchable-1.png   517.51KB   5 downloads