Request new Mozaic Scripts HERE

Gavinski · June 2025

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

Gavinski · June 2025

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

I just checked with a midi monitor and after making that change, it is now sending out 12 different CC messages.

I should mention a couple of other things - I actually need something that won’t require double taps, as I need to work very fast, sending rapid messages at very precise times. Think of drumming - you wouldn’t want to double tap to get a single hit at a particular time! Also, the ideal for me would be if I could use a button on a hardware controller to trigger the randomise action in Mozaic. Is Drambo a better candidate then? If so, how would one go about this?

wim · June 2025

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

You have to "upload" the script after making the change. Then save it if it's working as it should.

Gavinski · June 2025

@wim said:

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

You have to "upload" the script after making the change. Then save it if it's working as it should.

Ah OK thnx

Gavinski · June 2025

@Gavinski said:

@wim said:

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

You have to "upload" the script after making the change. Then save it if it's working as it should.

Ah OK thnx

Yep, looks like that worked. Do you know if there is a way for me to map a button on a hardware controller to trigger the double tap on the Randomize knob by any chance?

wim · June 2025

@Gavinski said:

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

I just checked with a midi monitor and after making that change, it is now sending out 12 different CC messages.

I should mention a couple of other things - I actually need something that won’t require double taps, as I need to work very fast, sending rapid messages at very precise times. Think of drumming - you wouldn’t want to double tap to get a single hit at a particular time! Also, the ideal for me would be if I could use a button on a hardware controller to trigger the randomise action in Mozaic. Is Drambo a better candidate then? If so, how would one go about this?

As mentioned in the help of the script ...

Double-Tap the randomize knob to set random values for the 16 listed cc’s. You can also turn the knob past mid-way, or map a cc to the AU parameter and send 64 or higher to it. The Strength knob alters how far the cc’s move on randomization.

You can trigger it from a midi controller by sending to the knob 1 knob 0 AU parameter.

It wouldn't take long at all to cobble together a stripped down version of this script. I would consider doing that, but not tonight as it's time to hit the hay.

I'm not saying Drambo is a better candidate, but it would avoid coding. I was under the impression you were pretty well versed with Drambo. Maybe I'm misremembering.

I'm sure there are way better ways to do it than what I quickly tired, but something simple like this, with the button midi mapped to a controller?

wim · June 2025

@Gavinski said:

@Gavinski said:

@wim said:

@Gavinski said:

@Gavinski said:

@wim said:
@gavinski, It may work to change just one line of that script to limit it to one CC.
Near the bottom of the script, find ccendknob = 21 and change it to ccendknob = 6.

Great Wim, I’ll try that, thnx!

I did that Wim, then pressed Save, but the UI still looks the same.

You have to "upload" the script after making the change. Then save it if it's working as it should.

Ah OK thnx

Yep, looks like that worked. Do you know if there is a way for me to map a button on a hardware controller to trigger the double tap on the Randomize knob by any chance?

The double-tap isn't required. That's just a mozaic shortcut to setting knobs to the middle position. The knob just needs to be turned to 64 or greater. Each knob has an AU parameter. So all you need to do is trigger a value greater than 64 to the knob 0 AU parameter. (Sorry for the typo in my earlier post).

wim · June 2025

Good luck @Gavinski. I'll check back in the morning to see if you still need a custom script.

Gavinski · June 2025

Thanks so much Wim, I’ll check that out. I did read that line in the script help, btw, but I maybe read it too quickly as I didn’t entirely get what you were saying, but I understand now. Re Drambo, no, I have only the tiniest familiarity with it, have almost never used it

@wim said:
Good luck @Gavinski. I'll check back in the morning to see if you still need a custom script.

wim · June 2025

Hi @Gavinski - I was in the mood for some coding, so I made a streamlined single random cc value trigger script. No worries if you don't make use of it - I just did it for the heck of it.

https://patchstorage.com/one-shot-random-cc-trigger/

Gavinski · June 2025

Thanks > @wim said:

Hi @Gavinski - I was in the mood for some coding, so I made a streamlined single random cc value trigger script. No worries if you don't make use of it - I just did it for the heck of it.

https://patchstorage.com/one-shot-random-cc-trigger/

