[RELEASE] Official XBMC boblight Addon

I have now seen a few movies with Philips AMBX set. Here are my experiences on the ATV1;

- 1080p h.264 (MKV, x264) works most of the time but sometimes drops frames. My bet would be the added CPU cycles from boblight addon, boblightd, combustd and ruby.
- Colors of the lights are not accurate and needs calibration.
- Update speed is lagging some, which is noticeable sometimes. I'm afraid to touch this as it might cause more dropped frames.

I wonder what it would take to remove combustd and ruby from the equation...

Wikking, if you are still having problems, let me know. I will try to cook up a guide revolving the new addon and AMBX.

bobo1on1 Wrote:Ehm no, you still need to have libboblight on your system and a running boblightd somewhere.

Sure, but all you need to do on Live is download the source, compile & install. Also get libboblight. Then run the addon and were done right?

Or am i missing a step?

Well sure, then it should work.

Can this script be updated to look for libboblight.so in a custom path?

I run openelec, and /usr/lib is mounted read only, if I could manually specify a path for libboblight.so, I could keep boblightd and libboblight.so in the user data area.

Sure, but it's a lot easier to just set the LD_LIBRARY_PATH environment variable on your system before starting XBMC, or is that in a read only section too?
Otherwise, just look for libboblight.so in the addon code, and add a path before it.

bobo1on1 Wrote:Sure, but it's a lot easier to just set the LD_LIBRARY_PATH environment variable on your system before starting XBMC, or is that in a read only section too?
Otherwise, just look for libboblight.so in the addon code, and add a path before it.

This is read only as well, unfortunately.

I was hoping for a more "official" change, than me hacking the code for my own installation.

I'm working on getting boblight added as an official package in Openelec, but in the mean time allowing users to run everything from the data area would be a good work around. If I can get the Openelec maintainers to accept my fork, this may not be needed.

then i'll wait until this exactly will happen *whistles*

Memphiz Wrote:then i'll wait until this exactly will happen *whistles*

I've submitted a pull request.

Boblight won't be accepted into the "main" os, but it will work as an addon. I've created an addon that should be accepted into the build and works with the modifications I made to this script.

@bleze
I'm still unable to get the AMBX-device working with boblight-SVN. It would be so kind of you if you could cook up a guide to getting this thing to work properly!


@Adam B.
As you have already posted your addon in the openelec-forums, do you think you could also support the AMBX-device?

Wikking Wrote:@Adam B.
As you have already posted your addon in the openelec-forums, do you think you could also support the AMBX-device?

I don't have an ambx device, so I'm not exactly sure what's needed to get it working.