Long Slow Fades between elements - AUM?

AudioGus

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Would love to be able to play cc values and have attack/hold/decay on them. Even velocity ranges for cc.

Kelmanbob

Many thanks for the suggestions. Lots of avenues to go at. I’m ultimately most interested in Mozaic. I was imagining a modular app when I was looking for appropriate apps, the kind of thing @brambos rejected for the script-based version of Mozaic. Look forward to it.

Janosax

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Will Mozaic be able to display faders too or only knobs? I’d really like to have a surface controller like TouchOSC but in AU format.

brambos

@Janosax said:

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Will Mozaic be able to display faders too or only knobs? I’d really like to have a surface controller like TouchOSC but in AU format.

One of the available layouts has 10 vertical sliders on it.

Carnbot

There's a brilliant new LFO AUv3 coming soon to apeMatrix and I'm using it constantly in every host now. Has 8 LFOs with multi AU out ports with apeSoft's great LFO options which have random, long cycle times and also each pair of LFOs has an X/Y pad which can perform the LFOs.

If you buy apeMatrix you'll be able to use it in AUM too (not sure when the beta is finished though)

Janosax

@brambos said:

@Janosax said:

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Will Mozaic be able to display faders too or only knobs? I’d really like to have a surface controller like TouchOSC but in AU format.

One of the available layouts has 10 vertical sliders on it.

Are layouts fully customizable?

Carnbot

@brambos said:

One of the available layouts has 10 vertical sliders on it.

Looking forward to this, I saw the sequencer you posted on Twitter, looks great. So glad you went with multiple layout options.

brambos

@Janosax said:

@brambos said:

@Janosax said:

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Will Mozaic be able to display faders too or only knobs? I’d really like to have a surface controller like TouchOSC but in AU format.

One of the available layouts has 10 vertical sliders on it.

Are layouts fully customizable?

Nope, they’re as fixed as a hardware midi controller.

Janosax

@brambos said:

@Janosax said:

@brambos said:

@Janosax said:

@brambos said:

@klownshed said:

@brambos said:

@bleep said:
Ah, tempo sync off, of course. Somehow I never used that in Rozeta LFO ... I agree that the numbers you have found there, @CracklePot, are plenty enough.

I’m still going to make that uber-slow LFO preset for Mozaic

Would you be able to just make a fade go up, rather than follow an LfO?

Also could a script be triggered for a one shot operation?

For example, if I wanted to trigger a fade with a note value, could I just initiate a loop from 0-90 which just stopped when it got to 90 unless retriggered? Another script could go the other way with a different trigger.

Your overall arrangement could then be a bunch of triggers firing off other sequences and scripts at will.

Sure, all that should be fairly trivial. You could use a note input for triggering such fades, or a button on the screen. And the durations could be scripted/hardcoded, or controlled via knobs.

Will Mozaic be able to display faders too or only knobs? I’d really like to have a surface controller like TouchOSC but in AU format.

One of the available layouts has 10 vertical sliders on it.

Are layouts fully customizable?

Nope, they’re as fixed as a hardware midi controller.

Is there already a layout with a bit of everything like that?

If not yet, could you consider making one? That could be very useful for more than 80 % users I suppose

aplourde

@CracklePot said:

@Antkn33 said:
24 hours might be ridiculous. But I would like 4-8 bars or so.

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

I think you can get those rates already?

I don’t get the request for longer LFO periods for Rozeta. If I turn off Tempo Sync and set the rate to minimum, it is imperceptibly slow to me. I set up a Saw Down at the minimum rate with Tempo Sync off and AUM set to 120 BPM. The cycle lasted over 5 minutes and more than 150 measures. I can’t even hear it changing moment to moment, I just notice the change after a while.

One thing that's a bit confusing is that the display isn't accurate at the lowest setting. It says the lowest value is 0.01Hz, which would be 100 seconds or 1.66666 minutes. However, there's a bit of play at the bottom of the knob and you can move the knob for a ways while it still says 0.01Hz.

If you move the knob down from a faster rate and stop as soon as you see 0.01Hz you will get the expected rate. But as @CracklePot noted, the lowest value is actually around 0.00318Hz, which is around 315 seconds.

It is, in fact possible to get values in between those, but there's no way to accurately replicate that as the display only shows 0.01Hz. Perhaps this could be fixed?

That said, the "problem" people have with Rozeta LFO is in the tempo sync'ed option. Here the slowest value is 8 bars; at 120 bpm that's 16 seconds. It's very easy to want a tempo synced LFO at 16 or 32 bars as that would likely correspond to a verse or chorus section.

---

@brambos One request for Mozaic: please have a way for the LFO to only send out a change in value. A square wave is really only two values, but Rozeta LFO sends out a constant stream of the same value. It's common to use control signals for multiple functions and a square wave is useful as a trigger, but when the same value is sent repeatedly it causes multiple triggers. Also, with super-slow LFOs we don't need constant streams of the same value. Thanks!

