Request new Mozaic Scripts *HERE*

wim

In Cubasis, tap the List Browse button to get to presets. You can save under User Presets there.

raabje

@wim said:
In Cubasis, tap the List Browse button to get to presets. You can save under User Presets there.

I see list/browse but the plugin doesn't allow me to save the current setting...? I use IOS 16.4. But it is ok, I will find a work around for this.

wim

@raabje said:

@wim said:
In Cubasis, tap the List Browse button to get to presets. You can save under User Presets there.

I see list/browse but the plugin doesn't allow me to save the current setting...? I use IOS 16.4. But it is ok, I will find a work around for this.

I know it works. You're trying to save in the user Folder, not in the Factory folder, right?

raabje

@wim said:
I know it works. You're trying to save in the user Folder, not in the Factory folder, right?

Yes, that is the trick. Problem solved, thanks!

Gavinski

Is there a script to convert CC values to note values? My thought was to use a cc looper like Ribn sending out midi loops to instruments, perhaps put through something like Rozeta Scaler to quantize them. Looked on Patchstorage using search term ‘convert’ and didn’t find one. Cheers!

McD

@Gavinski said:
Is there a script to convert CC values to note values? My thought was to use a cc looper like Ribn sending out midi loops to instruments, perhaps put through something like Rozeta Scaler to quantize them. Looked on Patchstorage using search term ‘convert’ and didn’t find one. Cheers!

I couldn’t find a script either so I started investigating the idea. We can add more features but this
Script takes the CC value and uses it in a MIDI Note output as the requested notes.

@OnLoad

@End

@OnMIDICC

  // MIDIByte1 will hold the Channel + “B0” (176 decimal)
  Log MIDIByte1  
  // MIDIByte 2 holds the CC Number
  Log MIDIByte2
  // MIDIByte3 holds the CC Value which I’m assuming should be mapped to a Note Number
  Log MIDIByte3
  Log {  }



  // Channel “0” which AUM calls 1, MIDIBYTE3 from the incoming CC as a “Note”   
  // and “80” as an arbitrary volume/velocity setting.
  SendMIDINoteOn 0, MIDIByte3, 80
  // We also need to turn these notes OFF. The final “100” is the number of milliseconds
  // to wait before sending out the OFF command. Again arbitrary.
  SendMIDINoteOff 0, MIDIByte3, 0, 100

  // Arbitrary choices can be assigned to knob controls.
  // Notes can be sent based upon selectable scales with arbitrary “Root” options.

@End

This is all you really need to start… just copy it into the Moziac code screen and plumb up a CC source for testing and a Synth target. I used Rozeta LFO (turning off 2 of the 3 LFO’s)
And Pure Piano.

@OnMIDICC
  SendMIDINoteOn 0, MIDIByte3, 80
  SendMIDINoteOff 0, MIDIByte3, 0, 100    
@End

wim

Probably not exactly what you're looking for but might be interesting to take a look at.
https://patchstorage.com/cc-trigger-to-notes/

wim

BTW, there are some really good examples in the manual for using the internal LFOs to play notes.

McD

The first thing you will notice is that Ribn as a CC generator sends a torrent of “notes” so some way of filtering out notes is a nice enhancement:

@OnLoad

  LastTime = SystemTime 
  NoteTime = 100

@End

@OnMIDICC

  ThisTime = SystemTime

  if (ThisTime - LastTime) > NoteTime
    SendMIDINoteOn 0, MIDIByte3, 80
    SendMIDINoteOff 0, MIDIByte3, 0, NoteTime
    LastTime = ThisTime
  endif

@End

Larger values for NoteTime can slow down the stream even more and sustain notes too since it also determines the time to a NoteOff event. Mozaic times the delay of sending Note Off for us.

NoteTime is a good candidate for adding a Knob controller.

This was made from 3 instances of the script with 3 cc sources and different NoteTime settings:

McD

