MOZAIC Help Line

Pxlhg

Hey @McD Could (would) you (ask) to try to translate this generalisation of Per Norgards infiniti series: to Mozaic

McD

@Pxlhg said:
Hey @McD Could (would) you (ask) to try to translate this generalisation of Per Norgards infiniti series: to Mozaic

I’ll try to code a solution… I can’t imagine how to prompt Meta AI to read a webpage and implement what it details in a mix of text and math.

Try this script (if you need assistance learning to load a script - just ask):

@Description
  === Infiniti Series Loop Generator ===
  Knob 0 controls Loop Length

  Knob 1 controls Transposition (from root = 60 = C4)

  Knob 2 controls Number of Notes per Beat

  Knob 3 controls Note Lengths

@End

@OnLoad  

  ShowLayout 4

  n = [0]
  Count = 0
  root = 60 // C4
  MaxLoop = 12
  Call @InfinitiSeries
  // PPQN = 3
  ppqn = 3
  SetMetroPPQN ppqn
  NoteLength = 500 // in milliseconds

  Parameters = [MaxLoop, root, ppqn, NoteLength]
  Log {Parameters = [MaxLoop, root, ppqn, NoteLength]}

  Call @LabelKnobs
@End

@InfinitiSeries

  // generating the Infiniti series into Array "n" - up to MaxLoop notes
  n[0] = 0
  n[1] = 1
  for i = 1 to MaxLoop
    n[2*i] = n[2*i-2] - (n[i] - n[i-1])
    n[(2*i + 1)] = n[2*i-1] + (n[i] - n[i-1])
  endfor

@End

@OnMetroPulse

  // SendMIDINoteOn 0, 60, 100
  // SendMIDINoteOff 0, 60, 0, 500
  // Log {Note = }, NoteName  n[Count]+root
  SendMidiNoteOn 0, n[Count]+root, 100
  SendMidiNoteOff 0, n[Count]+root, 0, NoteLength
  if Count < (MaxLoop - 1)
    Inc Count
  else
    Count = 0
  endif

@End

@OnKnobChange

  // Parameters = [root, MaxLoop, ppqn, NoteLength]

  knob = LastKnob
  value = round GetKnobValue knob
  Log {Knob = }, knob, { Value = }, value
  // value = round TranslateScale value, 0, 127, 1, 100
  Log {Knob = }, knob, { Value = }, value

  Parameters[knob] = value

  root = parameters[1]
  if knob = 0
    Parameters[knob] = round TranslateScale value, 0, 127, 1, 20
    MaxLoop = parameters[0]
    Log {Loop = }, MaxLoop
  endif
  if knob = 1
    Transpose = round TranslateScale value, 0, 127, -20, 20
    Parameters[1] = root + Transpose
    Log {Transpose = }, Transpose
  endif 
  if knob = 2
    Parameters[2] = round TranslateScale value, 0, 127, 1, 24
    SetMetroPPQN  Parameters[2]
    Log {Notes per Beat = }, Parameters[2]
  endif
  if knob = 3
    NoteLength = 100*parameters[3]
  endif
  Call @InfinitiSeries
  Call @LabelKnobs

@End  

@LabelKnobs

  LabelKnob 0, {Notes=}, Parameters[0]
  LabelKnob 1, {Trans=}, Parameters[1] - 60
  LabelKnob 2, {PPQN=}, Parameters[2]
  LabelKnob 3, {Lngth=}, Parameters[3]

@End     

Pxlhg

@McD said:

@Pxlhg said:
Hey @McD Could (would) you (ask) to try to translate this generalisation of Per Norgards infiniti series: to Mozaic

I’ll try to code a solution… I can’t imagine how to prompt Meta AI to read a webpage and implement what it details in a mix of text and math.

Sorry I thought you would spot the example in the pretty short text, my bad.

McD

@Pxlhg said:

@McD said:

@Pxlhg said:
Hey @McD Could (would) you (ask) to try to translate this generalisation of Per Norgards infiniti series: to Mozaic

I’ll try to code a solution… I can’t imagine how to prompt Meta AI to read a webpage and implement what it details in a mix of text and math.

Sorry I thought you would spot the example in the pretty short text, my bad.

@Description
  === Infiniti Series Loop Generator ===
  Knob 0 controls Loop Length

  Knob 1 controls Transposition (from root = 60 = C4)

  Knob 2 controls Number of Notes per Beat

  Knob 3 controls Note Lengths

@End