brambos

@aplourde said:

@CracklePot said:

@Antkn33 said:
24 hours might be ridiculous. But I would like 4-8 bars or so.

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

I think you can get those rates already?

I don’t get the request for longer LFO periods for Rozeta. If I turn off Tempo Sync and set the rate to minimum, it is imperceptibly slow to me. I set up a Saw Down at the minimum rate with Tempo Sync off and AUM set to 120 BPM. The cycle lasted over 5 minutes and more than 150 measures. I can’t even hear it changing moment to moment, I just notice the change after a while.

One thing that's a bit confusing is that the display isn't accurate at the lowest setting. It says the lowest value is 0.01Hz, which would be 100 seconds or 1.66666 minutes. However, there's a bit of play at the bottom of the knob and you can move the knob for a ways while it still says 0.01Hz.

If you move the knob down from a faster rate and stop as soon as you see 0.01Hz you will get the expected rate. But as @CracklePot noted, the lowest value is actually around 0.00318Hz, which is around 315 seconds.

It is, in fact possible to get values in between those, but there's no way to accurately replicate that as the display only shows 0.01Hz. Perhaps this could be fixed?

That said, the "problem" people have with Rozeta LFO is in the tempo sync'ed option. Here the slowest value is 8 bars; at 120 bpm that's 16 seconds. It's very easy to want a tempo synced LFO at 16 or 32 bars as that would likely correspond to a verse or chorus section.

---

@brambos One request for Mozaic: please have a way for the LFO to only send out a change in value. A square wave is really only two values, but Rozeta LFO sends out a constant stream of the same value. It's common to use control signals for multiple functions and a square wave is useful as a trigger, but when the same value is sent repeatedly it causes multiple triggers. Also, with super-slow LFOs we don't need constant streams of the same value. Thanks!

Sure, just check if the new value is different from the last and don’t send it out if it’s the same. The beauty of a script concept is that you can change anything to fit your specific use case.

brambos

@aplourde

Here's an ultra-slow LFO which checks if the new value differs from the last one:

@Onload
  var0 = 60    // set this to # of minutes per lfo period
  var10 = 15   // set this to CC# you want to control

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetTimerInterval 2000 // check every 2 seconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, var10, var1 
    var0 = var1
    log {LFO value:}, var0
  endif 
@End  

And here's a modified one which constantly cross-fades between MIDI channel 1 and MIDI channel 2 (using CC7 for volume):

@Onload
  var0 = 2    // set this to # of minutes per lfo period

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetLFOType 0, {triangle}   // set up the LFO as a triangle
  RestartLFO 0.25 // start at the highest phase

  SetTimerInterval 500 // check every 500 milliseconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, 7, var1 
    SendMIDICC 1, 7, 127 - var1  // send the inverted value to channel 1
    var0 = var1
  endif 
@End  

I will add both to the Mozaic presets as example scripts

Will

loverly!

Jocphone

@brambos that first slow LFO example had me confused until I realised that you were re-using var0 in the OnTimer section and it had no relation to its value in OnLoad.

I’m going to find the variable names a pain to remember what value goes where. Like programming registers in assembly. Thought I had left that way of working long behind!

brambos

@Jocphone said:
@brambos that first slow LFO example had me confused until I realised that you were re-using var0 in the OnTimer section and it had no relation to its value in OnLoad.

I’m going to find the variable names a pain to remember what value goes where. Like programming registers in assembly. Thought I had left that way of working long behind!

I'll consider an elegant mechanism for user-defined variable names at a later stage. For now I decided against it, to avoid having to force users to declare variables and having to consider variable scope - which is probably a lot more painful for a lot more people than having to remember what went into var0 and what went into var99.

Something is always going to be painful, and for me conceptual accessibility was highest priority. Understanding scope is not easy for beginners.

Jocphone

@brambos said:

@Jocphone said:
@brambos that first slow LFO example had me confused until I realised that you were re-using var0 in the OnTimer section and it had no relation to its value in OnLoad.

I’m going to find the variable names a pain to remember what value goes where. Like programming registers in assembly. Thought I had left that way of working long behind!

I'll consider an elegant mechanism for user-defined variable names at a later stage. For now I decided against it, to avoid having to force users to declare variables and having to consider variable scope - which is probably a lot more painful for a lot more people than having to remember what went into var0 and what went into var99.

Something is always going to be painful, and for me conceptual accessibility was highest priority. Understanding scope is not easy for beginners.

Yeah I understand. My team maintain a DSL at work, mainly JavaScript and custom HTML, so I see the pain that non developers go through with some of these concepts.

I had assumed that all the variables were global but I guess, from our previous discussion as well, that you do have bigger plans for Mozaic.

