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.
Poly 2 in Logic Pro
Has anyone been using poly2 in logic as a midi fx? I’m finding the midi signal drops out when stopping the transport - the only way to bring it back is to back out of the project and reopen it.
Really looking forward to using this in conjunction with KQ Voice loopback sending midi to multiple tracks/channels within logic
Comments
I contacted the dev directly and he’s looking into it!
many plugins are malfunctionig in Logic, Apple just needs put their shit together, with current AUv3 implementatiom they caused a lot of headsche to third party plugin devs…
Isn’t really Apple fault that some AUv3 plugins/instruments have problem in LP4i?
Tell me then, why are so many other AUv3 functional without any hussle?
This is a mystery…
This is getting ridiculous @ErrkaPetti
Apples AUv3 implantation in Logic Pro far from 'perfect' when comparing to some other hots, even the project management is far behind for example Gadget and NS2 and ZenBeats (while I don't personally gel with it) does for example midi-learning way better than the 'midi-scripter hack-arounds' just to name a few things.
Apple may be Apple but it doesn't mean they do 'everything right' and there's no point in defending their decisions at every possible opportunity that pops up
Samu pojka, breath!
It must be a combination of both Apple and the developers if an AUv3 app doesn’t work well into Logic.
As an example, Auturia iSem Synthesizer hasn’t been updated for more that three years, still works flawless in Logic…
How do we explain that?
Defending Apple? This little 3 trillon dollar company perhaps need some support and love…
Last time I checked iSEM was un-able to stay in tune on devices with native 48K sample-rate and recording automation using the knobs didn't work at all. So yeah 'working' and 'working' can be two different things depending on how one looks at it
Was iSEM even built to support recording knob automation?
Hav’nt possibilities to test it just now besides Logic…
A couple of examples that have been giving me a hard time:
The sample position and beat position don't always match up, plus they drift by different amounts and periodically reset themselves with respect to the timestamp. Makes life difficult if you're trying to do sample accurate timing, particularly if Logic is looping.
When you start the transport Logic gives the AU an 8 millisecond "count in" before you hit the first beat, and the sample position and beat position can go negative. I've not seen any other iOS host do that, it's not documented (Ha!) anywhere that I could find, and it caused havoc for me because I wasn't expecting negative beat positions.
If a developer has been working with Logic on the Mac then they'll know about this sort of stuff. But anyone who started out on iOS/iPadOS using hosts like AUM, Cubasis, NanoStudio, etc. is in for a rough ride...
Hmmm… I don’t get it, but do you mean that Logic for iPad has a bug that cause problem on timeline (drift problem)?
I have read thousands of comments on different forum about Logic Pro for iPad, and, ever never read anything about this?
No, it's not something you'll encounter in Logic itself, it's a problem for anyone who develops audio units.
As Samu said, Logic's AUv3 implementation isn't perfect: it has some unusual behaviour that isn't present in other hosts, plus some of the timing information it provides to an Audio Unit isn't completely reliable. So Audio Units that rely on Logic to provide accurate timing information (such as sequencers or tempo synced effects) may go out of sync or not work properly if the developer was unaware of Logic's behaviour.
Also @brambos mentioned somewhere that way how logic implements AUv3 automation is at least not the one which is described as prefered by apple in documentation, or something like that (doesn’t know details).
There are other areas where the AUv3 support in Logic halts a bit as well...
As an example the 'Midi Modulator Plug-In' relies on each Plug-In / AUv3 supporting 'touch automation' thus if a plug-in doesn't support it (ex. auGEN X) it's not possible to use the modulator to automate it's parameters, ie. no way to browse AUv3 parameters within the Midi Modulator Plug-In... (At least I've not found a way to do that and midi-routing is another 'thing', though I'd never say it but bring over the Environment to the iPad so we can route the stuff freely).
It is possible to 'draw' automation for all auGEN X parameters, just not touch assign or record them...
So yeah, the next 'update' will be interesting to check out whenever it drops...
Do we have any logic beta testers in here know if these issues are being worked on and when an update might drop?
It won’t happen - beta testers at Apple is trained to shut up and be quiet…