644 replies to this topic

[littlesat]

Not true...

A tuner van be connected to either input one or input two...

So no fixes triple loops...

Edited by littlesat, 28 January 2016 - 17:28.

[Rob van der Does]

So what exactly isn't true then?

[MiLo]

The six "extra" tuners can dynamically connect to any one of the A/B tuners, they're not "fixed" to one or the other. All six could be connected to "A" at the same time.

[Rob van der Does]

Ah, yes, but if you fully use the box one (standard) Unicable LNB will be fully occupied by the 8 tuners. Of course other combinations can be possible.

[Erik Slagter]

Anyway, we (myself en athoik) have found several bugs in the VU+ supplied code, and besides, the code is really bad. It's full of copy-and-paste art. We already reduced it to about half it's size and still continueing. We want to finish that job before we're going to release. But it won't take long now.

[Rob van der Does]

Anyway, we (myself en athoik) have found several bugs in the VU+ supplied code, and besides, the code is really bad. It's full of copy-and-paste art. We already reduced it to about half it's size and still continueing. We want to finish that job before we're going to release.

Good work! Better a long wait and a job well done than the other way around!

 

Why is it that I'm not surprised VU didn't do a professional job.....

[sector_d]

Hello All,

 

What are the community feelings about the chances that FBC tuners can enable STBs to tune to MIS (Multiple Input Stream) transponders?

What about other type of modulations such as 32APSK ?

[athoik]

What are the community feelings about the chances that FBC tuners can enable STBs to tune to MIS (Multiple Input Stream) transponders?

Where did you find the information that FBC tuners can tune to MIS?

(currently it works for sure using TBS cards with some patches from crazycat for STV and Enigma2, also PLS works, T2-MI will be the next to test)

Edited by athoik, 9 February 2016 - 14:12.

[WanWizard]

MIS support will be part of OpenPLi 5, for tuners that support it. Athiok is working on that. I don't think that as of today, any of the existing boxes do though.

[sector_d]

 

What are the community feelings about the chances that FBC tuners can enable STBs to tune to MIS (Multiple Input Stream) transponders?

Where did you find the information that FBC tuners can tune to MIS?

(currently it works for sure using TBS cards with some patches from crazycat for STV and Enigma2, also PLS works, T2-MI will be the next to test)

 

I'm not stating it does. I am asking about the chances it can be done.

Because, as I see it, with FBC I would say the physical limitation is not there anymore. It should all come down to driver/ SW implementation.

 

But I'm not sure, hence I'm asking. I believe it should be possible to tune to MIS and also anyother different type of modulations with FBC hardware and the right low-level SW development.

[Erik Slagter]

The difference between "normal" and "multistream" is tiny. So I guess any tuner can handle it, if instructed properly. I also guess that's not going to happen, because mult-streams are used for distribution, which they now can do without scrambling. It's a bit comparable to 8PSK on DVB and 16/32PSK on DVB-S2. It's probably very well possible to support, but restricted by "the powers that be". So little chance to be released for consumer devices, including FBC.

[Huevos]

There seems to be a problem with FBC/Unicable.

 

Tested on 2 different setups at different locations.

1) Solo4K, LNB Inverto IDLB-QUDL42-UNI2L-1PP, Tuner A, Advanced, Unicable, SCR 1, 28 East. Tuner C, Advanced, Unicable, linked to tuner A SCR 2.

2) Solo4K, LNB Inverto IDLU-32UL40-UNBOO-OPP, Tuner A, Advanced, Unicable, SCR 1, 28 East. Tuner C, Advanced, Unicable, linked to tuner A SCR 2.

 

Start a recording on tuner A. Zap to another channel. Tuner C is now active. Stop recording on tuner A (automatically or manually). Now there is picture break up on tuner C, or no picture at all.

 

Or just set tuner C as preferred, and there will always be picture break up.

 

All recordings and viewed channels work fine until the root tuner is not in use.

Edited by Huevos, 9 February 2016 - 19:27.

[Erik Slagter]

What image/enigma are you testing with?

Edited by Erik Slagter, 9 February 2016 - 19:48.

[Huevos]

Test was using PLi FBC code.

[athoik]

I have both tuners connected to the same multiswitch ATM. So no Unicable to test.

Currently the leafs (linked) tuners can attach to any of root tuners, but when linked the root stays active.

I'll make some tests and see if I can reproduce that error using multiswitch.

Huevos, are you using our solo4k experimental branch? Or you notice that using the original VU+ code?

OK. You answered.

Edited by athoik, 9 February 2016 - 20:00.

[littlesat]

Using Pli fbc code on Pli image?

Edited by littlesat, 9 February 2016 - 20:09.

[athoik]

My test case, vusolo4k is in standby and another box is connected and watching tv.

Then the vusolo4k goes out of standby, tuner C consumed.

After a while the other box goes in standby, tuner A is not released.
 

---- links
    tuner 0, prev_links: , next_links: 2,
    tuner 1, prev_links: , next_links:
    tuner 2, prev_links: 0, , next_links:
    tuner 3, prev_links: , next_links:
    tuner 4, prev_links: , next_links:
    tuner 5, prev_links: , next_links:
    tuner 6, prev_links: , next_links:
    tuner 7, prev_links: , next_links:
    tuner 8, prev_links: , next_links:
    tuner 9, prev_links: , next_links:
++++ links
<   975.250110> [eDVBFrontend] dont close frontend 0 until the linked frontend 2 in slot 2 is still in use
<   977.486624> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 37(16)
<   980.290381> action ->  InfobarShowHideActions toggleShow
<  1021.602815> action ->  InfobarShowHideActions toggleShow
<  1035.250368> [eDVBFrontend] dont close frontend 0 until the linked frontend 2 in slot 2 is still in use
<  1095.250580> [eDVBFrontend] dont close frontend 0 until the linked frontend 2 in slot 2 is still in use
<  1155.250964> [eDVBFrontend] dont close frontend 0 until the linked frontend 2 in slot 2 is still in use
<  1215.251489> [eDVBFrontend] dont close frontend 0 until the linked frontend 2 in slot 2 is still in use

What happens in unicable scenario?

Edited by athoik, 9 February 2016 - 20:29.

[MCelliotG]

Well, I can confirm that thanks to Athoik's tireless efforts we have a flawlessly working MIS implementation on an Openpli5/SatDreamGr experimental image he compiled for tests on my VuDuo and my TBS5925 USB card! Channels are scanned and zapped in lightining speed, a lot faster than they do on pc, and the USALS/diseqc motor works very very fast and accurately as well!

 

Here are a bunch of screenshots I just took!

 

11179V 5W (RAI)




 

 

As a DXer myself, and personally speaking, I find it so funny to see exact and non-ending SNR in db on a Vu+ receiver, as we all know the drivers they provide are useless for someone to measure the signal in accuracy! Not the case anymore!

We are currently working on T2-MI and more stuff we'd like to see, currently I haven't tested yet if the tuner locks APSK modulations although I'm optimistic it does, and blindscan for this tuner!

[MCelliotG]

More MIS frequencies

12648V 5W (TNT France) amazing HD quality!




 

Edited by glamourservices, 10 February 2016 - 00:36.

[MCelliotG]

12188Η και 12341Η 4.9Ε (Zeonbud) the T2-MI stream 20 on 12188 is locked but gives 0 channels ftm!