It occurred to me that the “number of notes per second” (density) should be distinct from the “length of each note” so I added the extra variable to allow for this level of control:

@OnLoad

  LastTime = SystemTime
  Density = 500
  NoteTime = 50

@End

@OnMIDICC

  ThisTime = SystemTime

  if (ThisTime - LastTime) > Density
    SendMIDINoteOn 0, MIDIByte3, 80
    SendMIDINoteOff 0, MIDIByte3, 0, NoteTime
    LastTime = ThisTime
  endif

@End

And made a demo of using 3 instances again with the lovely Mersenne into Velvet Machine to get an awesome pad for the really long note lengths with low density:

McD

I added 4 Knobs to control:

Density of Notes
Length of Notes
Volume of Notes
Probability Note will Play

@OnLoad

  LastTime = SystemTime
  Density = 100
  DensityLabel = round(Density/5000 * 100)
  LabelKnob 0, {Dens=}, 100-DensityLabel,{%}
  NoteTime = 50
  Volume = 100
  Probability = 100
  SetKnobValue 0, round(Density/5000 * 127)
  SetKnobValue 1, round((50/5000)*127)  
  SetKnobValue 2, Volume
  SetKnobValue 3, Probability/100 * 127
  LabelKnob 1, {Len=}, NoteTime
  LabelKnob 2, {Vol=}, Volume
  LabelKnob 3, {Prob=}, Probability, {%}
@End

@OnMIDICC

  ThisTime = SystemTime

  if (ThisTime - LastTime) > Density  
    Chance = Random 1,100
    if Chance < Probability
      Log Chance
      SendMIDINoteOn 0, MIDIByte3, Volume
      SendMIDINoteOff 0, MIDIByte3, 0, NoteTime
    endif
    LastTime = ThisTime
  endif

@End


@OnKnobChange

  if LastKnob = 0
    knob = GetKnobValue 0
    Density = round (TranslateScale knob, 0, 127, 10, 5000)
    Log Density
    DensityLabel = round(Density/5000 * 100)
    LabelKnob 0, {Dens=}, 100-DensityLabel,{%}
  elseif LastKnob = 1
    knob = GetKnobValue 1
    NoteTime = round (TranslateScale knob, 0, 127, 10, 5000)
    LabelKnob 1, {Len=}, NoteTime
  elseif LastKnob = 2
    Volume = round(GetKnobValue 2)
    LabelKnob 2, {Vol=}, Volume
  elseif LastKnob = 3
    knob = GetKnobValue 3
    Probability = round (TranslateScale knob, 0, 127, 1, 100)
    LabelKnob 3, {Prob=}, Probability, {%}
  endif

@End 

And made a demo using 4 instances:

I posted the script in this form on patchstorage:

https://patchstorage.com/cc-composer-v1-0/

wim

I checked patch storage but didn't find anything. Has anyone created a Logic Pro thread generator in Mozaic yet? Is this something that Mozaic is capable of?

jjpl2001

Hello. Playing both strings and piano simultaneously can be challenging. When you play a note more than once, the strings plugin triggers additional string sounds, gradually increasing the volume. If you play fast repeated chords on the piano alongside the strings plugin, the volume of the strings keeps increasing to an unreasonable level.

What I want is to prevent note retriggering while the sustain pedal is held down. The pedal should be able to sustain any new played notes but shouldn't allow to retrigger the sustained notes again until the sustain pedal is released.

I came across a sostenuto code on patchstorage that converts the sustain pedal into a sostenuto pedal. However, there's a problem with it. It only sustains the notes that were held down when the pedal is pressed. If you play any new notes, they won't be sustained. (That is how a sustenuto pedal should work, but is not what I need)

You can check out the original sostenuto in the following link to get an idea of how it works:
https://patchstorage.com/sostenuto/

wim

@jjpl2001 - I'll take a look at this but I'm only going to communicate here.

Your multiple posts in different threads are very counter-productive. Can you delete those duplicate posts and/or refer them here?

