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
Thank you gdog. But I still could not find all 3500 presets within the circled window only 128 of them. Cheers, ED
You have to select the bank first (tap the lower circled window), there are 41, then the preset - can be upto 128 presets in each bank = 3500presets
Unintuitive as heck and rather subpar preset system in this. My video on this app covered most of the functionality btw, if you don't want to read the manual you'd probably benefit from watching it
.
Is there any way to access the sample files used in Quanta 2 factory presets for use in your own presets? If there is, I’m not seeing it.
Apparently only by editing those presets and then saving your own
But this is true to the source simulation of hardware synthesizers, made for the desktop mainly, a long time ago. Cmon Gav!
I thought this thread was all about Quanta 2...
Me too, I almost thought that I’m posting in the wrong thread. 😂
Thanks Gavinski I must do! Cheers, ED
Same, I've had to do a few double takes lol.
Ah OK I got it now. Yep a little wonky way of doing this-agreed Gavinski. Thanks guys I was chasing my tail round in circles, I really appreciate you all in showing me the light. Off to watch more tutorials esp. Gavinski's. You guys ROCK! Have a super weekend to my fave group on earth. Cheers, ED
Hi folks ... can we keep this thread for Quanta 2 please? Also, all these DIscovery posts might be missed in future by someone searching for Discovery information. Thanks
I've yet to read the manual but does anyone have any tips on how to set it up so that when you do pitch bends it will track as expected? On any presets I’ve tried, the pitch is always slightly sharp, so that if I slide from a C3 to a C4, it is playing the C4 as something closer to a C#.
The pitchbend-depth (in Discovery) is set per layer...
If you're using a preset with more than one layer the pitch-bend depth needs to be set for all active layers?!
Or are we back to Quanta 2 now?! (I'm confused since this thread mixes multiple synths).
Ah haha, yes, I am asking about Quanta 2, but I understand your confusion Samu 😅
I guess it's worth to report it to the developer and prepare for some lecturing about how to use their apps.
For me on the 11" M1 iPadPro I can't even see that much of the on-scren keyboard in AUM
And yes, something is wonky with the pitch bend-scaling with the on-screen keyboard...
Not even just with the onscreen keyboard. I also can't get it to work normally with a mpe keyboard like velocity keyboard. I know from a glance at the Quanta 1 thread that there can be various reasons why this doesn't work. I just don't have the time to investigate it properly so I hope someone else who has spent more time with Quanta 2 and who understands expected mpe behaviour can tell me whether there is some kind of implementation failure or bug, or whether there is something I need to adjust to get it to work as expected. I've tried adjusting settings like MPE on or off, pitch bend range etc but have not been able to get pitch working as I want. Thnx Samu
Im getting fairly consistent crashes when making changes to grain pitch in Quanta 2, esp when there’s complex modulation going on. Am going to try and track it down a bit more.
Did the beta end ?
@Gavinski I tried around with Quanta 2‘s pitchbend and after some fiddling i think i found out how to set it up that it works ;-)
On the Settings tab setup
1) the pitchbend range
2) enable the ‚active‘ button that is lit
The active pitchbend-override enables a mode, where the dialed-in factor for pitchbend does not matter as longs as its not its default value zero.
The pitch-bend has to be added to tune of osc1, osc2 or sample tune and its weight needs to be modified from zero.
I checked the correct bending by used an un-bend osc1 (remove the pitch-bend from the modulations) versus a pitch-bend osc2 and pitch-bend sample and tested 3,5,7,12 and 24 settings and they all seemed okay. (BTW, whenever changing the pitch-bend range, the pitch-bend gets re-assigned to osc1/osc2/sample and i had to removed it again from osc1 for every test)
The midi input came from Xequence keys and played C5 with hold enabled which corresponds to the center value of the tune dial, then moved the pitch-bend of Xequnce either to top (+8191) or bottom (-8192) and checked for the correct pitch difference between osc1 and osc2/sample.
@Samu You are right, the on-screen keyboard of quanta 2 does not bend correctly - on my test seemed to pitch only a bit less than half of the selected range.
Wow, thnx Ki, will check that when I get time. I will also email the devs regarding the problem with the onscreen keyboard. Strange that got out the gate with such a major bug. Probably best if other people bothered by this also send them an email. Thnx again
I am getting so many crashes with this, they happen when I touch various places on the UI. Kinda unusable. Lemme know if you figure anything out please!
Sure … are these happening in standalone/AUv3 etc? AUM?
Have you identified any particular UI elements which trigger crashes when touched/operated? If so I can try to reproduce.
Happening in AUM as AUv3. One thing I reproduced so far is a crash that consistently happens when I click somewhere near (but not exactly on, the Settings tab. Roughly in the spot shown in this photo. Btw, those dimmed out
tabs are incredibly hard to read, right? Even at high brightness, but almost impossible to see at the low brightness levels which most iOS users would use to save battery.
That was crash 'fixed' (tap on empty space) in the AppStore version a day after I bought Quanta 2...
...are you running the AppStore version or a beta?
Latest appstore version
Weird, I can't make it crash
(11" M1iPadPro, iPadOS18.0.1).
Are you sure you have the latest version? Because they fixed the brightness after I "complained" to them on Discord. You can see that in Samu's screenshot.
Same, except I'm on 13 inch M1 and on the 18.1 beta. Could be due to the beta, no clue.