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.

Request Mozaic help midi output depend on chord input

123457»

Comments

  • heshes

    I use BS-16i instead of Layr, but otherwise the same. But the app setup can't have anything to do with those syntax errors you're getting. Those can happen only if the script text you're using is somehow different from what I'm running.

    Not sure why you seem to be getting those, could be related to apps you're using to copy, the browser you're viewing in, etc.
    Safest way would be to:

    1. view raw version in Safari,
    2. select all and copy,
    3. go into AUM with apps setup like you have,
    4. open Mozaic,
    5. start 'New' project (just to be safe),
    6. delete the @OnLoad . . . @END that exists in new project (important)
    7. , then paste raw text in and save.
  • BellowsBellows

    Hi Hes,
    I failed to mention. I am not getting the syntax errors any longer. The problem is that after the higher octave note is activated it never turns off. It like another midinoteoff needs to be somewhere. I don’t think my copy and paste is the problem though I will do it again. I have been using this procedure you describe. At one time it was working much better.Now that I am back home on my WiFi I don’t have to bounce between devices.

  • heshes

    Okay, that helps. Again, though, it would not be related to setup.

    I'm not sure what exactly you mean by "after the higher octave note is activated it never turns off."

    By design the notes will increase (or decrease) in pitch in any run where you're pressing the next key before releasing previous one. To get notes back to standard pitches you just need to make sure you release all keys. Are you still getting octave-offset notes after you release all keys and then start playing again?

  • heshes

    Interesting that you bring up midi note off as possible problem. It works fine for me using built-in keyboard in AUM. But now that you mention that I'm not sure why it works for me. Since the script is altering only the "midi on" commands (substituting higher pitch notes) but not changing the 'midi off' commands at all. So if it's sending on for note 72 it may still be sending 'off' for the original note 60. So maybe it is setup related, can't figure out why it works for me at all now! I will do some checking.

  • heshes
    edited April 2020

    See if adding these lines after 'sendmidithru' in @OnMidiNoteOff event change anything:

       . . . 
   sendmidithru   ( line is already there, don't duplicate)
   if heldcount = 0
     sendmidicc midichannel, 123, 0
   endif
  • heshes
    edited April 2020

    Checking on setup was a brilliant idea! Checking with a different synth I get the stuck note problem. I think BS-16i is probably counting note on and note off commands, and issuing its own 'AllNotesOff' command to avoid stuck notes when it thinks a noteoff has been sent for each noteon.

    I'm still not sure how it could have worked at all for you before, when it was doing only upward runs. In any case, I am working on it now. . .

  • heshes
    edited April 2020

    @bellows . Okay, I'm now using the free Viking Synth with Mozaic in AUM. It was giving me the stuck note before, but I think it's fixed. Maybe it will all be working now! Ha, probably not, but I think we're getting closer. Same link has updated version:
    https://gist.github.com/hsitz/ca9c80f1093b39d134a308c638524e28

  • BellowsBellows

    Hi Hes,
    I have something to add also. It appears if you use a plucked sound that decays to nothing that things are working better. But when you use a sustained sound like organ you can see that it is not.

  • BellowsBellows

    Hi Hes,
    Yes we have a winner 🙀🎶. The script is working well now. Very exciting. I am using the Viking synth in AUM and having fun with the internal keyboard. I just want to play with it for a while before I look for limitations.I think the fact that Viking is monophonic May have something to do with its success. I see that if you trill on a m2 interval you can rise through the octaves quickly. I don’t know if that is a bug or not but I like it. Thanks so much for getting us to this point. 🙏
    Bruce

  • BellowsBellows

    Hi Hes,
    I stumbled across an interesting method to accomplish what you have done. I was playing with GeoShred which has a great automatic octave switching feature.
    You can see it here.

    The octave explanation starts at about 5.15.
    Jordan Rudess demos and explains it.
    As he explains the With the auto octave on the software senses any interval larger than a tritone (3 whole steps for instance C to F#) . For instance if you play the G and then C (a major 5th) the next note played will be played in the octave closest to the last note. It works very well in GeoShred and as I write this I am thinking I will try it with my accordion and GeoShred.
    I hope you find this interesting and that you are well.

  • BellowsBellows

    Hi Hes,
    You had mentioned once before using a foot switch instead of legato playing to activate octave switching. At the time I thought you meant on a per note basis. Now I see it as an on/off for a mode. BTW, Greg-V has a new octave feature. When you hold down a note and play a fifth above it plays an octave above the held note instead of the fifth.
    I hope you are doing well. No need to post if you are busy. I have had to take breaks also.👀

  • heshes
    edited April 2020

    Yeah, foot switch would allow up run or down run mode without legato. Right now, a legato step can initiate one of those modes, which stays in effect until legato stops. With footswitch you would go into one of those modes and not be dependent on legato, but for that reason you'd also be in that mode until you turned it off with your foot. Footswitch could toggle between (1) normal mode, (2) up run mode, and (3) down run mode, and could also have a fourth: (4) normal mode, but with legato-induced up or down runs (i.e., what Mozaic script does now).

    That geoshred auto-octave thing looks pretty easy to program. I may get to doing those revisions today.

  • BellowsBellows

    Great to hear from you Hes and I am glad you are still interested in this. Thanks 👍

Sign In or Register to comment.

© Vanilla Keystone Theme 2025