jjpl2001

@wim said:
@jjpl2001 - I'll take a look at this but I'm only going to communicate here.

Your multiple posts in different threads are very counter-productive. Can you delete those duplicate posts and/or refer them here?

Sure, im on that, I though different people were looking at them, so sorry for that

wim

@jjpl2001 said:

@wim said:
@jjpl2001 - I'll take a look at this but I'm only going to communicate here.

Your multiple posts in different threads are very counter-productive. Can you delete those duplicate posts and/or refer them here?

Sure, im on that, I though different people were looking at them, so sorry for that

No problem. You didn't get a response to the request in the one thread and were trying to get attention for it. I get that.

wim

@jjpl2001 said:
Hello. Playing both strings and piano simultaneously can be challenging. When you play a note more than once, the strings plugin triggers additional string sounds, gradually increasing the volume. If you play fast repeated chords on the piano alongside the strings plugin, the volume of the strings keeps increasing to an unreasonable level.

What I want is to prevent note retriggering while the sustain pedal is held down. The pedal should be able to sustain any new played notes but shouldn't allow to retrigger the sustained notes again until the sustain pedal is released.

I came across a sostenuto code on patchstorage that converts the sustain pedal into a sostenuto pedal. However, there's a problem with it. It only sustains the notes that were held down when the pedal is pressed. If you play any new notes, they won't be sustained. (That is how a sustenuto pedal should work, but is not what I need)

You can check out the original sostenuto in the following link to get an idea of how it works:
https://patchstorage.com/sostenuto/

Hiya @jjpl2001. Here's something for you to try out. If it works as you think it should I'll polish it up and post it on patch storage as it seems like a useful tool. If it doesn't then let me know what to fix or change.

BTW, any ideas what to call this?

@Description
MODIFIED SOSTENUTO v0.1
Sustain new notes but do not retrigger notes when the sustain pedal is down.

Any notes held down when sustain "on" is received remain on until the sustain "off" is received. If a note being sustained is played again it will not be retriggered, but new notes will trigger and be sustained as well. On sustain "off" notes being held by the script will be released, with the exception of notes still being held down.

Example: Press sustain while holding down notes C and D. Now release C and D. The notes will continue to play. If you press C or D again they will not be triggered. Now press note E (still holding sustain down) - it will be triggered and sustained. Continue to hold E and release sustain. C and D will stop sustaining, but E will continue to sound until it is released.

Script idea credit: Audiobus forum member @jjpl2001
@End

@OnLoad
  _sustainCC = 64
  sustain = NO
  noteIndex = -1
  FillArray notes,-1
  ResetNoteStates NO
@End

@OnMidiCC
  if MIDIByte2 <> _sustainCC
    SendMIDIThru
  else
    if MIDIByte3 = 0
      sustain = NO
      Call @SustainUp
    else
      sustain = YES
    endif
  endif
@End

@OnMidiNoteOn
  SetNoteState MIDIChannel,MIDINote,YES
  Call @SearchStack

  if (not found) or (not sustain)
    Call @AddNote
    SendMIDIThru
  endif
@End

@OnMidiNoteOff
  SetNoteState MIDIChannel,MIDINote,NO
  Call @SearchStack

  if found and (not sustain)
    SendMIDIThru
    Call @RemoveNote
  endif

@End
  
@SearchStack
  searchIndex = 0
  found = NO
  
  while notes[searchIndex] <> -1 and searchIndex < 1024 and (not found)
    if notes[searchIndex] = (MIDIChannel * 0x100) + MIDINote
      found = YES
    else
      Inc searchIndex
    endif
  endwhile
@End

@AddNote
  // Add the note to the stack
  Inc noteIndex
  notes[noteIndex] = (MIDIChannel * 0x100) + MIDINote  
  // log {Added note }, notes[0], { }, notes[1], { }, notes[2], { }, notes[3]
@End

