Velocity sensitive widgets?

MeyanDR

Stumbling into the wonderful world of loopy pro, I bump into some challenges.

I want to midi map a boppad (midi controller) to 4 widgets, buttons.
This makes it easy to re-pitch midi when changing a song.
But the widgets (buttons) don't seem to pass velocity. Am I overlooking something, is there a workaround?

thanks

espiegel123

@MeyanDR said:
Stumbling into the wonderful world of loopy pro, I bump into some challenges.

I want to midi map a boppad (midi controller) to 4 widgets, buttons.
This makes it easy to re-pitch midi when changing a song.
But the widgets (buttons) don't seem to pass velocity. Am I overlooking something, is there a workaround?

thanks

Can you provide more details/specifics about what you are trying to do/accomplish?

What do the buttons do? What actions do they execute?

MeyanDR

Thanks for your response!
I work with drum triggers, each trigger I midi map to one button. This button sends out a midi note to moziac and then to Koala sampler. This way I can add midi effects on each different trigger and change sounds easily.
But I have the impression that the button widget is not velocity sensitive.

espiegel123

@MeyanDR said:
Thanks for your response!
I work with drum triggers, each trigger I midi map to one button. This button sends out a midi note to moziac and then to Koala sampler. This way I can add midi effects on each different trigger and change sounds easily.
But I have the impression that the button widget is not velocity sensitive.

It sounds like you should be sending the midi to your Mozaic script and the mozaic script sending to Koala. Mozaic’s output can also trigger midi bindings as needed.

MeyanDR

@espiegel123 said:

@MeyanDR said:
Thanks for your response!
I work with drum triggers, each trigger I midi map to one button. This button sends out a midi note to moziac and then to Koala sampler. This way I can add midi effects on each different trigger and change sounds easily.
But I have the impression that the button widget is not velocity sensitive.

It sounds like you should be sending the midi to your Mozaic script and the mozaic script sending to Koala. Mozaic’s output can also trigger midi bindings as needed.

Thanks for the help! i found a way to make it work!

MeyanDR

Just sharing this in case anyone faces the same problem in the future.

To control different pads of 1 midi controller separately.

1. for each pad you want to control, create one midi channel.
2. You isolate the midi note of each pad before sending it to Mozaic. (See picture 1)

3. You create a Mozaic channel for each midi note of your controller. (See photo 2)

4. Below you'll find the code I used to create a midi pitch object. (Thanks chatGPT)
5. You can save a preset for each note, which you can select afterwards in the "steps" widget.
6. You can send each Mozaic channel to one or several samplers or synths.

This allows you to change setup easily and quickly. Or on e.g. adding round robin on one path while keeping everything else the same.

Anyway, there are other ways, but this works for me!
Hopefully now we are a little closer to an ideal world.

MeyanDR

@OnLoad
   transposeAmount = 0 // Default transpose amount (in semitones)
   LabelKnob 0, {Transpose} // Label the knob
   SetKnobValue 0, 64 // Center knob at 64 (no transposition)
@End

@OnKnobChange
   if LastKnob = 0
      // Manually scale the knob value (0–127) to transpose range (-12 to +12 semitones)
      transposeAmount = (GetKnobValue(0) - 64) / 5 // Adjust scale as needed
      Log {Transpose set to: }, transposeAmount
   endif
@End

@OnMidiInput
   if MIDICommand = 144 or MIDICommand = 128 // Note On or Note Off
      transposedNote = MIDINote + transposeAmount

      // Ensure the note stays within MIDI range (0–127)
      if transposedNote >= 0 and transposedNote <= 127
         SendMIDIOut MIDICommand, transposedNote, MIDIVelocity
      endif
   else
      // Pass other MIDI messages through
      SendMIDIThru
   endif
@End