(2015-01-01, 21:33)Veronica Wrote: [ -> ]in kodi OE5.0 you need to uncheck the whole "VAAPI hardware acceleration" option, not only the "prefer VAAPI" one. But OE 5.0 was supposed to have the freeze bug fix (confused).
100% incorrect. VAAPI acceleration and prefer VAAPI renderer should both be checked/enabled. The default/OOTB settings are correct for OE 5.0.0 (stable)
(2015-01-01, 19:05)asleulv Wrote: [ -> ]Thanks. Was able to install OE5.0 and added the recommended adjustments to the settings. However I'm still struggling with videos freezing while subtitles and audio continuing. Was hoping this issue would disappear after the update.
Is this the dreaded Intel bug? If so the workaround in the wiki isn't working for me.
1) there is no dreaded intel bug anymore, it is fixed
2) complaining of playback issues without logs is useless
3) this thread is for setup/install related issues involving my EZ setup script. Playback issues belong in the Linux support forum (or OpenELEC forums, if it's OS-related).
Hi everyone, I just purchased a chromebox and opted to do the standalone install. I downloaded ubuntu and was just about to install it. I was at the point where I had to press esc within 5 seconds or it will boot to the hard disk. Well, I was using my wireless keyboard and I guess it didn't pick up on me pressing ESC. Now I'm stuck where it is immediately booting to the hard disk and I can't do anything about it. I've tried to shut it down and restart over and over thinking that I might be able to press ESC faster than it boots up, but apparently not.
What are my options at this point? I'd really love to get this going!
*I am using a USB keyboard now, not the wireless one
(2015-01-01, 23:15)Steve325 Wrote: [ -> ]Hi everyone, I just purchased a chromebox and opted to do the standalone install. I downloaded ubuntu and was just about to install it. I was at the point where I had to press esc within 5 seconds or it will boot to the hard disk. Well, I was using my wireless keyboard and I guess it didn't pick up on me pressing ESC. Now I'm stuck where it is immediately booting to the hard disk and I can't do anything about it. I've tried to shut it down and restart over and over thinking that I might be able to press ESC faster than it boots up, but apparently not.
What are my options at this point? I'd really love to get this going!
*I am using a USB keyboard now, not the wireless one
Im confused...if you are attempting to do the standalone install why would you "I downloaded Ubuntu and was just about to install it".
The very first post lists the steps and instructions for standalone.
Are you sure you are doing Standalone and not dual boot?
(2014-12-31, 16:32)MauiSteve Wrote: [ -> ]Matt Devo- Thank you.
I installed a standalone OpenELEC a week ago. Such a pleasure to pass the old sluggish android box on to another family member.
Your script went fine but I ran into the overscan problem during install and I could not see about the first 4 or 5 characters at the left margin during install.
I've got an old 50" Panasonic Plasma Viera and I messed around with settings to try and eliminate the overscan but never found success. The biggest trouble came during selection process for USB back-up or write of OpenELEC. I could not see the number the script was expecting. I ended up moving the USB to a different location and hit a 1 and that got things going. I did not have a different spare monitor to use.
I guess there is not a good way to have your script tab about 5 characters to the right... I may build a few more Chomeboxes for less technically inclined buddies, so I'm not looking forward to the overscan problem again.
Cheers.
I had the same problem with the overscan...made the install a bit dicey but figured it out in the end.
(2015-01-01, 23:30)dtviewer Wrote: [ -> ]Im confused...if you are attempting to do the standalone install why would you "I downloaded Ubuntu and was just about to install it".
The very first post lists the steps and instructions for standalone.
Are you sure you are doing Standalone and not dual boot?
he's installing Ubuntu only, which is perfectly fine, no different than installing OpenELEC only (other than the script won't create the install media for you).
I picked up an Acer CXI Chromebox. Will the dual boot script work with this? If so does anyone know how to turn off the firmware write protect? Thanks.
(2015-01-01, 23:47)kenz Wrote: [ -> ]I picked up an Acer CXI Chromebox. Will the dual boot script work with this? If so does anyone know how to turn off the firmware write protect? Thanks.
cmon dude, did you even bother reading the first post?
Running Openelec 5.0 on the Asus Chromebox for a few days now. Working flawlessly together with my Lightpack.
Big thumbs up for Matt for making this so easy!
So no one else has noticed that the Chromebox doesn't output the proper RGB video levels for video playback with OpenELEC? I had never really checked it before since I only use my Chromebox for audio. Today i gave it a shot with OpenELEC 5.0 it outputs 16-235 and enabling the 16-235 option in the menus just further compresses the video levels to something even more narrow.
(2015-01-02, 01:24)Stereodude Wrote: [ -> ]So no one else has noticed that the Chromebox doesn't output the proper RGB video levels for video playback with OpenELEC? I had never really checked it before since I only use my Chromebox for audio. Today i gave it a shot with OpenELEC 5.0 it outputs 16-235 and enabling the 16-235 option in the menus just further compresses the video levels to something even more narrow.
I'm going to wager you haven't read the wiki / applied the full-range output setting as noted?
(2015-01-02, 01:32)leo5111 Wrote: [ -> ]i bought this 1 because with keyboard and mouse was pretty good deal http://www.amazon.com/gp/product/B00LB11...UTF8&psc=1 now logicly the keyboard&mouse they sell it with "SHOULD" work in bios, but we will see 
that's not a logical conclusion at all, since in a stock configuration there is no need for it to work in developer mode or on the legacy boot menu. I suspect they never even tested it in those scenarios
(2015-01-02, 01:24)Stereodude Wrote: [ -> ]So no one else has noticed that the Chromebox doesn't output the proper RGB video levels for video playback with OpenELEC? I had never really checked it before since I only use my Chromebox for audio. Today i gave it a shot with OpenELEC 5.0 it outputs 16-235
That's not specific to the Chromebox, it's the expected and default behaviour for Intel GPUs. They default to the standard consumer 16-235 level (which all HDMI gear accepts as default levelspace - and is often the only levelspace output from boxes like DVD players and Satellite/Cable boxes), at least they do when you are running a "TV" resolution like 720p, 1080i or 1080p. (16-235 is the 'normal' level space for digital video - it's what Blu-ray, DVD and broadcast digital TV uses)
As Matt has said, you need to enable full range driver output as per the wiki if you want 0-255 output levels.
Quote:and enabling the 16-235 option in the menus just further compresses the video levels to something even more narrow.
The 16-235 option is to output 16-235 levels if you have a GPU that thinks it is outputting 0-255 levels , but need to output 16-235 to feed regular gear (so Kodi does the output levelspace conversion internally rather than leaving it to the GPU)
Matt,
I have followed your instructions and successfully installed the dual boot option. Now I just want to have the standalone option. What process do I need to follow to start over and install the standalone option? Please advise.
(2015-01-02, 02:06)pglover19 Wrote: [ -> ]Matt,
I have followed your instructions and successfully installed the dual boot option. Now I just want to have the standalone option. What process do I need to follow to start over and install the standalone option? Please advise.
just follow the standalone setup instructions. If you're running OE, you can back up your config using the OE backup function (Settings/OpenELEC/General), copy the backup file to another PC, and restore after completing the standalone setup,