Kodi Community Forum

You can start to implement VAAPI via EGL, then you get the correct colors without any RGB stretching. Concentrage your lack of patience into learning some C++ to contribute.

I'm putting my chromebox in production again but am a bit lost where to start from.

- I've followed the FP for single install with OE (I have the seabios)
- I've then used a custom OE build to test new intel drivers (from you fritsch)

Which road should I follow to start again as a OE box ?

- Booting with the reset plug pushed doesn't do anything
- Ctrl ALT F2 gives me an error, says I should boot with ctrl, but not better.

Thanks

(2015-02-06, 17:55)c0mm0n Wrote: [ -> ]I'm putting my chromebox in production again but am a bit lost where to start from.

- I've followed the FP for single install with OE (I have the seabios)
- I've then used a custom OE build to test new intel drivers (from you fritsch)

Which road should I follow to start again as a OE box ?

- Booting with the reset plug pushed doesn't do anything
- Ctrl ALT F2 gives me an error, says I should boot with ctrl, but not better.

Thanks

If you already have followed the standalone configuration instructions, all you should need to do is insert a USB drive with your custom OE image loaded onto it and boot. You should get a menu asking you whether to boot from USB or SATA.

(2015-02-06, 15:07)bhampton Wrote: [ -> ]Soli,

Does this result in Vaapi hardware acceleration or something else like DVXA or ...??... Could you check if you don't mind? Just look under the acceleration tab in video playback expert settings.

I have Kodi running on 3 very different computers... A PC, a Mac, and a Chromebox... but the OpenElec using Vaapi hardware acceleration is giving me problems I would rather not have.

edit - Never heard of RGB FIX option.... I do rely on the the Broadcast RGB Full flag.

-Brian

Isn't DXVA some Windows thingie? I use Vaapi and everything plays fine. Can you point me to a troublesome vc1 file?
The RGB FIX is equivalent to the Broadcast RGB Full flag when using OE. But since Kodibuntu is a full blown distro, the xrandr stuff needs to run as an display manager init script. That way it works both when booting into Kodi or the Desktop.

(2015-02-06, 18:08)naloj Wrote: [ -> ]

(2015-02-06, 17:55)c0mm0n Wrote: [ -> ]I'm putting my chromebox in production again but am a bit lost where to start from.

- I've followed the FP for single install with OE (I have the seabios)
- I've then used a custom OE build to test new intel drivers (from you fritsch)

Which road should I follow to start again as a OE box ?

- Booting with the reset plug pushed doesn't do anything
- Ctrl ALT F2 gives me an error, says I should boot with ctrl, but not better.

Thanks

If you already have followed the standalone configuration instructions, all you should need to do is insert a USB drive with your custom OE image loaded onto it and boot. You should get a menu asking you whether to boot from USB or SATA.

Thanks found that, issue was my projector not showing boot screen, now fixed by using a standard screen.

(2015-02-06, 17:55)c0mm0n Wrote: [ -> ]I'm putting my chromebox in production again but am a bit lost where to start from.

- I've followed the FP for single install with OE (I have the seabios)
- I've then used a custom OE build to test new intel drivers (from you fritsch)

Which road should I follow to start again as a OE box ?

- Booting with the reset plug pushed doesn't do anything
- Ctrl ALT F2 gives me an error, says I should boot with ctrl, but not better.

Thanks

Where did you download the custom Openelec build? interested in trying it out

Matt did it, but everything seems now in the current release. (VAAPI-MCDI)

(2015-02-06, 18:45)c0mm0n Wrote: [ -> ]Matt did it, but everything seems now in the current release. (VAAPI-MCDI)

Thank you appreciate the input.

(2015-02-06, 18:14)Soli Wrote: [ -> ]

(2015-02-06, 15:07)bhampton Wrote: [ -> ]Soli,

Does this result in Vaapi hardware acceleration or something else like DVXA or ...??... Could you check if you don't mind? Just look under the acceleration tab in video playback expert settings.

I have Kodi running on 3 very different computers... A PC, a Mac, and a Chromebox... but the OpenElec using Vaapi hardware acceleration is giving me problems I would rather not have.

edit - Never heard of RGB FIX option.... I do rely on the the Broadcast RGB Full flag.

-Brian

