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.

App Development?

2»

Comments

  • Master_AscendantMaster_Ascendant

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Thank you.. yeah, this is defiantly a journey for sure!

  • brambosbrambos

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Indeed, but even Obj-C is not lock-free. Basically, in the render thread you should stay away from anything but C, C++ or assembler.

    And for AUv3 you can not use swift (yet). So if you would like to keep that avenue open, Objective-C is the way to go.

  • Master_AscendantMaster_Ascendant
    edited April 2017

    @brambos said:

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Indeed, but even Obj-C is not lock-free. Basically, in the render thread you should stay away from anything but C, C++ or assembler.

    And for AUv3 you can not use swift (yet). So if you would like to keep that avenue open, Objective-C is the way to go.

    Sweet.

    Edit: Yeah, I would definitely like to keep an open mind with all that for sure. I would love to create an AUv3 app. I'm kind of thinking of trying to create a kind of simple visualizer or something to start with. Just something I can use to get my hands dirty in audio programming but I'm not sure. I would like to create some sort of instrument in time but even just a simple visualizer is going to take some work. It's hard to say what will be doable in the years to come as I learn but I'm hoping for the best. lol. Thanks! :)

  • Master_AscendantMaster_Ascendant

    Just found AudioKits Vimeo: Here. I set the link to the beginning of when they started posting. Looks like a lot of fun!

    I think I'll be playing with the Playground thing for a min. as I begin learning this stuff which I think is with Swift but I'm not sure.. I'll be looking more into it today and in time be learning C, Obj-C and C++.. I think starting with Objective-C. I'm really excited about this. It's going to be a lot of fun and a dream come true if I can do ANYTHING with any of this at all. Thanks for the help everybody! I really appreciate it a lot, and I'm hoping this will help others in and into the future etc.

    If I can at all make anything out of this all I think I'll make some video tutorials or something. Not that I have ever done anything like that before, have always wanted too, but anyways.

    Here's to a hopeful future!

    Thanks again!

    • MA
  • moodscapermoodscaper
    edited April 2017

    @brambos said:
    And for AUv3 you can not use swift (yet).

    I think again, it depends what you're doing. If you're doing apps that require you to do your own rendering / processing, then yeah, totally get that. I leave that sort of thing to you guys :smile: But...

    I've got AU working using audio nodes 99% there with Swift from AVFoundation, pretty much the same way I got IAA working. I did need a couple of C functions to do the bridging in and out of the Core Audio layer, but it works.

    But of course, none of this is documented (yet...) so I'm waiting for Apple to break my stuff sooner or later :smile:

  • moodscapermoodscaper
    edited April 2017

    edit - double post.

  • Master_AscendantMaster_Ascendant

    Awesome.. this is really fascinating! Thanks guys! :)

  • nrgbnrgb

    @Master_Ascendant said:
    I'll be looking more into it today and in time be learning C, Obj-C and C++.. I think starting with Objective-C.

    I'd start with at least a little C. After getting over the first couple of hurdles I think it's quite an easy language to grasp and it'll make the move into ObjC much easier.

  • Master_AscendantMaster_Ascendant

    @nrgb said:

    @Master_Ascendant said:
    I'll be looking more into it today and in time be learning C, Obj-C and C++.. I think starting with Objective-C.

    I'd start with at least a little C. After getting over the first couple of hurdles I think it's quite an easy language to grasp and it'll make the move into ObjC much easier.

    Ok, thanks.

  • mathieugarciamathieugarcia

    "Modern" C++ (C++11/14/17), and some Obj-C, but just to handle iOS basics, just like @brambos suggests. It will take time to master C++, or any programming language really, so you should start by some "general" programming lessons; take your time. It will require a lot of patience, trials & errors. Then, you should learn about concurrency, which is far from easy, but gladly there're plenty of resources readily available.

    You need to study signal processing as well. I would recommend: http://www.dspguide.com/, and if it seems too complicated, then you'll need to get back into simple algebra & trigonometry.

    That's a long journey, but you will get there!
    Cheers!

  • Master_AscendantMaster_Ascendant

    @mathieugarcia said:
    "Modern" C++ (C++11/14/17), and some Obj-C, but just to handle iOS basics, just like @brambos suggests. It will take time to master C++, or any programming language really, so you should start by some "general" programming lessons; take your time. It will require a lot of patience, trials & errors. Then, you should learn about concurrency, which is far from easy, but gladly there're plenty of resources readily available.

    You need to study signal processing as well. I would recommend: http://www.dspguide.com/, and if it seems too complicated, then you'll need to get back into simple algebra & trigonometry.

    That's a long journey, but you will get there!
    Cheers!

    Thanks!!! :P

  • realdavidairealdavidai

    @brambos said:

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Indeed, but even Obj-C is not lock-free. Basically, in the render thread you should stay away from anything but C, C++ or assembler.

    And for AUv3 you can not use swift (yet). So if you would like to keep that avenue open, Objective-C is the way to go.

    What would be a consequence of code that is not lock free? Crashes? Performance?

  • brambosbrambos

    @realdavidai said:

    @brambos said:

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Indeed, but even Obj-C is not lock-free. Basically, in the render thread you should stay away from anything but C, C++ or assembler.

    And for AUv3 you can not use swift (yet). So if you would like to keep that avenue open, Objective-C is the way to go.

    What would be a consequence of code that is not lock free? Crashes? Performance?

    Mostly glitches and weird audio breakups at random, unpredictable moments.

    It's basically the CPU picking its nose, waiting for unimportant stuff to finish while it's in the middle of the most time-critical part of your code.

  • realdavidairealdavidai

    @brambos said:

    @realdavidai said:

    @brambos said:

    @moodscaper said:
    Really depends what you want to build. I would avoid Xamarin for music apps though, even thought it's great for cross-platform consumer / business type apps. AVFoundation may get you part of the way in Swift. Really depends what you have in mind... All my apps are 95% Swift FWIW. Worth keeping in mind (as @brambos said), you could write say your UI and higher level classes in Swift, then use Obj-C or even C++ / C to do some of the more time-critical stuff. My $0.02. Good luck!

    Indeed, but even Obj-C is not lock-free. Basically, in the render thread you should stay away from anything but C, C++ or assembler.

    And for AUv3 you can not use swift (yet). So if you would like to keep that avenue open, Objective-C is the way to go.

    What would be a consequence of code that is not lock free? Crashes? Performance?

    Mostly glitches and weird audio breakups at random, unpredictable moments.

    It's basically the CPU picking its nose, waiting for unimportant stuff to finish while it's in the middle of the most time-critical part of your code.

    I see is there a developer slack channel where iOS AU developers can peer support? I'm not a developer just someone who would like a more stable, less glitchy, AU multi-instancing world. I gather that the Apple support is not cutting the mustard. I'd be willing to setup a slack channel if one does not exist

  • [Deleted User][Deleted User]

    Also look into libpd since I remember read somewhere it's possible to embed pd abstraction (wrap) into C coding (ofx maybe?) and bypass some of the hard code that the devs are pointing you. (I could be wrong but almost as start seems less difficult IMHO) mobmuplat or pdparty are a bit more fun to not being frustrate by pure coding. When you get really serious into developing the obj-c ftw!

    Making Musical Apps
    Real-time audio synthesis on Android and iOS
    http://shop.oreilly.com/product/0636920022503.do

    ;)

  • Master_AscendantMaster_Ascendant

    Found this:

  • Master_AscendantMaster_Ascendant

Sign In or Register to comment.

© Vanilla Keystone Theme 2024