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
@wim As I thought, your Midi CC Morph Pad script is awesome fun with the Novation CIRCUIT macros. Just needed to change CCs to 80-87 and was jamming those mods like crazy. Great stuff!
I still haven't bought this yet. I read these threads and all of the back and forth regarding coding details... and I back off from buying.
Please don't take this as any slight... but has anyone here using Mozaic, created a script, or used someone else's to create a piece that they couldn't have made with apps they already have or are already available? If so, got a demo video?
@brambos I do think a little demo video walking through something simple would be of help getting some of us off the fence on this.
I remember all of the back and forth in the threads regarding Modstep. All of the language and descriptions sounded so complicated and foreign that I never felt like I could grasp even the basics. Then, I actually bought the app and watched a few videos. I discovered that it wasn't' anywhere near as complicated as I'd assumed based on the long esoteric threads here on the forum. It was actually a lot easier to learn and pick up after just a few of Jakob's basic videos.
If there was a quicky walk-thru making something simple. And then showing how easy it is to use other's scripts... it may take some of the mystique out of it. Just a thought.
To be honest, I haven’t used it yet myself, so it’s good to hear someone is.
Gonna enhance it with some of the great ideas offered here soon I hope. Problem is I keep getting too many ideas for new scripts! The possibilities are endless.
Having the ideas is the best part!
Quick question, not sure if it’s answered earlier in the thread. Is there any issues with Mozaic au parameters in AUM?
I fired up TC DATA and assigned the 2 CCs I had set up there to control the XY pad of Mozaic within AUM but no effect. All the channels, numbers and sources were matched correctly.
Anyway, loadsa fun. I was just trying to get a bigger XY pad using TC-DATA.
I'm not in a coding from home mood at the moment either but the scripts people are coming up with are worth the investment and a good starting point for tweaking.
The way I see it MIDI isn't going out of fashion any time soon and Bram needs to fund his coffee somehow.
Hmmm... that might be enough for me. Even if I have no interest in learning Mozaic’s code language.
@brambos would it be possible in theory to set up a script with Mozaic to use a Bluetooth qwerty keyboard as a midi controller?
Heh. Interesting. Not right now, since keypresses aren't received as user input events, but it should be possible to do something like that. Let me ponder that one...
That would be great considering the Mozaic AU already has access to a bluetooth keyboard, would be possible to make some really interesting uses for it.
I think the trickiest thing would be introducing a 'mode' where keyboard input is routed to the UI instead of the code-window (the tricky part obviously making it non-obtrusive and non-confusing, because 'modes' are like UX boobytraps in that regard ).
Yeah that’s true, maybe if it’s just simply when the code window is not in view and it’s in controller view only?
It's not perfect but that mode does exist and it's called "Accessibility Control" in iOS
(Settings > General > Accessibility > Switch Control). Search the forum here, a while ago I've given detailed instructions on how to set it up.
What you do is map gestures to BT keyboard keys. These can be short taps, but these can also be slides, turns, two- or three-finger gestures etc.
I don't know however if the knobs and faders in Mozaic support it (StreamByter does ), they would have to evaluate slides and turns on the control no matter what the current value is (kind of a general increment/decrement gesture).
The disadvantage of this mechanism is that it depends on a fixed position of on-screen controls, so you better don't touch that AU window!
There are apps that use user input events from the bluetooth qwerty keyboard, f.e. Garageband: when I hold the cmd-key I see a dialog with 5 pages of keypresses that I can use!
@brambos I saw a pic the other day of the Bluetooth keyboard you have with the little yellow dial to choose which iOS device to switch to. I thought hmm, I have that same keyboard in the closet and it’d be cool if I could control iOS audio apps with it. Did something similar back in the day with Ableton, scripts and a gaming keyboard. +1
The keyboard connectivity can be handled by SideCar (formerly Double Decker).
"Use an ordinary Bluetooth QWERTY keyboard to add a wireless MIDI controller."
WebMIDI and WebBluetooth can also be used to translate keystrokes to MIDI messages. I keep waiting for that to take off.
Top-tip! I never had a BT keyboard before, but now I should really try this out
Yeah Sidecar is pretty useful but only 10 keys are configurable, so being able to control via Mozaic directly and configure any key would be a much better experience by comparison. Plus you need to use slide over view with sidecar.
Here are three scripts I wrote based on Arthur Kerns' excellent (and free!) midiFILTr-PG Probability Gate MIDI Effect. The only issue with Kerns' midiFILTr-PG is that it is not AUv3, so you can only use one instance. But now with these Mozaic scripts you can have as many instances as you need.
nice one
Here's a script snippet i wrote that implements double-tap and tap-and-hold gestures on the pads. This is useful for extending the functionality of the limited GUI options.
@Bryan Cool idea - i added multipad support and restructured your code a bit
Speaking about BT keyboard, would it be possible for the editors to scroll to the cursor position ?
Yes, it’s on the list, but I haven’t gotten to it yet
Just released version 1.0.2
User Events
You can now define your own user events for more efficient reuse and separation of code:
Array initialisers and array copying
You can now initialise arrays (and copy them) in a more efficient way:
Improved timing of received MIDI events
Due to different (rounding) implementations of various MIDI sources events could be received just before, on, or just after a new beat starts. Not nice if you want to make a MIDI looper or recorder. So this has now been made more robust so that any events coming on the beat are actually captured in the correct beat.
And many other things.
Many nice things still on the to-add-list.
Time to write my looper
I’m interested in how you plan to record more than 1000 notes with the arrays limited as they are. I guess allocate more than one, then chain them?
I checked out of this thread for a bit... are all the scripts being kept in one place? ie. was there a host platform that was decided upon for Mozaic scrips? Or, are they pretty much all scattered around this and other threads?
Kinda curious if there's one place to browse all the groovy scripts created and shared thus far.
The unofficial location until something official comes along...
https://wiki.audiob.us/mozaic_plugin_engine#user_contributed_scripts
Maybe not all, but all those people have taken the time to post.
Interesting!
By which events, apart from "OnLoad", can user events be triggered?
@brambos: Loving Mozaic. Was able to quickly whip up an interface for toggling the mute state of Loopy tracks. I would love it if pads could take a number that set the pad color -- and also if individual pads would have labels.