Thnx Wim, I'm already using the other one in a project I'm working on, invaluable really, it solved a problem I couldn't have solved otherwise. I'll download this too for future use, thnx!

Gavinski · February 2

Is there a Mozaic script which will do this?:

I’d like to press a button on an external MIDI controller, routed through Mozaic, and have Mozaic send a random Program Change to an AUv3 synth in AUM each time the button is pressed. The script would need a way to set a minimum and maximum PC range.

Might also be useful if there's an option to use a note message (either a single defined note, or just any note) as the input trigger for Mozaic.

Also ideal if there was an option to just do all this inside Mozaic itself with a button press, without need for an external controller.

hes · February 2

@Gavinski said:
Is there a Mozaic script which will do this?:

I’d like to press a button on an external MIDI controller, routed through Mozaic, and have Mozaic send a random Program Change to an AUv3 synth in AUM each time the button is pressed. The script would need a way to set a minimum and maximum PC range.

Might also be useful if there's an option to use a note message (either a single defined note, or just any note) as the input trigger for Mozaic.

Also ideal if there was an option to just do all this inside Mozaic itself with a button press, without need for an external controller.

I was fooling around tonight checking out how good ChatGPT is at programming Mozaic, and it turns out to be really quite good, I think. Here's a script that took just a few minutes to create and test, exactly as it came from ChatGPT, with no edits. It seems to work fine for pressing a pad to create a random PC message. I didn't test it for the external note trigger, but I did ask it to put that logic in there. Read the code, especially header at the beginning that gives a little more context. It could use refining, but if this is close to what you want let me know what needs to be changed.

// ------------------------------------------------------------
// Random Program Change Sender
//
// Layout 2: Pads + Knobs
// Pad 0: Send random Program Change now
//
// Knob 0: Min PC (0..127)
// Knob 1: Max PC (0..127)
// Knob 2: Out Channel (1..16)  (set to 0 = use incoming channel)
// Knob 3: Note Trigger Mode
//         0 = Off
//         1 = Any Note triggers
//         2 = Specific Note triggers
//
// Pad 1 (optional): Learn Note (sets the specific trigger note)
// ------------------------------------------------------------

@UpdateUI
  ShowLayout 2
  LabelPads {Rand PC}

  LabelKnob 0, {Min }, minPC
  LabelKnob 1, {Max }, maxPC

  if outCh = 0
    LabelKnob 2, {Ch }, {In}
  else
    LabelKnob 2, {Ch }, outCh
  endif

  if trigMode = 0
    LabelKnob 3, {Trig }, {Off}
  elseif trigMode = 1
    LabelKnob 3, {Trig }, {Any}
  else
    LabelKnob 3, {Trig }, {Note}, trigNote
  endif

  LabelPad 0, {Random PC}
  LabelPad 1, {Learn Note}
@END

@ClampRange
  if minPC < 0
    minPC = 0
  endif
  if minPC > 127
    minPC = 127
  endif

  if maxPC < 0
    maxPC = 0
  endif
  if maxPC > 127
    maxPC = 127
  endif

  if maxPC < minPC
    t = minPC
    minPC = maxPC
    maxPC = t
  endif
@END

@SendRandomPC
  Call @ClampRange

  // If range is a single value, always send that
  if maxPC = minPC
    pc = minPC
  else
    pc = Random minPC, maxPC
  endif

  // Choose channel: outCh=0 means use MIDIChannel (from last incoming event)
  ch = outCh
  if ch = 0
    ch = MIDIChannel
  endif

  // If still 0 (e.g. pad press with no prior MIDI), default to channel 1
  if ch < 1
    ch = 1
  endif

  // Send Program Change
  SendMIDIProgramChange ch, pc

  // Update status (reuse pad 0 label to show last PC)
  LabelPad 0, {PC }, pc
@END

@OnLoad
  // Init (one per line)
  minPC = 0
  maxPC = 127
  outCh = 1        // 1..16, or 0 = use incoming channel
  trigMode = 0     // 0 off, 1 any, 2 specific
  trigNote = 60    // default C4
  learnArmed = 0

  ShowLayout 2
  Call @UpdateUI
@End

