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
Perhaps all the developers should be asking Apple to sort ios to make it standard throughout all apps. It's going to get even more complicated if the devs have their own workarounds.
Have Steinberg ever put this app on sale?
Can anyone confirm a higher CPU overload after updating to 1.4?
http://goo.gl/2kOuA
@Michael No. Cubasis has never been on sale.
I am sort of stumped as to why everyone says midi is broken and iOS needs to fix whatever. It's working great in BM2>Alchemy>Drumjam>Thumbjam>whatever else I try. It's broken in Cubasis.
@boone51 Midi Clock always starts halfway through a Drumjam pattern no matter which app I use it with.
@Michael_R_Grant does this happen even when you have already "primed" DrumJam with the current tempo (by running the midi clock source for a short while beforehand) and done the real playback start from a stopped state?
Can you give detailed reproducible steps with specific other apps and setups? Thanks!
@Michael_R_Grant I don't really get that. I do have to "prime" it as the dev mentions above, but then it's typically fine. I've experienced some sync issues after a certain amount of time but I think I've determined that's almost always when I have too many apps open. Also, when I sync clock in drumjam I can see the tempo turn blue and that's how I know it's syncing correctly. It's not doing that when I'm trying to hook it up to Cubasis' clock.
In the spirit of full disclosure - I'm no midi pro. It's quite possible I'm not doing something right, but I've been able to fumble my way through the other setups.
I tried with cubasis and bm2,giving drum jam a 1 bar count-in (bm2) and a 2 bar count-in (cubasis)
In drum jam I placed the bass drum kick,set at its 1st variation (single kick....and I'm assuming that kick should start on the bar?)
For both bm2 and cubasis,the kick would sync between a 1/4 or a bar and 1/2 a bar late.
Edit
No other apps were running and this was done with Audiobus.
@commonstookie please report exactly how you configured the midi clock sync between these apps, it is a very important detail! Which was the midi clock source, etc? Note that Cubasis only sends the midi start/stop events and not the tempo tick events.
Let's take Cubasis out of the equation for now and just set it up so that BM2 sends clock to DrumJam. For example, in DrumJam's MIDI setup make sure all midi connections are turned off. Then in BM2's main MIDI setup set DrumJam to ON in the output column and enable both MIDI OUT and CLOCK SEND buttons at the bottom. Then when you hit play in BM2 you'll hear DrumJam crank up, once it has settled on BM2's tempo hit stop twice to return to zero. Hitting play should work as expected from then on with no need for count-in.
Jesse,hello
Followed your instructions to the letter and recorded the audio file.
Am emailing you a pick of it so you can see exactly where the recording starts....1/4 of a bar late!
Ah, it appears in BM2 the MIDI Latency setting does affect how DrumJam responds. When I was testing the MIDI latency setting in BM2's MIDI settings was set to 50ms, and things worked as I mentioned above. If I lowered the value to 0ms, it starts acting like commonstookie reported. Once I set it to 15ms or above it acts normally. I'm not entirely sure what is going here or how BM2's clock messages are affected by this setting, but it at least explains a discrepancy in experience.
Thank you Jesse
So the next cubasis update needs....
Adjustable midi latency setting
Yea.
@sonosaurus when I sync funkbox, baseline, iElectribe inc Gorillaz edition or Molten to Cubasis midi clock it does send tempo as the bpm changes in all these apps ???
Are tempo tick events something different to this ?
@DaveMagoo do you have BM2? If so can you see if you can get clock to sync from Cubasis to there? I can't seem to do it.
Will give it a try when I get home
@sonosaurus The example I recall is running Loopy HD and Drumjam, both at 90 BPM. Loopy is on pause. I set Drumjam to receive Loopy's midi clock and neither app is playing at that time. While in Drumjam I hit play in the Audiobus side panel to start Loopy (Loopy then plays from the start of its loops by default). The Drumjam pattern starts automatically upon hitting play in Loopy because I've set it to receive the midi clock, but it plays from the middle of the pattern rather than the beginning for its first time through. Drumjam is therefore "out" compared to how I want it to sync up with Loopy.
This is only my recollection, though, so I will make absolutely sure when I get home!
@Michael_R_Grant I think what you're talking about is that the drumjam pattern will just pick back up wherever it stopped in the process when you hit play. I think if you hit pause, then rewind on the AB panel while in drumjam with the clock synced, the next time you hit play they will both start from the beginning of their patterns. I *think that's what you're looking at in that scenario above.
@boone51
First try I got 214,748,364 bpm in BM2....
I will keep you posted
Yeah, I got 999 in BM2 and Alchemy. Thanks @DaveMagoo.
Just been tinkering and turned all the main midi settings off all together on BM2 and pressed start on Cubasis.
It starts BM2 but you have to match the tempo with Cubasis, I had to set the tempo 120.4 in BM2 to match Cubasis and stay in time.
I think the problem of Midi Sync is that every app developer use your patch, and they need the same Standard for haven't problem....
I think now it's time that ONE developer make a Midi Sync Standard and I think the best for make this is AUDIOBUS...
Sebastian, Michael, let me know what you think...
And Jesse from thumbjam
Has any one successfully used the punch in / out tool? I must be missing a step but I can't get it to work. I was trying to punch in 1 bar of iFretless via audiobus, then I quit all programs and tried in cubasis to see if it would punch in and out on its own no luck.
None of us got that far!
We're still stuck on the clock.
I'm giving up on the clock for now. If any one figures out how to make a punch in Cubasis I'd love to know the secret.
Just tried the punch and it works great! The first one will start rec when it hits the left locator, likewise punch out will stop when it hits the right locator. You do have to push rec and play to get it to work. The 3 rd one will start recording after count in. Haven't tried tried the last one..
Ok I think I was missing the step of using the right left region thingies to set the in and out. I'll let you know.
Ok it's just a lot more convoluted than I'd hoped. First you have to split out and delete. The offending measures. Otherwise Cubasis records on top of your previous take. Once you snip that out you can use the right left locators to set up the punch. It's a lot of steps but I'm happy cause that one bad note has been replaced!