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
I got the update and tried a simple 16 bar project with BeatHawk and Model D as AUs on MIDI tracks one and two. Nothing else. Track one sending kick, snare, and closed hat MIDI notes to BH. Track two sending a two-bar six note bass line to Model D. Tried to freeze track one and got a track with no audio. unfroze that and found BH suddenly back on its default kit. Then I tried freezing Model D. Got a track full of harsh digital noise that bore no resemblance to what I’d recorded. Unfroze and it returned to my recorded MIDI notes. All the while I was trying this experiment I kept hearing glitches that sounded similar to bit-reduction effects whenever I touched the interface to make an adjustment. Also, before I tried freezing anything, I tried enabling and adjusting the channel strip EQ for track two (the model D instance) any touch on the EQ caused the audio to drop out and/or the transport to momentarily stutter. That was the reason I started trying to freeze things. Since other people don’t seem to be having these sorts of issues with Cubasis, I’m looking for suggestions. On an iPad Pro 12.5 running iOS 11.2.6. Using highest Cubasis latency setting on the Cubasis update from earlier today (4-18-18)
As far as I’m concerned, NONE of the iOS DAWs to date are stable enough to truly be called pro, but Cubasis isn’t even fun to use as a toy running this way, so I hope it’s just some conflict of settings or something. I want to use Cubasis or Auria because they have the kind of workflow I prefer, but they are the least stable DAWs I have on my device... for years now.
Ahhhh... it is so nice, all the Model D instances now, the mixing/freezing working. Jeez, the navigation is so good now too compared to the old days, so quick...
I just wish I could Frankenstein Cubasis and BM3 together!
Well there’s your problem, you’re missing 4” from your iPad... no wonder it’s unstable!
Ah, weell guess you have a point there, @busker
.
BTW, I tried an even simpler project using Cubasis’s minisampler drums and 1 instance of Model D, four bars long. Try to freeze with any of the freezing options and none “work”. One way creates a track of horrible noise, the other two create audio of incorrect length/timing, and using the audio-stretch to put it back still doesn’t create an audio track that sounds like the original when unfrozen.
I put four instances of Model D into AB3 using the same preset I was using in Cubasis and that works fine, even playing complex and rapid parts, so I don’t think Model D or low resources is the problem. Even the missing 4”
doesn’t seem to cause problems for me using AB3 or AUM.
Out of curiosity, @ZenLizard, how it behaves in Auria? I'm interested in Model D, but so many reports of bad performance when using it with DAWs turned me off...
Worth noting is that in order to stay up to date with AUv3 support the latest iOS version is next to mandatory.
So if freeze is not working with for example Model D AUv3 and Cubasis 2.4.1 it’s time to go iOS11.3...
Also worth noting that GarageBand can't properly freeze AUs either, so my guess is that it's more of an Apple problem than anything else.
I know I have irritated several friends extolling the virtues of iOS Music Production and Auria Pro in particular, especially in the home studio environment. I just get excited that for my needs, a platform is as easy & intuitive to use as my favorite Tascam 488mkII 8 track PortaStudio was, but that said platform has pro quality audio performance as well.
But I have told several cats about Cubasis too, especially if I know they use Cubase on the desktop. As time has gone on I really dig both DAW's, and at their price relative to what desktop DAW's cost, suggest getting both. You don't have to go fanboy on it and choose just one.
Auria is great for mixing, mastering, projects with lots of audio tracks, music in the rock, country, acoustic genres, etc. Cubase really excels with MIDI, it's a bit more stream lined (no subgroups, etc), and the "feel" and layout probably appeals to electronic music producers more than Auria's very deep, Pro Tools like layout...at least I would assume so.
Opening a project I had issues with when track freezing after updating to 2.4.1 was kickass. Everything just works so smoothly now. So thank you @LFS Lars...you & your team are doing great work.
@ZenLizard I am sorry you're having the issues with both
DAW's. iOS 11, an iPad Pro....you certainly should be able to use both apps, those AU's, etc. without those hassles. I have an Air 2 on iOS 11.3 and can do the things you describe no problem.
Maybe try going to iOS 11.3 and see if that helps? Also both Lars @LFS with Steinberg and @Rim with WaveMachine Labs are really good at helping users with bugs & performance issues. Try the Cubasis & Auria forums too. Good luck man...
Thank you @LFS for all that you do. I love it when you drop by to tell us that Cubasis has just got even better
Since we’re living in the age of entitlement and this thread’s clearly past the tipping point for feature requests, I’ll pitch in my oar and ask for midi clip export.
For my use, to be able to export the chunk I have selected in the timeline to Dropbox would be perfect.
Dear all,
Thanks for your great feedback about Cubasis 2.4.1 so far.
For those of you, who have reported problems regarding track freeze/mixdown:
With iOS 11.3, Apple introduced changes in the handling of Audio Unit instrument and effect plug-ins.
Alongside other improvements, Cubasis 2.4.1 provides compatibility in this area, resulting in improved track freeze and/or mixdown results with resource intensive AU instruments.
Therefore, having iOS 11.3 or higher installed is mandatory to profit from this improvement.
Additionally, third party AU instrument and effect plug-in app vendors have to support Apple’s recent change as well.
If you experience issues in this area, please make sure to inform the appropriate instrument/effect plug-ins app vendors. Until the issue gets addressed by them, Cubasis’ real-time track freeze/mixdown options (located in setup) might be worth a try as a feasible workaround.
Hope that helps.
Best,
Lars
@LFS Thanks for the update! Most areas of Cubasis work pretty well now.
I do have a quick question and if the function is not available or doable at the moment consider it a feature-request.
When adjusting the audio bounds on the time-line to make a quick trim it would be very handy to have the audio-editor reflect those bounds.
Currently when entering the audio-editor it does not respect the bounds set on the time-line.
As a result the 'trimming' has to be done twice, once on the time-line and once again in the audio-editor.
If the audio editor would reflect the edits made on the time-line it would make it super easy to trim/chop out parts of the main recording as trimming would create a new file that could then be saved to the media bay if desired.
If there is a way to 'copy' the left/right markers from the time-line to to audio-editor it would save some time and increase the work-flow.
Thanks in advance.
/Samuel
+1
Would love more waveform display options...
‘Summed stereo’ ‘Halved’
A 'Convert Track to Mono' with option with Keep Left, Keep Right & Mix would be quite handy too especially after freezing mono sources or preparing samples for the Mini Sampler.
Other good to have options would be 'Freeze/Render' Event to Media Bay thus avoiding having to freeze long tracks when only part of a track is needed. This would also be super handy to create 'sample clips' that could be loaded to Mini Sampler.
Exporting Midi could easily be implemented in the same manner that Audio can be saved to the Media Bay.
(When editing Audio there's a neat 'Save to Media Bay' option, so adding a button to the midi-editor with 'save event as midi to media bay' would make perfect sense).
I'm quite sure there's a lot of brain-storming going on in the Cubasis team but I also feel that @LFS will welcome most of the 'crazy' ideas ventilated here at the AB forum
Great ideas! Was just wishing this yesterday as I happened to save an audio clip to media. Hope they can implement these ideas.
Can we have higher pitch bend options so that MPE controllers can glide notes properly in compatible AUs and in Cubasis's own instruments, please?
It would be cooler to have a scale tool that scaled the note lengths along with the clip, that you drag by hand. You can scale by any factor this way.
Even better would be a 2d lattice tool that you could use to scale or deform the selected notes, with user configurable lattice resolutions.
Samplitude can do your first one, which was my initial feature request in this thread, I just dont have a video of it handy.. The timestretch tool on the timeline works that way. Seems like the Cubasis one should too. i actually think Cubase does it.
Thanks. I didn’t update to 11.3 on my iPad yet, and that had crossed my mind as a potential cause, so I’ll do that.
Just highlighting the issue with the Audio File editor in Cubasis that doesn't respect audio event bounds.
So how does one automatically snap the left right bounds in the audio editor to match audio event on the time line?
Manually selecting the area and trimming it creates a new file so the only thing missing here is to automatically set the start & end in the audio editor to match the audio event on the time line.
Currently tapping on 'Select' in the audio editor selects the entire file if adjustments have been made.
Suggestion here is to add 'long tap' on Select to select the area used by the currently selected audio-event.
I think this is at least worth considering...
Updated iOS and reopened the BeatHawk/Model D project. Froze both tracks. Worked as advertised.
While I’m at this, I have a question about the drum kits inside the minisampler and microsonic. Is there any way to pan individual drums and cymbals? The reason I was plugging in BH is because pan control of each kit piece is essential for balancing the mix. I could use the microsonic and minisampler kits instead of an AU or IAA/AB plugin if there is a way to do it that I’ve overlooked.
Only way I've found is to use one track per drum, not an optimal solution I know...
Create a track with all the drums first then duplicate the track and remove the un-needed drums from the copies.
This also makes it possible to EQ & Process each drum sound individually which is a nice bonus.
I’m sorry, I didn’t try it out in Auria before updating. Working well now so far, though.
Big time. Would be nice for using with ‘save to media’. My current workflow is a lot of Cubasis<—>BM3 and sending exact clips quickly would be huge.
If I were still working with a real drummer and kit, I’d have at least eight mics on the kit and therefore at least eight tracks for drums, so that’s actually not so different. I just realized that would allow use of pieces from different kits together also. Thanks. Good idea and I’m going to use it.
I think you're stuck making multiple tracks and panning them instead. Since they're built in, the overhead should be low, and many people like to individually EQ drum hits anyway.
I do find myself really wanting track folders, or a "minimize track" option, in situations like this. It very quickly gets impossible to see the overview of a project.
i would love see more tracks. This style of waveform wastes so much space to me. I dont need left and right displayed all the time... actually never on the timeline.
‘Minimize track’ sounds like it would work great.
It does get hectic pretty quickly with adding more tracks. I think collapsable groups would be awesome.