@OnKnobChange
  if LastKnob = 0
    minPC = (((GetKnobValue 0)) * 127) / 127
  elseif LastKnob = 1
    maxPC = (((GetKnobValue 1)) * 127) / 127
  elseif LastKnob = 2
    // 0..127 -> 0..16
    outCh = (((GetKnobValue 2)) * 16) / 127
  elseif LastKnob = 3
    // 0..127 -> 0..2
    trigMode = (((GetKnobValue 3)) * 2) / 127
  endif

  Call @ClampRange
  Call @UpdateUI
@End

@OnPadDown
  if LastPad = 0
    Call @SendRandomPC
  elseif LastPad = 1
    learnArmed = 1
    LabelPad 1, {Play note...}
  endif
@End

@OnMidiNoteOn
  // Learn mode: set trigger note from first received note
  if learnArmed = 1
    trigNote = MIDINote
    learnArmed = 0
    Call @UpdateUI
    Exit
  endif

  // Optional note-trigger behavior
  if trigMode = 1
    // Any note triggers
    Call @SendRandomPC
  elseif trigMode = 2
    // Only specific note triggers
    if MIDINote = trigNote
      Call @SendRandomPC
    endif
  endif

  // Pass notes through unchanged
  SendMIDIThru
@End

@OnMidiNoteOff
  SendMIDIThru
@End

@OnMidiInput
  // Pass everything else through
  if MIDICommand <> 0x90 and MIDICommand <> 0x80
    SendMIDIThru
  endif
@End

@Description
Press "Random PC" pad to send a random Program Change.
Set Min/Max PC with knobs.
Optionally trigger by notes: Off / Any / Specific (learn).
@End

In case anyone's interested, here's the exact prompt that generated the script above. I was already in a session where I had asked it to review the Mozaic documentation and projects on Patchstorage, and I was having it help me with a different utility. Part of the prompt is literally copied from the post above where @Gavinski asked his question:

Okay, switch gears.  This is a different utility, quite a simple one.  Here's description of what I want:

I’d like to press a pad in Mozaic and have Mozaic send a random Program Change each time the 
button is pressed. The script would need a way to set a minimum and maximum PC range, 
which could perhaps be knobs on the pad layout.

Might also be useful if there's an option to use a note message (either a single 
defined note, or just any note) as the input trigger for Mozaic, in addition to me pushing a pad.

Gavinski · February 2

@hes, nice one, that mostly works hehe. Pressing for a random PC messages works, and I was able to get it to learn which note would trigger a random PC message being sent. The UI is not set up to let me use any note input to trigger a random PC message. But then I realised I can just map any note or button to Mozaic Pad 1 using AUM’s midi mapping. Cheers!

Gavinski · February 2

@Gavinski said:
@hes, nice one, that mostly works hehe. Pressing for a random PC messages works, and I was able to get it to learn which note would trigger a random PC message being sent. The UI is not set up to let me use any note input to trigger a random PC message. But then I realised I can just map any note or button to Mozaic Pad 1 using AUM’s midi mapping. Cheers!

But actually, it would still be useful to have something in the UI allowing any note to trigger a PC change - as I can’t set that up in AUM’s system, I would always need to define a specific note.

Also, btw, all the knob are displaying decimal values too when changed, would be better if they didn’t

Gavinski · February 2

@hes I tried to get ChatGPT to fix it but it didn’t do it right, Claude came through though, here is a slightly improved version with a third pad added and no decimals (edited this to fix a problem where it wa sending on wrong channel)

// ------------------------------------------------------------
// Random Program Change Sender
//
// Layout 2: Pads + Knobs
// Pad 0: Send random Program Change now
// Pad 1: Learn Note (sets the specific trigger note)
// Pad 2: Toggle Note Trigger Mode (Off/Any/Specific)
//
// Knob 0: Min PC (0..127)
// Knob 1: Max PC (0..127)
// Knob 2: Out Channel (In/1..16)
// Knob 3: Note Trigger Mode
//         0 = Off
//         1 = Any Note triggers
//         2 = Specific Note triggers
// ------------------------------------------------------------

