Looplab Pros and Cons

mrdibs · Post by **mrdibs** » Mon Aug 27, 2007 10:18 am

Really the only reason I've upgraded was for looplab. I thought that the ability to read rex and acid files in a loop player that wasn't REASON or STYLUS RMX was a cool thing. One because it didn't have to run in a separate program and two because it didn't require me to import all of my sample files into a proprietary format.

The other thing is that I just lost three whole loop libraries that I had pain stakingly RECYCLED when I had an HD crash. I figured this would be a good opportunity to re-slice some beats in a more efficient way. All in all, it's great, save these few issues:

1. It uses a proprietary format. You can't export REX2 files from it.
2. There should be a checkbox that allows you to automatically move the loop startpoint to the first slice.
3. I have some old programs with loops in keygroups. There is no way to take each individual sample into LoopLab without creating separate programs for each sample. I guess what I'm asking for is a multi sample version of LoopLab.
4. I have yet to have LoopLab recognize slices in an ACIDIZED WAV file.
5. When slicing a large folder of drum loops, you can just slice save the sample and move on. Every time you go to the next sample, it asks you if you want to save or discard the program you are working in. SOOOO LAME from a workflow point of view. IF I WANTED TO SAVE A PROGRAM FROM MY SLICED SAMPLE I'D HAVE HIT THE "CONVERT" BUTTON! I appreciate the fact that the program treats me like I'm a 2 year old, but all in all, I could do with a preference parameter for turning off reminders.

Oh, and drag and drop from the Pro Tools edit window would sure be nice. I mean, jeeze... Every other sampler program on the market does that!

Overall I will say that V2.01 is all around a more viable plug in. It's more responsive and the file system makes way more sense. It's still a memory/CPU hog but hey... I guess you can't have everything...

carrythebanner · Post by **carrythebanner** » Mon Aug 27, 2007 11:18 am

mrdibs wrote:Oh, and drag and drop from the Pro Tools edit window would sure be nice. I mean, jeeze... Every other sampler program on the market does that!

Weird, no problems with this for me. Tried it on a friend's PT system and it worked fine, from the sequence and the region bin, to the key mapper area and to the parts list.

charlzj · Post by **charlzj** » Sun Sep 02, 2007 9:22 pm

Good ideas MrDibs.

I would add:

1. Once you've sliced and mapped a loop, the slice should auto-highlight when you trigger it from a MIDI key. When you've got a couple of bars or so of 16th note slices, it gets tricky locating a particular slice.

2. It's good that mouse-selecting a slice will trigger it, but that feature goes away once you've keyboard mapped it. bummer.

3. Those LoopLab "Half" and "Double" speed buttons should be assignable to MIDI keys for on-the-fly switching.

needlz1906 · Post by **needlz1906** » Mon Sep 03, 2007 8:11 am

Yeah I agree that really sucks because i chop samples up to 50 slices sometimes and it would save me alot of time if I knew which key was triggering what....[/quote]

RCory · Post by **RCory** » Mon Sep 03, 2007 4:57 pm

mrdibs wrote: 1. It uses a proprietary format. You can't export REX2 files from it.
..

I'm sorry to hear about your troubles - I haven't had the chance to experiment with Loop Lab yet.

fyi, Nothing exports REX files except Recycle.

mrdibs · Post by **mrdibs** » Tue Sep 04, 2007 8:58 am

charlzj wrote: 3. Those LoopLab "Half" and "Double" speed buttons should be assignable to MIDI keys for on-the-fly switching.

You know, I hadn't noticed that the "Rules" section disappears in favor of LoopLab. That's pretty lame.

carrythebanner · Post by **carrythebanner** » Tue Sep 04, 2007 9:39 am

mrdibs wrote:You know, I hadn't noticed that the "Rules" section disappears in favor of LoopLab. That's pretty lame.

Well, in LoopLab there's only one sample being used, and hence only one layer, so what would you expect rules to accomplish? Granted, a multi-sample version of LoopLab would be great, but since it currently only works with one sample at a time I don't see any point for rules in LoopLab.

mrdibs · Post by **mrdibs** » Fri Sep 07, 2007 1:55 pm

carrythebanner wrote:Well, in LoopLab there's only one sample being used, and hence only one layer, so what would you expect rules to accomplish? Granted, a multi-sample version of LoopLab would be great, but since it currently only works with one sample at a time I don't see any point for rules in LoopLab.

If you scroll up and look at what we were discussing, you'll see that we were talking about setting up a keyswitch to toggle the tempo multiplyer in LoopLab. It just seems to me that putting such an option in the same window as other keyswitching options makes more sense than creating a new window just for MIDI routing things for LoopLab. That would be the point for rules in LoopLab.

mrdibs · Post by **mrdibs** » Fri Sep 07, 2007 1:56 pm

I was trying to slice up a 3 beat drum fill. Try slicing anything smaller than a bar... MachFive looks at you like you're nuts! LAME!!!

carrythebanner · Post by **carrythebanner** » Fri Sep 07, 2007 3:01 pm

mrdibs wrote:
carrythebanner wrote:Well, in LoopLab there's only one sample being used, and hence only one layer, so what would you expect rules to accomplish? Granted, a multi-sample version of LoopLab would be great, but since it currently only works with one sample at a time I don't see any point for rules in LoopLab.
If you scroll up and look at what we were discussing, you'll see that we were talking about setting up a keyswitch to toggle the tempo multiplyer in LoopLab. It just seems to me that putting such an option in the same window as other keyswitching options makes more sense than creating a new window just for MIDI routing things for LoopLab. That would be the point for rules in LoopLab.

Oh, I thought you meant assigning a MIDI CC to control the half/double buttons (just like how most other buttons work -- you right-click to get a MIDI automation dialog).

At least right now, MachFive's rules only apply to turning layers on & off, not controlling the various paramters. Without some serious forethought and organization, trying to shoehorn the current rules scheme to include everything in M5 would get hairy and would largely be redundant; I'd just like to see CC control of the half/double buttons.

needlz1906 · Post by **needlz1906** » Fri Sep 28, 2007 7:32 pm

Finally got my copy of Machfive2....the fact that you can't see what waveform you're triggering with the MIDI keyboard is VERY ANNOYING...hopefully it will be in the next update..

Also, does the slice extension work when you're triggering a REX or sliced .wav file with a MIDI keyboard or do I have to push play in the transport in order for it to work?

bjornln · Post by **bjornln** » Sat Sep 29, 2007 11:56 am

needlz1906 wrote:Finally got my copy of Machfive2....the fact that you can't see what waveform you're triggering with the MIDI keyboard is VERY ANNOYING...hopefully it will be in the next update..

Have you reported it as a bug or a feature request to motu ?

/B

needlz1906 · Post by **needlz1906** » Sat Sep 29, 2007 7:21 pm

i think I reported it as a bug lol....I went to the tech link thingy...

bobbybland · Post by **bobbybland** » Tue Jun 09, 2009 3:32 pm

needlz1906 wrote:Finally got my copy of Machfive2....the fact that you can't see what waveform you're triggering with the MIDI keyboard is VERY ANNOYING...hopefully it will be in the next update..

Also, does the slice extension work when you're triggering a REX or sliced .wav file with a MIDI keyboard or do I have to push play in the transport in order for it to work?

Did this ever get updated to where you can see the slice your on graphically while triggering from the keyboard?

MOTUnation.com

Looplab Pros and Cons

Looplab Pros and Cons

Re: Looplab Pros and Cons

Re: Looplab Pros and Cons

And another thing!

Re: