Sessions's Composer...
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
You can slice loops in MU.LAB too.
The only difference is that Muzys also had an auto-slice function, cfr the Add-A-Loop function.
Did that make the big difference?
The only difference is that Muzys also had an auto-slice function, cfr the Add-A-Loop function.
Did that make the big difference?
-
- KVRist
- 268 posts since 8 Nov, 2002
I don't know how to slice loops in Mulab so i can't compare, but if i remember well Muzys autosliced them and created a part with event data, but i'm not sure now.
-
- KVRist
- 268 posts since 8 Nov, 2002
EDIT: Deleted, double post
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Yes and you could also map it to the keyboard and play the slicesJuan Mendoza wrote:I don't know how to slice loops in Mulab so i can't compare, but if i remember well Muzys autosliced them and created a part with event data, but i'm not sure now.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Except for the auto-slicig, all is possible in MU.LAB:
Open the sample editor
Add locators at the hit points
Right-click -> Create MultiSample using Locators
Make a sequence that triggers the notes of this multisample
You can also play the slices via the MIDI keyboard

Open the sample editor
Add locators at the hit points
Right-click -> Create MultiSample using Locators
Make a sequence that triggers the notes of this multisample
You can also play the slices via the MIDI keyboard
-
- KVRist
- 268 posts since 8 Nov, 2002
Here's the key IMO.mutools wrote: Make a sequence that triggers the notes of this multisample
When you slice a loop, let's say a breack, sometimes the slices are in non quantized positions, so create a sequence that plays the loop exactly as it was before the slicing could be impossible or hardly achiveable. And for me that's the great thing of loop slicing, play it exatcltly as it is but in different tempos, or substitute the slices by different sounds that play the same groove. I don't see a way to efectively make this without a huge amount of work, and for me that's the real difference, not only autoslice the loops.
Anyway, if you implement a feature like this, IMO, this should have lower priority than many other aspects, and i'd see as more than normal if it's not implemented for M4 or 5. Anyway just MHO
-
- KVRist
- 268 posts since 8 Nov, 2002
... also, I'd apreciate much more to see a thing like the zyklus improvisor implemented than a REX style loop manager because there are many tools that does loop slicing out there and nothing like zyklus
-
- KVRist
- 442 posts since 21 Jan, 2008
+1Juan Mendoza wrote:... also, I'd apreciate much more to see a thing like the zyklus improvisor implemented than a REX style loop manager because there are many tools that does loop slicing out there and nothing like zyklus
-
- KVRAF
- 2938 posts since 18 Jul, 2005
I don't appear to have this option? Do you mean the sample editor from within Multisampla? I have an audio part in the main composer that I've added a bunch of locators to, but I'm not getting this option in the part editor. Or any option to add this part within Multisampla.mutools wrote:Except for the auto-slicig, all is possible in MU.LAB:
Open the sample editor
Add locators at the hit points
Right-click -> Create MultiSample using Locators
Make a sequence that triggers the notes of this multisample
You can also play the slices via the MIDI keyboard
//Edit: Nvm, found a simpler way.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Note that an 'audio file' and a 'sample' are not the same thing in MU.LAB.
The 'Create MultiSample Using Locators' is a sample function.
The 'Create MultiSample Using Locators' is a sample function.
-
- KVRAF
- 2938 posts since 18 Jul, 2005
Logically, yes. But personally I think both create new sample from selection and create new multisample from selection locators should both be available from the sequencer audio part context menu. It's an unnecessary extra step as it is now, IMO.mutools wrote:Note that an 'audio file' and a 'sample' are not the same thing in MU.LAB.
The 'Create MultiSample Using Locators' is a sample function.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
That would entail loading up an unlimited length audio file into limited RAM, I would imagine...
-
- KVRAF
- 2938 posts since 18 Jul, 2005
How so any more than the command that is already there?pljones wrote:That would entail loading up an unlimited length audio file into limited RAM, I would imagine...
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Audio file playback plays direct from disk. You could have thousands of gigabytes of sound playing. Sample playback plays from RAM. You are constrained by how much RAM your system has.
Based on the fact there are so few implementations of it, I expect it's very difficult to have multi-sampling of the nature you're suggesting direct from disk. Certainly, the implementation would be independent of the RAM-based version. (Without care, it would also encroach on the patents for DFD sample playback.)
Based on the fact there are so few implementations of it, I expect it's very difficult to have multi-sampling of the nature you're suggesting direct from disk. Certainly, the implementation would be independent of the RAM-based version. (Without care, it would also encroach on the patents for DFD sample playback.)
-
- KVRAF
- 2938 posts since 18 Jul, 2005
Still not grasping your point, I'm afraid. This command already exists in the program, just not in this particular place.pljones wrote:Audio file playback plays direct from disk. You could have thousands of gigabytes of sound playing. Sample playback plays from RAM. You are constrained by how much RAM your system has.
Based on the fact there are so few implementations of it, I expect it's very difficult to have multi-sampling of the nature you're suggesting direct from disk. Certainly, the implementation would be independent of the RAM-based version. (Without care, it would also encroach on the patents for DFD sample playback.)
