Accessing looplab

[sleepypete]

Hello all, I have what may be a newbie question, so be patient with me if you can.

I'd like to access looplab for a sample I've dragged from my sequencer, Pro Tools 8. However, The looplab options don't show in the main window. All I can see is the key-mapping editor. I've found a workaround where I can bounce the sample down to disk and then import the file to to a part in Mach5 2. This allows me to access looplab but the process would flow so much better if I could simply drag and drop a sample from my sequence window and start using looplab right away.

Hopefully I'm missing something, or this cool feature became less cool and feature-like. Thanks for the time,

pete

[carrythebanner]

Instead of dragging the sample onto the keyboard mapping area, drag the sample onto the parts list (along the left side of MachFive).

[sleepypete]

Instead of dragging the sample onto the keyboard mapping area, drag the sample onto the parts list (along the left side of MachFive).

Thanks for the quick response, carry. I've already tried what you were suggesting and didn't put that in my post, my bad. This is the error I received:

INVALID PROGRAM Couldn't load preset file 'Audio 1_03.L.wav*Audio 1_03.R.wav'

It doesn't let me proceed from there. Ideas?

pete

[carrythebanner]

Hmm, I also got the same error when I dragged from the sequence into MachFive — but after closing & reopening the MachFive window, it worked fine.

[sleepypete]

Hello Carry,

Unfortunately, de-instantiating the plugin and calling it back up didn't work. Could this be a problem with the RTAS version of the MachFive 2? What sequencer and OS are you using?

[carrythebanner]

I didn't remove and re-instantiate the MachFive plug-in — I just closed the plug-in window and re-opened it. If that doesn't work for you, maybe try dragging audio files from the region bin or Finder instead and see if that works.

I tried it with the RTAS version of MachFive 2.0.2 in Pro Tools HD 7.4 on a G5 running OS 10.4.11.

[sleepypete]

Yo Carry,

Thanks for the input. I've tried all of those suggestions and the only thing that seems to work is bouncing to disk and pointing Mach5 to the file itself. Not the best workflow, but it's the only thing that allows me to use my own recorded samples.

For my setup, I am running MachFive 2.02 in PT LE 8 on an eight core mac (2008) in OS 10.5.8