Posted 26 February 2016 - 15:46
And by the way I am not the only person to notice the driver issue. 3 independent setups have tested OpenViX, OpenPLi, OpenATV and Blackhole. All found the same issues with the current drivers. Even if you just set up tuner A and no other tuners a quick flick through transponders on satfinder shows the issue.
Don't shoot te messenger! I can't test it myself without access to a unicable system. The reply from VU+ sounded quite logical to me.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 26 February 2016 - 16:22
Posted 26 February 2016 - 17:11
Before I start "accusing" VU+ again, I'd please like to see experiences of other unicable users.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 26 February 2016 - 19:26
When you communicate with VU can you also add the resume recording from standby without sound issue....
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 28 February 2016 - 11:33
1 question, I would like to know what can be set as the lowest SR (symbol rate) for reception at Vu solo 4k with new version software VTI 9.0.1. Is it now finaly possible to achieve reception in the full range of SR 1-45 Msym/s ?
2 question What is the maximum number of satellites that I can insert into my database (satellite setting) ?
Thank you for the practice of evidence-based information ( DX sat interest )
Posted 28 February 2016 - 12:19
Posted 29 February 2016 - 10:22
Before I start "accusing" VU+ again, I'd please like to see experiences of other unicable users.
Another obvious test that demonstrates this driver problem...
Tuner A, 28.2E, Unicable, SCR1. No other tuners configured.
Current channel BBC1 HD (FTA channel). Reboot receiver. Between when the infobar appears and when the channel opens there is a pause of several seconds, and the "tuned failed" message flashes up on the screen. Eventually the channel opens.
FTP the old drivers to the Solo4K and reboot. The channel is now displayed instantly.
@Erik, the driver issue has already been confirmed by another poster further back through the thread. If you haven't got the hardware to test, I would ask you to please listen to this user that does. Tested as above with the latest PLi image. Right now I am not even talking about linked tuners. These drivers don't even work right when only the root tuner is configured. Just zapping from channel to channel on the root tuner shows there is an issue (tuned failed messages and pregnated pause opening FTA channels).
Edited by Huevos, 29 February 2016 - 10:23.
Posted 29 February 2016 - 16:00
Ok, noted 
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 4 March 2016 - 11:27
Huevos, I have submitted your bug report.
And I have a reply.
There is a problem in tuner setup.
Problem would be solved if setup is as below.
Setup:
Tuner A, Advanced, Unicable, SCR 1. Tuner A is the root tuner.
Tuner C, Advanced, Unicable, linked to tuner A, SCR 2.
Tuner D, Advanced, Unicable, linked to tuner C, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner D, SCR 4.compared to
Tuner A, Advanced, Unicable, SCR 1. Tuner A is the root tuner.
Tuner C, Advanced, Unicable, linked to tuner A, SCR 2.
Tuner D, Advanced, Unicable, linked to tuner A, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner A, SCR 4.I think we should consider automatically assigning the links for unicable as well, but it might be complex.
Erik it is not true.
I have tested all linked to A,
And I have tested A linked to C linked to D linked to E, etc
Both combinations work fine with the old drivers.
Both combinations do NOT work with the newer drivers.
Is http://code.vuplus.c...26da558fd06da39 related to this bug?
Or http://code.vuplus.c...80d5f4b335ea383 ?
Edited by Rob van der Does, 4 March 2016 - 11:28.
Posted 4 March 2016 - 17:21
It looks like the first commit is a real fix for FBC tuners (but won't it break other tuners/types), the second is a Q&D workaround. It looks like all frontends are continuously left in "full on" mode after this commit is applied, blech.
This looks like:
- old FBC tuner driver did not implement frontend off/standby and left it on always
- newer driver implements it but reveals issues
- now the enigma code simply leaves all frontends always on
Then reinstating the old driver would actually have my preference, because it breaks FBC the tuners at worst, leaving all other tuner types alone.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 4 March 2016 - 18:56
Then reinstating the old driver would actually have my preference, because it breaks FBC the tuners at worst, leaving all other tuner types alone.
IMHO that will not be an option, as this 'issue' will probably be present in all future drivers as well. So that would prevent you from updating drivers for lifetime.
Posted 4 March 2016 - 19:45
as this 'issue' will probably be present in all future drivers as well.
This is in fact why everyone should refuse to adapt these kind of dirty work-a-rounds.... Only when this is refused by the teams VU has something to do to fix it..... But actually other teams do just please them by accepting durty work-a-rounds.... So we get to the never ending story of making from enigma2 a big spagetti code... 
I still have the hope VU does fix it...
I think you should agree that these facts
- old FBC tuner driver did not implement frontend off/standby and left it on always
- newer driver implements it but reveals issues
- now the enigma code simply leaves all frontends always on
Are something VU should still improve in their drivers.... The tuners must be able to shut down!!!! The fix to leave them on is in fact not done... So I still have the hope VU will fix it... The tuners should be able to go OFF without work-a-round in E2 to keep them ON... And that is why we consider to keep the older drivers...
Edited by littlesat, 4 March 2016 - 20:05.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 5 March 2016 - 09:54
They should at least have implemented enable/disable frontend standby as module parameter, just like xtrend did. Then people with problems with just turn it off. I just checked and there is no such option.
Edited by Erik Slagter, 5 March 2016 - 09:55.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 5 March 2016 - 10:31
The way you explained it it looks like a driver-issue to me. But knowing how hard it is to convince the VU-devs, I really hope you'll manage this time.....
Posted 6 March 2016 - 11:26
What about a random pixels aka "pixels storm" on an internal LCD after shutdown or reboot?
Posted 6 March 2016 - 12:24
Yeah, nice one But not really a prio #1 issue
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 6 March 2016 - 12:27
The way you explained it it looks like a driver-issue to me. But knowing how hard it is to convince the VU-devs, I really hope you'll manage this time.....
I think most of it (power saving of the frontends) should be implemented in the driver, maybe a little exception code for the FBC case in enigma, like with the other added features of FBC. The whole concept of eight tuners sharing two physical input is something new for enigma, and it needs some code to handle that. But I think a few lines should be sufficient and the rest should be handled by the drivers themselves. I don't feel like applying the patches from VU+.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 6 March 2016 - 16:27
But you feel like waiting for a proper driver-fix by VU 
Posted 7 March 2016 - 10:16
@Erik
Low priority is not a problem. Just I check: we have it all or just me?
Posted 7 March 2016 - 11:37
No, it also appairs on my solo4k display but I don't care about that, it is only visible during a reboot
Aan de rand van de afgrond is een stap voorwaarts niet altijd vooruitgang....
On the edge of the abyss, a step forward is not always progress....
Hardware: 2x Daily used Vu+ Ultimo 4K - Vu+ Duo 4K SE and a lot more.... - VisioSat BiBigsat - Jultec Unicable Multiswitch 4 positions: 19.2/23.5/28.2 East - Diseqc motorized flatdish antenna
Software : HomeBuild OpenPLi Develop and Scarthgap builds, local cards driven by OsCam
Press the 
button on the buttom right of this message
Have you tried our wiki yet? Many answers can be found in our OpenPLi wiki
0 members, 37 guests, 0 anonymous users
