G-Force vis-plugin porting to XBMC, need help plz

the vis'es .xml file

remember though that some audio codecs take much more cpu time than others to decode so it's good to keep default resolution low

fps-display is in work

and i want to optimize the plugin, but don't know how fast i can get the little thingy. startup is very slow because the compilation of the script is not very optimised and reserves many small memoryblocks. a memorypool should speed it up.... when i have some time...

(gamester17 @ april 15 2004,10:59 Wrote:remember though that some audio codecs take much more cpu time than others to decode so it's good to keep default resolution low

also if you have hq resampling on that sucks quite a bit of cpu.

maybe rather than having questor add framerate to g-force, it should be added to xbmc itself, that way all vis's could benefit from it. a bool could just be added to vis_info struct:

struct vis_info
{
            bool bwantsfreq;
            int isyncdelay;
            bool bdisplayframerate;
};

that way vis's themselves could still determine whether it was being shown (probably from setting in xml), but all vis maker's wouldn't have to duplicate this code.

(i'm cross posting this in the visualization plug-in interface forum)