[SOLVED] Why does ML9 treat audio files differently from other DAWs?

[oldcastle]

Hi,

First and foremost, this question is intended to help me understand why ML works the way it does, rather than to compare it to other DAWs.

I've been playing with Bitwig and Reaper (on Linux, of course ) and I noticed that importing audio files (.wav) is straightforward on those two. You just import it, and that's it. However, on ML, you have different ways of working with an audio file. There is no such thing as "import it and that's it." And things get a bit funnier when you import a loop sample at 120 bpm into a track set to 110 bpm, for example. Because of that, I think ML can look a bit overwhelming for those coming from different DAWs. So, any shedding of light here will be appreciated.

[MuTools]

First of all, also MuLab can use audio files in the standard way: Drop an audio file on the composer and choose Audio Stream. That will play the audio file as it is.

Another option is to chop the audio file into slices and tweak each slice individually including stretching, pitching, filtering etc. That's the Audio Sequences.

You can also use an audio file as a pitched sample like in a traditional Sample Player.

So that's why there are different methods to use an audio file.

Relevant doc pages:

https://www.mutools.com/info/M9/docs/mu ... mples.html
https://www.mutools.com/info/M9/docs/mu ... ences.html
https://www.mutools.com/info/M9/docs/mu ... mples.html
https://www.mutools.com/info/M9/docs/mu ... poser.html

[oldcastle]

Ah..ok I got it. Thanks!