Posted 16 December 2017 - 09:31
vu and tuner driver was more a nightmare 
dvb-api 5 not correct implemented
inversion on /off broken in the first gen mipsel boxes
dvb-t2 scan need a close binary to scan nit
fe_info report wrong only current delivery systems not all
slow io when read tuner infos
switch delivery system with api5 call broken all models (dvb-t , dvb-c)
and we have report the issue for 2 years now and vu do nothing
Posted 16 December 2017 - 12:02
+1 !!Regarding Kodi, I think we should BAN that word... So many resources wasted, giving back to our satellite hobby 0, nothing, null!
Posted 16 December 2017 - 12:24
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 16 December 2017 - 15:38
Posted 16 December 2017 - 16:11
Better ever now and then it does not work anymore... And Kodi's youtube is nice... and updated...
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 16 December 2017 - 16:16
Posted 16 December 2017 - 16:35
Also works with FEC set to 9/10 on sf4008.
Yeah! It works on my Zgemma receiver too, no need for FEC:AUTO or special DVB-S2X FEC values, thx!
Posted 16 December 2017 - 17:08
This is often the case, but in fact not correct, if the user doesn't ask for "auto" FEC, it shouldn't be used.
* 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 16 December 2017 - 17:32
This is often the case, but in fact not correct, if the user doesn't ask for "auto" FEC, it shouldn't be used.
Yes but it is out of our hands if the hardware or drivers does it automatically.
Posted 16 December 2017 - 19:34
Yes, it's clearly a driver or even hardware omission, not our fault.
* 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 16 December 2017 - 22:12
Edited by Matrix10, 16 December 2017 - 22:13.
Posted 16 December 2017 - 22:15
Don't think anyone is debating that?
Bugs are everyone, and VU+ is not an exception. Bugs are there to be fixed. Nothing new here too...
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 December 2017 - 08:22
But we also know that VU refuses to fix several (very old) bugs, and they often first try to 'fix' things by changing their E2, instead of first trying to fix things correctly in the drivers.
And on top of that they never ever reply to any private (bug)report.
And hardware will never be better then the applied firmware.......
Posted 17 December 2017 - 09:18
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Posted 17 December 2017 - 10:12
nice criticism at VU + addressbut this is the best quality hardwareAnd if someone tells me that is not so then he must have more yearsexperience in electronics of me 35+ years90% of users are more than happy
Where did you read that my remark was aimed at 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 17 December 2017 - 10:25
Do you have a complete list... probably we can try to forward it to vu now. Over the last months they are really solving things we mention.
What Babsy said in post #101...
Here is example code that catches broken drivers. Vu+ hybrid DVB-T2/C gets trapped here because it only lists its current mode, not all modes it is capable of. This means DVB API output is unreliable and we are forced to get this tuner info from /proc/bus/nim_sockets instead. That should not be necessary. If we just used tuner info from DVB API Vu boxes would not work.
https://github.com/H...er.py#L689-L690
Edited by Huevos, 17 December 2017 - 10:26.
Posted 17 December 2017 - 12:20
Also the dreambox with original image (Dreambox OS) shows the S2X NOT CORRECTLY. Box can scan this channel, but there is more work needed with enigma2.
https://www.online.e...14-2b726bf4f0f3
DM920UHD DVB-S2X TRIPLE tuner + Triple M.S tuner DVB-S2X, DVB-T2/T, QboxHD, QboxHD Mini, Icecrypt T2300HD,
Qviart Lunix3 4K, Raspberry Pi 4 Model B 4GB & 8GB
Vertex 4K60 4:4:4 600MHz
Posted 17 December 2017 - 12:37
Edited by Matrix10, 17 December 2017 - 12:40.
Posted 17 December 2017 - 13:38
I think we can all agree to that.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 17 December 2017 - 14:42
Please be kind enough to mention duo2 symbol rate issue alsoDo you have a complete list... probably we can try to forward it to vu now. Over the last months they are really solving things we mention.
Edited by amila4341, 17 December 2017 - 14:43.
0 members, 27 guests, 0 anonymous users
