104 replies to this topic

[ntj]

Just want to join in to report that Disable the lcd4linux has helped me in my "tune failed" problem (sometimes when zapping signal showing 0% and getting a "tune failed" and then tuned OK) on my VU+ Ultimo 4K

 

Problem has been there on openpli 6.1, 6.2 and 7.0 but not on the "factory" VU+ image. first i tried to change the Diseqc and bought a Spaun, did not help.

I have 2 S2 fbc tuners and one non fbc DVB-C tuner and the "tune failed" problem has only been seen on the fbc tuners.

 

This input will probably not help in finding where the problem is but i just want to write that it helped me also on the Ultimo 4K box.

[WanWizard]

I do find it interesting that it happens only with the FBC tuners, and not with legacy tuners...
 
Can you remember if it happened only on leaf tuners ( C - H ), or on the root tuners ( A - B ) as well?

[anudanan]

I´m surprise that my two uno4kse with the same fbc tuner don´t have those problems

Are there different driver code for the fbc tuners from vuplus for duo4k and uno4kse.

Maybe it has to do with the higher speed of the duo4k and a timing bug inside the drivercode?

Edited by anudanan, 8 March 2019 - 18:36.

[Erik Slagter]

I can't explain it. Let's leave it there.

[ntj]

I do find it interesting that it happens only with the FBC tuners, and not with legacy tuners...
 
Can you remember if it happened only on leaf tuners ( C - H ), or on the root tuners ( A - B ) as well?

 

It happens both on A and B , i have not reflected if it happens also on C-H, 

Maybe i will enable the lcd4linux just to check (just happy that it works right now so lets see "Don´t change a working system")

[WanWizard]

I wonder why LCD4linux is installed by default on every box with a display, as it is clearly not needed for the default LCD skin. A legacy thing, from before we had these skins?

[Erik Slagter]

Is it? I remember having to install it always explicitly.

 

But afaik it's not activated by default, so harmless. Saves the people from having to search for the plugin and install it. Just like other related, receiver-specific stuff.

Edited by Erik Slagter, 8 March 2019 - 19:09.

[ntj]

 

I do find it interesting that it happens only with the FBC tuners, and not with legacy tuners...
 
Can you remember if it happened only on leaf tuners ( C - H ), or on the root tuners ( A - B ) as well?

 

It happens both on A and B , i have not reflected if it happens also on C-H, 

Maybe i will enable the lcd4linux just to check (just happy that it works right now so lets see "Don´t change a working system")

 

 

 To answer your question, tested to start 3 recordings with enabled lcd4linux and zapped and once also got the problem with tuner D.

[WanWizard]

Is it? I remember having to install it always explicitly.

 

But afaik it's not activated by default, so harmless. Saves the people from having to search for the plugin and install it. Just like other related, receiver-specific stuff.

 

No, it is installed by default (controlled by the machine feature "colorlcd"), and if installed, it is "on" by default.

[-M-]

One thing I thought about...

I think it is an explanation why users with SatCR (unicable) LNB's are not affected. The FBC tuner will not tune on zapping. The tuner in the box tune to the 'transponder' frequency in the cable and these are the same. It is the LNB that will tune. So I think the spooky delay is when the FBC tuner is tuning.

[WanWizard]

Quite possible, it must be something like that.

[Abu Baniaz]

Am I correct in that OpenPLI use 20181226 drivers whereas OE-A use 20190212 drivers?

[athoik]

That's right, this the trade-off having stable images than having nightly builds.

Of course it would be nice if more people could join the "beta / testing" team and make releases going out much faster.

[Florie]

How to join?

[WanWizard]

It is not open to the public at the moment. We did that in the past, with the result that all end-users installed testing images, and the flooded the forums with "it doesn't work' reports.

 

We haven't yet found a way to control that.

[Bbbb]

Hello, recently I have a VU + DUO 4k and the zapping is also very slow.

 

I am not an expert at all, but notice that the delay occurs when the transponder is changed.

 

The found trick on the dutch forum of user Lemmingsbeest works great.

His advice:

Try the following:

Go to the channel that gives "tuning failed" and wait a while for the picture.

Then go to menu, settings, channel search, manual search, then change search mode to user-defined transponder, set FEC to auto and then press ok.

Recipient then seeks on that transponder then confirm green button ..

Then back to your channel list ...

Repeat on other transponders that also have that problem ..

I now have a Vu Ultimo4k and have had that problem on some transponders ..

 

Only if I do a "fast scan" do I have to do this trick.

I always find it annoying to have to do that............and hope that this problem is easier to solve.

Thx

[WanWizard]

Remove lcd4linux, as mentioned above.

[-M-]

How with OpenPLi 7.1, will the lcd4linux be installed by default?

 

PS. I found it strange that this is included, but not epgsearch. I think it is very very few people that want the lcd4linux, but many want epgsearch.

[Erik Slagter]

I'd rather find out how lcd4linux can slow down zapping and fix that.

 

I've not seen this phenomenon ever. It may be because I am not using all of the fancy lcd4linux stuff, like weather and other cloud services.

[littlesat]

Just a speculation...

 

Could be the OSD for that display that need to be communicated to the (extra) display, which might withhold some 'progress'... as it is e.g. not running in a separate thread within the LCD4Linux plugin?