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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
Thanks @uncledave, I did see the similarity to ladder logic but your explanation with NO and NC will help me I am sure.
You might relate to StreamByter. In some ways for things like this it can be more compact, sometimes reducing several lines of more procedural Mozaic code to a single statement. I'm much more comfortable with coding in Mozaic, but I can definitely appreciate some of the purpose-built elegance of StreamByter. And, hex is the default nomenclature.
I may do a StreamByter version of this just to dust off my Streambyter skills. I need to do that sometimes or it's like starting over every time. If I do then I'll post it for illustrative purposes.
That would be interesting to try, Streambyter. One reason is that I am experiencing some Bluetooth dropouts. It seems to only happen when I am using a Mozaic script . I am not sure of this but would like to test it out. In fact I think I will play the Hammond app without it for a bit. The problem is it is much more fun with this script and the footswitches.
Bruce
It's highly unlikely that Mozaic is causing any Bluetooth dropouts or is more sensitive to them than other apps. It's the host that manages Bluetooth connections. To Mozaic or any other app it is just incoming midi. It either gets there or it doesn't.
I believe you Wim. It is just a feeling I had. I am trying to figure what causes these drop outs but really have no clue yet. They are annoying but since it is only on the footswitch controls I can live with them.
Bruce
@Bellows : you need two sendmidi> @wim said:
I agree. @Bellows might want to have a MIDI monitor before and after the script just in case something in his script is resulting in some MIDI getting through or not getting through unexpectedly.
Bellows, I see you're being well cared for. Both wim and _ki have helped me with similar challenges. What benevolence!
But for posterity and future lurkers, I want to add the MIDI Designer could probably do this too. I'm controlling my whole complex setup with MIDI Designer. Incrementals ("steppers") are a piece of cake in MD.
Steve
Thanks for your creativity.
Would be useful to have it with a GUI to connect any midi controller to it for up/down increments
That is a fine idea. Actually my original idea was to use this same type of incremental script for program change and CCs each on a separate footswitch as opposed to using foot pedals. I really appreciate compact hardware. My Airturn Bluetooth foot controller Has 6 footswitches in a very small package.
The current script is working quite well for drawbar configurations. I am very happy with it. I added one more step to the sequence. I think it will be useful for other parameters controlled by note numbers. Incremental program changes could be very helpful. Even incremental volume though less expressive than a pedal might be beneficial.
Thanks for commenting,
Bruce
I think https://patchstorage.com/hypno-sequence/ might work for you for this.
👏
I have been experimenting. I did experience the BLuetooth footswitch dropping it’s connection to Audiobus while running only the Hammond app with no Mozaic used at all during the session. No monitor though.
Just for the record, Mozaic off the hook
Bruce
@Bellows My experience with Bluetooth text input keyboards is that they disconnect pretty quickly when typing stops, presumably to save power. When that happens, the next character typed restores the connection, but is not transmitted. This requires some getting used to. I wonder if a BT MIDI source may do something similar. This could be a problem for your footswitches, since there may be significant time between presses. I wonder if it could be changed with the device's configuration app.
My BlueBoard hasn't timed out after 30 minutes of not being used, fwiw
I will check this out in experimentation. It usually surprises me when it disconnects.
I have had a software problem with my footswitches that was solved today by the company. I think there was corruption 🙀.
This may help with my dropouts. I will test more ASAP.
Thanks for your input.