Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

How do I….curv a sound to zero after all key releases?

2»

Comments

  • edited July 2024

    @McD said:
    I would send the keyboard input to something like an organ app. If any key is down you have signal.
    If all keys are up you have no signal. That organ app can be fed into the detector app (Drambo or FAC Envolver) to generate a CC stream. When that CC stream = 0 you know no keys are down.

    >

    i would prefer this, because it's easy and level independant.

    for "midiots"..
    a cc stream is simply a series of midi control change messages.

  • @rototom said:

    @McD said:
    I would send the keyboard input to something like an organ app. If any key is down you have signal.
    If all keys are up you have no signal. That organ app can be fed into the detector app (Drambo or FAC Envolver) to generate a CC stream. When that CC stream = 0 you know no keys are down.

    >

    i would prefer this!

    for "midiots"..
    a cc stream is simply a series of midi control change messages.

    Why? What do you prefer and how does this solve the problem?

    I understand what CCs are. I don't understand how the above is set up or how it solves the problem.

    Not being funny in any way, I'm just curious if this does indeed solve the problem and if so, can someone explain how this would be set up to solve the problem?

  • i would prefer this, because it's easy and level independant.

  • @rototom said:
    i would prefer this, because it's easy and level independant.

    Not helpful.

  • Hmm, i don‘t own BA-1 (yet, waiting for the next sale…) but i followed this thread from the initial post.

    .

    And while checking the posted MiRack solution, i came up with the idea for a midi script sending out a CC to
    control the output volume of BA-1. Pressing at least a single note would reset the volume to ‚normal‘, but when
    the last note is released, a timer gets started to send out falling CC values regularly until 0 is reached.

    I tested that idea on last saturday (after @McD mentioned me…), when i had some time. The initial
    implementation worked well, but had no UI and i didn‘t like that it was so limited in its use-case, didn‘t like
    the linear fall-off etc and therefore i invested some more time ;-)

    .

    The finished script allows to define two states (ON - one or notes active, OFF - no note active) and their
    CC-value together with transition time and a curve factor (negative values slower start than linear, positive
    value faster start than linear - in fact this internally defines a gamma curce like for image brightness remapping)

    One can specify the CC-channel, CC-ID and also if the midi input should be echoed to the output. With that
    addition the script can be used either to drive AUv3 and channel parameters or be used directly to add a CC
    to the midi stream to use midi learn inside the destination plugin.

    I also added a simple visualisation using the XY dispay, the circle starts in the left side when the first note
    is pressed and stays in the center at the ON level when the off-2-on transistion is finised. When releasing
    the last key, the on-2-off transition is shown right to the center.

    The knobs can be tweaked interactively, for instance if no note is active, the OFF state level knob controls
    the CCoutput value and if a note is active, the ON state level knob controls the CC output value to allow
    easier setup.

    The default setting shown in the screenshot controls AUMs track 1 volume with no attack time and a long
    release fade to zero if routed to AUMs 'Midi Control' (ie Chan 1, CC 7)

    Other use-cases:

    • Fade channel volume down if playing for longer time (ON value < OFF value, long ON transition time,
      medium OFF transition time, curve factor negativ to get slower changes at start)

    • Quiet start with no attacks (ON: v 127, time 2s, curve -2, OFF: v 0, time 2s, curve -2) for the initisal notes

    Link to script on patchstorage

    .

    @Fruitbat1919 For your use-case with BA-1 and long reverb FX time, my suggestion would be to drive the
    main volume knob of BA-1. I don‘t know which host you using (for AUv3 param control) and if BA-1 allows
    to midi-learn (for setup in midi thru + cc mode) , but with some info i probably can help with the setup.

  • @Fruitbat1919, @_ki created a 403 line script for us all. Thank you both!

  • @_ki said:
    Hmm, i don‘t own BA-1 (yet, waiting for the next sale…) but i followed this thread from the initial post.

    .

    And while checking the posted MiRack solution, i came up with the idea for a midi script sending out a CC to
    control the output volume of BA-1. Pressing at least a single note would reset the volume to ‚normal‘, but when
    the last note is released, a timer gets started to send out falling CC values regularly until 0 is reached.

    I tested that idea on last saturday (after @McD mentioned me…), when i had some time. The initial
    implementation worked well, but had no UI and i didn‘t like that it was so limited in its use-case, didn‘t like
    the linear fall-off etc and therefore i invested some more time ;-)

    .

    The finished script allows to define two states (ON - one or notes active, OFF - no note active) and their
    CC-value together with transition time and a curve factor (negative values slower start than linear, positive
    value faster start than linear - in fact this internally defines a gamma curce like for image brightness remapping)

    One can specify the CC-channel, CC-ID and also if the midi input should be echoed to the output. With that
    addition the script can be used either to drive AUv3 and channel parameters or be used directly to add a CC
    to the midi stream to use midi learn inside the destination plugin.

    I also added a simple visualisation using the XY dispay, the circle starts in the left side when the first note
    is pressed and stays in the center at the ON level when the off-2-on transistion is finised. When releasing
    the last key, the on-2-off transition is shown right to the center.

    The knobs can be tweaked interactively, for instance if no note is active, the OFF state level knob controls
    the CCoutput value and if a note is active, the ON state level knob controls the CC output value to allow
    easier setup.

    The default setting shown in the screenshot controls AUMs track 1 volume with no attack time and a long
    release fade to zero if routed to AUMs 'Midi Control' (ie Chan 1, CC 7)

    Other use-cases:

    • Fade channel volume down if playing for longer time (ON value < OFF value, long ON transition time,
      medium OFF transition time, curve factor negativ to get slower changes at start)

    • Quiet start with no attacks (ON: v 127, time 2s, curve -2, OFF: v 0, time 2s, curve -2) for the initisal notes

    Link to script on patchstorage

    .

    @Fruitbat1919 For your use-case with BA-1 and long reverb FX time, my suggestion would be to drive the
    main volume knob of BA-1. I don‘t know which host you using (for AUv3 param control) and if BA-1 allows
    to midi-learn (for setup in midi thru + cc mode) , but with some info i probably can help with the setup.

    Have downloaded and will try it out tomorrow, thanks. Thank you for your kind effort and for explaining it all so well :)

  • wimwim
    edited July 2024

    Nice @_ki !

    That's exactly how I envisioned such a script, but wasn't enough motivated to write myself. Only your's is far better than I would have done.

    How did you manage to get Italics in the labels??

  • McDMcD
    edited July 2024

    @wim said:
    Nice @_ki !

    That's exactly how I envisioned such a script, but wasn't enough motivated to write myself. Only your's is far better than I would have done.

    How did you manage to get Italics in the labels??

    He probably sneaks the italics into his favorite Text Editor “Textastic”. It does show up in the Mozaic code as italics in the LabelPad statements.

    You know how professional programmers are about their favorite editors.

  • @wim I‘m just using unicode letters for italics and bold. There are several full alphabets available in the standrad apple fontset (they have less heigth than the regular font, so bold still looks smaller)

  • wimwim
    edited July 2024

    @_ki said:
    @wim I‘m just using unicode letters for italics and bold. There are several full alphabets available in the standrad apple fontset (they have less heigth than the regular font, so bold still looks smaller)

    Awesome. Thanks for the quick reply.

    I can even make NMOᗡ ƎᗡISԀ∩ labels now if I want. 😂

  • @_ki Wow, amazing stuff!

Sign In or Register to comment.