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
finally sugarbytes' support guys could reproduce my problem, so here is the global picture:
from sugarbytes forum's support team:
"I could reproduce the problem. To me it seems the crash happens inside the AB framework.
AB is making some updates on their engine soon which maybe solves it.
I'll continue investigating once the AB update is there."
from AB (this) forum:
"I've forwarded this to the Sugarbytes developers. Lets hope they can figure out what's going on."
from RME (fireface UCX) forum:
"We use audio completely per the standard, so I don't expect an issue."
i hope there's a solution for this soon, i am really looking forward to use AB2 and sugarbytes' rocking apps with my audio interface in my live performances.
i invested in the best apps and hardware to try to take ios music to it's top quality level, also put my self and my gear at disposal of sugarbytes, AB and RME teams.
now the ball is not in my court. i wish it was!!
Thinking about getting this app so has this issue been resolved?
Edit: I have an akai eie can someone confirm that it works with that interface?
It works fine with akai eie. One of my favorite apps.
dear audiobus, sugarbytes and rme teams:
i perform in 2 weeks at the great, massive and independent festival "fusion" in germany.
when i decided to join these great apps together with this state of the art fireface ucx audio interface, i did it with the intention, not to be the coolest guy (which would be also worthy), but to give the best quality and performance to the audience.
to take ios music to a standard quality comparable to computer performance.
but at this point, after weeks and weeks waiting and asking your for support, the situation is the same: sugarbytes apps DON'T work INSIDE audiobus WHEN rme interface is plugged.
audiobus 2.1 is here, and nothing has changed. sugarbytes apps crash as soon as i choose one of the 18 inputs of my rme interface.
it seems i must be the only guy in the hole world who wants to make music using audiobus+sugarbytes+rme, but i also have got rights! i also payed! i also have feelings!! i want my equipment to work.
is so much what i am asking for?? fusion's audience won't enjoy neither audiobus nor sugarbytes this time it seems.
thanks again for your patience (i don't have of that, i just have perseverance).
Almost any form of hardware audio interface you use is going to have problems with some apps. For instance, I use a Focusrite Scarlett 2i4, and I can tell you now, Grain Science will absolutely never work on my rig when the Focusrite's going. That's not anyone's fault, and "rights" have nothing to do with it.
It's a new world of technology here, which means that there's a lot of new issues, too. If you haven't already, contact Sugar Bytes and let them know the specifics on your issue. They may be able to give you further information, or troubleshoot the issue on their end. You should test the setup with a different audio interface and check. Turnado and all Sugar Bytes stuff works fine on my Focusrite...
edit: Obv I hadn't read the thread very closely, I see you have contacted Sugar Bytes and the audio interface devs. From RME's answer, I'd think the problem is with their stuff.
@calcutta thanks for your reply. you're right what you say. but i just can't give up. these apps are amongst the most solid and best supported, i don't know about grain science.
i wrote rme's and sugarbyte's teams also weeks ago. here the threads:
http://www.rme-audio.de/forum/viewtopic.php?pid=96996#p96996
http://www.kvraudio.com/forum/viewtopic.php?f=108&t=409548&p=5775574#p5775574
more or less each one says it must be a problem of the other...
Yeah, that's the down side of new technology.
For the record I could be wrong and it could be a coding issue with the app. I'm not savvy enough in backend technology to prove my theories, unfortunately.
I'll be honest, I'm kind of cynical that this issue will be resolved, at least not intentionally (and probably not sooner than later). Your fastest solution would probably be to try a different audio interface. You should see if you could borrow one from someone you're gigging with, and test it really quick backstage.
@ecce_cello said:
Let's try another approach: Are you showing that interface on stage? Would something like a Focusrite 18i20 work for you as well?
hi sebastian, what you mean? if it's an offer, I really appreciate it.
but it's just I have designed all my setup with this interface in mind, many internal routings (using it's fantastic app totalmix), adjustments and even a tricky workaround with the toshlink cable to redirect some inputs digitally...
I couldn't just start from scratch using another interface. also I couldn't take the risk of using it before having tested the device extensively during at least two weeks.
and I really made a huge investment in this audio interface, I just hope it works soon, without being a too big pain in the ass for you guys.
I second what @Calcutta said. IOS music is in its relative infancy so while it is grown up enough to be used in a professional setting you may need to be inventive with your set-up and ready for at least some compromises. I'm sure you're not going to give up, do you?
ahá! AB version 2.1.2 makes a little (but great) improvement to my rme+audiobus+sugarbytes' apps problem.
now i can use sugarbytes apps, and also choose any of my 18 inputs BUT ONLY if i choose an app as an output. but NOT the default output in audiobus.
that's really weird, as choosing AUFX space and turning dry/wet slider to 0, is like using default output... but it seems the way AB handles audio by itself, causes the same crash than before.
but at least now i can use my fireface ucx + sugarbytes apps + some apps!!! as output.
i hope this problem gets totally solved soon. i got responses from rme and sugarbytes support teams, i really appreciate it, and i have serious hopes.
Glad to hear ecce-cello!
How did Fusion go?
@hmtx fusion festival always amazes me.
it's a huge festival with almost 90.000 people, totally self-managed and independent, but so well organized... each artist has it's driver and transport, stage manager, producer, audio-engineer from the festival. they don't pay good, but you get so well threated in return, that it's a totally satisfactory experience.
i will repeat!
finally! this new update of audiobus sdk and sugarbytes' apps totally fix my problem using my RME audio interface inside audiobus.
i'm so happy. thanks guys for the well done work.
I had the same problem. Delete and reinstall Audiobus, sugar bytes shows up just fine after.