Hi @RoChess .. You´re right about the home screen getting a higher CPU spike than in plugins. But my CPU never went above 30, and running a trailer from MP with leds on, just hit about hit the 15 cpu mark, so i don´t think this stress my system.I have tried lowering the FPS and play around with the delay time, but it only shows if i use the mediaportal capture mode... I can run it at max with no delay in ambibox, and dont see any flicker when playing video file from mediaplayer .... If i play files from mediaportal i do not see any fps hits over 30, in ambibox.
Run MediaPortal in windowed mode, but maximize the window size to entire screen. Then have task manager and/or your favorite app such as HWMonitor run in the background to monitor CPU/task usage.
I know MediaPortal for me on Titan Extended home screen uses an enourmous amount of CPU cycles (60-80%), but the moment I open a plugin it drops (5-10%). Granted I am still on MePo v1.08, but I'm tired of upgrading to upgrade, and it doesn't exactly bother me. Still such CPU usage would clearly interfere if AmbiBox was doing any active LED control.
I do not use the MediaPortal method to drive my Lightpack though; just AmbiBox itself. It works fine for me, and haven't found the time to mess with it yet.
MP is 1.10 and i got an i5 CPU with 8gb of ram. @Lightning303 thinks it could be how atmolight connects to ambibox, or rather how it´s not connecting proberly to ambibox. I use the mediaportal capturemode, what do you use?? Do you let atmolight control ambibox??