@RemoveNote
  // Remove a note from the stack
  repeat
    notes[searchIndex] = notes[searchIndex+1]
    if notes[searchIndex] = -1
      noteIndex = searchIndex - 1
    endif
    Inc searchIndex
  until notes[searchIndex] = -1 or searchIndex = 1024  
  // log {Removed note }, notes[0], { }, notes[1], { }, notes[2], { }, notes[3]
@End

@SustainUp
  idx = 0
  repeat
    chan = Div (notes[idx] & 0xFF00), 100
    note = notes[idx] & 0x00FF
    if not (GetNoteState chan,note)
      SendMidiNoteOff chan,note,0,1
      searchIndex = idx
      found = YES
      Call @RemoveNote
    else
      Inc idx
    endif
  until notes[idx] = -1 or idx = 1024
@End

jjpl2001

@wim said:

@jjpl2001 said:
Hello. Playing both strings and piano simultaneously can be challenging. When you play a note more than once, the strings plugin triggers additional string sounds, gradually increasing the volume. If you play fast repeated chords on the piano alongside the strings plugin, the volume of the strings keeps increasing to an unreasonable level.

What I want is to prevent note retriggering while the sustain pedal is held down. The pedal should be able to sustain any new played notes but shouldn't allow to retrigger the sustained notes again until the sustain pedal is released.

I came across a sostenuto code on patchstorage that converts the sustain pedal into a sostenuto pedal. However, there's a problem with it. It only sustains the notes that were held down when the pedal is pressed. If you play any new notes, they won't be sustained. (That is how a sustenuto pedal should work, but is not what I need)

You can check out the original sostenuto in the following link to get an idea of how it works:
https://patchstorage.com/sostenuto/

Hiya @jjpl2001. Here's something for you to try out. If it works as you think it should I'll polish it up and post it on patch storage as it seems like a useful tool. If it doesn't then let me know what to fix or change.

BTW, any ideas what to call this?

@Description
MODIFIED SOSTENUTO v0.1
Sustain new notes but do not retrigger notes when the sustain pedal is down.

Any notes held down when sustain "on" is received remain on until the sustain "off" is received. If a note being sustained is played again it will not be retriggered, but new notes will trigger and be sustained as well. On sustain "off" notes being held by the script will be released, with the exception of notes still being held down.

Example: Press sustain while holding down notes C and D. Now release C and D. The notes will continue to play. If you press C or D again they will not be triggered. Now press note E (still holding sustain down) - it will be triggered and sustained. Continue to hold E and release sustain. C and D will stop sustaining, but E will continue to sound until it is released.

Script idea credit: Audiobus forum member @jjpl2001
@End

@OnLoad
  _sustainCC = 64
  sustain = NO
  noteIndex = -1
  FillArray notes,-1
  ResetNoteStates NO
@End

@OnMidiCC
  if MIDIByte2 <> _sustainCC
    SendMIDIThru
  else
    if MIDIByte3 = 0
      sustain = NO
      Call @SustainUp
    else
      sustain = YES
    endif
  endif
@End

@OnMidiNoteOn
  SetNoteState MIDIChannel,MIDINote,YES
  Call @SearchStack

  if (not found) or (not sustain)
    Call @AddNote
    SendMIDIThru
  endif
@End

@OnMidiNoteOff
  SetNoteState MIDIChannel,MIDINote,NO
  Call @SearchStack

  if found and (not sustain)
    SendMIDIThru
    Call @RemoveNote
  endif

@End
  
@SearchStack
  searchIndex = 0
  found = NO
  
  while notes[searchIndex] <> -1 and searchIndex < 1024 and (not found)
    if notes[searchIndex] = (MIDIChannel * 0x100) + MIDINote
      found = YES
    else
      Inc searchIndex
    endif
  endwhile
@End

@AddNote
  // Add the note to the stack
  Inc noteIndex
  notes[noteIndex] = (MIDIChannel * 0x100) + MIDINote  
  // log {Added note }, notes[0], { }, notes[1], { }, notes[2], { }, notes[3]
