43 replies to this topic

[Baltus72]

Baltus72

Maybe the problem drivers.
Install VTI with the latest drivers and check.

Thanks a lot for the suggestion. :-)
I flashed the box with VTI v7 and updated the image with the latest patches.

There was no "Preferred tuner for recording" so I'll have to assume that it's the same behaviour as in old OpenPLi 2.4 images.

However, I got the same issue with tuner selection in VTI, which indicates that the "Preferred Tuner" Auto function is broken for my setup.
That would be extremely strange as my setup is as simple as it gets for multiple tuners, and it's been non working at least since late march.

I've double and triple checked with clean flashes, and there's only one conclusion: OpenPLi 2.4 works ok but everything else fails miserably.
Basically, it seems there must've been a change in the Auto feature implementation at some point in the core image that affects all releases

that are built upon that code.

The question now is: can it be fixed and where to report the issue? Or is it possible to rip out the Auto function code from version 2.4 and
replace the current code? I have no idea if the code is isolated enough to "transfer" to newer builds, but I'd sure love to try if it's possible.

[Rob van der Does]

"Preferred tuner for recording" is unique for PLi(based) images.

[Baltus72]

I finally manged to pinpoint the issue here...

It turned out Dima73 was right about the drivers, although it was probably not the way he suspected. :-)

Basically, the drivers have been broken for Ultimo and multiple DVB-C tuners for more than 2 years.

OpenPLi 4 works, but *only* when I replace the drivers with an old version from the archives. The last
working driver is "vuplus-dvb-modules-vuultimo-3.1.1-4.4.3-20120628.tar.gz". This one is more than

two years old, and it's been broken since "vuplus-dvb-modules-vuultimo-3.1.1-4.4.3-20120820.tar.gz".

Can someone with connection to the VU+ developers please report this so that it can be fixed?

[theparasol]

Can someone with connection to the VU+ developers please report this so that it can be fixed?

 

VU+ is a bad manufacturer for opensource: they seem pretty ignorant for any external input at all.

For that reason I will never buy nor advise others any of their boxes.

 

Since this bug is present for 2 years I dont believe you are the first to discover and report it.

Most likely scenario is it wont get fixed ever, VU+ present models are not affected so there is no problem for the manufactures in terms of sales drop.

However I certainly hope the bug you discovered and reported here will be fixed but I'm very sceptic about the chances that will hapen.

 

BTW: In comparison I'm quite happy with my xp1000 manufacturer, the 2 times I reported a glitch in the XP1000 drivers both time they fixed it within days.

[Trial]

Hi,

I would say try the original image. You must use an image before 17th of july because after that date they switched to new kernel.

 

If there is a problem I would have read in the last 2 years. I am also pretty sure that I tested a multi tuner cable setup in the last year at my brother home.

 

ciao

Edited by Trial, 17 September 2014 - 06:08.

[littlesat]

In the original vu image they can work-a-round differences in their drivers...
We can't as we also support other boxes and we want to prevent code like if vu then fix...

[Baltus72]

@Trial,
Thanks for the tip about trying the original image. I tested the latest image before the kernel switch (vuplus-image-vuultimo-20140714162755_usb.zip),

but I get the exact same problem. Once I set one channel to record I can not switch to another transponder, and that basically makes the box useless...
And yes, I'd certainly also expect this to be a known issue, but I can't see where there's any room for mistakes on my side when simply testing channels

that don't require any softcam. The only thing I'm not quite sure about is the image versions, 1.6 and 2.1. I picked 2.1 as I assume it's the most relevant.

On a more positive note, I've at least gotten OpenPLi 4 and the old drivers to work quite well besides one issue. I can use all channels and all tuners but

there is one problematic transponder that can cause problems, depending on the sequence. Let's say I use transponder A, B and C, where C is the one

that causes problems. I can watch and record freely on all tuners except: If I record from transponder A + B, I get "Tune Failed" on zap to transponder C. 
Likewise, transponder C will fail on recording if I already record one channel and watch a third channel from transponder A and B. In other words, I must
make sure that transponder C is never the last in line when I have 3 transponers active simultaneously. This can be partially worked around by using the
"Zap and record" option for timer recordings. I have no idea if that is a driver issue as well, but I'm open for any potential suggestions.. :-)
 

[sebastien_be]

Hi,

 

is this issue still up to date for anyone? Because for me it has never worked with OpenPli. Here is the Issue:

 

- Solo2 with 2 Sat Câbles (Dish of 80cm with Monobloc Hotbird 13° & Astra 19,2°)

- M7 Group CI Module with legit Telesat (belgian provider) smartcard - No cardsharing !

- CI Settings correctly configurated: Support multi channel YES

 

I can watch and record one channel correctly on Hotbird for instance. But if i go to another channel (from another transport stream) then i have a black screen.

 

Any idea what this can be due to? It works fine on VTI for instance, but not on OpenPli. On Blackhole it depends from versions.

 

Kind regards,

Sebastien.

[christophecvr]

Wit the CI off M7 Group You can only decode 1 tuner at the same time. tuners.

[Huevos]

If you use your card directly you won't have this limitation.

[goldeneye]

TeleSAT is using nano 01 (CWOE) on it's channels so a white CI is mandatory in his case... For non CWOE channels your suggestion is fine...

[sebastien_be]

I'm sorry but this is not correct. You maybe confusing with Canalsat France that has indeed Nano 01. Telesat Belgium is applied only on 2 channels.

 

The CI module can decode more than one channel, and the card also. The problem comes from OpenPLI.

CI Module for instance on my smartTV works fine to record one channel and watch another one (from different transport stream)

Works also fine with certified receiver and the card

Also works with Vu+ Solo and VTI image for instance.

 

Thanks for the support.

[Dimitrij]

test...

 

FTA service Hotbird 13° and same time PiP FTA service Astra 19.2° works?

[sebastien_be]

FTA services works but not crypted channels. OpenPli is indeed able to process 2 FTA channels from two different tuners. But when we ask it to process to crypted channels it doesn't work.

[Robinson]

How do you "process" encrypted channels? Using mgcamd by any chance?

[sebastien_be]

Using the official CI Module. So i'm not using any of the software emulators.

The same smartcard can decrypt 2 different channels in an official sat receiver so i'm pretty sure also the card is not restricted.

[Huevos]

With a CI module you can only open one channel at a time. Put the card directly in a card slot and use a softcam.

[Erik Slagter]

A bit unfair to blame OpenPLi for that

[sebastien_be]

Hi,

 

It is not correct saying a CI module can open only one at the time. If i use old version of OpenPli or Blackhole it works fine !

 

It's a but unfair not recognizing there is a development issue with OpenPli!

[littlesat]

With a ci you only can encrypt one transponder at once... That is a big disadvantage from ci....an older openpli or blackhole will not changed thar fact...

Edited by littlesat, 26 December 2015 - 08:39.