Hope you don't mind me picking up on aspects of the language that I am curious about..?

brambos

@Jocphone said:

@brambos said:

@Jocphone said:
@brambos that first slow LFO example had me confused until I realised that you were re-using var0 in the OnTimer section and it had no relation to its value in OnLoad.

I’m going to find the variable names a pain to remember what value goes where. Like programming registers in assembly. Thought I had left that way of working long behind!

I'll consider an elegant mechanism for user-defined variable names at a later stage. For now I decided against it, to avoid having to force users to declare variables and having to consider variable scope - which is probably a lot more painful for a lot more people than having to remember what went into var0 and what went into var99.

Something is always going to be painful, and for me conceptual accessibility was highest priority. Understanding scope is not easy for beginners.

Yeah I understand. My team maintain a DSL at work, mainly JavaScript and custom HTML, so I see the pain that non developers go through with some of these concepts.

I had assumed that all the variables were global but I guess, from our previous discussion as well, that you do have bigger plans for Mozaic.

Hope you don't mind me picking up on aspects of the language that I am curious about..?

No, not at all. Just know that very few things were just arbitrarily chosen; I have thought long and hard about the tiniest of details. But I agree the variable naming was thing I decided to compromise on for now.

All variables are currently global - that's what keeps it simple - but if you want to use user-defined names you'll have to declare them somewhere. Doing that upfront (at the top of the script) requires thinking ahead. I remember learning Pascal as a kid and it was one of the things that I really had to get used to. Declaring them inside loops and events makes their scope and life-cycle ambiguous. It's a tradeoff.

I could consider introducing alias names or something, where you define an alias for a predefined global for convenience. That would make it an optional mechanism which is backwards compatible with the model I have built now.

Jocphone

Oh god @brambos I wouldn't for a minute suggest that you are making arbitrary decisions!

No, no it was just me offering my perspective. I find that people have a hard time with naming generally and user-defined names doesn't fix this, but it can lead to much more understandable code. Also, it can do the opposite and that was my niggle with the first example, exacerbated by re-using the variable for a different purpose (I think?)

Fully agree about scope. Have seen experienced developers struggle with getting it right in an unfamiliar language.

I understand your idea about aliasing variables but language design is tricky, as you know, and little, seemingly innocent changes at the start can cause major difficulties as the language develops. I always try to err on the side of simplicity.

brambos

@Jocphone said:
Oh god @brambos I wouldn't for a minute suggest that you are making arbitrary decisions!

No, no it was just me offering my perspective. I find that people have a hard time with naming generally and user-defined names doesn't fix this, but it can lead to much more understandable code. Also, it can do the opposite and that was my niggle with the first example, exacerbated by re-using the variable for a different purpose (I think?)

Fully agree about scope. Have seen experienced developers struggle with getting it right in an unfamiliar language.

I understand your idea about aliasing variables but language design is tricky, as you know, and little, seemingly innocent changes at the start can cause major difficulties as the language develops. I always try to err on the side of simplicity.

Me too.

And language design is indeed tricky. Apple are now at their 4th attempt to get Swift right

aplourde

@brambos said:
@aplourde

Here's an ultra-slow LFO which checks if the new value differs from the last one:

@Onload
  var0 = 60    // set this to # of minutes per lfo period
  var10 = 15   // set this to CC# you want to control

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetTimerInterval 2000 // check every 2 seconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, var10, var1 
    var0 = var1
    log {LFO value:}, var0
  endif 
@End  

And here's a modified one which constantly cross-fades between MIDI channel 1 and MIDI channel 2 (using CC7 for volume):

@Onload
  var0 = 2    // set this to # of minutes per lfo period

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetLFOType 0, {triangle}   // set up the LFO as a triangle
  RestartLFO 0.25 // start at the highest phase

  SetTimerInterval 500 // check every 500 milliseconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, 7, var1 
    SendMIDICC 1, 7, 127 - var1  // send the inverted value to channel 1
    var0 = var1
  endif 
@End  

I will add both to the Mozaic presets as example scripts

Awesome! I can actually figure out what's going on in these.

I do, however, fully support the idea of aliases for the variables. That would certainly help in the immediate readability, especially in more complex scripts.

Feel free to post more examples, especially if you're working down the list of tool ideas that @ocelot provided; it would be great to understand the capabilities!

Antkn33

What is Mozaic?

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

@brambos said:

@bleep said:
^The problem with using Rozeta LFO is that it doesn't allow for long, slow transitions. This has been discussed here before, sadly @brambos does not think enough users are interested in very slow lfo rates

People were requesting 2-hour LFO periods. Yes, I think that's outside the range of a general purpose LFO tool.
However with Mozaic you will be able to create 24-hour LFOs if you want.

@brambos said:
@aplourde

