Reply to thread

Message: <blockquote data-quote="cybrmage" data-source="post: 230811" data-attributes="member: 51680">I haven't noticed any problems with 100% CPU usage.... But I'm using an Athlon X2 6000+....But... the driver does constantly run a background thread to drive the Equalizer/VU display... This thread runs at a low priority, so it will be pre-empted if the processor is needed for other tasks... Also, The plugin framework also runs a seperate process to collect the information that is displayed (also at a low priority)...To be sure, turn off the Equalizer display and see what the CPU usage is.... and see what the CPU usage is with the CybrDisplay plugin disabled... Let me know your results...The flickering on the display does appear to be related to the refresh rate of the display... The driver already has provisions for limiting the display refresh rate (because the code was originally wriiten for the iMON displays, and they crash if refreshed to quickly)... Try enabling the "Limit Equalizer display update rate" option and different update rates and see if you notice any improvement.Actually, the Bass engine does.... I just haven't had the time to experiment with them yet. (and the documentation is sparse)Holy... all the new features and you guys are still demanding MORE!!! You guys aren't testers from hell... you're just hellspawn!!! 8-} (just kidding!)There aren't enough custom characters to do that for for the Equalizer display... but there should be enough to do it for the VU meter display.... It may be something to consider for a (much) later version.At least you're aware of it... 8-}I program at a resolution of 1280x768... so I always get to see the entire form 8-}... But if any more options are added, well have to enforce a 1920x1080 resolution to be able to configure the plugin 8-}The frequency range is  0 to 44100hz divided into 512, 1024 or 2048 steps. (I use 1024 steps for the EQ display).. IE, the 256th FFT element returned is the data for (assuming 1024 steps) 44100/1024 * 256 =  11025hz.The log does not provide enough information to determine what caused the hang... but the logs do show a number of exceptions being thrown (one by another plugin and one by the MediaPortal core), so your guess as to the cause is probably just as good as mine... or it could be one of those one-in-a-million occurances that can't be duplicated.... Let me know if it hangs constantly and i'll see if I can find anything... I have never experienced a hang with MediaPortal... Crashing, yes... hanging, no...Regards,CybrMageNew version now available.</blockquote>

Verification