- Moderator
- #51
oh nothing, only, if you try to do this with your work on Ambilight, this can be awesome !yes i understand (I've seen many of them).. what should i do with it ?
oh nothing, only, if you try to do this with your work on Ambilight, this can be awesome !yes i understand (I've seen many of them).. what should i do with it ?
Ohhh, , it's true, i have say you can stop ( standby) the project, for helping to solve mp bug, but was my proposal (my opinion), but was only valid, if your rework need lot of time, if the rework was at the end, it's best to finish it ( like you have doing ).1. You tell me i should stop the projekt.. (i have finish implementation of this in BassVis) and now i have stop Support for this!
i have tryed, but without succes. and my time is limited with life.No hardware to test it self
Atmowin use many CPU ?3. high CPU utilization alone at AtmoWin
i can try to help, my ambilight system is down of my TV. and connected to my Workstation for test4. lack of Support (Show Hardware Test)
Atmowin use many CPU ?
25% AtmoWin, 5% WDM, 20% Example = 50% CPU Usage!.... this is high i thinkhum i think is not very big 25% for Atmowin
@legnod I made a quick test but i got a problem...I cant go to fullscreen mode (Step 3)... i always get an error message (take a look at the screenshot) and after that i have to exit example.exe because the program stops responding
Thanks...now it is working looks very good.
i can confirm the CPU load...its up to 40% ...it depends on the visualization and the amount of colors within the visualization ...most of the time its around 25-30%