@End

@RemoveNote
  // Remove a note from the stack
  repeat
    notes[searchIndex] = notes[searchIndex+1]
    if notes[searchIndex] = -1
      noteIndex = searchIndex - 1
    endif
    Inc searchIndex
  until notes[searchIndex] = -1 or searchIndex = 1024  
  // log {Removed note }, notes[0], { }, notes[1], { }, notes[2], { }, notes[3]
@End

@SustainUp
  idx = 0
  repeat
    chan = Div (notes[idx] & 0xFF00), 100
    note = notes[idx] & 0x00FF
    if not (GetNoteState chan,note)
      SendMidiNoteOff chan,note,0,1
      searchIndex = idx
      found = YES
      Call @RemoveNote
    else
      Inc idx
    endif
  until notes[idx] = -1 or idx = 1024
@End

Hi, It’s working, I tested it a couple of hour ago Live in a rehearsal and it works flawlessly.

The proposed name would be SustaiNuto or SustainNuto, something like that.
I don’t know how to thank you.

I thought the coding of this function I needed was going to be an easy thing until I saw your code… That’s where I realized that I had no clue. It was more complicated than what I though.

wim

You're welcome. I'm glad it works!
I'll put some spit 'n polish on it, then post a final version on patch storage.

No need to thank me - writing scripts is fun for me. This didn't take long to do. The only tricky part was keeping track of which notes to sustain and when to release them. It's always fun to know when a script is solving a problem, especially for live playing. 👍🏼

wim

SustaiNuto v1.0 is now posted on patch storage: https://patchstorage.com/sustainuto/

---

SustaiNuto v1.0 (15-Jun-2023)
Modified Sostenuto behavior for sustain pedals. Sustain new notes but don’t retrigger notes when the sustain pedal is down.

Any notes held down when sustain “on” is received remain on until the sustain “off” is received. If a note being sustained is played again it will not be retriggered, but new notes will trigger and be sustained as well. On sustain “off” notes being held by the script will be released, with the exception of notes still being held down.

Example: Press sustain while holding down notes C2 and D2. Now release C2 and D2. The notes will continue to play. If you play a C2 or D2 again they will not be triggered. Now press note E2 (still holding sustain down) – it will be triggered and sustained. Continue to hold E2 and release sustain. C2 and D2 will stop sustaining, but E2 will continue to sound until it is released.

Script idea: Audiobus forum member @jjpl2001 👍🏼👍🏼😎
Coding: wim / number37

cokomairena

Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

tyslothrop1

@cokomairena said:
Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

I like that idea, maybe as a triggerable chordbank with 8 or more pads. What a pity I can't get my head around programming.

Edit: in a way Drambo's sequencer works like that, remembering the last keys, that were pressed together. But you can't trigger them, but just put them on the timeline afaik.

wim

@cokomairena said:
Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

The Chord Pads AUv3 included with Tonality handles that very well - better than any Mozaic script could IMO.

Turn the option "MIDI Quickassign Mode" to Manual. Go to edit mode and long-press an empty pad until its border becomes highlighted. Play chords until you have the one you like, then tap the pad. It'll be stored on the pad.

You get what I think you're asking for and you also then have all the great editing, articulation, arrangement, etc, etc, features of the app at your disposal.

cokomairena

@wim said:

@cokomairena said:
Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

The Chord Pads AUv3 included with Tonality handles that very well - better than any Mozaic script could IMO.

Turn the option "MIDI Quickassign Mode" to Manual. Go to edit mode and long-press an empty pad until its border becomes highlighted. Play chords until you have the one you like, then tap the pad. It'll be stored on the pad.

You get what I think you're asking for and you also then have all the great editing, articulation, arrangement, etc, etc, features of the app at your disposal.

Mmm that sums all the keys i played it doesn’t only save the last chord afaik

cokomairena

@tyslothrop1 said:.

