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
And I was responding to musikmaschine's question.
But since you asked, it works fine, latency a tad higher (on my system) that I'd like since it has to make two trips, but still usable.
@Zymos said:
Thanks. Have you also tried running MIDI in parallel to any of the effects you've tried? (like to Gilderverb or Sparkle, effects that you can pitch or control with MIDI).
Only clock, haven't tried sending CC to any fx.
@musikmachine: great idea, but he 4+ only works with the powerplug, doesn't it?
Thanks Zymos! Are you mac or PC cause Asio4all latency is poor even recording midi into Live but i rarely use it so will have to play around with the latency settings.
Anyway it works with one interface, i was getting break ups initially and had to enable hardware buffer.
@papertiger you not using an iconnectmidi then? My idea was to run tracks through the iPads fx and do live tweaks. Was reading the comments on discchord and it sounds like a go with Lives external effect but i've never used outboard with Live. I'll update when i've tried it.
@animal, not sure. Also makes me wonder about mfis cause they're on all the time, you can't just disconnect the interface lol! I was wondering if there was some sort of overcharging protection built into the iPad and from what i'm reading batteries can't be overcharged so dunno, i'll have to ask iconnecivity cause they must have taken this into account...
They won't charge your iThings unless you're using one of the iConnect cables. If you want to avoid charging you can use a common USB A/B cable. Honestly keeping it topped off won't degrade your battery compared to normal charging/usage. The charging system in the iStuff is very refined nowadays.
@KDub: that's interesting, I didn't know that about the cables, are you sure? (feel like an idiot returning my 4+, now, without sufficient investigating). And are you also sure about the sophistication of longevity of batteries nowadays/in ios-devices? ( I have along history of dying Macbook-batteries after some time of not disconnecting it from the powerlead, different generations). Please elaborate, your info might save my ios-soul! (and I'll run right back to buy the 4+ again!)...
@musikmachine said:
nope. I'm in a weird place with music gear and I'm trying to sort out where I want to go. I definitely want the iPad to be part of it since I have it with me all the time and there are some apps that I really would love to integrate with my laptop/rest of things, but I'm suspicious of things like the iConnectMIDI, even though it's gotten excellent reviews. I'm constantly pissed off that I can't just plug the iPad via USB into my laptop and route audio/MIDI that way. I wish I didn't have to add another device to make that all work.
I'm on PC. I don't find ASIO4ALL requires any higher latencies than native drivers in general. But of course it also depends on what interface you are using it with....
I've said this before but- as nifty as audio pass through is, there's something to be said for the simplicity of just buying a decent iPad compatible audio/MIDI interface and plugging some cables into your computer.
@KDub said:
Do you mean with the CCK? Like i say i just pull the adapter out when it gets to 100% but it's good to know it doesn't overcharge. Battery doctor is a bit misleading cause it does the trickle charging thing and warns to unplug to avoid overcharging.
@animal it's true. Go back and buy another one and/or wait for the iConnectAudio4+. I'm going to have both.
@musikmachine yes the CCK works just fine.
@Everybody
Batteries:
I've had many discussions over the years about mobile devices and batteries and battery management/monitor apps and I'll give it to you straight. Power management in mobile devices was a thorn in the side of manufacturers for several years. There are a ton of variables that you can get stung by assuming a users usage behavior so there have been a LOT of flat, static, one-size-fits-all (but not really anyone) power management scenarios applied to mobile devices in the past. Fast-forward to today and I can say having owned and examined long-term Android, Windows Phone and Apple devices that the power management logic in these new devices is just brilliant. I think Nokia/MS and Apple have got the battery management logic down to a T. I'm really impressed by the iPhone 6, iPad Air and Air 2 however.
As with any of these things, when you first get one, is to just NOT WORRY about the charge indicator, just leave the damn thing alone and use it for a week. They all go through a learning phase when new and when updated. Those stats on a fresh iThing don't mean a damnThing for a few days...but they will and they'll be really accurate.
Battery monitor/management apps:
Get rid of them. Uninstall. They are ALL trash, placebo, CPU/battery wasters. They play on your fear and they all poll (or mess with) the built in power management system. Developers of battery management apps don't know the secret sauce that a particular manufacturer is judging usage by so the apps are always lying to you. This is your intervention. I'm your buddy. It looks like insurance. It looks like it would make sense. But it's crap. Fight you're OCD.
Those apps don't really know the status of your battery because you can't monitor for it, you can't expose in debug mode and it's not even published so why do that? Oh and it's a non-native app so it's its own battery degradation statistic. Ever think about that? Even the OS-native power management systems statistics are retarded until they come into parity with their own monitoring after several days. Apple and the rest do this because each battery is slightly unique and the best way to understand the charge and discharge of a battery is a) don't make assumptions and b) monitor and rate them real time.
Hope this helps. This was all said with Love.
Peace, love, and batteries man
I totally agree with what @KDub says
@Zymos said:
That's how I'm feeling. Wish they still made the non-plus version. I want the MIDI routing and I'll move the audio around myself. If they added actual D/A to it, that would be more interesting.
Could overcharging the iDevice shorten battery life or cause the battery to fail, I wouldn't recommend leaving it constantly charging as all these devices were created with the purpose of being mobile. If in a constant state of charging, heat could be the real problem especially if your device isn't 'naked'.
@knewspeak when you have USB power supplied to your iDevice its not charging the battery unless iOS lets it. It's not in a constant state of charging just because it's hooked up to power.
I did a little explanation of using the iCM2/4+ to do outboard FX processing a little while back.
https://www.facebook.com/MusicInclusive/posts/683300111748861
@syrupcore said:
I'm hoping the iConnectAudio4+addresses these concerns, so if an aggregated device or digital pass through proves unreliable or too complex you can simply use it like a regular class compliant audio interface. (with charging!)
@papertiger i hear ya, it's frustrating how restrictive the iPad is getting stuff in and out! jailbreak is the only way i know of being able to connect the iPad via the lightning cable but i don't want to void the warranty. Have you tried SBDs apollo remote recorder? It works but the vst is still in alpha and i'm using a wired broadband hub so can't set up adhoc, just waiting for an update.
@Zymos i'll have to check my settings, i recorded some chords into Live but there was a significant gap between my playing and the recorded notes.
I was thinking vaguely when i posted that it would work with Live's external instrument and google brought this up: https://www.ableton.com/answers/live-9-push-and-iconnectmidi2
I'll have to try it but hopefully i can tweak the latency settings further as it's usually better when using lives external instrument but it sounds like from Dereks' posts that S1 is worth a try so i might install that to test (thanks btw for the videos).
I've never had great luck with asio4all though but it's great to have aggregate audio on windows. I'm considering a mac cause everything for audio is baked in to the OS and it would be simpler to integrate. I went this route cause i'm using room correction software with my DAW plus i've already got 3 interfaces!
@KDub i'd been using BD (regarded as one of the best btw) with my smartphone for a couple of years, it does extend the battery life but i mainly use it it clear memory and junk, same on ios but i always forget to switch to it when charging, sounds like that's a good thing! Good to know it's not overcharging when left connected but how does the battery stay at 100%?
@bonso my thought was to wait for the ICA4+ and if things work well with that buy it, in the meantime i can power my iPad while using it as a midi controller and I can take audio in and out with AP.
Cheers all and have a good christmas and new years.
@KDub, Don't mean to be alarmist and information out on the web is sketchy at best, but I didn't mean that the iDevice was constantly charging when plugged in, no the device draws power until it reaches full charge, but then keeps topping this up as all iDevices continue to use battery power, indeed I believe the two main failures for Li-Po batteries and neither are that common, so no real need to worry. 1. The thermal failure of 'battery' control, basically the switch that controls the draw of power to the battery, this can happen when left constantly plugged in, due to the constant switching of the control circuit, causing failure in the switch. 2. When the power level of the battery cells drops to a low level and it is unable to power the control switch to draw power, therefore the battery will be unable to charge it's cells. This is the more common cause of failure, but usually after the battery has aged.
The main reason I draw attention to the first is because keeping any device attached to a 'charger' either the one supplied or in using ICM, could place extra stress on the batteries control circuit if connected this way constantly, I don't know if iConnectivety have conducted any tests to see if there are any risks using a device in this manner, but I am just trying to make you aware this could be a risk, albeit a small risk. BTW most batteries fail because they have reached the end of their life cycle.
@musikmachine, a lot of control apps like BD do let you shutdown and clear 'junk' processes from RAM and that will save power, it shuts down background processes. Sometimes does a better job than the OS.
Just had a go with Lives' ext instrument and effect and both work, very little latency either side. Great thing is i can have external instrument one one track and effect on another to do parallel processing. It is the best of both worlds.
well I just ordered one to give it a shot. Hopefully it's the missing link (literally and figuratively) so that I can actually use my iPad for music the way I want to with my laptop. Stupid questions for experienced users to follow!
The manuals a bit sparse and out of date so start with Dereks and the iconnectivity videos, they cover most things and setting up with your DAW.
I'm hoping I can do some connection videos for a few more DAWs shortly. I've covered S1 Pro 2 and Reaper, but I hope to get something done for Cubase, ProTools, Logic Pro X and Ableton Live as well in the New Year if I can.
Winning iConnectivity move: if the iConnectAudio4+ could act as a destination and D-to-A for audio pass through from the iConnectMIDI2+ and 4+. Computer be damned.
@syrupcore said:
If the iConnectAudio4+ cannot be used sans computer, I'll hold my money until someone figures it out. Literally the only thing I'm missing is a way to charge my iPad while providing the same audio and midi connectivity I get from my pre-iOS X-Station, which needs zero interaction with a computer to be fully useful with the iPad. I'm not spending a dime and will keep suffering with my battery life until some company puts together a better option.
Prefacing this with the fact that I'm using a Mac, my initial impressions of the iConnectMIDI 2+ are extremely positive. I was able to create an aggregate device that allows me to use my Apogee Duet 2 and the iConnectMIDI 2+ at the same time in Ableton Live, which is very exciting. Setting up the iPad for MIDI and audio in/out was like using any other device with Ableton - simple and easy.
I have had crackles here and there, but I can't say for certain whether they were due to the app I was using, my levels, or something else. I'll keep adding to this thread as I expore more, but the iConnectMIDI 2+ is, for me, THE missing link that'll enable me to incorporate my iPad with the rest of my studio. And at $89 it's a no brainer...
Question @papertiger - what do you have your clock source set to in the Audio Info panel in iConfig? It's best to set it to the Mac port and then resample both in the aggregate, setting the master to the other device. That will probably get rid of any crackling. Also worth checking the # of buffered audio frames and sync factor value settings. I have mine set to 2 and 4 respectively.
@MusicInclusive have you tried it? It's dead simple with Live once you set up the aggregate stuff, just external instrument, midi to iconnectmidi2+ (port 3) and audio from 3/4.
To/From 3/4 with the external audio effect and just route other tracks outputs to the external audio effect. Doesn't work with Turnado though.
Appreciate that tip about sync, i had no idea what to set those to but i have three clock sources; i assume 2 and 3 is for both my installed soundcards?
@papertiger i was able to map a control to Nave and write automation to a clip so midi should work as normal as it's bidirectional but i guess that will depend on the app.