Is this a bug?

[musikmachine]

I just realised i'm using 1.43 and i'd like to get the latest version.How do i get it?

I want to use liveslice in phrazor for audio and i'm trying to configure it to play different parts that i trigger with clips.

However when i'm looping clips some of the parts i've loaded into liveslice don't always retrigger.I am having a bit of trouble figuring the midi side of liveslice out so it may be that i dont have it set up correctly.

Does the midi controller config correspond to the midi playback config?

I can't quite figure it out

Cheers.

[ohm]

updates are emailed, you should have received yours already. please email support at livelab dot dk providing the email you used when purchasing, and state your method of payment (paypal or share*it), as well as your current email address. also check your spam folders, they could be eating your updates.

finally when you have received the latest version, see if the problem persists and if it does, contact me again.

[musikmachine]

Thanks ohm i found it.I'll let you know how it goes...

[musikmachine]

I think i have it sorted ohm,it was the midi config.

Is liveslice known to eat a lot of memory?I'm running two instances in the latest beta of xt2 and memory usage is 525mb!I am also running two instances of metallurgy so it could be those>more likely to be the beta though but i thought i'd ask,i've not noticed such high amounts with other plugins.

Cheers

[ohm]

regarding memory:

LiveSlice loads all audio data into memory, so if you have a lot of audio loaded it will use quite a bit of memory. If you load a 2mb loop in 16 bit it will take 4.5 mb of memory since the audio is stored in 32 bit internally, and the graphical representation takes some memory too, because of the fancy colors and all.
To check the memory use load up your sequencer, then bring up the task manager (hit CTRL+ESCAPE) and look for your sequencer in the "processes" tab. Then check the memory use before and after you load a plugin. Notice that simply opening the gui of a plugin will use some megabytes because of all the bitmaps used to display it, but it should never ever be 512mb !