Time stretching issues

[gwing]

I have been playing around with MuTools 10.5 demo and there's a great deal I like about it. The interface is clean and uncluttered and the rack system takes no effort at all to understand. It starts up almost instantly and it hasn't crashed once - despite my initial efforts to confound it.

The one thing I find odd is the importing of samples/clips, why do I have to choose the type ?
I understand how they are processed differently but I still find it peculiar.
Also, I tested it against Bitwig and (a demo version of) Studio One V7. I dropped a 2 minute mp3 file into scene 1 of their respective matrix/launcher slots. I also added two drum samples making a total of three clips. I found a 10 second section in the mp3 and looped it. When I played the clips both Bitwig and Studio One played the three clips perfectly in sync, beat matched etc. Mutools just couldn't cope, it was not in sync and there was the odd stutter. I tried different scenarios with the importing type but it made no real difference.

To sum up, I really want to like MuTools but I find the time stretching a limitation. Ideally what I'd like is a conventional time stretch algorithm ie Elastique or RubberBand alongside the current audio sequence idea. The audio sequence system is wonderful for playing around with loops in a creative way and certainly reminds me of my REX days with Reason

Thanks

Win 11, i5 12th gen, 16GB RAM, ASIO installed.

[MuTools]

I have been playing around with MuTools 10.5 demo and there's a great deal I like about it. The interface is clean and uncluttered and the rack system takes no effort at all to understand. It starts up almost instantly and it hasn't crashed once - despite my initial efforts to confound it.

Thanks

The one thing I find odd is the importing of samples/clips, why do I have to choose the type ?
I understand how they are processed differently but I still find it peculiar.

You're not alone with this feedback and i agree it's not ideal. Possibly this aspect will evolve in a future main update. Ideally there should not be a separation between short and long audio files and all audio clips would be of the same type, with the same features. That would be ideal from user side, but it's not a quick & easy thing to achieve technically.

Also, I tested it against Bitwig and (a demo version of) Studio One V7. I dropped a 2 minute mp3 file into scene 1 of their respective matrix/launcher slots. I also added two drum samples making a total of three clips. I found a 10 second section in the mp3 and looped it. When I played the clips both Bitwig and Studio One played the three clips perfectly in sync, beat matched etc. Mutools just couldn't cope, it was not in sync and there was the odd stutter. I tried different scenarios with the importing type but it made no real difference.

I assume it's an audio section with full-band continuous audio, right? MuLab's time stretcher indeed is not at best for this type of audio. If it's another type of audio, please share that 10 second audio sample. You can also email it to

To sum up, I really want to like MuTools but I find the time stretching a limitation. Ideally what I'd like is a conventional time stretch algorithm ie Elastique or RubberBand alongside the current audio sequence idea. The audio sequence system is wonderful for playing around with loops in a creative way and certainly reminds me of my REX days with Reason

It would indeed make MuLab better if it would also have a more standard time stretching algorithm for full-band / continuous music samples, besides MuLab's own time stretching algo which works great on stuff like drum loops or other audio samples with quite isolated sound sections.