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 @Gravitas
I’ve done 4 stepped tempo changes, with 5 minutes intervals. Start at 120>75>145>30>120.
AUM metronome (L) against CLOCKED driven 808 Rim/Claves (R).
I don’t know if relevant
iPad Air3 13.7 / no audio interface / AUM 48kHz 512 buffer size
5 audio clips were recorded from headphone out for each method (start + 4 tempo changes)
https://www.dropbox.com/s/2xjbnous5hg74pd/BPM.zip?dl=0
https://www.dropbox.com/s/3pakjrk6mnqwzt5/CLOCK .zip?dl=0
Wanted to make some screenshots but to make a point it would require so many at various zoom levels so decided against it. Better to hear and look at it for yourself.
@wim
You were spot on.
My takeaway is that if I were to do a live set with tempo changes I would figure out a way to combine them.
edit:
CPU was basically the same in both cases. 2-4%... not a single peaks around tempo changes... seemed like it only moved from 2% because of the UI interaction (changing bpm).
Thanks for doing all that testing. It's always better to gather objective data. I usually start with the "objective" assumption that I'm always right and don't take it any farther.
@0tolerance4silence @wim
Thank you both.
Lololol this made me smile.
🤣
@mifki its possible to add some more cable colors please???
Earlier in the thread someone suggested initial drag direction as a possible method for selecting cable color. I think that would be a great way to support 8 cable colors. (Left, right, up, down, and the 4 in betweens)
Hm I missed that, interesting idea.
i can see it a bit improved - after initial drag, circle color picker appears around connector - as soon as you enter some color area with dragged cable, it switches to this color (i mean cable). As soon as you leave outer cicle, color picker disappears ...
Agree on more colors being useful !
Another argument is that Chris Meyer in his quite useful book (with Kim Bjørn) and his learningmodular.com courses uses a system with
white/grey for v/oct,
blue for modulation,
green for clock,
red for gates and
yellow for audio,
which seems like a tidy system for color-coding. But to implement it we would need at least an additional cable colour (the white/grey one). and as others have suggested, a intentional way of selecting color would be really nice as well.
In case you are interrested the book is here
https://www.kickstarter.com/projects/1795693416/patch-and-tweak-exploring-modular-synthesis
and his courses can be previewed with a trial membership on "linkedin learning".
I would like to see a few more colors. I try to use each color for specific functions though for audio, since there are stereo options, I like to use green and red (green if its a mono signal). Then yellow for clocks, gates, command signals like reset, and blue for CV. A few more colors would definitely be handy. As for selecting which color, I’m ok with the current method...I do a ‘tap - small slide’ to see which color comes up and when I see the one I’m looking for I continue to drag it to the destination. The colors cycle thru so it doesn’t take long. However adding many more colors would make this method considerably less efficient. The idea of an initial direction would be a good solution for this.
Okay, here's another basic question.
I've connected up the Modal synth module with the Basic Midi module.
I'm getting sound, it changes frequency as I play it using my
midi keyboard but it inverts the velocity for some reason.
When I play quietly it plays loud, when I play loud it plays quietly.
Is this expected?
What do I do to make it respond to velocity correctly?
Thank you in advance.
Edit.
Here's the screenshot.
Does the same on mine. Have the velocity control the volume with a dual vca after the synth module.
@Jocphone
Thanks for confirming this.
I was thinking to try to invert the signal in some way
as the inbuilt tone changes according to velocity.
Still, if it isn't possible then a dual vca is the way.
According to the manual, the Strength input isn't exactly a volume parameter, and more importantly, it's bipolar whereas midi velocity is not:
So, it's only amplifying the excitation signal, not the overall volume to begin with. But also, midi velocity output is 0V - 10V, or 0 - 30dB, when it would need to be -5V to 5V to work as expected, I think, but as mentioned, would only affect the strength of the excitation signal.
@mifki any chance the strength input on the Audible Instruments Modal Synthesizer is inverted?
I read the manual entry for the real thing but it appears to work opposite to what @Gravitas and I would expect when fed with a velocity signal.
Okay, I've got Ableton Link working now.
It has been the most consistent so far.
I'm going to give another couple of days of testing
but after twenty minutes it's holding really well where
as with host sync it would've skipped a beat by now.
Hm it is indeed inverted, but the original Mutable Instruments code seems to be doing exactly the same. I need to do some research to see what's going on there.
How does velocity output, which goes from 0V to 10V map to an input that goes from -5V to +5V?
I don't know, from the Mutable Instruments code, I can't see how it can do what the docs say. For now, just use something like this to achieve the correct behaviour:
Could it be that we are misinterpreting what the docs say the strength input is for?
Either that or this defect has always existed in the opens source code and needs correcting for all implementations? Seems unlikely as Mutable Instruments code has been quite popular.
Thanks for this.
I think I see what's wrong there. I'll fix it I guess, even though it might break existing patches...
If it's doing the wrong thing it should be fixed I think. Wouldn't have thought there would be a number massive number of people using it if it only just came out that it was inverted.
+1 Was just wondering if there is a tip jar.
Most module developers I've seen have some sort of way of contributing if you check their web sites.
@mifki
I've encountered a couple of bugs.
Where do I send the info?
Via here or via email?
Downloaded miRack earlier this week and am having a great time with it so far, but am I completely missing something or is there no way to display/input parameter values?
I hear you.
Have a look in the utility section?
There maybe something there that you need.
Ah, thanks, that’s something. Though it’d be ideal to have (for example) long-press automatically display a value input box.
@shortsadvocate
I think it's like that by design.
It is emulating analogue equipment after all.
I'm quite new to it myself so I'm learning as well.