Edit: in a way Drambo's sequencer works like that, remembering the last keys, that were pressed together. But you can't trigger them, but just put them on the timeline afaik.

This is perfect! Thanks!

You can indeed trigger them if you have the selection tool activated

wim

@cokomairena said:

@wim said:

@cokomairena said:
Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

The Chord Pads AUv3 included with Tonality handles that very well - better than any Mozaic script could IMO.

Turn the option "MIDI Quickassign Mode" to Manual. Go to edit mode and long-press an empty pad until its border becomes highlighted. Play chords until you have the one you like, then tap the pad. It'll be stored on the pad.

You get what I think you're asking for and you also then have all the great editing, articulation, arrangement, etc, etc, features of the app at your disposal.

Mmm that sums all the keys i played it doesn’t only save the last chord afaik

Right. I hadn't noticed that. Turn "Note Removal in Quickassign" on to fix that.

Actually though, you'd still have to be playing the chord when you commit to the pad though. I'm not sure if that fits with "the last chord I played" idea. That seems to imply you might not be still playing the chord.

tyslothrop1

@cokomairena said:

@tyslothrop1 said:.

Edit: in a way Drambo's sequencer works like that, remembering the last keys, that were pressed together. But you can't trigger them, but just put them on the timeline afaik.

This is perfect! Thanks!

You can indeed trigger them if you have the selection tool activated

Cool, I didn't know that, gotta check out if you can record the output with the selection tool.

tyslothrop1

@cokomairena Just tried it, hosted the Drambo midiFX in Drambo and turned the host sync off, so I could trigger with the transport running in the host but not the plugin. I found a way to trigger the chords, that I find even better. If you open the pianoroll and activate the little speaker icon, you can zoom in, so you don't have to use the tiny step buttons and have the little menu pop up each time. The visual representation is also more intuitive and I like putting different inversions next to each other. Only downside, you have to keep your finger on the note you tap for a few milliseconds, so it doesn't get deleted.

Synthi

Just a (not so) small mozaic request: What about a Tintinnabuli script?? there is a lot of info about the Arvo Part Techniques and algorithm, I`ve used the Max4Live free tinntinabulator

but having inside the ipad would be awesome. Here is some info about how it works:

https://aestheticcomplexity.wordpress.com/2014/03/23/mapping-tintinnabuli-transformations/

cokomairena

@wim said:

@cokomairena said:

@wim said:

@cokomairena said:
Is there something like a retrospective chord capture?

I would like to play chords and when I play one that I liked press a button to capture it without having to play it again

The Chord Pads AUv3 included with Tonality handles that very well - better than any Mozaic script could IMO.

Turn the option "MIDI Quickassign Mode" to Manual. Go to edit mode and long-press an empty pad until its border becomes highlighted. Play chords until you have the one you like, then tap the pad. It'll be stored on the pad.

You get what I think you're asking for and you also then have all the great editing, articulation, arrangement, etc, etc, features of the app at your disposal.

Mmm that sums all the keys i played it doesn’t only save the last chord afaik

Right. I hadn't noticed that. Turn "Note Removal in Quickassign" on to fix that.

Actually though, you'd still have to be playing the chord when you commit to the pad though. I'm not sure if that fits with "the last chord I played" idea. That seems to imply you might not be still playing the chord.

Exactly. The drambo solution works perfectly, drambo remembers the last chord played.

@tyslothrop1 said:
@cokomairena Just tried it, hosted the Drambo midiFX in Drambo and turned the host sync off, so I could trigger with the transport running in the host but not the plugin. I found a way to trigger the chords, that I find even better. If you open the pianoroll and activate the little speaker icon, you can zoom in, so you don't have to use the tiny step buttons and have the little menu pop up each time. The visual representation is also more intuitive and I like putting different inversions next to each other. Only downside, you have to keep your finger on the note you tap for a few milliseconds, so it doesn't get deleted.

I can capture the chords on a tonality chordpad once i have them on drambo so its no problem.