Triggering slices with midi notes?

[rozzbud]

wow would be so cool to program the new launchpad pro to do exactly the same thing!

[sezare56]

Yep. With Event Processor Plus…

[license]

hey license,

yeah unfortunately not - the pattern i’ve generated contains a MIDI note which is specific to track 7, and CC data specific to a point in that track…

so any subsequent patterns need to built separately for tracks and start points etc.

nice thing is that they can also include extra data - filter position, amp decay, reverb send etc… so with some planning they can be quite versatile.

so, yeah… thanks for all the legwork you did on this, as it was your planning and ideas that i stole to try to get this working on the MPC.

thanks for the inspiration!

Aw, sorry it wasn’t reusable. Well, if you have a Novation Launchpad laying around I have a little app I started writing (my first C program lol!) to solve this problem, but it’s not ready for the big time yet. I just haven’t made it a priority to work on lately - well, that and I’m insecure because I’ve never put up any source code for public consumption before

The possibility of extra parameters piqued my interest too. I have some ideas around that.

I’m really stoked that I gave you some inspiration Thanks for making it come to life, I was afraid I just alienated everyone with my explanation.

[tomes]

alienate some, interest others. don’t sweat it.

some people just want a solution for this - which is understandable. it’d be great if it was a feature that just worked.

let us know how you get on with the launchpad pro. i know a few people who’d be interested in seeing that work.

[license]

Oh yeah, if I ever get a Pro I will definitely keep you posted! I’m actually keeping it cheap and cheery for now with a Launchpad Mini as the controller/display and a Raspberry Pi for all the heavy lifting. That makes it more accessible for me and hopefully for everyone else I have a run-of-the-mill MIDI interface talking to the OT so that adds another device to lug around but it all easily fits in a backpack without needing a screen (that’s the idea anyway).

[license]

Have not had the time to work on it lately but it’s the first thing on my mind. I’m away from the studio at the moment and won’t be back until after Christmas but I’ll keep you posted!

Also just to clarify, I’m using the cheapo launchpad mini - whichever models send the note data for that should work. Hopefully I’ll support more controllers later…

Actually depending on how much interest there is, I might throw up the Node code I had for this somewhere (e.g. github). I was having some serious issues with the MIDI libraries on ARM so I decided to stick with C but I did have the slice thing working in Node, at least in OSX.

[Modus_Op]

Oops. I just deleted my post somehow.
Coolness. Anxious to see if someone gets the Launchpad (any sort) to trigger slices… Until I read this it was totally off my radar, but now that I’ve watched a few video reviews etc, I think it would make a pretty great companion for the whole trinity… Especially the Pro, because you can customize it so much.

[Modus_Op]

Aww fudge. I just read that you need to use up a couple of scenes to do this. That’s kind of a bummer.
I still don’t understand why this isn’t a feature that someone thought might be useful when first coding the OT. Definitely not designed by people who like to a) finger drum, or b) play keyboards.
Sorry. Just expressing my frustration with the OS supposedly being “done”.

[Modus_Op]

thanks

your method won’t work just with note to cc mapping in a readymade box like event processor plus?

http://www.midisolutions.com/prodepp.htm

Hey, good call on this device. Might be worth looking into. One could then use any midi keyboard, I presume.

[license]

Actually I just remembered that I had another idea a couple days ago for triggering slices. Not sure whether this will work (and if not it may have been mentioned already), but this one wouldn’t require burning 2 scenes if you don’t want to. I don’t have my Octatrack handy (traveling on vacation) so I haven’t been able to test it but those with the right MIDI tools might want to try it:

OT SETUP

• Set the targeted track’s slice to 1
• Set one of the LFOs to square, at speed multiplier 1, at speed 1 (0 might work too, can’t remember), and set its target to slice #

MIDI PROCESSOR SETUP

• Pick a range of 64 notes
• For all notes in that range:
• • Send MIDI note to trigger the target track
• • Send MIDI CC to set the LFO’s DEPTH to the note number within that range

[license]

Also any Renoise users may want to try the Lua scripting built in to do the MIDI processing. Among the many options I’ve tried for MIDI processing, its performance is near the top!

[rozzbud]

Actually I just remembered that I had another idea a couple days ago for triggering slices. Not sure whether this will work (and if not it may have been mentioned already), but this one wouldn’t require burning 2 scenes if you don’t want to. I don’t have my Octatrack handy (traveling on vacation) so I haven’t been able to test it but those with the right MIDI tools might want to try it:

OT SETUP

• Set the targeted track’s slice to 1
• Set one of the LFOs to square, at speed multiplier 1, at speed 1 (0 might work too, can’t remember), and set its target to slice #

MIDI PROCESSOR SETUP

• Pick a range of 64 notes
• For all notes in that range:
• • Send MIDI note to trigger the target track
• • Send MIDI CC to set the LFO’s DEPTH to the note number within that range

did it work?

[license]

Nope Same effect as the regular slice CC. Which surprises me considering how fast/well the OT handles LFOs. This would seem to indicate that only goes for already assigned LFOs - the depth at least doesn’t update any faster than the slice CC.

[crypticresonance]

I see there are other guys/gils here trying the same…
My weapon of choice is a Korg padKontrol. No luck, but if anyone has an idea, I will listen.

[josker]

Bump. :-/

[license]

Working on it! Had a snag with the MIDI library I was using and I found a workaround a couple weeks ago.

I’m also trying to make this controller more modular so that it opens up other possibilities besides just playing slices. So, it’s going a little slower. But I know this slice thing has the most interest right now, so I’ll try to figure out what the minimum viable product with it, plus some other small things I want to gauge reactions to, is going to look like.

[midilifestyle]

Working on it! Had a snag with the MIDI library I was using and I found a workaround a couple weeks ago.

I’m also trying to make this controller more modular so that it opens up other possibilities besides just playing slices. So, it’s going a little slower. But I know this slice thing has the most interest right now, so I’ll try to figure out what the minimum viable product with it, plus some other small things I want to gauge reactions to, is going to look like.

Hey License. Other License here is eagerly awaiting your solution. I just got a quneo and was bummed that I couldn’t script it to trigger slices, so I’m eager to see what you come up with. I’d lend a hand if I knew the first thing about coding. Godspeed.

[rozzbud]

Upppppp!

[license]

I haven’t forgotten this… very far from it. Hopefully I push something usable to GitHub before I die

[sezare56]

Hi. I tried the pattern trick with Mpc 1000 jjos2xl, sending cc48, cc48, note, but it doesn’t work with Note Repeat and Timing Correct. Slice mode worked too.

I used a Yamaha Mep4 midi processor (I could use my Midi Event Processor). I chose note numbers corresponding to Cc48 and Cc17 (0,2,4,6,etc), convert notes to Cc48 and Cc17 and voilà. In that way I can use Note Repeat and TC, this can be done with any midi device sending notes and a midi processor.

Easy to record on the Mpc and realtime modification in sync with Note Repeat, Arpegios, Random Cycle, etc…

Once you’ve finished you can record it on the OT.