@OnLoad  

  ShowLayout 4

  n = [0]
  Count = 0
  root = 60 // C4
  MaxLoop = 12
  Call @InfinitiSeries
  // PPQN = 3
  ppqn = 3
  SetMetroPPQN ppqn
  NoteLength = 500 // in milliseconds

  Parameters = [MaxLoop, root, ppqn, NoteLength]
  Log {Parameters = [MaxLoop, root, ppqn, NoteLength]}

  Call @LabelKnobs
@End

@InfinitiSeries

  // generating the Infiniti series into Array "n" - up to MaxLoop notes
  n[0] = 0
  n[1] = 1
  for i = 1 to MaxLoop
    n[2*i] = n[2*i-2] - (n[i] - n[i-1])
    n[(2*i + 1)] = n[2*i-1] + (n[i] - n[i-1])
  endfor

@End

@OnMetroPulse

  // SendMIDINoteOn 0, 60, 100
  // SendMIDINoteOff 0, 60, 0, 500
  // Log {Note = }, NoteName  n[Count]+root
  SendMidiNoteOn 0, n[Count]+root, 100
  SendMidiNoteOff 0, n[Count]+root, 0, NoteLength
  if Count < (MaxLoop - 1)
    Inc Count
  else
    Count = 0
  endif

@End

@OnKnobChange

  // Parameters = [root, MaxLoop, ppqn, NoteLength]

  knob = LastKnob
  value = round GetKnobValue knob
  Log {Knob = }, knob, { Value = }, value
  // value = round TranslateScale value, 0, 127, 1, 100
  Log {Knob = }, knob, { Value = }, value

  Parameters[knob] = value

  root = parameters[1]
  if knob = 0
    Parameters[knob] = round TranslateScale value, 0, 127, 1, 20
    MaxLoop = parameters[0]
    Log {Loop = }, MaxLoop
  endif
  if knob = 1
    Transpose = round TranslateScale value, 0, 127, -20, 20
    Parameters[1] = root + Transpose
    Log {Transpose = }, Transpose
  endif 
  if knob = 2
    Parameters[2] = round TranslateScale value, 0, 127, 1, 24
    SetMetroPPQN  Parameters[2]
    Log {Notes per Beat = }, Parameters[2]
  endif
  if knob = 3
    NoteLength = 100*parameters[3]
  endif
  Call @InfinitiSeries
  Call @LabelKnobs

@End  

@LabelKnobs

  LabelKnob 0, {Notes=}, Parameters[0]
  LabelKnob 1, {Trans=}, Parameters[1] - 60
  LabelKnob 2, {PPQN=}, Parameters[2]
  LabelKnob 3, {Lngth=}, Parameters[3]

@End 

Pxlhg

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

McD

@Pxlhg said:

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

What would you like to see or hear it do differently? I like to run 2 instances and offset the PPQN (Pulses Per Quarter Note) to
contrasting settings and get polyrhythms. If you slide one of them out of service and back again you get them NOT aligning on the metronome which can be insane. Tweaking he Transposing Knob can be used to generate changes to the fixed note loops…

I suspect random notes changes would be just as useful. The Infinity Series seems somewhat arbitrary, IMHO but solving the best way to implement it in Mozaic was a nice little puzzle.

Pxlhg

@McD said:

@Pxlhg said:

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

What would you like to see or hear it do differently? I like to run 2 instances and offset the PPQN (Pulses Per Quarter Note) to
contrasting settings and get polyrhythms. If you slide one of them out of service and back again you get them NOT aligning on the metronome which can be insane. Tweaking he Transposing Knob can be used to generate changes to the fixed note loops…

I suspect random notes changes would be just as useful. The Infinity Series seems somewhat arbitrary, IMHO but solving the best way to implement it in Mozaic was a nice little puzzle.

It was a follow up on an another discussion you had with someone having made a sequence based on the Norgard stuff. I didn't know what you were talking about and that led me to the page with the code. So, it's a circle... 😂

I tried with only one but had 'transpose' ran by a very slow LFO and that worked pretty nice.

McD

@Pxlhg said:

@McD said:

@Pxlhg said:

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

What would you like to see or hear it do differently? I like to run 2 instances and offset the PPQN (Pulses Per Quarter Note) to
contrasting settings and get polyrhythms. If you slide one of them out of service and back again you get them NOT aligning on the metronome which can be insane. Tweaking he Transposing Knob can be used to generate changes to the fixed note loops…

