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
So, I'm on Big Sur / M1 Air, and Wotja 22 is crashing when it's scanning its own plugin? But I don't see anything in Components folder?
Could well be another plugin I suppose - I just looked on the web for the name as an audio unit plugin - I don't have 1st hand experience of it. I'll do some more research...
Wonder if this might fix some of the problem plugins on macOS too?
The plugin for Wotja is an AUv3 so it's not stored as a .component file in the /Library/Audio/Plug-Ins/Components folder - that's where AUv2 plugins are located. The other issue is that the plugin name you see in the 'scanning' list at the top of the window may not be the one causing the crash - sometimes the offending plugin name is only displayed very quickly and it's easy to miss.
Hmm, what's the best solution to complete the scan?
Which device / OS? On an iPad it's generally Atom 1 and 2 and MIDI tools, all by Victor Porof, that are known to cause a crash, so removing those temporarily will allow the scan to complete, and you can reinstall them afterwards. Wotja won't rescan unless triggered from in the app or after a complete reinstall (I believe, perhaps @impete can confirm?). A couple of users mentioned Kaspar might also cause an issue, but it didn't for me.
On macOS, the culprits are likely to be AUv2 plugins which reside in the /Library/Audio/Plug-Ins/Components folder. It's safe to move this folder temporarily, load Wotja (which should then complete the scan), and then replace the folder. Obviously, no AUv2 plugins will then be available in Wotja but until there's a more permanent fix it's the best way to get Wotja running.
I offloaded MIDI Tools, scanned, and then re-loaded MIDI Tools. Didn’t have issues with anything else.
Link in OP is dead now. Which I guess makes sense if it's released and pre-order is not relevant.
However, perhaps add a link to the app / details to OP for people like me seeing this thread for first time and interested to take a look at the app? Cheers.
It's easy to find info by navigating from the broken link of course, but if you have Edit still available on the post it may be worth adding.
https://intermorphic.com/wotja/22/
Almost certainly; it is common code!
Best wishes, Pete
Thanks for letting me know; I’ve passed that on to Tim! 👍
Best wishes, Pete
Unfortunately, with my first 90 seconds with the free version of 22 app, I've had 5 crashes.
This device is on 13.4.1
Known issue with older OS?
EDIT: At least a dozen crashes now. Looks like the app opens, scans for midi apps then crashes 10 seconds later. Every time.
Fixed - thank you very much!
Pete
Hi! I've been hoping to hear from an iOS user with 13.x - Apple added AUv3 support with iOS 14 - and we've not got any old iOS 13 devices for testing.
Having heard from you, I think that I will change the code such that if we detect iOS 13 or earlier, we don't scan for plug-ins.
I'll do that as soon as possible. Probably 22.0.5, which hopefully will be in a few days.
Best wishes, Pete
Hi @impete Cool. Happy to hear the bug report ws useful. All the best!
The support here for Wotja 22 has been incredible. Thank you all - you know who you are
Best wishes, Pete
Nice one @impete - I'll keep my eyes open for 22.0.4 on Testflight and report back asap...!
Lets see how this build works - I'm hopeful, of course
Best wishes, Pete
Hi! As noted elsewhere, I hope that 22.0.4 will fix the problems. Time will tell if we're going to need a further update beyond that!
Best wishes, Pete
Just thought I'd say that, without honest feedback from both existing and prospective customers, it is very hard for us to get things right. So, we truly appreciate all the support and comments we've had here!
Best wishes, Pete
yes, please...I am using iOS 13 and can't get the new Wotja to work at all - constantly crashing due to the scan (and I would be happy to just use the non-hosting features)
Great news. Thanks for your rapid efforts.
Hi folks, so I've tried using Harvest MINI (which is free) on my M1 Mac. However, I get this:
So I guess it isn't signed properly?
Pete
Any clues on how to use a plug-in chain? I’ve set an instrument but don’t know how to reference it in a mix.
Just documenting now!
Rough draft docs are here:
Wotja 22: we've added added support for plug-in hosting by the main Wotja app (iOS, macOS, Windows). Plugins can be in AUv3 format (iOS 14+, macOS) or VST3 format (Windows 10/11).
The hosted plug-ins as an "external" to the main Wotja application.
You can view the hosted plug-ins in the new Plug-ins tab.
Wotja plug-in hosting works by presenting you with a number of Chains of Instruments / FX. The first several chains are "Instrument" chains, that allow you to (first) choose a 'source' instrument (AUv3/VST3, depending on platform) in the first 'slot', and one or more FX in the following slots in the chain. The last chain is an optional Master FX chain, where you can have zero, 1 or more FX that are applied the summed output of all Instrument chains.
Instrument chains
There are X of these. You can use as many, or as few, as you want.
Instrument slot (the first slot): Touch/click the slot to browse from the available instrument plug-ins. Choose your favourite instrument plug-in!
Wotja Instrument: the "final output" from Wotja's Mix-level effects is presented as a "Wotja Output" 'Instrument' in the plug-ins tab when you try setting the instrument slot browser. If you select the "Wotja Output" as 'Instrument' for an FX Chain, then you can of course add other AUv3 FX within the chain to further treat it.
Wotja Instrument - audio filtering: By default, your Wotja Mix output in a chain will have output from the Mix FX. However, if you only want it to be driven by the sum of Wotja outputs from Tracks 2 and 3, select these tracks as your Track filter option.
AUv3/VST Instrument: create a chain with your fave AUv3 Instrument as the Instrument
*AUv3/VST Instrument - MIDI filtering: The instrument you select, gets its MIDI data from all MIDI data delivered by all Wotja tracks. However, if you only want it to be driven by (say) MIDI channel 2, select this as your filter using the option you see in the chain.
Chains - how they're mixed: If you have 2 or more FX chains set-up, then simply adjust the relative outputs from the two chains using the Sliders at the bottom of the chain - they're all added together.
Master FX Chain
You have a Master FX chain at the end, where you can apply AUv3/VST3 FX to the summed outputs of all the other FX chains you have set up. You can configure this to use zero, 1 or more FX that are applied the summed output of all Instrument chains.
Slot menu: Menu icon might show on right of the slot, if you have certain extra options available to you.
More info
** Hosted plug-in Scanning **
We're still working on this, but for now the initial scan of plug-ins is done automatically.
We are aware that this doesn't always work well, especially on Windows.
Refresh/rescan from the plug-in browser screen, select the button (show icon) to re-scan.
AU 2 not all plug-ins are supported, depending on how they are signed
Hope this helps!
Pete
Folks - I think Harvest is the only macOS plug-in causing problems. I've contacted the developers.
If any of you are in touch with them, perhaps you could point them to this forum, or towards our contact form; clearly, we'd like to track down and resolve this!
Best wishes, Pete
Thanks for the heads up on the manual for plugins @impete - it’s all fairly self explanatory but good to have it laid out anyway… I can’t quite figure or is it’s possible to swap, remove, or change the order of plugins within a chain or not though…
Is it planned to have the external plugins more closely integrated with the network as time goes on, or will they stay where they are now?
Quick update - the latest iOS beta which @impete has been working hard on doesn't crash when scanning with all the previously troublesome plugins installed (Atlas, Miditools, Kaspar)...winner winner chicken dinner...!!
Thank you for the fast response, Pete! I have Sunrizer patches playing now as a proof of concept. Though I did manage to trigger a crash. I’ll see if I can duplicate it.
Hi! The way to do this is to use the Action menu to export/import...
You can also import/export chains - it is very powerful!
I think the way we have it now, as a nice, cleanly separate part of Wotja is pretty good. So it is likely to stay as it is.
The internal plug-in system we use is much more complex / demanding, dealing the complexities of polyphony limiting etc. etc. - no room for external plug-ins in there
Best wishes, Pete
Ah brilliant, thanks Pete, I’d been trying to drag up and down with those three bar things, I never thought to simply tap on them, what a dope 😆
Nice one, all works a treat now, and with the routing into the chain via the output instrument I can get my head round it all a bit better… now to really focus on how the generator work 😁
Cheers fella!
Chris