MuTools

runaudio · Post by **runaudio** » Fri Mar 11, 2016 10:24 am

Sliceing Audio then you change the tempo it glitches

MuTools · Post by **MuTools** » Fri Mar 11, 2016 10:31 am

Maybe you set a loop in a slice and then when slowing down the tempo the audio loop plays?
If you don't find the cause, feel free to post a little project that demonstrates what you hear.

runaudio · Post by **runaudio** » Fri Mar 11, 2016 11:10 am

okay i have added a project what you will see is that the loop is 120 bpm and also slice the loop as well now slow the tempo down you will hear the slice loop glitching i will email you the loop as it is to big to upload on here 256k is only allowed

MuTools · Post by **MuTools** » Fri Mar 11, 2016 11:43 am

The loop you sent me is not used in the project. So i can't check this. Please keep it simple and upload a simple project demonstrating the issue via Google drive, DropBox, WeTransfer, ...

pquenin · Post by **pquenin** » Thu Mar 17, 2016 1:34 pm

When not in Mulab, in the MUX VST, it's not easy to have a multisample quickly ready to use.If you open a multiSampla device, or a multisample player and drop a loop file on it, it create a single note zone that is preselected.
You have to deselect it and reselect it to have the waveform display at the right.
What is nice is that the loop is automatically sliced, but there's no way to create all the zones for each slice.
You can create a sequence, or a multisample using the markers, but then you have to open a second multisampla and select the created multisample...
Can it be improved ? Or is there another way ?

I also think that multisamples must be separated files, and that the file format must be exposed so we can create tools to convert SFZ or other formats in Mutools multisamples.

MuTools · Post by **MuTools** » Fri Mar 18, 2016 6:45 am

pquenin wrote:When not in Mulab, in the MUX VST, it's not easy to have a multisample quickly ready to use.If you open a multiSampla device, or a multisample player and drop a loop file on it, it create a single note zone that is preselected. You have to deselect it and reselect it to have the waveform display at the right.

That's fixed in the next version, then it immediately shows the relevant properties pane at the right.

What is nice is that the loop is automatically sliced, but there's no way to create all the zones for each slice. You can create a sequence, or a multisample using the markers, but then you have to open a second multisampla and select the created multisample...

Why do you have to create a new multi-sample player? After doing "Create Multi-Sample Using Markers" you can select that new multi-sample in the same multi-sample player. Right?

I also think that multisamples must be separated files

Yes i agree with the need for that. It's implemented in the next version.

and that the file format must be exposed so we can create tools to convert SFZ or other formats in Mutools multisamples.

Mmm, i'd rather support SFZ. That would solve even more. Right?

Michael L · Post by **Michael L** » Fri Mar 18, 2016 8:52 am

mutools wrote:Mmm, i'd rather support SFZ. That would solve even more. Right?

Are you considering enabling editing & creating sfz files as well as loading & playing? Could we then easily exchange sample sets among Mux instruments and across hosts?

MuTools · Post by **MuTools** » Fri Mar 18, 2016 11:04 am

Reading SFZ files is on the wishlist, at first focusing on core sample sets, not yet sure about all the synth details. Pquenin you also mentioned "other formats", which ones do you mean? Can those also be converted to SFZ? If yes then SFZ could be the interesting common format.

pquenin · Post by **pquenin** » Fri Mar 18, 2016 4:01 pm

mutools wrote:Why do you have to create a new multi-sample player? After doing "Create Multi-Sample Using Markers" you can select that new multi-sample in the same multi-sample player. Right?

Yes you're right, but what is confusing is that the Multisample window that is opened is the one witch refer to the old "mono-note" multisample, you have to open the Multisample window again to work on the new multisample. But well, I can do with that.

What is more annoying is that sometimes (often ? but don't understand why) when you create your first multisample by dragging the loop over a note in the Multisample window, the loop waveform that is displayed in the righrt panel is not sliced.
I seems to happen in a "fresh" song if you don't have already tried to slice the loop before.
Then you can't slice the loop except by choosing "create sliced sample part" but then it creates a new rack with a multisampla, a new track, and a new sequence in Mulab and certainly crashes the host if you are doing this in another host with the MUX VST (have to check this). I suppose that all options in the menu that are linked to Mulab will have problems in the MUX VST.

mutools wrote:Pquenin you also mentioned "other formats", which ones do you mean? Can those also be converted to SFZ? If yes then SFZ could be the interesting common format.

Well I was thinking of not popular formats, for instance those you can find on mobile app such as Nanostudio, BeatMaker, Caustic... And it was mainly to convert drum kits from those app to use them in the MUX, because it's simpler than synths formats, so I can code the tools myself, because I'm not a genious at coding.
But SFZ is an open format so I agree it's better to convert into SFZ, if MUX is able to read SFZ files.

MuTools · Post by **MuTools** » Fri Mar 18, 2016 8:03 pm

pquenin wrote:What is more annoying is that sometimes (often ? but don't understand why) when you create your first multisample by dragging the loop over a note in the Multisample window, the loop waveform that is displayed in the righrt panel is not sliced. I seems to happen in a "fresh" song if you don't have already tried to slice the loop before.

When a sample file already contains markers or when there is a corresponding xml file with saved markers then these markers are used. When there is no such existuing marker info then no markers are used. But when you create them yourself, then they will be visible thruout the project as samples are only loaded once. Hope that explains it.

Then you can't slice the loop except by choosing "create sliced sample part"

Use the "Add Transient Markers" function, that will slice up the loop.

and certainly crashes the host if you are doing this in another host with the MUX VST

Did a quick test with a preliminary MUX 7 Vst version in Reaper, didn't crash here upon using "Create Sliced Sample Part" though that function is not relevant in MUX Vst. (taken note)

pquenin · Post by **pquenin** » Fri Mar 18, 2016 11:13 pm

mutools wrote:Use the "Add Transient Markers" function, that will slice up the loop.

OK thanks.

Did a quick test with a preliminary MUX 7 Vst version in Reaper, didn't crash here upon using "Create Sliced Sample Part" though that function is not relevant in MUX Vst. (taken note)

I have also tried this with the latest MUX 6 in Tracktion and no crash. And this function can be usefull in the MUX too as the created part is available as a sequence in the browser...

Michael L · Post by **Michael L** » Sat Sep 03, 2016 12:54 am

mutools wrote:Reading SFZ files is on the wishlist, at first focusing on core sample sets

I necro'd this FR thread on .sfz to point out that there is a new and free utility for rapid mapping of samples to sfz 2.0 format, with youtube tutorials: http://vis.versilstudios.net/sfzconverter.html
And, a 50% sale until Sept 6 on Chicken Systems' Translator 6 that converts Kontakt, Ableton, FL Studio, Logic EXS, Battery, MachFive and other formats to .sfz (and v-v). http://www.samplerzone.com/catalog/prod ... ucts_id=28
So, if MuLab reads .sfz you could convert all your sample libraries to use in a Mux module.
Would this be generally useful?

pquenin · Post by **pquenin** » Mon Sep 05, 2016 8:01 pm

Thanks for sharing this...