Here's an ultra-slow LFO which checks if the new value differs from the last one:

@Onload
  var0 = 60    // set this to # of minutes per lfo period
  var10 = 15   // set this to CC# you want to control

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetTimerInterval 2000 // check every 2 seconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, var10, var1 
    var0 = var1
    log {LFO value:}, var0
  endif 
@End  

And here's a modified one which constantly cross-fades between MIDI channel 1 and MIDI channel 2 (using CC7 for volume):

@Onload
  var0 = 2    // set this to # of minutes per lfo period

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetLFOType 0, {triangle}   // set up the LFO as a triangle
  RestartLFO 0.25 // start at the highest phase

  SetTimerInterval 500 // check every 500 milliseconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, 7, var1 
    SendMIDICC 1, 7, 127 - var1  // send the inverted value to channel 1
    var0 = var1
  endif 
@End  

I will add both to the Mozaic presets as example scripts

@brambos said:
@aplourde

Here's an ultra-slow LFO which checks if the new value differs from the last one:

@Onload
  var0 = 60    // set this to # of minutes per lfo period
  var10 = 15   // set this to CC# you want to control

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetTimerInterval 2000 // check every 2 seconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, var10, var1 
    var0 = var1
    log {LFO value:}, var0
  endif 
@End  

And here's a modified one which constantly cross-fades between MIDI channel 1 and MIDI channel 2 (using CC7 for volume):

@Onload
  var0 = 2    // set this to # of minutes per lfo period

  var0 = 1 / ( var0 * 60 )
  SetupLFO 0, 0, 127, no, var0
  SetLFOType 0, {triangle}   // set up the LFO as a triangle
  RestartLFO 0.25 // start at the highest phase

  SetTimerInterval 500 // check every 500 milliseconds
  StartTimer  
@End

@OnTimer 
  var1 = round ( GetLFOValue 0 )
  if var0 <> var1 // only send when value has changed
    SendMIDICC 0, 7, var1 
    SendMIDICC 1, 7, 127 - var1  // send the inverted value to channel 1
    var0 = var1
  endif 
@End  

I will add both to the Mozaic presets as example scripts

brambos

@Antkn33 said:
What is Mozaic?

It's a roll-your-own AUv3 MIDI Plugin Plugin I'm making. Should be ready for beta soon.

Antkn33

nice can’t wait!

espiegel123

@Antkn33 : a midi macro language AUv3 Bram Bos is working on.

Antos3345

Does anyone know how to slow down the LFO to like 4 /8 bars ? I put the rate on a low setting and it’s still too fast.

uncledave

@Antos3345 said:
Does anyone know how to slow down the LFO to like 4 /8 bars ? I put the rate on a low setting and it’s still too fast.

Which LFO are you using? Rozeta LFOs or the LFO functions in Mozaic?

Antos3345

@uncledave said:

@Antos3345 said:
Does anyone know how to slow down the LFO to like 4 /8 bars ? I put the rate on a low setting and it’s still too fast.

Which LFO are you using? Rozeta LFOs or the LFO functions in Mozaic?

Rozetta lfo

What is Mozaic ?

uncledave

@Antos3345 said:

@uncledave said:

@Antos3345 said:
Does anyone know how to slow down the LFO to like 4 /8 bars ? I put the rate on a low setting and it’s still too fast.

Which LFO are you using? Rozeta LFOs or the LFO functions in Mozaic?

Rozetta lfo

What is Mozaic ?

See farther up on this forum page. Mozaic is a MIDI scripting language created by Bram Bos, the author of Rozeta. It includes a nice user interface (GUI), and there are many scripts you can download from Patchstorage. Using Mozaic, you can probably go extremely slow.

audiblevideo

@Antos3345 said:
Does anyone know how to slow down the LFO to like 4 /8 bars ? I put the rate on a low setting and it’s still too fast.

mLFO does this 127,032 beats (31,758.00 bars). Is that slow enough?

bygjohn

Apologies in advance if someone’s already mentioned this - I’ve skimmed most of the thread.

One possible problem with using any MIDI LFO is the steppiness due to MIDI only having 128 steps between min and max. This will become more obvious at really slow rates.

NB I’m making an assumption here, that MiRack internally has smoother LFO control. I’m reasonably confident this is the case, but happy to be corrected if not.

One possible way round this would be to use MiRack multi in/outs in effects slots in AUM, with a stereo VCA for each channel (eg BogAudio Mix2) and an LFO per VCA. You might need a scaler/offset module for each of you don’t want to go for full range. Pipe the inputs to the VCAs and set the LFOs to control level, with the outputs going back to the same channels as the inputs.

A plus would be that there are a couple of really slow LFOs in MiRack, should that be needed.

An example setup with two channels. In this case you don’t really need the scaler modules as the LFOs have scaler and offset built in, but with some other LFOs they might be needed: