(2015-02-07, 20:50)fritsch Wrote: [ -> ]Hehe - yes. Lanczos3 Optimized puts a whole lot of pressure on the GPU. But this should only be used for SD and max 720p content anyways. See the "Use HQ Scalers when scaling above:" 20% setting.
Lanczos3 upscaling 1080 to 1080 is just insane and unneeded.
Yep, I was using those settings so Lanczos3 was only used for SD content - still a bit too loud unfortunately. The difference to my eyes between bilinear and Lanczos3 wasn't enough for me to put up with the fan noise!
(2015-02-07, 20:51)Matt Devo Wrote: [ -> ]Lanczos3 requires significantly more CPU, which drives up the temp, which kicks up the fan speed. It's certainly a good test to see how loud your box can get 
Definitely, just a bit too loud was the result!
Any of you experience white static screen when rebooting? I use Yatse on my phone as my remote, to reboot... The box appears to start the reboot cycle, then it shows the static screen, then black screen, then static again... and this will continue until i shut the box off, or use Yatse to restart it again... sometimes it'll have a long pause on the black screen.
I'd recommend updating to the latest firmware or legacy BIOS, whichever is applicable for you, as the current version fixes some video BIOS configuration issues. Otherwise, I'm curious as to why you need to reboot the box - it's not Windows after all ;-)
I've noticed something rather strange. After an upgrade to Kodi, I've encountered a situation where my screen had a blueish hue to it. Similar to what one would see if one of pins to the monitor was broken. Nothing I did would fix it until I rebooted the Chromebox.
This happened twice to me - once on the home screen, and second time while playing a movie (exiting the movie returns everything to normal, but every attempt to re-start resulted in the same hue problem).
Has anyone seen anything like that?
Maybe I'm crazy... But sometimes when addons are updated I get script errors, I've had some addons get to 90% and stop... Sometimes rebooting clears up these issues...
(2015-02-08, 02:07)igjunk Wrote: [ -> ]I've noticed something rather strange. After an upgrade to Kodi, I've encountered a situation where my screen had a blueish hue to it. Similar to what one would see if one of pins to the monitor was broken. Nothing I did would fix it until I rebooted the Chromebox.
This happened twice to me - once on the home screen, and second time while playing a movie (exiting the movie returns everything to normal, but every attempt to re-start resulted in the same hue problem).
Has anyone seen anything like that?
I can confirm this.
It looks like the blacks are washed out.. More like grey.
It looks the same when you play around in the RGB levels (limited colorrange) 16-235
A startup and its solved.
I need some help please. I have a chromebox with openelec. Everything was working fine but now i cant connect to wifi. When i select the network and then connect "working" shows up at the bottom of the screen for a split second and then nothing. I get no screen to input the wifi password. I turned off wireless connections and reenabled them but nothing. Whats wrong? Everything was working OK. Please help.Thanks
I am on wired gigabit but I recently saw a strange issue when booting up with the wpa supplicant, most probably due to the latest OpenElec release. maybe you dig through their forums.
(2015-02-07, 20:44)ant_thomas Wrote: [ -> ]To keep my HP Chromebox quiet I had to use Bilinear scaling instead of Lanczos 3. Other than that I have no complaints.
I assume the scaling is implemented in GPU shaders and not on the CPU.
I can't say if this would help the celeron chromebox but on my i3 brix using dual channel ram dropped GPU usage by 20%. This allowed GPU to stay at a lower boost Mhz range (~600 vs 900) which reduced fan noise significantly. Tested on Windows using MadVR but I would expect similar results in Kodi.
When I went to reboot my chromebox with openelec, nothing is displaying any more.
Any advice on how to debug this?
It was working fine, then I noticed that no audio was playing. I rebooted the box, briefly saw the initial bootup process (using quick boot) and then no signal to tv.
Hooked it up to the computer monitor, still nothing.
The chromebox is configured for openelec only.
Please help.
Thanks
Seems like the machine booted up fine, but not using HDMI as the display out.
The theory I have is that on last reboot, the machine auto updated to 5.01
Any idea why it would change the default video out option?
I recently set up an Asus Chromebox using the install script for dual-boot Ubuntu+Kodi. Everything was working fine until the video froze while playing a file off my networked server. The audio kept playing, however. I could not stop the video, or alt+tab, "\", alt+F4, etc. No response from the keyboard or IR remote. I finally had to push the power button to reboot. The video plays fine on other (Windows, ATV2) boxes. I tried turning off software auto-updates to see if it happens again. Anyone else experience this?
EDIT: It just happened again after playing for 15 minutes. Help!
(2015-02-09, 05:02)pcdude Wrote: [ -> ]I recently set up an Asus Chromebox using the install script for dual-boot Ubuntu+Kodi. Everything was working fine until the video froze while playing a file off my networked server. The audio kept playing, however. I could not stop the video, or alt+tab, "\", alt+F4, etc. No response from the keyboard or IR remote. I finally had to push the power button to reboot. The video plays fine on other (Windows, ATV2) boxes. I tried turning off software auto-updates to see if it happens again. Anyone else experience this?
EDIT: It just happened again after playing for 15 minutes. Help!
I had the exact same issue with dual boot Chrome+ Ubuntu (14.10), but when playing a file locally (from an external USB drive), I was actually going to create a post for the same thing! I believe this can be resolved by turning off 'Prefer VAAPI render method' within Settings > Videos > Acceleration. Make sure Expert settings are enabled. I think this may have solved the problem for me, but I haven't had a chance to fully test yet.
Matt Devo, are you able to confirm whether there are any specific acceleration/playback settings that need to be applied for Ubuntu? I've replicated the recommended settings from the Wiki, but as with pcdude I also experienced occasional crashes.
That "was" the proper fix and it's supposed to correct a bug that has been removed from OpenElec 5.0.
Of course,... I guess if you are running Kodi off a full Ubuntu install that's a different config. either way turning off prefer Vaapi Render is known to fix that problem.
And,... if you do the "Broadcast RGB" "Full" tweak to get the right video output then the Prefer Vaapi Rendered is supposed to be off also....