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
Dubstation 2 updated with GUI opened still allow for crackle free Ravenscroft 275 playing. Cpu goes from 90% DS2 closed to 40% DS2 opened. This is as AU in AUM with 128 buffers played by Nanokey Studio in chord mode (easy scale).
I am using RC275 strictly as IAA with no problems. Not sure why AU is important with this app. Multiple instances not as important as on a synth. Having the onscreen display also not so important to me as I choose one setting and go. Is it the principle of the thing?
@tja , nothing special. RC picks up my controller as a source, I keep the volume in the upper right as low as possible. It is not perfect... An errant crackle here and there, at least 98% good and no problems with mixing down, of course,
@tja, I am on 10.3 into Cubasis. Maybe the OS is the problem.
I hope 12 will clear it up as I am looking to buy a used pro 2 this week. I guess if RC gives me the same problems Beathawk will come into play.
Pianos are from the 1600's. They have to break at some point.
Maybe try one of the new toy pianos. The 88 Key "Hasbro in Pink" is a stunner for $29.99. Sampled at an actual Day Care with
children in the mix. Update your thinking of what a Piano is.
[Commenter ducks as the forum throws shoes at him].
I think selecting the right tool for the situation is key. RC275 and
Colossus are amazing solo pianos but using them in a complex CPU environment is playing with fire.
For complex DAW mixes these pianos are overkill with too many layers requiring too much attention. When I hear a @LineLineman Synthony the piano is surrounded by synths, strings and the occassional mouth trumpet. Dropping all the soft layers and release layers and all the extra stuff from RC275 would like solve the problem.
How can this be done? Maybe use a lower quality piano that cuts through the mix but holds up when the CPU is juggling 21 balls
(maybe spinning plates is a better analogy). We tend to audition pianos in isolation and find some flaw. I'll bet those flaws would be hidden when the brass section joins in.
Start with IAA instances that just plumb audio and are not made to run multiple instances in 340MB RAM spaces with makes them need disk streaming and a lot of attention from the DAW.
Good candidates for lower but not unacceptable pianos?
I'm sure there are more. Use the right tool for the situation and you'll get more work done. Cheaper tools produce a lower level of quality but only marginally so.
Anything that reduces CPU at recording time can help:
No FX in the AU/IAA App
The largest latency you can live with
Reduced polyphony for Linear Jazz without sustain pedal
But those are production tricks. You just want to create right?
Of course, buying the iPad Pro might help give more CPU support for the perfect piano that lights your fire. Worth a shot and let us know if that's the solution.
For those with limited funds... settle for the piano that seems to lets you make tracks with the least pain.
I bought the BeatHawk Acoustic Grand on sale and as an AU instrument it's just awful. Inside BeatHawk it's really nice.
BeatHawk was designed for a different use case than say Korg Module.
We rated piano products in isolation but in a complex mix I'll bet we'd go for the one that cut through the mix which is usually just the piano with the most high end frequencies.
We suffer in a world of constraints but the technology keeps advancing to allow us more and more control over our music.
Or less control with better results if you like to sprinkle in randomness and automated composing tools.
Life continues to be good. Create!
That's not a bug... that's a feature. Good luck. More notes means more processing. There are the usual tactics:
maximize the buffers allocated
stop any none essential CPU activity
In my experience RC275 holds up well against the other high quality Pianos. Colossus is so awful as a AU that I have to record it on my Mac to get anything done.
The best hope I have for a Piano AU that's useful is a custom made version of Salamander in the Virsyn AudioLayer product.
The current headache there is the fact that I choose iCloud to store my files and that Piano takes up to 45 minutes to load.
The workaround is to store samples locally but my 128GB iPad is full so I'm wrestling with what Apps to delete to test it. My Colossus Piano with all the models I bought probably consumes 20GB so I could delete it for testing but downloading Colossus from iTunes takes 4-8 hours per IAP. My first product to go was Neo Soul Keys Studio but I really need to step up... maybe SampleTank, Auria Pro. Can you feel the pain a horder feels loosing access to the "good stuff"? Time for a new iPad with 256 or better yet 512GB.
Anyway, crackles are not proof of bugs. They might find some optimizations that provide more headroom for extra notes but that's just making a product more robust. Bugs are programming errors that cause unintended crashes or incorrect behaviors.
IOS Crackling is a given with the right set up. Laptops also can be driven to crackling with enough effort.
@bedhedproducer just put up a Cubasis Project with 26 tracks.
Of course, he plays real instruments and not AU simulations that work right up to the limit of an iPad that can run IOS 11.
I feel your pain... believe me. I want everything to just work. But I can break almost anything by pushing too many notes or too much FX processing or multiple instances.
For sure it’s a bug: absolutely stable audio if used with Dubstation 2 (GUI opened) in various hosts, or in GarageBand (without even need Dubstation 2). There are graphics priority thread issues in iOS11, some apps have audio crackles issues some other don’t. RS275 is very glitchy in that regard and almost unusable in some situations. But I must say it runs with very good polyphony amount in GarageBand or with AUM/ApeM/DS2, absolutely crackle free. So it’s not a CPU issue, more of a 50/50 iOS/RS275 issue IMO, and it sounds so good, it’s my best iOS buggy piano!!
@tja and @janosax, if you recall we hugged them a lot about the pedal noise. Eventually a rep appeared and it was corrected. I am not really having the problem using 10.3 (if 11 is part of the cause) but one of you could get in touch with the guy, if it is important to you, and put in your difficulties. It was the last Ravenscroft thread when it was on sale in June, I think.
Regarding the R275 issues (sorry for such a long first time post but ill get my issues out in one shot):
I have been discussing this bug with UVI support for several weeks now, they have referred the matter to developers. The support has been respectful and I have tried my best to describe my observations objectively. This is difficult because the fault is so elusive. Remember these guys need to be able to reproduce the fault to begin trouble shooting.
Note I have also referenced this discussion thread in my reports.
What I have observed is the glitch occurs most frequently (but not always) on pedal release, I observe a peak in CPU usage (observable using the CPU load indicator in Cubasis when running as an AU in Cubasis). I was able to capture the Audio during a glitch to send to UVI. UVI requested a video but I have not been successful in doing that.
Occasionally a glitch will also involve a loss of midi key presses as well.
I notice the glitches when I am playing the keyboard as a piano, as a pianist might. I have found it impossible to reproduce the glitch by just randomly pressing keys and pressing the pedal.
If using the Ravenscroft Audio Unit plugin with Cubasis I Record a midi passage from the keyboard and replay that passage, the glitches I observe do not occur in the same part of the passage.
Since I am now using the Ravenscroft as an AU plugin with Cubasis I have also observed what an earlier poster mentioned the AU quit while Cubasis continues to function - but restarting Cubasis was the only way to recover. Again this is an elusive bug that I have not yet been able to video for evidence.
Not so objective an observation but some days I have no problems at all, yet other days the glitches and/or AU stoppages are intolerable.
I like the Ravenscroft piano sound so I am willing to try to help them get a fix sorted - I see only three reviews on the Apstore - I’d like to give them 5 but i simply can not give them any score without this bug being fixed.
If you can carefully describe or best of all video an event for UVI support, or at least confirm observations this would be the most help.
Doug
Note I use an iPad Pro and ensure all other apps are shut down before running either Ravenscroft ap or Cubasis with the Ravenscroft Audio Unit. Either option behaves the same with respect to the glitches but the Audio Unit sometimes just ups and quits. Note I have had almost zero success with Ravenscroft in Cubasis with an inter-ap audio connection.
Damn. I knew I should have spent more and got the iPad Pro 10.5" for the storage and for the IOS 12 update:
https://forum.audiob.us/discussion/23242/water-will-flow-my-thoughts-on-au#latest
I will need to upgrade eventually 'cause I love the Crudebytes products but not the crashing in DAW's with IOS 11 and iPad 2018 due to 360 RAM limits that will be relaxed but only on the Pro's. Pro iPad will be for those aspiring to the finest tools... tools that work well.
Have you tried with Dubstation2? I’ve very little hope that this RS275 bug or some BH2 bugs will be fixed... I’ve sent them a mail with YT illustration videos about those issue including RS275 in July, they said they will work on all of these issues but I really don’t know if they will fix them. They shouldn’t need a video from you as I already sent them mine almost two months ago...
That’s crazy. Please UVI, fix it!!!
I'm a bit unclear on how Xequence works, but I took a crack at it and seem to be able to send MIDI to Ravenscroft without issue. Can you give me a walkthrough to create the problem you're having, or whatever, @tja? Save me some time trying to parse this thread ;-)