#1

Not sure theres a tremendous need for more but the multiple updates since release may require something new

Along with my own question (below) i thought i’d ask: can you think of anything useful which hasnt been addressed in the original docs?

I’m embarrassed to ask about something that must be exceedingly basic to most of you but, how exactly does aleph’s midi OUTPUT work? I thought I understood the way it should be routed but i’m not getting expected results

If i understood a simple connection (press a footswitch, send a note) i’m sure i could sort out the other more complicated routing. The first hurdle keeps tripping me up though

#2

Are you asking about the Midi note outtput, or the Midi cc output?
For the Midi Note, you need to send some velocity or you won’t get a thing. For the Midi cc, the channel is going from 0 to 15 instead of from 1 to 16 (so you need to send 0 instead of 1, etc), but the cc number is the same. Apart from that there is nothing special to know. Anything else?

#3

Well @Yann_Coppier this exposes my unfamiliarity with midi usage in general

I’ve been trying to use aleph to trigger sound out of some synths (nord drum, roland cmu, yamaha rx11 & tx7).

If i want a button press or METRO tick to trigger a sound, which do i use? note or cc?

Is any scaling needed?

I originally assumed setting the SW output to the midi note VEL input would work…but nothing happens

#4

Well it all depends, but if you want to trigger a note - like you’d do with a keyboard - then it is a… note. CCs will help you modify the sound, but you could mute/unmute your sound this way, which could be heard as a trigger as well (although it isn’t). If you want METRO to trigger notes, then put METRO/VAL to 127 for max velocity (or whatever you think is best) and send it to MOUT_NOTE/VEL, after choosing the note you want to target in the INPUT section. You might find out that it’s sending one note once and nothing more (haven’t tried myself this way so I assume it’ll be the case), because it’s only sending 127 all the time (so no “note off”, or VEL=0). If so then you can use a TOGGLE object: put the value of the METRO to 1 again, and toggle between 0 and 127. Your tempo will be divided by two (you’re sending a note each second beat), but it’ll hopefully work.

Oh, and the scaling is just from 0 to 127 for everything using MIDI - also to pick a note, as that represents about 10 octaves (10 times 12 semitones) and half. That corresponds to an ambitus going from 20 Hz or less to above 20.000 Hz, so all you need is in here. Finally if you want to go from CV to MIDI you’ll have to calibrate: find the minimum and maximum you are receiving (for instance with a Koma Kommander I get values between about 80 to 3100). Remove the minimum (SUB 80), multiply it as much as you can so you get close to 32767 (MUL 10), mostly so you get more precision when dividing in the end, and then divide to get a number going from 0 to 127 if possible (DIV 237). Now the Commander can control any MIDI source from 0 to 127, sending to CC or to notes/velocities with as much precision (meaning not much, but well) as MIDI can offer.

1 Like