@UpdateUI
  ShowLayout 2
  LabelPads {Rand PC}

  LabelKnob 0, {Min }, minPC
  LabelKnob 1, {Max }, maxPC

  if outCh = 0
    LabelKnob 2, {Ch }, {In}
  else
    LabelKnob 2, {Ch }, outCh
  endif

  if trigMode = 0
    LabelKnob 3, {Trig }, {Off}
  elseif trigMode = 1
    LabelKnob 3, {Trig }, {Any}
  else
    LabelKnob 3, {Trig }, {Note}, trigNote
  endif

  LabelPad 0, {Random PC}
  LabelPad 1, {Learn Note}
  
  // Pad 2 shows current trigger mode
  if trigMode = 0
    LabelPad 2, {Trig: OFF}
  elseif trigMode = 1
    LabelPad 2, {Trig: ANY}
  else
    LabelPad 2, {Trig: N}, trigNote
  endif
  
  // Set knob ranges to show integer values
  SetKnobValue 0, minPC
  SetKnobValue 1, maxPC
  SetKnobValue 2, outCh
  SetKnobValue 3, trigMode
@END

@ClampRange
  if minPC < 0
    minPC = 0
  endif
  if minPC > 127
    minPC = 127
  endif

  if maxPC < 0
    maxPC = 0
  endif
  if maxPC > 127
    maxPC = 127
  endif

  if maxPC < minPC
    t = minPC
    minPC = maxPC
    maxPC = t
  endif
@END

@SendRandomPC
  Call @ClampRange

  // If range is a single value, always send that
  if maxPC = minPC
    pc = minPC
  else
    pc = Random minPC, maxPC
  endif

  // Choose channel: outCh=0 means use incoming MIDIChannel
  ch = outCh
  if ch = 0
    // Use the channel from last incoming MIDI event
    // MIDIChannel returns 0-15
    ch = MIDIChannel + 1  // Convert to 1-16 for display
  endif

  // If still 0 (e.g. pad press with no prior MIDI), default to channel 1
  if ch < 1
    ch = 1
  endif

  // Send Program Change
  // SendMIDIProgramChange expects 0-15, so subtract 1 from our 1-16 value
  SendMIDIProgramChange ch - 1, pc

  // Update status (reuse pad 0 label to show last PC)
  LabelPad 0, {PC }, pc
@END

@OnLoad
  // Init (one per line)
  minPC = 0
  maxPC = 127
  outCh = 1        // 0 = use incoming channel, 1..16 = fixed channel
  trigMode = 0     // 0 off, 1 any, 2 specific
  trigNote = 60    // default C4
  learnArmed = 0

  ShowLayout 2
  Call @UpdateUI
@End

@OnKnobChange
  if LastKnob = 0
    minPC = Round ((GetKnobValue 0) * 127) / 127
  elseif LastKnob = 1
    maxPC = Round ((GetKnobValue 1) * 127) / 127
  elseif LastKnob = 2
    // Knob value 0..127 maps to outCh 0..16
    // 0-7 = 0 (In), 8-15 = 1, 16-23 = 2, etc.
    knobVal = GetKnobValue 2
    if knobVal < 8
      outCh = 0
    else
      outCh = Round ((knobVal - 8) * 15) / 119 + 1
    endif
  elseif LastKnob = 3
    // 0..127 -> 0..2
    trigMode = Round ((GetKnobValue 3) * 2) / 127
  endif

  Call @ClampRange
  Call @UpdateUI
@End

@OnPadDown
  if LastPad = 0
    Call @SendRandomPC
  elseif LastPad = 1
    learnArmed = 1
    LabelPad 1, {Play note...}
  elseif LastPad = 2
    // Cycle through trigger modes: Off -> Any -> Specific -> Off
    trigMode = trigMode + 1
    if trigMode > 2
      trigMode = 0
    endif
    Call @UpdateUI
  endif
@End

@OnMidiNoteOn
  // Learn mode: set trigger note from first received note
  if learnArmed = 1
    trigNote = MIDINote
    learnArmed = 0
    Call @UpdateUI
    Exit
  endif

  // Optional note-trigger behavior
  if trigMode = 1
    // Any note triggers
    Call @SendRandomPC
  elseif trigMode = 2
    // Only specific note triggers
    if MIDINote = trigNote
      Call @SendRandomPC
    endif
  endif

  // Pass notes through unchanged
  SendMIDIThru
@End

@OnMidiNoteOff
  SendMIDIThru
@End

@OnMidiInput
  // Pass everything else through
  if MIDICommand <> 0x90 and MIDICommand <> 0x80
    SendMIDIThru
  endif
