[raptorjr]

raptorjr. And.i tell you that the addon doesn't ignore the settings in the boblight.conf (its not able to ignore it even if it wanted to). Both settings play a role in boblight configuration. In boblight.conf you tweak each color for fitting to the attached leds/hardware. Boblight addon is only able to tweak options which apply to all channels (saturation, treshhold and so on). Thats limited/intended by the client / server design of the whole boblight construct.

And thats why the defaults CAN'T be made more generic then they are. Because everyone can diddle in the boblight.conf as he wants and turning the defaults into crap.

TBH thats what you did...

I don't really understand how you can say that? As my pictures show, when everything is set to default values it looks bad. How can that be my fault?
The changes that i made to boblight.conf afterwards made boblight-X11 look good, XBMC addon still looked bad with fast/slow preset. That was when i first tried to get help.

Sure, you can say it is not possible to make good default values in XBMC addon depending on different LED hardware, then you should remove the fast/slow presets, it makes the user think it is good default values. If you really should have some presets in XBMC addon, the values in that presets should be so neutral that they in no way interfere with the boblight.conf settings. So if things look bad you can refer to that the user has messed up boblight.conf. Now the presets totally mess up anything you try to change in boblight.conf. Even though it don't touch the same settings, the result looks like it does. No matter what i changed in boblight.conf the effect was minimal to the output when i thought that the presets was a decent way to start with. As can be seen in my pictures also.

So my suggestion would be if you want to have presets in the XBMC addon, don't let those settings in any way affect the colors. The presets colors should entirely rely on boblight.conf.(unless the presets have names like bright/dark/vivid or something) The presets can control other things, like the speed that don't affect the colors. And since the name of the presets is fast/slow that wouldn't be a bad start. Then when the user has that working, they can go to custom and adjust the other values.

But i guess it doesn't really matter what i say. In some way we got a bad start(probably my fault) and you probably won't listen to what i have to say looking at things from a user perspective. But that is okay, it works for me now, and if someone else have the same problem as i have at least they can find this thread and a solution.