Triggering slices with midi notes?

Elektron Gear Octatrack
#163

For sure !
You kneed an Octatrack to check if it works, and to understand how it works otherwise you will maybe loose you’re time and go crazy. Manual is not enough I think.

CC17 is the Cc for Start point position in the sample, or the Slice No, in Slice mode.
Ot reacts slowly to that Cc so there are mistakes.
But it works with the Cc48 wich controls the crossfader, set with Slice No values, depending on the number of Slices.

Cc17 can be sent to record Slices variations. But if you want to hear them, you have too “turn off” crossfader Slice settings…

Good luck !

#164

I’m trying to resurrect this old thread.
I had this working fine…
http://www.bome.com/forums/viewtopic.php?f=3&t=12243
But as has been mentioned this uses the CC17, and so you have to have a 50ms delay (as mentioned on thread post)

…Am I right in thinking I can dispense with this using cc48 ?
Can anyone testify to ‘immediate’ slice triggering from an external midi note through a “midi processor” (insert your favoured device here) > Octatrack ?

If so, what’s the methodology please ?

Cheers

#165

No latency with CC48, with my Ep+.
I wrote almost everything about my personnal procedure above.
More details on demand. :wink:

1 Like
#166

thanks :slight_smile:
So the outgoing message as per the previous thread is :

// PLAY SLICE SETUP:
// oo is what OT Audio Track number your slices are
// rr is Octatrack MIDI Auto Channel
oo=1
rr=11
//
// ----------------------------------------------------------------------
pp=oo+35
rr=143+rr

The results of this then being fed into the sysex message :
rr pp 7F

I am having trouble reconciling that with the cc48 (or indeed cc17) instruction.
Is it a conversion of the value into hexadecimal or something ?

#167

Sure ?
Me = 143 beautiful girls + Me
Magical. :smile:
7F is hexadecimal for sure, equals 127.
Other things are weird to me.
Were are Cc numbers?
Incoming messages?
Outgoing messages?

#168

lol
you greedy bastard 143 to yourself !
the bit i missed out was this :

// SLICE SELECT SETUP:
// Assuming all pads are sequential note numbers, set qq to be the lowest MIDI note number of the pads
// Set rr = Octatrack Auto Channel
qq=60
rr=11
//
// -----------------------------------------------------------------------------
oo=oo-qq
pp=oo*2
rr=175+rr

resulting in midi message :
rr 42 pp

#169

rr 42 pp

OK rr is midi channel and pp is slice number value. This one is x2 because there are 64 slices for 128 values.
Not sure about 42
Slice CC : 11 (hex) or 17
Xfader CC : 30 (hex) or 48

#170

just noticed this , so sorry for delayed reply. impressive detective work . thanks :slight_smile:

#171

If you could share this with me that would be much appreciated !
Especially ‘controlling comb fillter pitch with midi notes’

#172

You want me to share Ep+ with you ?
I won’t go to London ! :smile:

You want to do it with Bome ?
Basically I just mapped midi notes to the FX CC controlling pitch.

#173

Ah I see… Thanks :grinning:

#174

Still trying to get this working.

Have cc17 working. Can control all 8 tracks… Any slice on any track etc.
But that’s a 50ms delay

Have cc48 working. Set scene 1 at slice 1 and scene 2 at slice 64 and trigger any slice on the selected track via midi with 0 latency.

But as soon as I try cc48 and cc17 it starts mis behaving and triggering wrong slices. At 30 ms delay on the note it kind of works… Rarely mis triggering , but certainly not sample tight.
Can anyone help ?
Exactly what delay are u applying to the note to get this to work ?

#175

Do you send midi messages in the right order?
CC17, CC48, note.
No delay, with Ep+.

1 Like
#176

hmm drove myself mad yesterday.
yes, in short I think so.
But in Bome Midi Translator, I was adding a 1ms delay to each to have them trigger ‘very quickly’ after each other. I’ll double check this next time I fire up. Cheers for coming back to me. Any chance you could send me the text file you mention a few posts back detailing how you have set up ?

#177

You mean the text file for Ep+?
It won’t help you with another product I think, as it should be sysex.
I don’t use any delay for triggering slices with Ep+ to make it work.
I map notes to CC17, then to CC48, then to a triggering note.

#178

ok makes sense. thanks for replying. misunderstood

1 Like
#179

Oh Shit !!
It works !!
Sezare56 you are a gentleman for continuing to reply to my dumb ass messages while I got my head around this . It’s way simpler than I thought. Thank you :slight_smile: Happy Days .

TriggerSlicesWithMidi
For anyone that’s interested,
That’s the BomeBox Script. For it to work set tracks 1 through 4 to midi channels 11 through 14 respectively. turn slices on for those tracks, load up sliced samples and play from c-1 upwards to trigger slices starting at one (one slice per note)

Mad Props to All in this thread for sussing it out

6 Likes
#180

:thup::content:

1 Like
#181

Would you be able to supply the exact text file / script that you have for ther midi solutions +box … I a thinking of buying one of these boxes so i can play slices on my keyboard and it would be great to have it working the same way you have it Thanks …

#182

For sure. What kind of midi controller would you use ?