2015-07-13, 01:26
Hi
Just a little bug with the latest build. Pop up notifications now have no text.
Just a little bug with the latest build. Pop up notifications now have no text.
(2015-07-13, 01:26)rob77 Wrote: Hi
Just a little bug with the latest build. Pop up notifications now have no text.
(2015-07-13, 02:01)charlieroot Wrote: Same here, started with #0711.
(2015-07-13, 08:29)Milhouse Wrote: @popcornmix: this is the commit that causes the high CPU load in Music > Files in build #0304:
(2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out?
(2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out?No problem at all. I do the same. Sometimes I update every day, sometimes not for a week or two. To update or not depends on if it has any interesting commits (fixes, features) you like or need to have/test.
(2015-07-13, 17:41)popcornmix Wrote:I'm using these Mulhouse builds on my rpi2 attached to my Sony LCD en wired ethernet to my router. No dvb devices and no pvr stuf whatsoever(2015-07-13, 17:34)Bartmaniac Wrote: Just a quick question. Everyday I download the newest build and install it. Maybe that is not necessary? Is it OK to do it every day in and out?
I update pretty much every day. I use Leopold's add-on to update easily.
So there is no problem with doing this.
Is it necessary? Depends why you are using these builds. If you want to help with testing, and see new features as early as possible, then sure, update every day.
If you don't then sticking with a stable build may be better.
(2015-07-13, 02:41)Milhouse Wrote:I was just getting to posting about the bug. Good to see it'll be fixed soon.(2015-07-13, 01:26)rob77 Wrote: Hi
Just a little bug with the latest build. Pop up notifications now have no text.
(2015-07-13, 02:01)charlieroot Wrote: Same here, started with #0711.
Thanks both - are you referring to the Kai Toast notifications (notifications that appear in the bottom right corner of the screen, in Confluence)?
Would it be possible to upload a screen shot, or describe a really easy way to reproduce? I rarely see notifications...
Edit1: OK I can see the problem, running "texturecache.py notify ThisIsTheTitle ThisIsTheMessage 5000 warning" should display a Kai Toast (notification) with a title and message, but there is no text.
Edit2: Seems to be due to PR:7323 - there's a mention of it there already so hopefully fixed soon.
Edit3: Should be fixed by PR:7491 - I'll include this in the next build if it's not already merged. Thanks for reporting.
(2015-07-13, 18:29)invisable Wrote: Hi Millhouse, can I ask if your still including your latest librtmp in Openelec 16 the only reason I ask is because I noticed the test build release you made on May 16 (#0516) the librtmp is slightly larger then the ones on the recent builds ?
Many Thanks.
(2015-07-13, 14:13)popcornmix Wrote: Thanks Milhouse - good detective work as usual.
I suspect reverting the offending commit, could help audio playback cpu, but is likely to harm video playback cpu.
I've pinged @FernetMenta who may be able to help find a fix for both.
# uname -a
Linux OpenELEC 4.1.2 #1 Tue Jul 14 01:59:49 BST 2015 armv6l GNU/Linux
# vcgencmd version
Jul 14 2015 01:21:05
Copyright (c) 2012 Broadcom
version 41afcc6c933c1bc44ebdedc5aaf965b685b604e7 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20150714015859-#0713-ga1fff18 [Build #0713]
# vcdbg log msg 2>&1 | grep DTOK
001573.535: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
popcornmix Wrote:This is an early attempt to support high quality deinterlace at 1080i resolution (we previously used a simpler "bob" deinterlacer for HD).
By default the "Auto select" deinterlace method will still choose "bob" for HD video, but you can now change that to "Advanced" and you should get higher quality deinterlace even at HD resolution.
It does need some overclock. Something like:
is recommended for now (which will set your warranty bit). We'll get the overclock requirements down in a future build.Code:core_freq=400
v3d_freq=400
over_voltage=2
force_turbo=1
This update is thanks to Raspberry Pi founder Eben Upton, who rewrote the VPU deinterlace code to work on the QPUs (3D hardware).