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
I suspect it is due to the difference in their origins. OB-Xd V3 was presumably an update to the earlier OB-Xd on iOS, while Discovery is a new port of a desktop VST. Structuring the parameters so they can be shared with the AUv3 host may be more work than we imagine. The host and the AUv3 plug-in are separate processes in Unix-speak, so sharing data is non-trivial.
The desktop version of Discovery shows all the AUParameters (at least when used with Logic) grouped per layer which allows per layer automation which is not possible by only using Midi CC's which target the currently selected layer.
There are other things that also need attention as well, like how do we edit all four layers at once without having use external keyboard modifiers?
I'm sure that in due time we'll get there...
Also entire code base of original Discovery and Discovery Pro was written years ago by Arguru (Juan Antonio Arguelles) who died tragically in 2007 so i guess current dude who runs company just took it after his dath and probably isn't that good dev (Arguru was genius, such great devs are rare animals) .. but that's just my wild guess which ports of their stuff takes soo much time and there is so much not ideally solved things ..
Last night I spent hours going through all the Discovery presets adding a prefix to each one to indicate their group type ie, Lead, Pads etc. I used the Menu/Overwrite function, but as I discovered a couple of hours later, I also have to tap SAVE 🤬 which I didn’t do!
I contacted discoDSP and asked if a OB-Xd3 DISC tab could be added to make preset selection easier, they replied by saying-
The Disk Mode feature might be a better fit for Discovery Pro. 😶
At least they wrote back to you..
I get the impression they misunderstood your request. You were talking about a discription category. They answered with something about disk being more expensive.
It seems to me a folder structure that splits the presets by categories would be what is needed.
Maybe they can make an iap to upgrade to pro.
Yay!
One small step for a user…one giant leap for DiscoDSP!
😎
/DMfan🇸🇪
With that kind of reply it's I would just return the message and ask when will Discovery Pro for iPad be released
No, I clearly stated that the DISC tab in OB-Xd3 sorted the presets into their instrument types and this DISC tab would be we suited to Discovery
I have asked the question 😉
TBH I’m not totally convinced that the lack of AUparams is down to rushed release or whatever… I think it may be by design.
Since it comes with pre-mapped midi identical with the hardware counterpart, the idea was probably that you can control the hw from sw and/or the other way around (exchange presets, remote control etc). If that’s the concept and default mapping can’t be removed then mixing in param automation would be a good recipe for a lot of user frustration.
Is there a way currently to unbind the default midi mapping?
I don't see why that would normally be a problem. When you control AUv3 parameters you direct the midi to the host's control system, not to the plugin.
Also, in AUM at least, you can allow/disallow individual midi CC's in the channel settings, so it could be blocked there whether or not the synth can un-map controls.
For me in Ntrack studio (ios) it doesnt sound when Ive closed a project until I select a new patch and then select back the one I had previously set as an AU3.
Is anyone else finding this in other DAWs or is it an Ntrack issue perhaps?
Sure, there are ways around it and I wouldn’t expect it to be a problem for you but it may become one for others.
I remember requesting from brambos to allow switching off default midi mapping because it interfered with the rest of my setup - and the solution was to not use the app in that setup/context.
The problem is not necessarily the plugin itself, but the context it is in. Say you have an existing customised template for your controller(s) and Disco port has to be armed for whatever… and while you are controlling your other gear (via param automation) Disco params change in the background without you noticing… or you’ll need to remap everything for the sake of one plugin.
Also the hw integration aspect I mentioned - I can’t confirm but could imagine Disco spitting out CC when param change occurs which may lead to unwanted changes down the chain.
Generally I would say it can quickly become messy when these two methods are mixed in a larger setup / project without careful consideration.
On the other hand I was just speculating after reading some comments, so hopefully it is only late and will work fine once out.
I (successfully) imported a 3rd party preset bank into Discovery standalone, but it is not appearing in the AUv3 version. Anyone know if this is a bug or there is something that has to be done? I don’t remember seeing guidance in the manual about this situation and I can’t see anything in the app that allows me to save a bank rather than just a preset.
There was another update this morning implementing shared storage container to sync stuff between stand-alone and auv3 but still no exposed AUParameters…
Thanks Samu, my god, this really was a hella sloppy port. I hope they up their game for their next release. Cheers for the info.
Downloaded the new version. When I share an FXB file to the Discovery app, the app just crashes immediately. When I add the FXB file directly to the Discovery folder in On My iPad, it does appear in the standalone, but still does not appear in the AUv3. So it appears this functionality is still missing in the updated version 🤷
There is something very wrong with the UI code. Multitouch doesn’t work and the knobs are unresponsive often when compared with other plug-ins. I’m getting audio dropouts with just Discovery in my Drambo project and DSP use is low.
It’s got really bad stuff in the UI code somewhere. It lags like hell trying to drag its windows around the screen in Drambo. Moog Mariana is snappy and responsive, no issues.
They really need to test better, this is really shoddy UI work
It sounds great
I’m only seeing CC7 linked to the Gain knob on Layer One, not the Master Volume. Can’t figure out what I’m doing wrong.
Picked this up in the Black Friday Sale. It’s quite a beast. Tried it via IDAM iPad Pro M1 into a M2 Pro Mac and was getting crackles so must be heavy on CPU or something
maybe depends on what patch and if they're using all 4 layers. I've loaded 2 instances in a Nanostudio2 projects of mine that already had several auv3 synths & fx loaded on a 10th gen ipad and didn't notice any issues.
Just came across this on Patchstorage
2560 Nord Lead 2 Patches. Should be able to load in Discovery if they aren’t already inside.
https://patchstorage.com/2560-nord-lead-2-patches/
😳 2560! nice find 👍🏼
After I load a bank in Discovery, only the first patch in the bank is available. I will try to figure out what I am doing wrong.
I dont even have discovery yet, but I saw this and thought people would like it. make sure to double check directions on patchstorage sometimes there is an extra link provided.
you need the pro version to import these banks
Thank you for the explanation. That makes sense. If I remember correctly, the pro version is not available for iOS.
As an early Christmas present for all members, here are the working sysex banks I found.
About 130 banks, probably some duplicates, already converted to fxb.
The Sven Saur presets from patchstorage are also included, I found them somewhere for Discovery (not the Pro version).
If anyone finds a commercial bank in the zip file (but I don't think so), please let me know. I will delete the bank and upload a new zip.
Thanks for sharing! Wow, there’s more presets than I know what to do with already with this synth. Now it’s just a mind-numbingly huge list.