@End

@Description
Press "Random PC" pad to send a random Program Change.
Set Min/Max PC with knobs.
Pad 2 cycles note trigger: Off / Any / Specific (learn via Pad 1).
Channel: In uses incoming MIDI channel, or set fixed 1-16.
@End

hes · February 2

@Gavinski said:

@Gavinski said:
@hes, nice one, that mostly works hehe. Pressing for a random PC messages works, and I was able to get it to learn which note would trigger a random PC message being sent. The UI is not set up to let me use any note input to trigger a random PC message. But then I realised I can just map any note or button to Mozaic Pad 1 using AUM’s midi mapping. Cheers!

But actually, it would still be useful to have something in the UI allowing any note to trigger a PC change - as I can’t set that up in AUM’s system, I would always need to define a specific note.

Also, btw, all the knob are displaying decimal values too when changed, would be better if they didn’t

As I said, I haven't tested, but for allowing any note to trigger the PC message you should just set up Mozaic in AUM's usual routing matrix to have an external keyboard (or, actually, just anything, internal or external, that sends notes) as input. Just regular input to Mozaic. You don't go through AUM's AUv3 control system, which seems like what you must be doing if you're using external midi to trigger Pad 1. Then you make sure Knob 3 is set to 1:

// Knob 3: Note Trigger Mode
// 0 = Off
// 1 = Any Note triggers
// 2 = Specific Note triggers

The knob labels can be easily changed using the Round (or RoundDown) function.

Gavinski · February 2

@hes said:

@Gavinski said:

@Gavinski said:
@hes, nice one, that mostly works hehe. Pressing for a random PC messages works, and I was able to get it to learn which note would trigger a random PC message being sent. The UI is not set up to let me use any note input to trigger a random PC message. But then I realised I can just map any note or button to Mozaic Pad 1 using AUM’s midi mapping. Cheers!

But actually, it would still be useful to have something in the UI allowing any note to trigger a PC change - as I can’t set that up in AUM’s system, I would always need to define a specific note.

Also, btw, all the knob are displaying decimal values too when changed, would be better if they didn’t

As I said, I haven't tested, but for allowing any note to trigger the PC message you should just set up Mozaic in AUM's usual routing matrix to have an external keyboard as input. Just regular input to Mozaic. You don't go through AUM's AUv3 control system, which seems like what you must be doing if you're using external midi to trigger Pad 1. Then you make sure Knob 3 is set to 1:

// Knob 3: Note Trigger Mode
// 0 = Off
// 1 = Any Note triggers
// 2 = Specific Note triggers

The knob labels can be easily changed using the Round (or RoundDown) function.

Ah ok, see my last post though, that version is working fine, must have missed the knob functionality you mention, but the revamped script is clear and is working, thnx again

Gavinski · February 2

edited this to fix a problem where it wa sending on wrong channel

@Gavinski said:
@hes I tried to get ChatGPT to fix it but it didn’t do it right, Claude came through though, here is a slightly improved version with a third pad added and no decimals (edited this to fix a problem where it wa sending on wrong channel)

// ------------------------------------------------------------
// Random Program Change Sender
//
// Layout 2: Pads + Knobs
// Pad 0: Send random Program Change now
// Pad 1: Learn Note (sets the specific trigger note)
// Pad 2: Toggle Note Trigger Mode (Off/Any/Specific)
//
// Knob 0: Min PC (0..127)
// Knob 1: Max PC (0..127)
// Knob 2: Out Channel (In/1..16)
// Knob 3: Note Trigger Mode
//         0 = Off
//         1 = Any Note triggers
//         2 = Specific Note triggers
// ------------------------------------------------------------

@UpdateUI
  ShowLayout 2
  LabelPads {Rand PC}

  LabelKnob 0, {Min }, minPC
  LabelKnob 1, {Max }, maxPC

  if outCh = 0
    LabelKnob 2, {Ch }, {In}
  else
    LabelKnob 2, {Ch }, outCh
  endif

  if trigMode = 0
    LabelKnob 3, {Trig }, {Off}
  elseif trigMode = 1
    LabelKnob 3, {Trig }, {Any}
  else
    LabelKnob 3, {Trig }, {Note}, trigNote
  endif

  LabelPad 0, {Random PC}
  LabelPad 1, {Learn Note}
  
  // Pad 2 shows current trigger mode
  if trigMode = 0
    LabelPad 2, {Trig: OFF}
  elseif trigMode = 1
    LabelPad 2, {Trig: ANY}
  else
    LabelPad 2, {Trig: N}, trigNote
  endif
  
  // Set knob ranges to show integer values
  SetKnobValue 0, minPC
  SetKnobValue 1, maxPC
  SetKnobValue 2, outCh
  SetKnobValue 3, trigMode
