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
All seems good now.
Wow quick update, Audiobus seems ok now....:)
The midi sync needs some work though I think...
When syncing target is BM2 on starting from NXT I get a short delay before BM2 audio starts playing, which is then out of sync with NXT.
When sync source is BM2 and with midi latency set at 30ms I get a perfect synced start but the bpm's do not match as BM2 is slightly faster and things go out of sync quickly
I noticed that when NXT's bpm is set at 120 and BM2's bpm is set at 119 they sync perfectly when triggered independently of each other eg: not synced.
Maybe something to do with the BPM increments, in BM2 each bpm is adjustable by 100 increments where as in NXT each bpm notch is adjustable by 1.
Anyone else get this ?
Just trying Cubasis....
Edit: Just tried Cubasis.....
When sync source is Cubasis I get a perfect synced start but the bpm's do not match as Cubasis is slightly faster and things go out of sync quickly
I noticed that when NXT's bpm is set at 120 and Cubasis's bpm is set at 119.5 they sync perfectly when triggered independently of each other eg: not synced.
Again maybe something to do with the BPM increments, in Cubasis each bpm is adjustable by 10 increments where as in NXT each bpm notch is adjustable by 1.
I wonder if there is a way for the Dev to address this ?
Which dev? It sound like any of the apps could be at fault.
@funjunkie that's a good point...should read Devs
I thought it may have been due to the lack of finer bpm increments in NXT that resulted in the incorrect bpm's being synced.
I just tried Cubasis clock synced to BM2 and BM2's bpm doesn't even change to match with Cubasis'
Their displayed bpm's are also different when triggered independently but matched by ear eg: not synced.
I'm gonna try loopy and a few others inc midi bridge next.....
Tried Loopy.....
Note: Loopy at 119.7bpm is equal in speed to 120 bpm in NXT not synced.
When NXT is the clock input for loopy it syncs and shows NXT at 120 bpm and Loopy at 119.7 slightly opaque as in you can't change it in loopy so NXT it's telling loopy the correct bpm !!!
One thing I noticed is when I press the back button to return both apps timelines to zero while synced it resets NXT's timeline but starts loopy playing again so I cannot reset and start again to sync I have to press NXT at the right time. I found this also to be the case with BM2.
When loopy is the clock master it seems to work fine with some bpm adjustment on loopys side, start stop seems ok too.
Tried DM1....
The bpm sync's fine, the start timing is off as DM1 comes in a little late. The back button starts DM1 so as with loopy and BM2.
Tried Funkbox...
Same results as DM1.
To be fair the back button in NXT is handy to get the timing right for apps that have a slight delay when starting them as you can start with the back button and then time pressing play in NXT to play them in sync.
Korg iElectribe for me is the only one app that go straight in sync with Cubasis and Loopy.
Bingo!
Changed the Audiobus frames from 256 to 512 and BM2 is now working flawlessly as clock/sync start for NXT
edit: and vice versa !
Wierd how this affects clock sync, as soon as I change the frames back they go out of time again.
I Just need to add that I had to open Audiobus then BM2 then NXT for it to work, if I opened AB then NXT then bm2 it crashed BM2 every time.
Time for a Jim Beam to celebrate!
Gonna experiment some more
@Sinapsya gonna try ielectribe...
@DaveMagoo, thanks for checking this out and reporting results. Yes, it's working! Getting perfectly synced start using the setup that you listed and starting everything using MidiBus.
Not getting the synced start when starting from BM2, though. Will keep working w/ it. Any suggestions?
hmm, I have sync source set for BM2 and sync target for BM2 and that's giving a synced start from NXT. Would think that that would cause some mayhem...
tried a different file in BM2 and switched the tempo. Started and stopped the song and now NXT is sync starting from BM2 w/out using MidiBus. Cool! Nice to have the option to use MidiBus, too.
EDIT: and working in other direction… NXT as clock source to BM2 w synced start, no MidiBus needed.
EDIT AGAIN: Sorry, maybe more of a hit and miss w/ this. It's not consistently starting in sync w NXT as clock source.
Good sync start w Cubasis master to NXT, but tempo drift after a few bars. Getting no synced start with NXT as master. BM2 clock w NXT rock solid, no drift, to my ears at 144 BPM after a few minutes of playing.
Seems in general, have to reset the Master app (BM2 or Cubasis) to start for synced start to take.
Yeah best result so far here is BM2 sending clock sync-start to NXT the only rock solid option I found yet, no midibus used.
It works the other way but the start timing is off, and I have to time when I start BM2 very precisely and independently but the bpm's do sync, it's the start from NXT that's out slightly.
@sinapsya iElectribe when synced goes at twice the bpm....not sure why....any ideas ?
maybe a MIDI Thru port open? Or if you're running Midibus, it could be sending the signal back on itself (that happened to me when I first started using Midibus).
@CalCutta just running iElectribe & NXT through Audiobus at either 512 or 256.
Managed to get ielectribe synced at the right bpm. I just selected MIDI sync target in NXT as network and the bpm synced, with just the late start from ielectribe. It also starts with the back button on NXT starting ielectribe instead if returning it to the start ready for playing all sections of both in sync.
Once the both are playing in sync you can retrigger NXT live with the back button to better allign the 2 audio streams.
so whats going on with this app, did the dev ever make those tutorials he promised?
is this abandoned looks like no word for a while, ?
https://www.facebook.com/ElectrifyNXT
I was so disappointed with this after all the hype, it was expensive and now has not had an update in six months...I think the dev had more ambition than he could deliver....
The last update did something to the audio output, it all just sounds thinner and it's like the compressor/limiter can't keep up, making these loud "attacks" on every initial part. Also the very loud burst/pop-sound issue (again related to the unstable dynamics processing I guess) isn't fixed. If/when those issues are fixed, I don't really see other problems with it that I'd consider a deal breaker. Fun, good sounding groovebox (well, will hopefully be once the dynamics issues are fixed).
The facebook and twitter are quiet from dev created posts, but he has replied to other posts on FB, most recent on April 24th.
Sadly no tutorial vids and no manual (last posts on FB were about that). I'm worried this could become abandonware, but I hope not as it has great potential.
Whatever the rights or wrongs, it got released with some hype and then kinda got trashed by a lot of advanced users. Maybe the dev took that bad, or alternatively may not have the time for the constant updates which we see coming from some of the great devs whose work we support.
Either way - I still have great fun with this so I hope it still gets some love from the dev.
I like certain elements on this app and really hope it's not abandoned. It's very easy to get interesting rhythms out of this thing.
This is still probably the single App I use most and although it has its own strange little foibles for me there's no show stoppers and in combo with Loopy HD, to record synced Audiobus inputs, its an easy way of working on iPad. The lack of support however is a real shame. The Dev directed everyone to the forum for the App then quickly stopped posting there. You never know what's happening in someone's private life so I hope all is well for him, but it would be nice to see a few additional touches and a bit of love for the App.
The dev promised that he wouldn't abandon this app like he did the previous version, so it's disappointing that he isn't engaging properly with his customers and potential customers at the moment. You're right about the sound, @ChrisG - comparing its output with Launchpad, it's obvious that the sound in the latter is much 'fuller' and I don't remember Electrify being that thin before. I just gave it a go at lunchtime, though, and there's still lots of potential here, despite the problems.
Its a great app just needs a bit more development to shine, I think the release of gadget may have had a part to play but maybe we will see a great update soon.....
when you say great, do you mean in spite of the issues brought up like the sound quality etc... or are you not experiencing the issues on your iPad?
Yeah I'm definitely experiencing the issues with sound....just 'hopeful' we see a great update this year
Well I deleted it not long after buying it, I was really hoping it would do the things I wanted but ran like crap on my ipad3.
I will reinstall it someday when I get a more powerful ipad, but it does have many issues and used to crash a lot when I was using it
I'm using an iPad 4 and I can't say that I particularly suffer from problems with the sound or with it crashing. The things that still bother me are that sometimes the sound in the edit page is significantly different from the sound once the clip is frozen. It also still intermittently suffers from an edited loop not playing until it would loop for a second time.
I also feel that Nxt outgrew the effects interface from the original Electrify. On delay based effects in particular I'd have liked much more control over exactly what delay time and feedback I was using. I'd also hoped that the automation engine, which is great, would be extended over all parameters. Currently there are significant ones missing, particularly for modulators.
All that said I still think its a great App. I love to make strange noises with cheap hardware like monotrons, patch blocks, and Korg's synth kit. The ability to record them in Audioshare, chop them and dump in Nxt with instant tempo sync makes these units much easier to incorporate in some fashion. With solid loop editing and resampling into Loopy with your Audiobus effects there's still plenty of fun to be had
is the time stretch independent pith and time?
@kobamato yes, but you need to understand how to set the bar length correctly if you want to get loops to consistently play as you recorded them. Also pitch control is not as fine as I'd like because of the small rotary control used to set it. This can make it difficult to tune some strange analog warbling that you've captured accurately to the rest of your track. This is another one of those areas where the capability has outgrown the interface.