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
… which in turn can be addressed by scripting commands… Aargh. There goes my head again all over the wallpaper.
Just to add: if you're using an iPhone and didn't select iCloud for storage, mixes composed in previous versions of Wotja are saved in separate folders so they don't appear automatically, but you can move them manually in the Files app. Annoyingly all the folders are called 'Wotja' so it's not immediately obvious which is which.
Splat
Just my 2 cents opinion, to so speak - but using Wotja cross-device is much easier if you use iCloud for storage; even if you only use it for the Wotja app, and nothing else!
Pete
I am having great success with the AU3 version and AUM. So far I can’t really get the AU3 version to route MIDI inside Cubasis. I’d like to be able to easily record the MIDI notes into several Cubasis MIDI tracks (similar to what I used to do with Logic/Noatikl AU). Has anyone had success using the AU3 version outside of AUM? I am able to use the stand-alone with Virtual MIDI with Cubasis but I am unable to get the MIDI transport synced outside of the AU3 version with Cubasis.
Hi
Trouble here too in Cubasis 3.
I load WJ into a Midi track as an AU. In WJ I set the MIDI output to CB and disable the internal synth (ISE) ... and turn off Patch Change sending
The WJ project has 1 track, 1 cell with 2 generators. One generator on midi ch 1, the other on midi ch 2.
In CB WJ now starts and stops playback with CB transport.
On the WJ Track in CB I can see all the WJ MIDI input sources. Omni, Channels, tracks. I set this input to ... hmmm.... well that’s a conundrum. WJ is going to send on multiple channels. Omni will probably de channelize? Choosing a particular channel will ignore the others? So for the tile being I set the midi input to All Ports. ( this might be as issue later... ).
Of course the WJ track in CB doesn’t make any sound ... WJ is the instrument. So now I make another midi track in CB with a piano, set it’s midi input to WJ midi ch 1. Play. Nothing. Switch the midi input to WJ Omni. Again nothing. Switch it to All Ports ... I get some WJ notes!
Seems to only work on MIDI input= All Ports
I can’t get input from the second WJ generator on midi ch 2 no matter how I configure the midi settings in CB.
It appears to me that the individual WJ midi outputs just aren’t working in CB in an AU instance? Selecting All ports I think is getting a dump of all the WJ notes.
Now in the user guide it states that the AU version doesn’t support Virtual MIDI outputs... but that does t refer to the inputs shown inside CB does it?
Any clarification from impete would be greatfully received! For now though back to my desktop...
Hi @ltf3 and @oldlibmike
There is a bug in the current version of Wotja that we spotted last week, which is fixed in version 26.1.0 (coming in a day or 2), where the MIDI for different virtual MIDI ports wasn't routed properly - too many Channel's worth of notes were going to say Wotja MIDI Channel 1 Virtual MIDI port.
That said, an AUv3 for iOS isn't allowed to create virtual MIDI ports, so you'd have seen this only with the Standalone Wotja for iOS / macOS, or the AUv3 for macOS.
I know zero about Cubasis, alas. I think to figure out MIDI routing in Cubase might require asking in their forums. If you find anything, I do hope you'll share what you learn!
I think that to get the routing you might want, either requires input from some Cubase expert; or perhaps requires the Standalone Wotja in combination with (say) Ableton Link to handle the synchronisation.
With best wishes,
Pete
Thanks Pete... you are probably correct.
Midi routing is just a pain in iOS. There’s so much potential but implementation is a mess .
If it helps anyone else I had some success by running Wotja outside of Cubase with sync via Abelton Link. Although CB doesn’t support Abelton Link directly you can rig it by running an AU in CB that does!
I add EG Pulse to a track. It syncs to CB because it’s an AU. Now tun on Link in Pulse. Run Wotja separately outside of CB and let it connect to Pulse’s Link sync. When CB runs, Pulse does too and that in turn keeps Wotja running. Works well enough. Now the MIDI outputs of Wotja will be available as midi inputs in CB for recording.
But on the whole it’s more fun on the desktop.... just is.
I actually got Cubasis and NanoStudio 2 working with the AUv3 Wotja finally! In Wotja, I had to select the output destination and manually select either Cubasis or NanoStudio2 as a destination. Once I did that, filtering each track to "all midi source" and a selected channel number seemed to work perfectly. I didn't get state saving to work quite right but if I manually save things seem to work pretty well. I concur that MIDI on iOS is always an adventure!
This might sound surprising, but I’ve only recently started using Wotja on the iPad. So I know little about advanced midi routing there. But I have to say that, while I still stick with the desktop most of the time, the one thing that has become an absolute joy is building up synth and fx chains on the iPad using an Apple Pencil.
I like it so much that I’ve started to use Sidecar on my studio Mac to shift the desktop version over to my iPad to work on synth ideas that way.
For me it’s feels a very natural way to work. There really is something quite satisfying about interacting with the synth engine in this way. And it’s way more accurate than using a mouse or me poking at a screen with my big fingers. It’s very easy to make small changes.
It’s quite the game changer. It’s still different but it bring it much closer to being as involving for me as working with hardware synths is.
Revisited my setup and with WJ running as an AU in CB3 it definitely only sends/receives on MIDI ch1. I’ve verified this with a midi monitor running in CB.
Unless somehow my WJ is running in lite mode ( ie 1 midi channel ) I don’t see how it can work. My standalone instance has a ’Pro’ label... nothing to indicate on the AU version.
Nice update.👍
Just an image with Wotja as AU3 on top. After recording in Cubasis you can see different notes/patterns going to 2 tracks on midi channel1 and 2 respectively. @ltf3
EDIT - worked once but not consistently. So....still a bit wonky.
So, @oldlibmike: is the MIDI in that CB3 track feeding into Wotja? And what is the result? This is the part of this app that i don’t get yet. Are you using a follower in Wotja?
@ltf3 I've had mixed results. In my example, I have a pattern generator going to MIDI 1 and a rhythm generator going to MIDI 2. The first run went perfectly (and I posted). Stopped Cubasis/restarted and it did not work (so I edited my response). Rebooted the iPad and once again it worked - lol. So a bit flaky but not sure if its Cubasis or Wotja. For the record, AUM seems rock solid with the AU Wotja. "When it works" - the MIDI is being generated by Wotja. The other tracks are set to route "all midi source" and I then filter to the desired channel.
Get ready for Wotja 21.7.0
Pete, you tease! I'm dying to see what the update is.
Ooh, does that mean it's been submitted to the App Store?
@cooksferryqueen I'm such a meanie!
@Masanga not yet - just a few days away now - I think we're "code complete", with just some templates etc. to sort out.
This is a major update, without a doubt!
The templates alone are going to be worth the wait. I'm a caveman thrown into the cockpit of an X-wing till I copy @UMCorps's homework.
@Masanga they're always worth the wait. However, I'm currently blocked from sending a cool Beta update internally as AppCenter is down
Nooooo! Hulk need beta! AppCenter not like Hulk when Hulk start tweaking knobs with big green Hulk fingers.
@Masanga Hulk needs to check his in-box!
Hulk see beta drop e-mail, but App Center still flaky and take many goes to let Hulk in with Hulk GitHub credentials, then tell Hulk no releases available. Hulk keep smashing till App Center get show back on road.
Dumb question (maybe?) but how does this go with external hardware synths? Anyone doing this?
I've never tried with an external MIDI device, but it does do 16 channels of MIDI out. You could mess around with the free version to check it works, though I think that's still limited to one channel out.
Not dumb. It’s a really good way to use the core composing engine. Loads of examples on my YouTube page. Here’s one of them
https://youtu.be/UY1634kScxQ
And a shorter more recent clip here
https://instagram.com/p/CFAEwvwB2Qo/?utm_source=ig_web_copy_link
@UMCorps take a bow - beautiful
Ta.
But also worth underlining that use in this way is designed into the app. The midi side of the engine has lots of options you can use to direct continuous controllers to modulate the target snth(s) in all kinds of subtle ways.
And there is the invaluable tuning mode which when selected, forces Wotja to send either Middle C or A4 on all channels until you tell it to stop. Which makes it a doddle to quickly tune up multiple synths or oscillators.
And not forgetting the brilliant Timothy Didymus who use Wotja to drive both multiple synths and an instrument he built using turntables activated by midi driven relays to spin tuned glasses to create a glass harmonica.