KX V3538L and KX Mixer memory usage

Maddogg6 · Nov 27, 2006, 08:56 PM

Ok - I know this was brought up before - But I'm not finding a thread on this topic.. so here it is...

What I have found is KXMixer memory usage can be as low as 3MB (with minimal ProFx DSP set up.) As soon as I add the dynamics Processor - it adds about 28MB as soon as I 'tweak' the Dynamics processor.

Then there are times (not always, I suspect this is affected by M$ memory management) - KX Mixer reports using as much as 36MB - then if I open the mixer - it drops to 8MB-12MB - If I open and tweak the dynamics processor - it jumps way up in memory usage again.

Sorry to pick on the dynamics processor - but it seems to be the 'biggest' offender. I suspect it has something to so with the custom skin for its tweak screen.

Russ · Nov 27, 2006, 11:52 PM

Yeah, this was brought up previously. It is suspected that it is caused by the changes Eugene is making to the skinning system used by kX (and hopefully will be resolved in the next version). It is not only with the Dynamcis Processor plugin, but with all skinned plugins that use the kX gui library (i.e. does not include ProFX and UFX as they use their own gui code).

BTW: As Lex mentioned, if you minimize the DSP window (or the mixer window), the memory usage is reduced even further, but this does not completely free up the memory, as it is still reserved (VM/Private Bytes).

Maddogg6 · Nov 28, 2006, 12:43 AM

Quote:

Originally Posted by Russ

BTW: As Lex mentioned, if you minimize the DSP window (or the mixer window), the memory usage is reduced even further, but this does not completely free up the memory, as it is still reserved (VM/Private Bytes).

This isn't always true - and I didn't remember seeing dynamics processor being the major culprit, but I have found that removing DP from the DSP has always freed up the ~28MB...so... - I posted... maybe it will help someone who didn't put those points together like apparently I didn't - hehe...

Russ · Nov 28, 2006, 01:06 AM

Also, you will want to minimize the (skinned) plugin window (once) too (if it is open), but again, that does not free up the reserved memory . Unloading any of the skinned plugins will free up the extra memory reserved by that particulair plugin.

i.e.
kX seems to keep something like 30MB reserved (probably for use by kX Mixer and other skinned kX applets), and some skinned plugins (or using multiple skinned plugins) can bring that number way up, but unloading these plugins will bring it back down to the minimim (@30MB), but nothing (afaik) short of quitting kX Mixer will free up that last @30MB of reserved memory.

Nov 27, 2006, 08:56 PM	#1
Maddogg6 Tail Razer Join Date: Jun 2005 Location: Bernyurass, AZ - USA Posts: 4,027 Rep Power: 0	KX V3538L and KX Mixer memory usage Ok - I know this was brought up before - But I'm not finding a thread on this topic.. so here it is... What I have found is KXMixer memory usage can be as low as 3MB (with minimal ProFx DSP set up.) As soon as I add the dynamics Processor - it adds about 28MB as soon as I 'tweak' the Dynamics processor. Then there are times (not always, I suspect this is affected by M$ memory management) - KX Mixer reports using as much as 36MB - then if I open the mixer - it drops to 8MB-12MB - If I open and tweak the dynamics processor - it jumps way up in memory usage again. Sorry to pick on the dynamics processor - but it seems to be the 'biggest' offender. I suspect it has something to so with the custom skin for its tweak screen.

Nov 27, 2006, 11:52 PM	#2
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,561 Rep Power: 62	Yeah, this was brought up previously. It is suspected that it is caused by the changes Eugene is making to the skinning system used by kX (and hopefully will be resolved in the next version). It is not only with the Dynamcis Processor plugin, but with all skinned plugins that use the kX gui library (i.e. does not include ProFX and UFX as they use their own gui code). BTW: As Lex mentioned, if you minimize the DSP window (or the mixer window), the memory usage is reduced even further, but this does not completely free up the memory, as it is still reserved (VM/Private Bytes).

Nov 28, 2006, 01:06 AM	#4
Russ HardwareHeaven Extreme Member Join Date: Jan 2005 Posts: 5,561 Rep Power: 62	Also, you will want to minimize the (skinned) plugin window (once) too (if it is open), but again, that does not free up the reserved memory . Unloading any of the skinned plugins will free up the extra memory reserved by that particulair plugin. i.e. kX seems to keep something like 30MB reserved (probably for use by kX Mixer and other skinned kX applets), and some skinned plugins (or using multiple skinned plugins) can bring that number way up, but unloading these plugins will bring it back down to the minimim (@30MB), but nothing (afaik) short of quitting kX Mixer will free up that last @30MB of reserved memory.