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.
Need Advice from AUv3 Fans....
Ok guys...I really appreciate you guys feedback and I really need some advice on my new plugins.
As you know, when you use AUv3 in an iOS DAW like GarageBand, the interface is smaller, because Apple insists on make you use the virtual keyboard which is always up. That takes a lot of konb/slider space away. So here is what I was thinking of doing, and tell me if this makes sense:
Use the full non-AUv3 version to make the presets and share them with the AUv3 version. I'll still have the main editing features on the AUv3 version, but not the full version. Furthermore, I think I figured out a way to make a standalone iOS app and be able to only purchase once. This gives you the App version for free on your desktop, so you can make presets from your Mac and the full iPad version to be shared across the AUv3.
I'm not lazy...I could make a multi-windowed version on the AUv3, but was curious to know how many people actually make full-blown presets on the AUv3 version.
Comments
My guess is that this constituency is weighted more to making their own presets than the rest of the real world...with your stuff I rarely feel the need to develop on top of what you already give us
But I may well be in the minority (here).
@JohnnyGoodyear Yea man, this is the stuff I need to know. Who actually creates presets. As much as I love the iPad, I actually am much quicker in creating presets with a mouse on the computer.
Personally I prefer the AU versions kept simple. Just the knobs and sliders best used for playing on the AU and program on the main app. Pretty much how PPG have done it with the Phonem.
@Fruitbat1919 Yea, that made sense to me as well. No need for the full-blow editing. Just the main tweaking stuff and let the presets speak for themselves.
Just be careful not to leave out something that some may consider makes the app what it is. For example: The Virsyn Addictive Pro is a great synth, but if they left out the Arp on the AU, it would be a disappointment for many
There is at least one AUv3 that has a 'scrollable' UI that works pretty well for editing.
The app in question is KQ MiniSynth
http://appshopper.com/music/kq-minisynth
I really do like the approach Wolfgang Palm has taken with his PPQ apps (iPhonem at least).
He includes a 'Preset Player AUv3/AU-X' in the bundle meaning you use the full app to edit the sounds and use the AUv3 Plug-In to play the presets in a host app with selected parameters for live-tweaking.
Also a 'tabbed' AUv3/AU-X solution might work pretty well.
Have all AUv3 on the iPhone (except iSymphonic), use most of all the FX among which Frekvens hits the topscore (sometimes when you load it -message to DEV- the frequency knob is locked)
I'm ok with setting up presets stand alone and using the limited interface. Do it !
@Samu I think the scrolling would be possible. It's still a bit complicated from a programming perspective.
NO NO NO NO NO.......If you take the preset editing away from the AUx - then this takes away one of the main benefits of AUx which is saving your changes within your project so you don't lose them, or manage to change them by editing elsewhere.
@AndyPlankton
Hehe your NO NO response made me laugh. I could just imagine you waggling a walking stick at the face of your iPad while doing it
Waggling, shaking his fist, stamping his foot AND holding his breath until he turns blue.
He's probably right though
The grumpy old men of AudioBus - love it
I think the scrolling gives me the best of all worlds....
I should have said MO MO MO MO MO being as I also spat my falsies out first
Have you noticed how spit guards become so much more of a necessity as we get older. I never would share a mic again
I'd hate to have to exit workflow to create presets somewhere else. That's one of the main attraction of AUs for me ... that they're just there in-app when you need them. Besides, what do you do when you get a tweak that's just right in the AU and then you want to save it? Open a standalone app and re-create all the changes you made?
What about tabs, or a toggle to different pages? Kind of like Gadget does in Phoenix, for instance. There's a toggle between Synth and Mod/FX pages. Or Chiang Mai's Osc/Filter and EQ/Amp pages.
Scrolling can be a bit difficult in that you have to be careful to select a part of the screen that doesn't affect a control.
I'm also in favor of tabs/buttons with different pages. I don't create a lot of presets but if so, it's done in the moment...something is tweaked and I say "I like that, let me save it"
But for this it's not so much of a hassle for me. When i got the rhodes i created 5-6 intances i like the most. I'm assuming the controls available on the iphone would still be on here, just not the key noise, dirt, DIRT. ;p
For those worried about cut down AUs and saving.
The new WaveMapper AU saves changes for the AU and the full app, so it is possible to have a cut down app and share presets without major problems. Could even make a folder just for the app within each host so that you don't change settings for projects.
I'm also able to make a new preset in WaveMapper full while it's AU is open in ModStep and changing the folders back and forth updates them, bringing the new preset straight into the AU
So my favoured approach for anything complex is a cut down AU that shares well with the full app. Anything less complex try to keep it all in the AU.
If this holds true for all AUv3 apps, I like the idea of a simplified interface along with a 'Edit in full version' button that would use whatever iOS protocol is needed to launch the app in question directly.
@GospelMusicians Appreciate you asking this here.
Very much this, particularly if the interface is a little cramped in the first place.
What about editing a preset that you have used in more than one song, and tweaked slightly differently for each one, when you edit, are you not destroying your settings for each of the other songs using that same preset ?
Complicated use-case: the host is supposed to do state saving. So by editing a preset later on, you would normally not change anything in an existing track. However, if the plugin doesn't allow changing the setting in the first place, any tweaking would require going endlessly back-and-forth between host and standalone and creating a new preset every time (to override the captured state in the host).
Plugins are meant to accomplish total integration of instruments and effects in the host-environment. Removing the integration aspect from this equation by requiring a separate standalone mode feels like you're conceptually trying to fit a square peg in a round hole. The peg will get stuck at some point.
Before AUx came along we were all complaining that there was no total recall and too much app switching unless using closed environments, now that we have AUx, and the possibility for total recall and eliminating app switching, we seem to be saying 'Well actually, we don't really need this'
Is it any wonder that we get the feeling that Apple does not listen, not only are we a very small part of the apple user base, but we are also very fickle in our requests.
The answer is not to reduce the UI, but to present the UI in a more ordered and less cluttered way, meaning that functionality and usability needs to come before aesthetics. I think that Viking has done this very well, it doesnt look like a Moog, but it damn well sounds like one, and is very easy to use.
Also, providing MIDI Learn for ALL controls in the UI would also help those who have MIDI controllers available.
Exactly, and put much better than I was trying to
Ok tested with the same preset in PPG WaveGenerator in 2 projects in Cubasis.
I can tweak individually and the tweaks are remembered within Cubasis. If I save in one project, that saves to the folder. My other tweak stays the same as it was, until I move to another preset, at which time, I should save it as another preset.
It's quite easy to manage. Keep the original preset. If you change it, save it as a variation saved preset. Use a name code system so you know what's been changed and what it goes with I.e. Bass 01 CU (project Name)