I suspect random notes changes would be just as useful. The Infinity Series seems somewhat arbitrary, IMHO but solving the best way to implement it in Mozaic was a nice little puzzle.

It was a follow up on an another discussion you had with someone having made a sequence based on the Norgard stuff. I didn't know what you were talking about and that led me to the page with the code. So, it's a circle... 😂

I tried with only one but had 'transpose' ran by a very slow LFO and that worked pretty nice.

I need to try this LTO trick. The Transpose knob is fun to create melodies so I’ll bet is works great.

I had to check and confirm that Mozaic exposes knobs as AU parameters to AUM and it does. That means I don’t have to write the CC event instructions… just set it up in an AUM project. Nice… then I noticed every possible control option in Mozaic is on the list. There’s a lot of them.

Gavinski

@McD said:

@Pxlhg said:

@McD said:

@Pxlhg said:

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

What would you like to see or hear it do differently? I like to run 2 instances and offset the PPQN (Pulses Per Quarter Note) to
contrasting settings and get polyrhythms. If you slide one of them out of service and back again you get them NOT aligning on the metronome which can be insane. Tweaking he Transposing Knob can be used to generate changes to the fixed note loops…

I suspect random notes changes would be just as useful. The Infinity Series seems somewhat arbitrary, IMHO but solving the best way to implement it in Mozaic was a nice little puzzle.

It was a follow up on an another discussion you had with someone having made a sequence based on the Norgard stuff. I didn't know what you were talking about and that led me to the page with the code. So, it's a circle... 😂

I tried with only one but had 'transpose' ran by a very slow LFO and that worked pretty nice.

I need to try this LTO trick. The Transpose knob is fun to create melodies so I’ll bet is works great.

I had to check and confirm that Mozaic exposes knobs as AU parameters to AUM and it does. That means I don’t have to write the CC event instructions… just set it up in an AUM project. Nice… then I noticed every possible control option in Mozaic is on the list. There’s a lot of them.

Remember tho that AUM has its own midi learn system, so you don't need to manually scroll through lists to find the thing you want to control, it should be absolutely painless!

McD

@Gavinski said:

@McD said:

@Pxlhg said:

@McD said:

@Pxlhg said:

@McD said:

>

Ha! Pretty darn cool (if somewhat chaotic on the control side). Thanks for giving it a go. Awesome!

What would you like to see or hear it do differently? I like to run 2 instances and offset the PPQN (Pulses Per Quarter Note) to
contrasting settings and get polyrhythms. If you slide one of them out of service and back again you get them NOT aligning on the metronome which can be insane. Tweaking he Transposing Knob can be used to generate changes to the fixed note loops…

I suspect random notes changes would be just as useful. The Infinity Series seems somewhat arbitrary, IMHO but solving the best way to implement it in Mozaic was a nice little puzzle.

It was a follow up on an another discussion you had with someone having made a sequence based on the Norgard stuff. I didn't know what you were talking about and that led me to the page with the code. So, it's a circle... 😂

I tried with only one but had 'transpose' ran by a very slow LFO and that worked pretty nice.

I need to try this LTO trick. The Transpose knob is fun to create melodies so I’ll bet is works great.

I had to check and confirm that Mozaic exposes knobs as AU parameters to AUM and it does. That means I don’t have to write the CC event instructions… just set it up in an AUM project. Nice… then I noticed every possible control option in Mozaic is on the list. There’s a lot of them.

Remember tho that AUM has its own midi learn system, so you don't need to manually scroll through lists to find the thing you want to control, it should be absolutely painless!

Good idea.

pejman

@brambos . Thanks for new update improving preset section. please add rename option for bank if possible. and add serch option for presets if possible.
in new update mozaic crash when i press backup preset icon on right corner above.

Gavinski

@pejman said:
@brambos . Thanks for new update improving preset section. please add rename option for bank if possible. and add serch option for presets if possible.
in new update mozaic crash when i press backup preset icon on right corner above.

Massive +1 on adding a search function. Even if subfolders make it less needed than it previously was.

egobeats

I tried prompting Gemini to give me a simple “ Mozaic midi echo “. Script.

It looks good, gave suggestions to tweak it, reduce cpu and overall making it more efficient.

It even provided steps to copy into Mozaic. I haven’t tried to run it. Just looking at the code generation. If I get bored, I’ll run a few and see wassup.

Gavinski

@egobeats said:
I tried prompting Gemini to give me a simple “ Mozaic midi echo “. Script.

It looks good, gave suggestions to tweak it, reduce cpu and overall making it more efficient.

It even provided steps to copy into Mozaic. I haven’t tried to run it. Just looking at the code generation. If I get bored, I’ll run a few and see wassup.

Haha, I think you'll likely be in for a nasty surprise, as the code will almost certainly have problems, but let us know how it goes! 😂

egobeats

lol, absolute fail. Love the confidence Gemini had that it “nailed it”

@Description:Randomizes incoming MIDI notes within a selected key and scale.
@Author: Gemini

// --- User Interface ---
@Knob1:Key
@Knob2:Scale
@Pad1:Randomize

// --- Constants ---
// Note names for the Key knob
DIM KeyNames[12]
KeyNames = {"C", "C#", "D", "D#", "E", "F", "F#", "G", "G#", "A", "A#", "B"}

// Scale definitions (intervals in semitones from the root)
DIM Scales[5][12]
// Major
Scales[0] = {0, 2, 4, 5, 7, 9, 11}
// Minor
Scales[1] = {0, 2, 3, 5, 7, 8, 10}
// Dorian
Scales[2] = {0, 2, 3, 5, 7, 9, 10}
// Mixolydian
Scales[3] = {0, 2, 4, 5, 7, 9, 10}
// Blues
Scales[4] = {0, 3, 5, 6, 7, 10}

DIM ScaleNames[5]
ScaleNames = {"Major", "Minor", "Dorian", "Mixo", "Blues"}

// --- Variables ---
DIM RootNote
DIM SelectedScale[12]
DIM RandomizeActive

// --- Initialization ---
@OnLoad
RandomizeActive = 0
SetKnobValue(1, 0)
SetKnobValue(2, 0)
UpdateUI()
@End

// --- UI Events ---
@OnKnob1
UpdateUI()
@End

@OnKnob2
UpdateUI()
@End

@OnPad1
RandomizeActive = Pad1Value
if RandomizeActive > 0 then
SetPadLED(1, 1)
else
SetPadLED(1, 0)
end
@End

// --- MIDI Events ---
@OnNoteOn
if RandomizeActive > 0 then
// Get the current root note and scale
RootNote = GetKnobValue(1) * 12
ScaleIndex = GetKnobValue(2) * 4
for i = 0 to 11
SelectedScale[i] = Scales[ScaleIndex][i]
end

// Find the notes of the scale in the audible range
DIM ScaleNotes[128]
DIM NoteCount
NoteCount = 0
for octave = 0 to 10
  for i = 0 to (ArrayLength(SelectedScale) - 1)
    CurrentNote = RootNote + (octave * 12) + SelectedScale[i]
    if CurrentNote < 128 and SelectedScale[i] ~= nil then
      ScaleNotes[NoteCount] = CurrentNote
      NoteCount = NoteCount + 1
    end
  end
end

// Pick a random note from the scale
if NoteCount > 0 then
  RandomIndex = random() % NoteCount
  NewNote = ScaleNotes[RandomIndex]
  SendNoteOn(NewNote, Velocity, Channel)
else
  // If no notes in scale, pass through original note
  SendNoteOn(Note, Velocity, Channel)
end

else
// Pass through original note if not randomizing
SendNoteOn(Note, Velocity, Channel)
end
@End

@OnNoteOff
// Send All Notes Off to prevent hanging notes
AllNotesOff
@End

// --- Helper Functions ---
function UpdateUI()
// Update Key Knob Label
KeyIndex = GetKnobValue(1) * 11
SetKnobLabel(1, "Key: " .. KeyNames[KeyIndex])

// Update Scale Knob Label
ScaleIndex = GetKnobValue(2) * 4
SetKnobLabel(2, "Scale: " .. ScaleNames[ScaleIndex])
end

pejman

@brambos .
i found new bug in new version 1,4 about preset name state saving.
1, launch AUM and in AUM open mozaic.
2, select one preset from internal mozaic user presets.
3 . press save button, you can see preset name in save box properly.
4, close AUM , and launch it again with opening last state .
5, press mozaic save button .

In the preset Name box, the name of the preset we opened earlier is missing.

there is no this problem in 1,3 version.

brambos

@pejman said:
@brambos .
i found new bug in new version 1,4 about preset name state saving.
1, launch AUM and in AUM open mozaic.
2, select one preset from internal mozaic user presets.
3 . press save button, you can see preset name in save box properly.
4, close AUM , and launch it again with opening last state .
5, press mozaic save button .

In the preset Name box, the name of the preset we opened earlier is missing.

there is no this problem in 1,3 version.

Thanks for the heads up, but I'm fairly certain this was always the same behaviour. Once you enter a name in the file dialog box it will be remembered for that session, but it is not saved in the state of the plugin so the next time the plugin is loaded the dialog box will be in default state again

pejman

@brambos
I have been coding continuously in AUM for 2 years now in Mosaic.
This problem did not exist in the previous version at all.

And I could easily increase a number to the name of the previous version of my preset even if I closed and reopened aum.

This is a very important feature. Please return this feature to Mosaic if possible.

If I could make a video of the previous version, I would definitely send it to you, but unfortunately I updated Mosaic on both my iPhone and iPad.

Gavinski

@brambos presets beginning with upper case characters are listed before lower case. Any chance to have an option where that doesn't happen? It means it's harder to find things when scrolling through user presets, as some Patchstorage patches use upper case for the first letter, some don't

pejman

@brambos .
my ipad is air2 with 15,8 ios version.
I have always done coding via iPad. Could this be related to iOS version that this feature exists for me, I mean keeping the name of the preset in Save Box Dialog.

brambos

@pejman said:
@brambos .
my ipad is air2 with 15,8 ios version.
I have always done coding via iPad. Could this be related to iOS version that this feature exists for me, I mean keeping the name of the preset in Save Box Dialog.

Let me look into it

pejman

@brambos said:

@pejman said:
@brambos .
my ipad is air2 with 15,8 ios version.
I have always done coding via iPad. Could this be related to iOS version that this feature exists for me, I mean keeping the name of the preset in Save Box Dialog.

Let me look into it

🙏❤️

brambos

@Gavinski said:
@brambos presets beginning with upper case characters are listed before lower case. Any chance to have an option where that doesn't happen? It means it's harder to find things when scrolling through user presets, as some Patchstorage patches use upper case for the first letter, some don't

I spent two hours yesterday just trying to get it to sort the files in that way, and it stubbornly refuses to, so I decided it wasn't worth pursuing horrible iOS file system any further.

Gavinski

@brambos said:

@Gavinski said:
@brambos presets beginning with upper case characters are listed before lower case. Any chance to have an option where that doesn't happen? It means it's harder to find things when scrolling through user presets, as some Patchstorage patches use upper case for the first letter, some don't

I spent two hours yesterday just trying to get it to sort the files in that way, and it stubbornly refuses to, so I decided it wasn't worth pursuing horrible iOS file system any further.

OK, thanks for trying Bram

Squishy

As one of the many newer owners of mozaic since the price drop who “doesn’t know code”, was up late last night combing through the mozaic patches looking for something to fix note velocity from my midi keyboard that doesn’t have that built in (neither does AUM). Searching ‘velocity’ on PS gave me so many hits but never found what I needed. But then I remembered StreamByter. It had multiple instances of this function already in the presets.
So just a friendly lil reminder: if you can’t find a patch for a thing you’re trying to thing, try StreamByter!

wim

@Squishy said:
As one of the many newer owners of mozaic since the price drop who “doesn’t know code”, was up late last night combing through the mozaic patches looking for something to fix note velocity from my midi keyboard that doesn’t have that built in (neither does AUM). Searching ‘velocity’ on PS gave me so many hits but never found what I needed. But then I remembered StreamByter. It had multiple instances of this function already in the presets.
So just a friendly lil reminder: if you can’t find a patch for a thing you’re trying to thing, try StreamByter!

Streambyter is often a really good choice, especially for very simple things such as this.

pejman

@brambos .
Can I ask you to widen the main window that shows the presets so that it shows more characters ( letters ) of a preset name?

And also, the last loaded preset is highlighted whenever we open the preset window.

Squishy

@pejman said:
@brambos .
Can I ask you to widen the main window that shows the presets so that it shows more characters ( letters ) of a preset name?

And also, the last loaded preset is highlighted whenever we open the preset window.

I kinda like that second feature…

pejman

@brambos.
thanks for new update ( file name remember ) works Just like before the update. And I'm very happy about that.
thanks 🙏🙏🙏❤️.
and thanks for adding banks.
How nice it would be if we could change the name of the bank whenever we wanted.

filo01

I'm totally lost. Could please tell me how to export (share) my own preset from Mozaic app to Files? The menu tree allows me only to choose preset (then the preset is automatically loaded and preset dialog is closed) or save it. I can't focus the preset nor tap to "share preset".