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.

Apple Plans Combined iPhone, iPad & Mac Apps to Create One User Experience

13»

Comments

  • @u0421793 said:
    Gadget runs on both, must be a miracle.

    What I don’t get is, if iOS developers want to make their apps work on MacOS, what’s stopping them from doing it now? Korg did it with Gadget. I assume they had to rewrite a lot, but they also get a nice $300 for the package.

    Gadget is a standalone app. The individual gadgets are AU/VST/etc. plug-ins. If Apple makes it so an iOS app can run on a Mac as is, how will it work for apps that use IAA or AUv3? Sounds like a lot of work for Apple and some big changes to be made, and then what will developers do with the opportunity? Maybe it would apply best to more basic apps than to music-making apps.

  • @lovadamusic said:

    @u0421793 said:
    Gadget runs on both, must be a miracle.

    What I don’t get is, if iOS developers want to make their apps work on MacOS, what’s stopping them from doing it now? Korg did it with Gadget. I assume they had to rewrite a lot, but they also get a nice $300 for the package.

    Gadget is a standalone app. The individual gadgets are AU/VST/etc. plug-ins. If Apple makes it so an iOS app can run on a Mac as is, how will it work for apps that use IAA or AUv3? Sounds like a lot of work for Apple and some big changes to be made, and then what will developers do with the opportunity? Maybe it would apply best to more basic apps than to music-making apps.

    But that might be much more difficult for independent developers. Korg is big enough and already had an own shop to distribute plug-ins etc.
    Moog f.e. is a famous but small team and if i understand that, they would be interested in plug-ins for mac/windows as well but have to focus on what they can control without huge work for support, testing, copy protection etc.
    For companies which are already into it it might not be a problem.
    I remember an interview about Beepstreet where he said the income of iOS isn´t really great and that might be one reason he tried to do AU/VST as well (Sunrizer, Dagger). But it seems it doesn´t worked out because of some reasons. Bad copy protection, too much support, too much competition.
    So it seems he is back iOS only maybe.
    Virsyn f..e ported most of their old code in new dress as iOS apps and their desktop tools are a grave and looks like from early 90´s.
    I think it´s hard to say which tool from which developer might have a better market other platforms or not.
    I mean i would love some U-he iOS apps but i doubt they will do this anytime soon.
    Apple could start it themselves and make kind of small Logic for iOS.
    But not sure.....think about you would get a fully featured and multi-touch optimized (if that would be even possible) Logic for iOS for about 50 dollar.
    When i see what´s all in Logic included now it would make as self contained app all iOS app i ever bought (and maybe most future ones) obsolete.
    So maybe it´s better for both markets when things stay where they are.
    Using ThumbJam as midi controller or record Model D with my favorite FX in Logic is already a great workflow (if that IDAM thing would work more stable yet).
    And at the end Apple still want to sell you mac and iOS devices and i doubt customers of mac will prefer to buy their tools just trough a mac app store (which has also some pros).

  • edited April 2018

    @lovadamusic said:

    @u0421793 said:
    Gadget runs on both, must be a miracle.

    What I don’t get is, if iOS developers want to make their apps work on MacOS, what’s stopping them from doing it now? Korg did it with Gadget. I assume they had to rewrite a lot, but they also get a nice $300 for the package.

    It's not the porting itself - that should be relatively straightforward*, but my estimation is that providing good customer support (and the troubleshooting that comes with it) on MacOS would eat up so much time that there's very little time left for actual new product development.

    *) in theory: in practice there will very likely be unexpected weird issues in the implementation of AUv3 on MacOS.

  • Sigh.... Just bring a f);&@;$%+} shared file system for f€~£|•%#^ sakes.
    How complicated is this?

  • @brambos said:
    I suspect user experience will suffer for anything but the most basic apps as UI design will become a schizofrenic mess. This is one of those concepts that I doubt Steve would have allowed; just because something is technologically possible doesn’t mean it makes meaningful sense.

    My point already for years. In the beginning you had just this small iPhone screens and the bigger iPad. The UI was especially developed for both nowadays you see apps like iDensity and Moebius Lab originally made for iPad also available for iPhone with more or less a downscaled UI which makes it just impossible to work with on an iPhone. Result in the end is for example negative feedback bij iPhone SE users that think the UI sucks.

  • @brambos said:

    @lovadamusic said:

    @u0421793 said:
    Gadget runs on both, must be a miracle.

    What I don’t get is, if iOS developers want to make their apps work on MacOS, what’s stopping them from doing it now? Korg did it with Gadget. I assume they had to rewrite a lot, but they also get a nice $300 for the package.

    It's not the porting itself - that should be relatively straightforward*, but my estimation is that providing good customer support (and the troubleshooting that comes with it) on MacOS would eat up so much time that there's very little time left for actual new product development.

    *) in theory: in practice there will very likely be unexpected weird issues in the implementation of AUv3 on MacOS.

    That's kind of what I figured. People get excited about this idea of being able to run iOS music-making apps on a Mac, but even if these rumored Apple plans are true, would it actually happen? Do iOS devs, large or small, even want it? As far as how iOS apps would look and run on a Mac, the security involved, the differences in hardware... so many issues, it sounds like a huge mess added to messes we already have. OTOH, as Cib suggested, as it stands, we have some fantastic capability using Mac and iOS as two separate platforms working together.

  • I think it would be great. Full touchscreen support on macOS and trackpad/mouse support on iOS could be very useful additions. Being able to run iOS apps on mac and vice versa sounds really great to me from a user perspective. They wouldn't have to be full screen on mac either, just a little plugin window, fine with me. No extra graphical stuff needed to develop then. The bit about macs leaving intel architecture in favour of ARM does worry me, as I'm afraid the hackintoshability we currently enjoy due to the usage of the same chips for PCs might come to a sudden end. And I like my hackintosh, it's an intel nuc skull canyon with a capacitive multi-touch acer screen, which I find quite useful even though the OS isn't optimised for touch (yet?)...

  • What Brambos said .. Screw it, I’m gonna use Reason w my iPad Pro as an RS remote

  • Microsoft goes for their universal apps approach by the greatest common divisor between their different API's. Apple goes for their bitcode to target different platforms.

    Which approach will prevail?

    Apple might have the smarter approach but Microsoft does have a lot of mass. The market is not that logic.

  • @bert said:
    Apple might have the smarter approach but Microsoft does have a lot of mass. The market is not that logic.

    Even with all that mass they had to abandon Windows Phone after pouring in money for years.

    To be honest the OS turned out pretty good in the end. It just took them way too long to create a well rounded concept coming from a 'me too' mentality.

    I won't say Apple is perfect, but in my experience genuine focus and attention tends to work better than trying to do it all.

    IMHO it's the same reason Nintendo is still around...

Sign In or Register to comment.