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.

Multiple Audio Outputs (poll)

I'm sure most of us would like to see these on most apps, but are you willing to pay for them?

Multi outs
  1. Which option most suits you?17 votes
    1. I would be willing to pay extra for the initial app for multi outs.
      29.41%
    2. I would not be willing to pay extra for multi outs.
        0.00%
    3. I would like the option as an IAP for multi outs.
      52.94%
    4. I don't need multi outs, even stereo is overkill. Bring back mono and SCZI !
      17.65%

Comments

    • It depends on the app
  • Presume you are considering apps that are suitable for multi outs.

  • edited March 2016

    I want multi outs on my monotron!
    [edit]
    On a more serious side I would love to be able to multi out most of my drum apps.

  • Yep, depends so I choose IAP.

  • Yes I want that,I need that (yesterday)
    Willing to pay :)

  • Multiple output ports are declared in the metadata of an app, so it's not something that can be enabled by an IAP. Sure, the ports could be non-functional (just output silence) until the user pays, but I think that would be very frustrating and confusing: you load an IAA port in Audiobus or AUM, but there's no sound, then you open the app and it says you must buy in IAP for it to enable the port. I don't like that idea.

  • @j_liljedahl said:
    Multiple output ports are declared in the metadata of an app, so it's not something that can be enabled by an IAP. Sure, the ports could be non-functional (just output silence) until the user pays, but I think that would be very frustrating and confusing: you load an IAA port in Audiobus or AUM, but there's no sound, then you open the app and it says you must buy in IAP for it to enable the port. I don't like that idea.

    Thanks for the info :)

    Is it fair to say then, that it seems that many Devs perceive the costs involved (time and money) to not be worth implementation of multi outs? Or is there another reason they seem to be avoided.

    Harkingback to my studio days, multi outs were pretty much always an option on what was considered Pro gear.

  • I think the biggest reason simply is that many devs don't know how to do it, or don't have the time or priority to learn, or enough incentive to spend a day working on it just to make a free update of their app.

  • Everybody — get everybody else to support my Quasonama idea, which will drive the demand for at least four channels of discrete audio through everything.

  • Export to stems would be enough for me. I really wish Rock Drum Machine etc... would do this.

  • I just want multi outs, don't care how I have to pay for them :)

  • @richardyot said:
    Export to stems would be enough for me. I really wish Rock Drum Machine etc... would do this.

    Or just create files per track (stems after all) in AS as AUM does so handily (although I'm using up file space very quickly this way :))

  • Or, perhaps the current design of the app makes it difficult to accomplish and would require refactoring that the dev doesn't really want to do. That's closer to the case for DrumJam, for instance, regarding adding separate outs for each pad (or loop instance). I could bore you with my excuses, but I won't (unless you beg)!

  • @sonosaurus said:
    Or, perhaps the current design of the app makes it difficult to accomplish and would require refactoring that the dev doesn't really want to do. That's closer to the case for DrumJam, for instance, regarding adding separate outs for each pad (or loop instance). I could bore you with my excuses, but I won't (unless you beg)!

    Begging :)

    Let people know we want to understand the issues in making apps, so that we can better understand the costs in time and hard work involved. Then we will all take you down the pub and get you pissed so you agree to do them ;)

    I know some people hate price rises, but multi outs is one thing I think is worth its weight in gold :)

  • @sonosaurus I think we hear you,but lets have a poll:
    Would you pay double€$ for Drumjam Pro with seperate outs for each loop/pad ?
    I would :)

  • What about the good folks at audiobus make a Dev kit for multis?? WHOOAAA I amaze myself

  • @Fruitbat1919 said:

    multi outs is one thing I think is worth its weight in gold :)

    More than their weight in gold, they are virtual, so they weigh nothing :D

  • @sonosaurus said:
    Or, perhaps the current design of the app makes it difficult to accomplish and would require refactoring that the dev doesn't really want to do. That's closer to the case for DrumJam, for instance, regarding adding separate outs for each pad (or loop instance). I could bore you with my excuses, but I won't (unless you beg)!

    I'm guessing it is down to the internal routing of the app and how early in the audio chain the sources are mixed within the app ?

  • @AndyPlankton said:

    @Fruitbat1919 said:

    multi outs is one thing I think is worth its weight in gold :)

    More than their weight in gold, they are virtual, so they weigh nothing :D

    Damn I thought that one would slip through the net B)

  • @Fruitbat1919 said:

    @AndyPlankton said:

    @Fruitbat1919 said:

    multi outs is one thing I think is worth its weight in gold :)

    More than their weight in gold, they are virtual, so they weigh nothing :D

    Damn I thought that one would slip through the net B)

    Would that be the net you have woven with all the virtual routing cables linking all these virtual outs to AUM hehe :D

  • @Frank said:
    @sonosaurus I think we hear you,but lets have a poll:
    Would you pay double€$ for Drumjam Pro with seperate outs for each loop/pad ?
    I would :)

    I would pay again for a DrumJam Pro app, ive more than got triple what I paid for the app in use.

    Would love to see Drum Jam expand with even more kits as well :)

  • edited March 2016

    Maybe we could have DrumJam Electro with synth sounds? Not sampled synth sounds....a built in drum synth :)

  • I would also like to see some synths with multi outs. Two stereo pairs. One with full sound, one pre FX.

  • edited March 2016

    The Poll may have been biased after Jonatan Liljedahl's technical insight that IAPs are impossible , so I've voted for "would pay more" . I think the best financing solution would be DrumPerfect model of a "bundle upgrade" to a Pro version with the multi -outs.

    Regarding how hard/timeconsuming/worthwhile it would be for the devs , I would throw into the argument the irony to me that some devs DO seem ok/happy/obsessed to dedicate the hours into adding internal fx , which of course users wouldnt want/need if they had multi-outs , especially with the arrival of AUs effectively duplicating the top notch proven goodies we have in our fx folders from dedicated fx experts.

    //Extrapolation : This is part of a wider issue as I see it in IOS , where many devs are trying to add additional unnecessary functions to the core of their app before the core functions are complete.
    My particular gripe here is midi sequencers , from Genome onwards & now ModStep ,
    the basic sequencing functionality is not fully fledged before they want to add audio & fx.
    In the pipeline Is Loopy Masterpiece , who wants to add fx . MidiSequencer Pro & SBD MidiLooper are both talking of adding audio & fx in time , before the midi app is even released .

    It seems to me many devs are / will be spending a lot of time on redundant areas of their apps such as mixers & fx , as these functions are duplicated & improved by dedicated apps which AB, IAA & AU make easier & more useable . I would ask them to focus on full implementation of their core functionality , & provide multi-outs so we can use AUM , Auria, Cubase etc with our preferred Fx . //extrapolated

  • @Wally

    Good point about adding lots of FX in app. AUM has made it so easy to add FX where we want them, so please Devs make multi outs a priority instead :)

Sign In or Register to comment.