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 Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Qneo / Voicisynth SDK Audiobus support

2»

Comments

  • I can do without this voice synth but I won't go without audiobus. Lots of other apps that do have audiobus folks, I see no problems in my other apps with audiobus and will leave the voice synth folks to play with themselves. Much like the tabletop crew , lol. Like I said I do not even remotely need this voice synth app.

  • I like VoiceSynth, and I've used it for a long time now. I was looking forward to using it in AB2. It's a shame about their choice to drop Audiobus. I hope they reconsider.

  • I have had some issues with stability. Putting certain apps in certain orders has frozen and crashed stuff. But really that's not a complaint, because it just came out. I would never expect perfection. The one facebook comment said it perfectly about just putting a message at the start of voice synth mentioning stability issues.

    You can't claim users have had problems after two days. Some iOS musicians are waiting for the weekend to play with AB 2. Any developer jumping ship this quickly is just ridiculous. Even if they are right and IAA becomes the shit... By then the ill will in people's heads will be enough for that company to be kaput.

  • Rob Fielding's comment on discchord provides some good, third party perspective as a developer. Remember, he made the amazing Cantor and Geo synthesizer. Some credibility in that. Then again, Rob ducked out of iOS development completely last I heard.

    Anyway, he relates to the difficulty of keeping up with Audiobus revisions.

    I just don't understand how this can be a problem for some devs, when apps like Bebot or Animoog can go for almost a year with no updates and they still work in Audiobus just fine

  • @PaulB said:

    @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.

    For the record: I don't even know if we removed Voice Synth from the Audiobus compatible apps listing or if it was the Qneo developers. I certainly have no recollection of doing it, neither has Mike. But it is the right thing to do anyway. If the developers don't want to support Audiobus in the future then users should not be encouraged to download it.

    Furthermore there is literally nothing we (Audiobus) can do at this point. This is one developer making a from our perspective hard to understand decision. Their app seems to work, they don't have to do anything right now, their users seem to be happy with how their app works and yet they're discontinuing a feature pretty much out of the blue. And then they blame us for it with a reason that makes no sense.

    They complain about us not supporting iAA. We've been working on incorporating IAA technology in Audiobus since June 2013. We're working on it right now. Audiobus developers know of this since September 2013 (we've announced it on the developer forum).

    They complain about stability issues. We know of no stability issues. The Qneo developers have not brought any stability issues to our attention. Blaming us for fixing bugs fast and in a responsible manner by releasing updates during a time of huge changes (iOS 6 to iOS 7 transition and most likely iOS 7 to iOS 8) is something that I cannot wrap my mind around.

    Qneo has benefitted from their apps being compatible with Audiobus to the tune of a couple thousand US dollars just from being listed on the compatible apps directory. If they think spending a few hours (the average time an iOS developer spends on making an effects app compatible with Audiobus) so be it.

    They can add their app back any time they want, they cold do it right now, we're definitely not stopping them.

    I suggest users ask them in a friendly manner to change their stance and in the mean time search for alternatives to Voice Synth in their Audiobus setups instead of relying on workarounds to make it work, since these could stop working with any update of their apps.

    I'm struggling a lot with understanding why they're doing this and I have no interest in furthering this completely unnecessary and in my opinion forced drama.

  • edited April 2014

    @Hmtx said:

    Rob Fielding's comment on discchord provides some good, third party perspective as a developer. Remember, he made the amazing Cantor and Geo synthesizer. Some credibility in that. Then again, Rob ducked out of iOS development completely last I heard.

    Anyway, he relates to the difficulty of keeping up with Audiobus revisions.

    I've attached a screenshot of Bebot, one of the oldest Synthesizers for iOS. Its last update is from a year ago. The Bebot developer added Audiobus support to it back then. It still works.

    That being said: Audiobus is a relatively new product on a platform that changes rapidly.

    Will there be updates during transitions between iterations of iOS? Yes.

    Did we release new versions of the SDK in the first days of Audiobus. Yes.

    Was this to be expected? Of course it was.

    If you add support for a new product then you should expect teething issues.
    That's why we launched Audiobus with a limited set of compatible apps instead of making the SDK available to the public straight out of the box. That's why the 2.0 SDK is still not public and why we're only offering access to it to seasoned developer who have proven in the past that they're capable.

  • @Sebastian said:

    I suggest users ask them in a friendly manner to change their stance and in the mean time search for alternatives to Voice Synth in their Audiobus setups instead of relying on workarounds to make it work, since these could stop working with any update of their apps.

    I agree this is the right (and best) way.

  • @Sebastian Your comments are clear and make perfect sense.

    I think we should take your advice and sent the developers polite comments via email urging them to reconsider. Also a more visible (and therefore perhaps more effective) thing to do would be to post those same polite requests on their FB page and via AppStore reviews.

  • @Sebastian said:

    @PaulB said:

    @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.

    For the record: I don't even know if we removed Voice Synth from the Audiobus compatible apps listing or if it was the Qneo developers. I certainly have no recollection of doing it, neither has Mike.

    I'm glad to hear this, although saying you both have no recollection of it is a strange way to phrase it. I'm sure you would know whether or not either of you had removed Voice Synth from the list since you heard of Qneo's intentions.

    @Hmtx said:

    Rob Fielding's comment on discchord provides some good, third party perspective as a developer.

    He also rewrites history. Rob added Audiobus and posted a video showing it working perfectly. There was then a delay, during which I contacted him and he told me that in tinkering around with other features, he had broken stuff that was working before and couldn't work out how to fix it. Some time after that, @sonosaurus was engaged by Jordan Rudess to get everything working again, which he did. Apart from a bit of a hiccup with naming new presets, which was quickly fixed, Geo Synth has worked brilliantly with Audiobus ever since with just one update when the introduction of iOS 7 broke something. Add to Rob's revisionism his continued soapboxing about how Geo Synth should only ever have been a MIDI controller (months after abandoning the whole iOS platform) and there you have his 'good, third party perspective'. The truth is, he has never had to keep up with Audiobus updates.

  • edited April 2014

    It sounds to me from the 'IAA is free' comment that QNEO are trying to save money on development costs. Period.

  • edited April 2014

    I know i'm not making new friends in THIS forum but to be honest:i was not going mad about the release of Audiobus 2 because at the end i want to do everything in ONE app and IAA comes closest to what i want for my workflow.Even with it's "quirks"i would prefer it every time over AB.I even did not buy the Multiroute upgrade yet (guess i'll do it anyway just to support a great developer)cause i don't know if i can make good use of it or not.My personal future is clearly the IAA route,using it with cubasis or auria feels already quite close to the use of a desktop DAW.I wish apple would care better about this stuff but at least they did not forget there are still musicians arround that like to use apple products for their creativity.I guess (hope)things will grow up with IOS 8.

    Though I'm pretty sure using AB more again with the release of Cubasis 1.8 cause IAA can't handle Midi CCs.

    I agree with the Voice synths dev that IAA should be the future and standard but that will only happen if apple wakes up one day.

    I disagree though that they kick out Audiobus support.That's a chuck norris roundhousekick into the customers face,let them just decide by themself if they wish to use AB or IAA.

  • Given their past track record I'm fairly confident that Apple will break something in IAA when they release iOS 8.0, forcing numerous developers, including Qneo, to scramble to update their apps to adopt the new Apple 'standard'.

    What? Me? Cynical?...

  • @PaulB said:

    Given their past track record I'm fairly confident that Apple will break something in IAA when they release iOS 8.0, forcing numerous developers, including Qneo, to scramble to update their apps to adopt the new Apple 'standard'.

    What? Me? Cynical?...

    touche :)

    But IOS7 was a very radical change compared to the older IOS.My hopes are (trying to be optimistic here :-) that they use 8 more to polish the current system.First leaks seem to confirm this theory.

  • Hope for the best, plan for the worst... :)

  • @Crabman said:

    IAA can't handle Midi CCs.

    Is that true? I thought Tabletop's Mastermind was handling Midi CCs through IAA?. I'm no expert on this I'm just using what works and learning on the way.

  • I have the answer as to why the folks over at voice synth issued such whacky statements......

    >
    DRUGS... It is starting to make more sence now at least.

  • @firejan82 said:

    @Crabman said:

    IAA can't handle Midi CCs.

    Is that true? I thought Tabletop's Mastermind was handling Midi CCs through IAA?. I'm no expert on this I'm just using what works and learning on the way.

    @firejan82 said:

    @Crabman said:

    IAA can't handle Midi CCs.

    Is that true? I thought Tabletop's Mastermind was handling Midi CCs through IAA?. I'm no expert on this I'm just using what works and learning on the way.

    Thats what the cubasis dev says:

    http://www.steinberg.net/forums/viewtopic.php?f=183&t=57782&sid=11407ab4d805308a07045fec66788114#p349680

  • WOW! There is certainly not much support for Voice Synth over at their own Qneo facebook page. Apple is going to be very busy making refunds for this app it appears. Why do developers shoot themselves in the foot like this?

  • @Crabman said:

    @firejan82 said:

    @Crabman said:

    IAA can't handle Midi CCs.

    Is that true? I thought Tabletop's Mastermind was handling Midi CCs through IAA?. I'm no expert on this I'm just using what works and learning on the way.

    Thats what the cubasis dev says:

    http://www.steinberg.net/forums/viewtopic.php?f=183&t=57782&sid=11407ab4d805308a07045fec66788114#p349680

    OK, I think I understand it a bit more now, it's virtual MIDI in the background handling those CCs and not IAA

  • https://www.facebook.com/pages/Qneo/107770329291794

    This is a link to the nearly 100 percent disapproval from their users on their very own facebook page LOL. just down on the left when you get there.

  • It will be really interesting to see what Retronyms does. They have been "planning" to add Audiobus support to their apps. for over a year. Their latest excuse was also that they were waiting for Audiobus to implement IAA. Another developer with ulterior motives using that lame excuse. Give the people what they want (in my Eddie Levert voice:)

  • What are the instabilities mentioned by QNeo anyway?

  • Wobbly legs...

Sign In or Register to comment.