@END

@ClampRange
  if minPC < 0
    minPC = 0
  endif
  if minPC > 127
    minPC = 127
  endif

  if maxPC < 0
    maxPC = 0
  endif
  if maxPC > 127
    maxPC = 127
  endif

  if maxPC < minPC
    t = minPC
    minPC = maxPC
    maxPC = t
  endif
@END

@SendRandomPC
  Call @ClampRange

  // If range is a single value, always send that
  if maxPC = minPC
    pc = minPC
  else
    pc = Random minPC, maxPC
  endif

  // Choose channel: outCh=0 means use incoming MIDIChannel
  ch = outCh
  if ch = 0
    // Use the channel from last incoming MIDI event
    // MIDIChannel returns 0-15
    ch = MIDIChannel + 1  // Convert to 1-16 for display
  endif

  // If still 0 (e.g. pad press with no prior MIDI), default to channel 1
  if ch < 1
    ch = 1
  endif

  // Send Program Change
  // SendMIDIProgramChange expects 0-15, so subtract 1 from our 1-16 value
  SendMIDIProgramChange ch - 1, pc

  // Update status (reuse pad 0 label to show last PC)
  LabelPad 0, {PC }, pc
@END

@OnLoad
  // Init (one per line)
  minPC = 0
  maxPC = 127
  outCh = 1        // 0 = use incoming channel, 1..16 = fixed channel
  trigMode = 0     // 0 off, 1 any, 2 specific
  trigNote = 60    // default C4
  learnArmed = 0

  ShowLayout 2
  Call @UpdateUI
@End

@OnKnobChange
  if LastKnob = 0
    minPC = Round ((GetKnobValue 0) * 127) / 127
  elseif LastKnob = 1
    maxPC = Round ((GetKnobValue 1) * 127) / 127
  elseif LastKnob = 2
    // Knob value 0..127 maps to outCh 0..16
    // 0-7 = 0 (In), 8-15 = 1, 16-23 = 2, etc.
    knobVal = GetKnobValue 2
    if knobVal < 8
      outCh = 0
    else
      outCh = Round ((knobVal - 8) * 15) / 119 + 1
    endif
  elseif LastKnob = 3
    // 0..127 -> 0..2
    trigMode = Round ((GetKnobValue 3) * 2) / 127
  endif

  Call @ClampRange
  Call @UpdateUI
@End

@OnPadDown
  if LastPad = 0
    Call @SendRandomPC
  elseif LastPad = 1
    learnArmed = 1
    LabelPad 1, {Play note...}
  elseif LastPad = 2
    // Cycle through trigger modes: Off -> Any -> Specific -> Off
    trigMode = trigMode + 1
    if trigMode > 2
      trigMode = 0
    endif
    Call @UpdateUI
  endif
@End

@OnMidiNoteOn
  // Learn mode: set trigger note from first received note
  if learnArmed = 1
    trigNote = MIDINote
    learnArmed = 0
    Call @UpdateUI
    Exit
  endif

  // Optional note-trigger behavior
  if trigMode = 1
    // Any note triggers
    Call @SendRandomPC
  elseif trigMode = 2
    // Only specific note triggers
    if MIDINote = trigNote
      Call @SendRandomPC
    endif
  endif

  // Pass notes through unchanged
  SendMIDIThru
@End

@OnMidiNoteOff
  SendMIDIThru
@End

@OnMidiInput
  // Pass everything else through
  if MIDICommand <> 0x90 and MIDICommand <> 0x80
    SendMIDIThru
  endif
@End

@Description
Press "Random PC" pad to send a random Program Change.
Set Min/Max PC with knobs.
Pad 2 cycles note trigger: Off / Any / Specific (learn via Pad 1).
Channel: In uses incoming MIDI channel, or set fixed 1-16.
@End