Isn't DXVA some Windows thingie? I use Vaapi and everything plays fine. Can you point me to a troublesome vc1 file?
The RGB FIX is equivalent to the Broadcast RGB Full flag when using OE. But since Kodibuntu is a full blown distro, the xrandr stuff needs to run as an display manager init script. That way it works both when booting into Kodi or the Desktop.

I tried the VC1 file you linked to earlier. I get artifacts as well. But come on man, why don't you just use software decoding on vc1. Seemed to work just fine. Anyways, reading the thread backwards it seems you've already got all the answers you seek.

(2015-02-06, 15:07)bhampton Wrote: [ -> ]Soli,

Does this result in Vaapi hardware acceleration or something else like DVXA or ...??... Could you check if you don't mind? Just look under the acceleration tab in video playback expert settings.

I have Kodi running on 3 very different computers... A PC, a Mac, and a Chromebox... but the OpenElec using Vaapi hardware acceleration is giving me problems I would rather not have.

edit - Never heard of RGB FIX option.... I do rely on the the Broadcast RGB Full flag.

-Brian

for hardware video decoding on Intel platforms, Linux = VAAPI, Windows = DXVA (heck if I know what OXS uses. OpenGL?). All he did was create a startup script to launch the display manager with the broadcast RGB flag, rather than setting it when Kodi launches. With OE, you have to do that latter via the autostart script.

(2015-02-06, 17:55)c0mm0n Wrote: [ -> ]I'm putting my chromebox in production again but am a bit lost where to start from.

- I've followed the FP for single install with OE (I have the seabios)
- I've then used a custom OE build to test new intel drivers (from you fritsch)

Which road should I follow to start again as a OE box ?

- Booting with the reset plug pushed doesn't do anything
- Ctrl ALT F2 gives me an error, says I should boot with ctrl, but not better.

Thanks

just reinstall from USB using the latest official OE release (currently 5.0.1). The recovery button and CTRL-ALT-F2 only exist when running the stock firmware with ChromeOS; with a standalone setup they are not valid.

(2015-02-06, 18:16)c0mm0n Wrote: [ -> ]Thanks found that, issue was my projector not showing boot screen, now fixed by using a standard screen.

May very well be fixed with an updated firmware. You can update the standalone firmware using the 'standalone fimrware updater' script in the OP.

(2015-02-06, 18:25)jskala Wrote: [ -> ]Where did you download the custom Openelec build? interested in trying it out

the ChromeBox has used the standard OE builds for a while now; custom builds are only used to test fixes for specific issues, which are then integrated into the next release. If there's ever a reason to run a custom build, it will be linked in the first post and/or wiki.

(2015-02-06, 19:02)Soli Wrote: [ -> ]I tried the VC1 file you linked to earlier. I get artifacts as well. But come on man, why don't you just use software decoding on vc1. Seemed to work just fine. Anyways, reading the thread backwards it seems you've already got all the answers you seek.

For sure... When I first found the problem I unchecked hardware acceleration for VC1 and was happy as a clown for a while. That does totally solve the problem. That's the default setting also.

But, Some VC1 titles I have can't seem to keep up with software decoding and they get choppy. If I could optimize that then I'm all set and happy as a clown again.

Two titles I noticed so far that seem to need VC1 hardware are The Dark Knight and Fast Times at Ridgemont High... maybe those are just very high bit rate. Maybe re-endoding some or just re-encoding all my VC1 titles would work... I don't really care how I find a way around the problem so long as I do.

If you could provide a clip , preferably a couple of minutes long, that the software decoder cant keep up with, i'd be willing to try it out on my setup.

Dell has the Chromebox for $150.

http://www.dell.com/us/p/chromebox-3010/...mebox-3010

The dell looks completely identical to the Asus. Is it?

(I realize the wiki says it has an AC wifi module, which is different. I was talking about the actual build, not the specs.)

Yeah but Dell is probably the best deal since you get AC wireless, but the N wireless is plenty fast already. (I think i get about 20 MB/s with my HP). You also get 2 RAM sockets so you can upgrade to 16GB RAM. But lets get real: no sane person would ever do that. So for all intents and purposes they are all the same. If you are able to, then get the version with 4GBs of ram installed, that seems to be the sweetspot.