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.
Qneo / Voicisynth SDK Audiobus support
Hello,
This is what's on the Qneo's Facebook wall :
IMPORTANT NOTICE TO VOICE SYNTH AUDIOBUS USERS
Audiobus support will be discontinued soon, as it does not meet the stability standards we want to offer our customers. The audiobus SDK in Voice Synth is currently malfunctioning. We advise to use Apple’s inter-app audio (IAA), which is free, integrated in iOS, and stable since introduction.
For continued audiobus support, please ask the audiobus developers to support IAA. Then all your IAA-enabled apps become audiobus compatible, while their stability will not be compromised.
Could you tell us what you think about that ?
(I'm just asking...)
Thanks
Comments
what a joke, I mean it is great to push IAA forward, but I don't think it is more stable than AB2. Is it?
And I don't think it makes any sense to limit users' choices just because the company can't figure out how to make their app work with AB2.
OK, I'll stop. Someone with a better perspective please chime in.
I'd be interested to hear the AB Team's perspective, but, like @hmtx, in my experience IAA has not been "stable since introduction." Would be interesting to hear an honest assessment of IAA from the developer side.
OK, so I guess it does make sense for a company to decide what market they want to pursue. It doesn't bother me when devs decide they can't support older versions of iOS for example.
I just think at this point it seems like an odd marketing decision to exclude Audiobus users. IAA has a long way to go before it is a great user experience.
@crony said:
Was this posted on April 1st?
2nd post from this member
I found the first more interesting
http://forum.audiob.us/discussion/100/voice-synth-from-qneo-all-korgs-synths
Oh my how things have changed.
Voice Synth has been removed from the Audiobus compatible app list. Apart from being a bit disingenuous, since the current version is still compatible, it inconveniences nobody other than current Audiobus users.
@richardyot said:
Sadly not.
I just left a comment on their FB-site.
So I have to switch to iVoxel, I think? Or I will wait for this new shiny vocoder app, some forum members gonna betatesting?
We're always working very hard on fixing bugs and other issues that are brought to our attention, especially any issues regarding stability.
That being said: We don't know about stability issues with the current version of the Audiobus SDK and none have been brought to our attention from the developers of voice synth or any of the other 1131 developers who have access to the Audiobus SDK.
@Sebastian None of us believe it's anything other than their lack of skill that is causing their problems, but removing Voice Synth from the Audiobus apps list before they update is helping nobody. A lot of Voice Synth users will avoid updating rather than lose the Audiobus compatibility.
@PaulB: I don't want to comment on that. The only thing I can currently suggest is asking them in a very friendly tone to rethink their decision.
That won't put the current (compatible) version back in the AB database...
...or are you saying devs can remove their own apps from your database?
@PaulB said:
It doesn't have to be in the database to run. You can just launch it manually while Audiobus is running in the background and if the SDK is still in Voice Synth it'll show up and work in Audiobus. Ugly hack-ish workaround but if you really want to use it...
And you should never update the app either if you want that to work.
I wouldn't point out this solution to anyone either, but some guys on Facebook are coming up with an even nastier one.
Jingle
Today's ugly Audiobus hacks are brought to you by: Inter-App Audio Drama. Please tune in next time.
Voice Synth disappeared from the lists in AB, but yes, as said here, if you open it first and then go to the Effect slot list, it's there and it works fine. I wonder where the instabilities are... Well, if this silly decision of blaming AB is what they' will keep, I won't upgrade this app anymore then, since its presence in the Effect slot is the only reason I use it.
Is... is now the right time to announce that we're helping sell $50.000+ USD per month of third party developer's apps through our websites? I've yet to come up with a good reason to voluntarily opt out of that...
@Sebastian I'm going to leave this discussion here, since I don't have Voice Synth. I just wanted to point out that removing Voice Synth from the database is only inconveniencing your own customers by forcing them to use this workaround. Not the greatest customer service...
The guys berated Audiobus publicly because they didn't want to (or couldn't?) fix their code. That's just lazy or rude or they have some odd agenda. I say Sebastian has the right to get nasty back. Quietly dropping their app from AB is probably the most civil way to do so.
Carry on folks. QNeo just made themselves irrelevant (to my workflow anyway). It will be interesting to see if they change their mind.
I was just pointing out that his aim is off. Better revenge to keep it in and have QNeo discover that none of their customers bother upgrading when they publish the next update.
Sorry, definitely stopping here...
I sent the guy an email asking him to reconsider the decision. I also mentioned that @sebastian and @michael are helpful friendly guys and if there are indeed technical issues they might help him work through them.
This is a great app. A shame to see it go, especially as the awesome level could be significantly increased with AB2's multiroute.
@paulb, you are unstoppable and you know it.
I'll personally still use it 'cause I like it way more than iVoxel, won't update, will probably see how it works in IAA (only ever used it in AB before).
Ha! My first demo for students yesterday used iVoxel with AB2.
https://www.facebook.com/photo.php?v=226214140901494&set=vb.100005387285135&type=2&theater
I had the idea to do some robot humor music for Moogfest and was thinking of getting Voice Synth. Um, not now.
I talked to a new potential music developer yesterday with a grand idea, and the conversation centered around AB. I said adding that will make it a worthwhile app and make you more money.
@sebastian Is there a technical reason to not have generic IAA nodes available within Audiobus chains?
No problem for me, I can use it as IAA in AudioShare inside Audiobus ;-)
@syrupcore said:
Please ask me that in a few weeks again.
@Sebastian ;-) .....hmmmm! Smells like something good is cooking in the Audiobus kitchen! :-D
Updated comment from the developer on the Facebook link. https://www.facebook.com/pages/Qneo/107770329291794
It seems the developer agrees with syrupcore about IAA being the way forward (edit: sorry, didn't mean to put words in your mouth):
For the record, I'm not saying IAA is the way forward—I have no idea. I just asked about it based on Qneo's statements. Sounds like the fellas might have something cooking.
Even if they do wind up adding IAA nodes in AB (which could be cool I guess) the loss of the AB panel in Voice Synth or other IAA only apps will not be wonderful.
So the audiobus dev claims that voice synth hasn't contacted them, and Voice Synth claims they have...
@calcutta AB dev claims they never had any bugs brought to their attention from the Voice Synth devs. That rings true so far: sounds like they contacted the AB team with an IAA feature request, not a bug report.
Ah ok, fair enough, I misunderstood. Apologies.