hes · February 2

@Gavinski said:

@hes said:

@Gavinski said:

@Gavinski said:
@hes, nice one, that mostly works hehe. Pressing for a random PC messages works, and I was able to get it to learn which note would trigger a random PC message being sent. The UI is not set up to let me use any note input to trigger a random PC message. But then I realised I can just map any note or button to Mozaic Pad 1 using AUM’s midi mapping. Cheers!

But actually, it would still be useful to have something in the UI allowing any note to trigger a PC change - as I can’t set that up in AUM’s system, I would always need to define a specific note.

Also, btw, all the knob are displaying decimal values too when changed, would be better if they didn’t

As I said, I haven't tested, but for allowing any note to trigger the PC message you should just set up Mozaic in AUM's usual routing matrix to have an external keyboard as input. Just regular input to Mozaic. You don't go through AUM's AUv3 control system, which seems like what you must be doing if you're using external midi to trigger Pad 1. Then you make sure Knob 3 is set to 1:

// Knob 3: Note Trigger Mode
// 0 = Off
// 1 = Any Note triggers
// 2 = Specific Note triggers

The knob labels can be easily changed using the Round (or RoundDown) function.

Ah ok, see my last post though, that version is working fine, must have missed the knob functionality you mention, but the revamped script is clear and is working, thnx again

Cool, glad you got it working. Main takeaway for me is that AI has improved a lot at coding since last time I checked it out. Knowing how to actually program definitely helps in subtle ways when crafting prompts, and in helping the AI fix things when there are bugs or it's not working quite as you want it.

This kind of coding, using AI to write the code in response to user prompts, has gained the name of 'vibe coding'. There are varying degrees of it, in most extreme the user ends up with a program without having written or directly edited any of the code at all. I think that's what we did here. Although actual programming skill helps a lot, as I said in previous paragraph, I have read many stories of non-programmers persisting and through iteration getting what they want, even though they don't understand the code. (Whether this is generally a good thing is debatable. But whatever your take on that, in context of simple scripts like this with Mozaic, seems like a good thing to me.)

Gavinski · February 13

Anyone know what happened to the mfxPan app by Audeonic? Seems it is not available on the Appstore any more. Looks pretty interesting, and seems there is not (yet?😛) a Mozaic script on Patchstorage for this. This is the feature set:

Performance Responsive Auto Panner - incoming events will generate complementary pan controller messages (CC 10) on the same channel as the incoming notes. Pans can be triggered by note (velocity), aftertouch or controller events. Pans are triggered if the incoming trigger event is within a specified range and the depth of the pan can be proportional to the range set. There are different styles of pans and each can be given a maximum depth, cycle time and pre delay.
The plugin is divided into two sections; TRIGGER, where the pan trigger characteristics are set and PAN where the pan related parameters are set:
trigger (menu) - selects what type of event should trigger an auto pan.
range from/to (menus) - a lower and upper range can be set so that a pan will only happen if a trigger event is within the set range. The default of 1 to 127 indicates that a pan will happen with any trigger event (subject to the threshold value below).
threshold (slider) - the minimum trigger event value to start a pan cycle.
pan limit (menu) - normally, the pan will cycle to the depth specified (PAN section), but setting this to 'scaled' will scale the depth of the pan to the trigger value. Setting to scaled means that the higher the trigger value, the further the pan will move (and vice versa)
parallel pans (menu) - normally, mfxPan will only start a new pan when the current pan cycle has finished. Setting this value to 'yes' disables that restriction and multiple concurrent pan cycles are permitted. This creates very interesting pan effects as when playing multiple notes simultaneously, the pans will 'work against' each other and the pan will push and pull in unexpected directions.
pan (menu) - selects the direction of the pan. A variety of styles are available.
depth (slider) - this is the maximum depth of the pan. The higher the number (max 64) the further right or left the pan will extend to.
cycle time (slider) - this is the length of time that the complete pan will take from start to finish, in milliseconds. Low numbers will create fast pans and higher numbers will create long sweeps.
pre delay (slider) - adding a pre delay in milliseconds will delay the pan following a trigger.

Krupa · February 13

I tried Claude the other day on mosaic scripts, I’m pretty sure that post would be a solid prompt for it @Gavinski

