2015-02-10, 01:55
(2015-02-10, 00:34)noggin Wrote:Well as I explained in an earlier post,I installed Kodibuntu, and it does not use pulseaudio, only alsa. Havent tried MCDI but I don't see why it shouldn't work. I had to install 3.18.5 kernel manually. And also Intel Graphics. I am not sure what benefits Intel Graphics has over the standard ones, probably just newer drivers or something, but html5 video was laggy without it (in google chrome). It boots into kodi-standalone in a couple of seconds, so for all intents and purposes it's just like OE , but with the added flexibility of a stable distro as the backbone.(2015-02-10, 00:30)Soli Wrote: I don't mean to be rude to anyone involved in OE, but the reason that I went for Kodibuntu instead of OE is that it is probably more compatible and stable in the long run.
To be frank, I've tried out OE in the past, starting from before the 0.x beta builds, and once in a while I try out a new build as well. Generally it works, but there's always *something* that doesn't. Regarding the Apple TV1 builds of OE, they were downright horrible, whereas Crystalbuntu 2 worked much much better.
Kodibuntu runs very very well on my HP Chromebox, it's just at little more time consuming to set up. And as a bonus, you get to install Google Chrome and watch Netflix.
Have you got MCDI VAAPI working OK in Kodibuntu? That works really well in OE 5.0.1 on my Chromebox.
I usually have the opposite response to using non-OE builds on my Chromebox. I have one running Ubuntu and one running OE. The Ubuntu one always takes a lot longer to get HD Audio (got that whole Pulseaudio stuff to contend with) and de-interlacing in quality (MCDI is a very nice thing to have) than the Chromebox, though the Ubuntu build does have advantages when it comes to building new TV Headends, running a VPN to access a remote network etc.