Note Remap - individual notes, not range

Midihub
1

Hi all,

Is it possible to have one modifier that can remap multiple single notes? Note remap only allows a range of notes, so in order to do what I want to do I would have to have multiple pipes for each note I want to change, and then I’m worried they will cancel each other out as notes outside each range will be discarded. I don’t have my Midihub yet - so haven’t actually tried this. Nonetheless one modifier for multiple single notes would be ideal.

Thanks

2

Hey, how many notes would you want to be remapped?

Currently, you’d place multiple parallel pipelines, so the ranges don’t cancel each other out or affect the results unexpectedly.

1 Like
3

Hi!

I was hoping to remap the sequencer output from one drum machine to another drum module), so it would be 11 individual notes, as follows:

C1-C3
E1-C#3
G#1-D3
C2-D#3
E2-E3
G#2-F3
C3-F#3
E3-G3
G#3-G#3
C4-A3
E4-A#3

I thought about running them in parallel (i.e. 11 separate pipes) using the same from and to ports but wouldn’t the current Note Remap modifier end up cancelling some of these out?

Thank you

4

On each parallel line, the same input gets processed, so each pipeline would work only with their range, discard the notes outside of it.

Of course having a single pipe capable of multiple single-note mappings would be more convenient for such use cases. :slight_smile: We’ll think about adding something for that.

But it’s possible to achieve what you’re after with the Note Remap pipes in parallel.

1 Like
5

Fantastic! Thank you for confirming that - can’t wait to receive my Midihub on Monday.

1 Like
6

Hello Giedrius!
Was this ever taken further?
Would be great to have one modifier, instead of many in parallel.
Thanks

7

Hi @OPT

Answering as @Giedrius may be sensibly AFK on a Sunday… :smiley:

It’s been possible to do this in one pipeline since they gave Transform ranges a few years back.

The new firmware now gives us CC Table which you can use to do a drum map in just a few pipes.

here’s what the output of a testing line would look like…

OPT_drum_map2
OPT_drum_map21574×878 128 KB

(showing the Ch10 CCs created by the CC Table being Transformed back into the notes you want)

…but you can do your drum map like the second , simpler, line instead.

I’ll finish my example and upload it later.
When you try it yourself, probably best to work with Note Numbers as we’re doing CC# → Note#

8

@OPT
Here’s the basic idea as a preset:
OPT_drum_map.mhp (1.1 KB)

Notes

  1. Pipeline 1 is designed for testing development only

    By using MIDI IN (and Channel Remap), we can monitor the messages created alongside those that are used in the CC Table mappings
    Only incoming notes 36, 40 (C1, E1) ❖ have been set

  2. Pipeline 2 is the real deal with two CC Table pipes to cover your 11 (CC → ) Notes

    Only incoming notes 36, 40 (C1, E1) and 68, 72 (G#3, C4) ❖ have been set for CC Table 1 & CC Table 2, respectively

  3. ❖ I have used Middle C = C3 for my numbers. Yours may be one of the other Note Value Display types.

  4. You will see that the Note Offs are shown as Note On, velocity = 0. If your receiving device needs a Note Off, an extra Transform can handle this.

  5. Slightly more tricky is when your input device sends Note Off with non-zero velocity. Let me know if you need to get around this.

1 Like