(2016-03-25, 03:53)noggin Wrote: There was a GUI tearing fix that stopped the tearing, but also (at least to me) appeared to reduce the fluidity of the GUI a little. Wonder if the older version you are comparing with didn't have that?
(2016-03-25, 07:30)wrxtasy Wrote: The newer OE updates with the Mali Turbo (GPU) have regained most of the lost GUI speed that you first saw when the GUI tearing fix went in a while ago.
I wouldn't say it's a tearing in a way I understand it. Rather, it's less fluid again: the Confluence "menu stripe" (or whatever it is the right way to call it) moves a little bit jerky. Not a problem at all -- just mentioned it FYI as a sign of a possible regression. Or maybe it's just my impression. I may later put 6.0.3 on another card and compare to be sure. Will let you know about the results.
Meanwhile I spend the most of yesterday testing this little beast with different TV sets and wanna share my impressions from 6.95.9.2 controlled with TV remote via CEC.
Pros: fast, stable and quite predictable. Almost ready for the show, but....
Cons (bugs and other drawbacks):
1. OpenELEC configuration add-on disappeared from the Confluence menu (I mean the secondary menu under the "System"). Still may be found and invoked via System -> Add-ons -> ...
2. OpenELEC configuration: some time ago the second keymap disappeared from the settings. At least I can't find it anymore to make my keyboard bilingual again. This is not needed for a normal operation, but updating a media library becomes a real pain in the *** if I need to manually type in the movie title in Russian. I can still make the screen keyboard bilingual, but it takes
lots of arrow keystrokes to proceed.
3. No 3D at all. It plays 3D as 2D all the time...
4. If I recall it correctly Unofficial Addons repo was pulled in automatically. It's not anymore. Once again, it's not a big issue, JFYI.
About CEC and integration with a TV set. After I programmed coloured TV remote keys for missed functions (context menu, info, quick audio and subtitle switching) I may live without extra remote just fine. But the different TV sets appear to behave quite differently as it comes to CEC. (Quite obvious, isn't it?)
Panasonic plasma: good enough for an everyday use. The only annoying thing is that it loves to double keystrokes over CEC often enough to mess the control now and then. But this is the only problem I've experienced so far. Is there a way to fix unwanted repeats coming through CEC? It bypasses lirc, doesn't it? (So far I've the gap in understanding how cec works. Some reading is obviously awaiting me...)
New Samsung 9-series (curved): The control is a little bit slow but stable. After keeping the TV off (odroid stays on) a lot of annoying console output is on the screen, but in a short while the normal operation is back. The garbage goes away and the remote becomes operational in 8-10 seconds or so. But there is
a lot of console complaining on the screen seen right after the TV is on. It looks like the player tries to "fix" something all the time the TV is off.
Older Samsung 6-series (flat): Total disaster. It only works until both TV and player stay on, what makes it unusable in practice. If I switch the TV off, it goes back on immediately. If I switch the TV input to another sources before switching it off -- it stays off but never picks up CEC again the next time I power on the TV and the control over the player is lost forever.
wrxtasy Wrote:Known issue the Console Logs output displaying on screen during reboot and TV on. Last on the list to fix.
Not happy to read this. I understand there's a lot of work you guys are doing, especially when very promising but quite problematic C2 is out. I quit programming about 20 years ago so I can't fix it myself if some coding is needed. Sorry for that...
However, from my point of view it may be a show-stopper for many use cases. Idiomatically, my auntie would call 911 having seen handful of console output on top of the media player graphic screen after switching on the TV
Many casual users will not notice a little shuttering we discussed last week or a lack of interface fluidity, for example. Everyone will for sure notice error messages on the screen. It may not be so important technically but still may ruine the overall non-tech user impression from using the device. Eventually, it's a media player, isn't it? So for the end user it ought to behave this way.
May be there is a workaround for this issue? Is there a way to put the console output to /dev/null or wherever, for example?
Thanx!