MUTOOLS

Trancit · Post by **Trancit** » Mon Jan 10, 2011 7:59 am

If you load a sample, which contains loop information in a sampler module, you always have to set the loop parameters (Start, End, Looping Forward etc...) manually...

Shouldn't the sampler module set them automatically???

Trancit

mutools · Post by **mutools** » Mon Jan 10, 2011 12:06 pm

How are you going to define which marker is used for what?

funk01 · Post by **funk01** » Mon Jan 10, 2011 5:35 pm

It would be great to put out a tutorial on youtube regarding this feature.

> DiGiT < · Post by **> DiGiT <** » Mon Jan 10, 2011 8:31 pm

i hope for at least a field that will tell you your loop length is "3 16th notes" etc. essentially having a calculator built into the interface that knows what the tempo is and how many samples at the current sample rate for every 16th note. you could make it as functional or as simple as you needed and it would just be plain convenient! i mean keep the sample index and visual display for reference or indeed editing as well. thats what i love about looping in my other favorite software.

Trancit · Post by **Trancit** » Tue Jan 11, 2011 12:19 am

mutools wrote:How are you going to define which marker is used for what?

How do other sampler do this???
Each sampler I know (and I tried a lot like EXS24, Kontakt, VSampler 3, NN-XT, NN 19, Mach Five, Lives internal Simpler and Sampler just to name some) loads samples with embeded loop information correctly.
Why should the sampler modules in MuLab not be able to do the same???

Trancit

mutools · Post by **mutools** » Tue Jan 11, 2011 9:32 am

Trancit wrote:
mutools wrote:How are you going to define which marker is used for what?

How do other sampler do this???
Each sampler I know (and I tried a lot like EXS24, Kontakt, VSampler 3, NN-XT, NN 19, Mach Five, Lives internal Simpler and Sampler just to name some) loads samples with embeded loop information correctly.
Why should the sampler modules in MuLab not be able to do the same???

Trancit

Investigating...

mutools · Post by **mutools** » Tue Jan 11, 2011 12:59 pm

It's a bug.

Fixed in MU.LAB 3.2.4:

http://www.mutools.com/mulab/patch

Change log: http://www.mutools.com/mulab-change-log.html

Trancit · Post by **Trancit** » Tue Jan 11, 2011 1:15 pm

Works perfect now, thx...

Btw, did you received my email about the resonance in the Multimodefilter???

Trancit

mutools · Post by **mutools** » Tue Jan 11, 2011 1:18 pm

Trancit wrote:Works perfect now, thx...

Btw, did you received my email about the resonance in the Multimodefilter???
Trancit

Yes, well received, thx, will reply asap.

mutools · Post by **mutools** » Tue Jan 11, 2011 8:08 pm

There seems to be a sonic bug in the new loop-marker code i added so i removed the 3.2.4 patch. Will fix the issue and upload 3.2.5 asap. Sorry about this.

mutools · Post by **mutools** » Wed Jan 12, 2011 9:13 pm

MU.LAB 3.2.5 patch available in:

http://www.mutools.com/mulab/patch

Change log: http://www.mutools.com/mulab-change-log.html

AIFF and WAVE loop marker support should be perfect now.

MUTOOLS

KVR Audio

Samples loaded in sample modules...