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
Hey @hypnopad , please try out version 1.1 when you get a chance:
If it looks OK then I'll upload it to patchstorage.com.
I overhauled quite a few things. You can now save up to 16 sequence presets in each instance. Once saved, presets can be recalled and loaded by hitting a note within a range of notes that you define. Reset can also be done with a user defined note. This scheme does depend on assigning a separate channel for those notes.
I also added a setting to temporarily enable setting notes for a step by sending the note. Set it back to normal mode to re-enable controlling the sequence. Selecting notes with a dial was getting tedious, so I added this feature. Just ignore it if it's not helpful for you.
Since I ( surely unwisely
) didn't take @_ki up on his kind offer to add migration code, please don't invest too much time into setting up sequences until we're confident that the release is good to go.
HYPNO SEQUENCE - Custom Round-Robin note sequencer
Script idea by Audiobus forum member @hypnopad. 👏😎👍🏼
QUICK START: Set a sequence length, then tap a pad and set note, gate, and velocity for each step. Velocity zero is a rest (no note will be sent for that step). Send notes to the script. Each note will trigger one step and advance to the next. When the last note has played the sequence will start over. Tap SHIFT for advanced controls (see below).
more...
ADVANCED: Expanded Controls Page - accessed by tapping SHIFT
▫️ CHANNEL OUT: You can choose to have steps output on the channel that triggers them (Ch. In>Out) or choose a fixed channel.
▫️ 🖊 STEP: You can choose which step to edit with this knob rather than tapping on the pads. This is handy for working from this page or for selecting steps from a midi controller mapped to the AU parameter for this knob.
▫️ RESET NOW: Turn this knob past 12:00, or double-tap it to reset the playhead of the sequnce to the beginning. You can also Reset Now by long-pressing any pad, or by sending a configurable note. (See SETTINGS below.)
▫️ RESET TIMER ⏳: This sets an inactivity timer. After a note is played the timer starts counting down. If it reaches zero the playhead is reset automatically. If a new note is received the timer is reset.
PRESETS
Each instance can save up to 16 sequences for instant recall.
▫️ PRESET: selects the preset number to save or recall, but doesn't load the preset.
▫️ SAVE: Turn the knob past 12:00 or double-tap it to save the current sequence to the selected preset number.
▫️ RECALL: Turn the knob past 12:00 or double-tap it. The current sequence will be replaced by the sequence saved in the selected preset number.
▫️ RECALL BY NOTE: Presets can be instantly recalled by playing notes on a special Control Channel. (See SETTINGS.)
SETTINGS
▫️ INPUT EDITING: Normally notes advance the sequence or do control tasks (🎶 Normal). You can enable notes to change the note of the currently edited pad instead (🎶 = Edit). Remember to change it back when done.
▫️ CTRL CHANNEL: Select a channel to receive control notes. This channel will NOT be used for advancing the sequence. Any note on any other channel WILL advance the sequence. You can disable control notes by setting this to OFF.
▫️ RESET NOTE: Select a note that will RESET the sequence if received on the Control Channel.
▫️ PRESET RECALL NOTES: This is a range of 16 notes to be used to instantly RECALL a saved sequence. (See PRESETS above.)
▫️ NOTE: Reset Note and Recall Note Range can't overlap. The script will relocate the Reset Note if it needs to. Keep an eye on both settings to be sure they don't rearrange unexpectedly as you set them.
▫️ THRU: When set to OFF, no MIDI passes through the plugin. The only output is the sequenced notes. If set to ON, MIDI messages other than notes pass through the plugin. (Notes never pass through.)
ADVANCED GEEKERY:
Many things can be pretty safely customized in the script without scripting knowledge. There's a @UserTweaks section at the top. You can change things like the order of the knobs, most of the defaults, and even the pad colors just by changing the part after the "=" sign for the parameters.
The most important setting is the assignments for the first four knobs, which show on the pads view. Knobs numbered 0-3 show on this page. You have to press SHIFT to see the rest, then you can't see the pads any more until you press SHIFT again. But there are a lot of other useful defaults you can set to save knob tweaking on new script loads.
Just be sure you don't have the same number for any two pads, don't assign any numbers over 21 to the knobs, and DON'T DELETE ANY SETTINGS. 😎
@hypnopad or anyone else - sorry, I found a bug already. I re-uploaded to dropbox. If you haven't already downloaded the one above then you're OK otherwise, please delete that script and re-download.
@wim First off- I can tell this device is going to meet my needs perfectly.
First impressions.
A couple buggy things to report and a couple ranges to adjust:
1. Velocity KNOB goes rest-1-130 instead of rest-1-127-play thru. Pad and upper window show the correct readings.
2. I think the note gate time should be biased lower. 1/64-1/32-1/16..... 1/1 should be good. Instead of starting at 1/16. (I’m looking at the desktop software and hardware round robins for these appropriate ranges).
3. I also think the timer should be biased lower. Roland drum modules ( where I first experienced round robin technology) start at .1 seconds and go to 8.0 seconds max in .1 sec increments. I really can’t see the musical usefulness above that time.
4. Reset range starts at E0. Why not earlier? No biggy. Just curious.
Like the keyboard input mode!
Will try a song tomorrow to test it out further.
It looks great... Thanks for adding the optional input scheme. After setting the notes it doesn't seem to go into a play mode when triggered with MIDI input.
I experienced the same thing. You need to set it back to normal mode on the twelfth knob on the second page.
Thanks - a labeling issue. Fixed.
Sure, that's one of the defaults that is easily customized in the
@UserTweakssection at the top of the script (default_ppqn). I'll make 1/64 the pre-set default so people don't need to.OK, that'll take a few more modifications, but will be easy.
I don't understand. There is no reset range. There is a reset note, which defaults to B1, and a preset recall range that starts by default at C2. I think you must have inadvertently adjusted the preset selection range. This makes me think that there should be some sort of a "lock" for those settings.
What would you say is a logical starting default for "reset note" and the lowest note of the "preset selection" range of notes?
That's by design so that you can pop around inputting notes on different steps until you're done.
...unless I'm misunderstanding you.
Is it OK if this just climbs in 1/64 increments, or at some point, for instance after 1/16, should it just go up in 1/16 increments? Or, does it double each time? 1/64, 1/32, 1/16, 1/8, 1/4, 1/2, 1/1? The easiest is just to have it increment in 64ths, but then you get a bunch of weird fractions like 23/14.
Would like to do it in a way that people might be used to seeing without going overboard on the complexity since after all, it's just a gate, not a note quantize.
@wim I have downloaded and added the Migration Manager, and am currently testing the migration feature. Hope i got the latest version.
In the one i updated, i had to fix a typo
I made it the note just before the preset range.
As long as it’s contiguous ( just below or above) I think it’ll be fine.
If you’re asking about hardwiring the note ranges, the lower the better.
The doubling is what I’ve seen in most instances. Yeah, it’s just note length not delay time where you’d want dotted or triplet values.
Thanks @hypnopad.
The timer change and other bug fixes are done. I can easily do the two changes above tomorrow.
Hello, everyone! Recently I discovered Drums Marbles scripts and they pair perfectly with Ruismakers. Kudos to TomSimmert. Also I thought can it go further to Mutable Grids? I saw m4l port but I'm not sure how is it possible to implement Grids drum maps into Mozaic structure? It's amazing for quick and creative drum programming and would make killer combo with all auv3 drum machines we already have.
@wim I finished testing the migration feature.
I had to update the Migration Manager to v1.1 to simplify integration with further scripts.
It was good task that i tried the integration, as your scripts uses an own timer but that‘s a) not running all the time and b) is too slow for the migration timeouts. So came up with a structural change in the manager, and was able to find a solution on how to cope with such cases.
During migration, i start your scripts timer with a different interval - when migration is done, the change is un-done
I uploaded the changed script and a text file describing the changes as zip to google drive
This is a great script, thanks @wim and @hypnopad
Thanks. I’m really happy how this script has turned out. It will fill an important niche that was missing on iOS. I feel lucky that @wim took the time to do this. I know from perusing the forum he seems to be one of the busiest/helpful members.
@wim is near the top in terms of forum human resources. And this script is a thing of beauty. Gotta put @_ki in the same category. Starting to feel like the Max 4 live community.
When I saw your GUI mock-up I thought that's a LOT of work and will be tricky
to get right... only @wim or @_Ki can probably make this well. And now you've
got them working together making it solid.
It's great when a problem is interesting enough for him to tackle it.
This will be a great script and serve to illustrate some great GUI tricks for
programmers to study and see how it can be done right.
+1
Also big thanks to the max 4 live devices this is based on.
Oh yeah, thanks to @_ki too for his additional wizbottery
Hey all that have tried out the Hypno Sequence script...
Glad you like it.
But please keep in mind that these are preliminary releases still with a few bugs and things that will change. Any work that you do in these won't be compatible with the newer script.
(Your host sessions saved with the old script will still work though since the session saves everything, including the script.)
Hopefully the final version will be today ... if I don't screw anything up.
@wim Did you pick up the modified v.1. script i supplied on the google drive ? Otherwise you can upload your latest version and i‘ll re-do the changes to that one - does take only 5 minutes, as i have documented all needed changes
@_ki is the master. It will be a long time before I get anywhere near his skill level. And even then I won't have the tenacity and discipline to do what he does.
I can't wait to take a look at this. I've been mulling over the approaches you might have taken to accomplish this. I look forward to seeing how you've done it.
And I know I've said it before, but can't say enough how much I appreciate your Textastic syntax grammar extension. I doubt I would attempt half of the scripts I have without it. It would be just too frustrating and slow.
Mozaic is great for generative stuff, but not as great for things that require a lot of fixed pattern storage and playback. I expect that miRack will have midi out soon. When it does it'll be a much better solution than trying recreate this in Mozaic.
@lazyass
So it's kind of like Reactable's SNAP, but with the "pattern" or "order of which notes to add or remove" selected using an XY grid.
I have a halfway finished script that basically does what you're asking, and with the way I've designed it, I don't think it would be a problem to have 256 different drum "patterns". I would assume that's how many it has, to stay consistent with the density knobs. Do you have access to a Mutable Instruments Grid?
You would have to know what the patterns are and enter them in yourself, because my script definitely won't ship with any patterns. Instead there will be a pattern editor, and you'll be able to export your pattern data, and copy it into the code to save it. If I add functionality for 256 patterns, it will probably come as a sequel to the first script, later this year.
Today i run into ‚maximum script size exceeded‘ errors after successfully dancing around the 80 event funcs limit the days before .
For the script length you don‘t get a warning, but instead the code at the end is silently omitted. To have an eye on that i‘ve (temporary) added a LengthGuard event with Log output right as last lines of the script that‘s called at the start of the OnLoad - if the script is too long again, i‘ll get a ‚Calling undefined event‘ error
I‘m nearly finished with that MutatoR script, probably needs about 20 more code-lines, but these are too complicated to figure out tonight - and i also need to condense the other code to be able to add this many lines
In my case the Mozaic script is 112 kilobytes long with 3240 lines.
I will be so glad when the MutatoR development is finally over and it‘s published. I started in january - but there was a big two month pause due to scripting fatigue
Hiya @hypnopad , @McD , @lukesleepwalker , @_ki
I've uploaded Hypno Sequence v1.10 to patchstorage.com. I think I have all the kinks ironed out at this point.
I didn't fully appreciate the concept until I spent some extended time testing it. It is actually really fun. Unlike most of my scripts, I may actually use this one. 😂
Thanks very much for taking the time to do this. I decided not to use it in this script since I feel like I need to fully understand most things I drop into my code (or have someone else drop in) and I didn't want to divide my attention half-way in. I'm definitely looking forward to seeing how it works and am sure it'll be a great help in the future.
Unless there are bugs to fix n this last script, I'm gonna take a little break from Mozaic scripting and get back on track learning (struggling to learn
) iOS AUv3 app development. That is until the next time I feel like my head's going to explode and I need to get back to something I can actually do for a bit.