I'm still playing with "Interval". My current config works really well with movies - change in interval actually seemed to have a positive effect on the colors as well (black actually occurs betters than before, but fast effects like the ending of my video seem to flicker a little with the white beam).
Oh and I use 5% LED depth but I'm planning to experiment with even lower values ...
prefix 41 64 61 00 18 4D
As you can see, speed is pretty high, but it works well ... I guess the amount of LEDs matters in this case as well.
I've got quite a bunch of LEDs (my TV is 80"), so the amount of data is pretty big ... I see a lot of folks use 38400 and 115200 ... you could give 115200 a try and see if it even matters for your setup.
Boblight Config Maker:
Can you describe (TV rear view) how your config looks like? As far as I can see, you should be able to do just that, but maybe I'm not understanding your setup.
Otherwise I'd like to look into adding the option if it isn't possible ...
Right now you can start: Left, middle, right. (mind the proper orientation of course, but bow orientations will work for all 3).
Did you experiment with letting the bottom left and bottom center set to zero? (dito for bottom right and bottom center)
My XBMC runs on a tiny AMD Fusion computer, so I'm sure apps like watchdog combined with boblight is pushing the [timing] limits.
I'm considering looking at something more potent, like the new intel NUC, but I'd prefer it to be potent enough for experimenting with SteamOS in the future as well.
I have seen others work with the Raspberry Pi, but I was thinking of using it independently. Meaning: "digitize" the video signal, have Raspberry Pi analyze it and control the LEDs so the Ambilight would also work with other devices ... problem so far is finding a HDMI pass-through device that allows digitizing (which comes with issues when the HDMI signal is encrypted) ...