Gavinski · February 14

@Krupa said:
I tried Claude the other day on mosaic scripts, I’m pretty sure that post would be a solid prompt for it @Gavinski

I gave it a few tries but didn’t get a working script out of it so gave up. Here’s a cleaner, tighter version of your request, based on the musically stronger “shift by scale degrees relative to the incoming note” approach:

Another Mozaic idea/request:

I love Rozeta Scaler, but a transpose slider isn’t always ideal. Imagine, instead, selecting a scale (preset or custom), and then having buttons representing the scale degrees rather than semitone offsets. For a diatonic scale, that would be seven degree buttons, plus two direction buttons: + and –

When a degree is selected, incoming MIDI notes would first be quantized to the chosen scale, then shifted up or down by that number of scale steps relative to each note. So “3” with “+” active would move each note up by two scale degrees. Selecting “1” would result in no transposition.

The advantage over a slider is that this would allow instant jumps to exact diatonic intervals without passing through out-of-scale notes. Great for live jamming.

I guess/know this is probably complicated, but wonder if anyone is up to the task (and the above one too haha!)

Edit: Also, rather than + or - buttons, just having rows of buttons similar to the way it is done in Fugue Machine Rubato, see below, is probably much better:

Krupa · February 14

@Gavinski ahh gutted, fingers crossed wimBOT is in the mood 😅

wim · February 14

@Krupa said:
@Gavinski ahh gutted, fingers crossed wimBOT is in the mood 😅

Ha ha! Not today.
Grandkid making sure I can't focus on anything for more than 20 seconds at a time, and wife who will surely beat me over the head with my iPad if I'm doing coding on Valentines day. 😂

Gavinski · April 8

Is there already a script that can do MIDI ratcheting on incoming notes? Or would any lovely soul here consider making one?

Ideally, the user could define a rate (1/16, triplets, dotted), with different buttons for different numbers of ratchets, and the ratchet would continue while a button is pressed, stopping at the next clock subdivision after the button is released.

It could maybe also have a simple burst mode, with a button press triggering a user-defined fixed number of repeats regardless of how long you hold it.

Would maybe be good to have some velocity controls with ramp up / down options.

Tried searching the Mozaic Patchstorage page for 'ratchets' but didn't get any relevant results. Thnx!

egobeats · April 8

@Gavinski said:
Is there already a script that can do MIDI ratcheting on incoming notes? Or would any lovely soul here consider making one?

This! This, This please.

Samu · April 8

@egobeats said:

@Gavinski said:
Is there already a script that can do MIDI ratcheting on incoming notes? Or would any lovely soul here consider making one?

This! This, This please.

Should be doable with any plug-in that provides Midi-Echo like Mela? (Ie. set the interval and number of repeats?!).

wim · April 8

@Gavinski said:
Is there already a script that can do MIDI ratcheting on incoming notes? Or would any lovely soul here consider making one?

Ideally, the user could define a rate (1/16, triplets, dotted), with different buttons for different numbers of ratchets, and the ratchet would continue while a button is pressed, stopping at the next clock subdivision after the button is released.

It could maybe also have a simple burst mode, with a button press triggering a user-defined fixed number of repeats regardless of how long you hold it.

Would maybe be good to have some velocity controls with ramp up / down options.

Tried searching the Mozaic Patchstorage page for 'ratchets' but didn't get any relevant results. Thnx!

What should happen if the incoming note ends but the button is still held down?
Should chords ratchet as well? If not, how should the script treat multiple notes?
How should ratcheting work when notes arrive off the beat?
Should ratcheting work when the host clock isn't running?
I don't understand the interplay of "with different buttons for different numbers of ratchets" and "the ratchet would continue while a button is pressed". What should happen if the set number of ratchets has played and the button is still held down?

(I'm not saying I would write such a script, but those questions would need to be answered no matter who wrote one.)

Gavinski · April 8

@wim thanks haha, I knew there must be many aspects I hadn’t considered. Tbh I don’t have strong opinions about the above, I guess wiser minds might have to decide what’s most desirable/feasible

Loopy Pro: Create music, your way.

Request new Mozaic Scripts HERE

Comments

Loopy Pro: Create music, your way.

Request new Mozaic Scripts *HERE*

Comments

Request new Mozaic Scripts HERE