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.

Patterning 3 by Olympia Noise Co (Released)

17810121315

Comments

  • @Antos3345 said:
    I am very happy that this app has been built for Auv3, but is it just a rebuild or are there some differences that are better ?

    The very short preview of new features :

  • @Antos3345 said:
    I am very happy that this app has been built for Auv3, but is it just a rebuild or are there some differences that are better ?

    Loads of new features ... here are a few ...

  • @Edward_Alexander said:

    I must say it looks exactly like Spacecraft 1 (?)

    This looks new...

  • @AudioGus said:

    @Edward_Alexander said:

    I must say it looks exactly like Spacecraft 1 (?)

    This looks new...

    Yup you can shape each step and control the rate 😎 amazing

  • @Antos3345 said:
    I am very happy that this app has been built for Auv3, but is it just a rebuild or are there some differences that are better ?

  • Great to know..my next purchase:)

  • @benkamen said:

    I had the same issue quite a few times, but there didn’t seem to be an issue with loading the kits. It even happened one time while the browser was open and I wasn’t even touching the iPad.

    I’m glad it’s not causing any major issues other than being annoying. I think it’s specifically p1 drumkits causing this, but not sure yet.

    In p1 and p2 the sample start end points were stored in sample numbers and now they’re stored as a percentage. I think that something in the data migration is causing the error message. But I haven’t been able to sit down and work on it yet.

    @galmandsværk said:
    This new version looks great! However, I like to control as much as possible via midi controls or with widgets in Loopy Pro. So, my question is: how many actions in Patterning 3 are available through auv3 parameters in Loopy Pro (etc) and/or via midi learn?
    Can I control delay and reverb values with midi messages? Or drum volumes? Or change patterns?
    If yes, then I’m ready to buy! 😀

    AU params - not yet. MIDI learn - most everything. If you find a param not MIDI assignable that should be, let me know.

    Great! Midi learn is fine 😊 Thanks for answering so quickly.

  • Welp, I now feel like my iOS library is set. Great job, ben kamen. My iOS mania started with the original and now the loop is complete. I can retire happy

  • @benkamen said:

    The main one I know people on this forum will be upset about is that the AU parameters are not yet exposed. please don't come at me with a pitchfork about it - but feel free to tell me how important it is to you. I rebuilt the entire MIDI mappings architecture with that in mind, so it's something that I should be able to do "quickly" - fingers crossed. I just ran out of time. That's number one on my list once I get through the initial launch period.

    The current beta of an equally iconic ios app is exposing its 1400 internal parameters in one update. Just saying....

  • @Wrlds2ndBstGeoshredr said:

    @benkamen said:

    The main one I know people on this forum will be upset about is that the AU parameters are not yet exposed. please don't come at me with a pitchfork about it - but feel free to tell me how important it is to you. I rebuilt the entire MIDI mappings architecture with that in mind, so it's something that I should be able to do "quickly" - fingers crossed. I just ran out of time. That's number one on my list once I get through the initial launch period.

    The current beta of an equally iconic ios app is exposing its 1400 internal parameters in one update. Just saying....

    Exposing that many parameters might make sense for some plugins but not others.

    I think the approach of midi mapping the most common functions is a good one, it is more accessible than AUv3 parameters in a lot of contexts.

  • wimwim
    edited May 27

    @espiegel123 said:

    @Wrlds2ndBstGeoshredr said:

    @benkamen said:

    The main one I know people on this forum will be upset about is that the AU parameters are not yet exposed. please don't come at me with a pitchfork about it - but feel free to tell me how important it is to you. I rebuilt the entire MIDI mappings architecture with that in mind, so it's something that I should be able to do "quickly" - fingers crossed. I just ran out of time. That's number one on my list once I get through the initial launch period.

    The current beta of an equally iconic ios app is exposing its 1400 internal parameters in one update. Just saying....

    Exposing that many parameters might make sense for some plugins but not others.

    I think the approach of midi mapping the most common functions is a good one, it is more accessible than AUv3 parameters in a lot of contexts.

    It also has the advantage of the mappings then being portable between hosts.

    The only time I use AUv3 parameters over MIDI mapping is when I need the added smoothness of AUv3 parameter fine control. That's almost never.

    [edit]: I haven't actually checked that Patterning MIDI mappings persist between sessions and hosts. I was referring to plugins where it does work that way.)

    [edit 2]: Unless I'm missing something, it seems midi mappings to parameters are saved per project, not globally unfortunately.

  • @wim said:

    @espiegel123 said:

    @Wrlds2ndBstGeoshredr said:

    @benkamen said:

    The main one I know people on this forum will be upset about is that the AU parameters are not yet exposed. please don't come at me with a pitchfork about it - but feel free to tell me how important it is to you. I rebuilt the entire MIDI mappings architecture with that in mind, so it's something that I should be able to do "quickly" - fingers crossed. I just ran out of time. That's number one on my list once I get through the initial launch period.

    The current beta of an equally iconic ios app is exposing its 1400 internal parameters in one update. Just saying....

    Exposing that many parameters might make sense for some plugins but not others.

    I think the approach of midi mapping the most common functions is a good one, it is more accessible than AUv3 parameters in a lot of contexts.

    It also has the advantage of the mappings then being portable between hosts.

    The only time I use AUv3 parameters over MIDI mapping is when I need the added smoothness of AUv3 parameter fine control. That's almost never.

    (edit: I haven't actually checked that Patterning MIDI mappings persist between sessions and hosts. I was referring to plugins where it does work that way.)

    Midi mapping means the app assigns CC and midi channels, instead of the user choosing? (Dunno--just guessing...)

  • @Wrlds2ndBstGeoshredr said:

    @wim said:

    @espiegel123 said:

    @Wrlds2ndBstGeoshredr said:

    @benkamen said:

    The main one I know people on this forum will be upset about is that the AU parameters are not yet exposed. please don't come at me with a pitchfork about it - but feel free to tell me how important it is to you. I rebuilt the entire MIDI mappings architecture with that in mind, so it's something that I should be able to do "quickly" - fingers crossed. I just ran out of time. That's number one on my list once I get through the initial launch period.

    The current beta of an equally iconic ios app is exposing its 1400 internal parameters in one update. Just saying....

    Exposing that many parameters might make sense for some plugins but not others.

    I think the approach of midi mapping the most common functions is a good one, it is more accessible than AUv3 parameters in a lot of contexts.

    It also has the advantage of the mappings then being portable between hosts.

    The only time I use AUv3 parameters over MIDI mapping is when I need the added smoothness of AUv3 parameter fine control. That's almost never.

    (edit: I haven't actually checked that Patterning MIDI mappings persist between sessions and hosts. I was referring to plugins where it does work that way.)

    Midi mapping means the app assigns CC and midi channels, instead of the user choosing? (Dunno--just guessing...)

    Sorry if I wasn't clear. Midi mapping just means that you can control parameters directly by midi. It doesn't imply whether or not you have a choice in the mapping. Some apps have fixed mappings, some let you change them, and some let you learn them by sending a message from a controller.

    Patterning has learn for parameters; I don't think it has any way to manually enter values like AUM does.

  • It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

  • @wim said:
    It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

    I set up a blank project with mappings i use and use it as a starting point. While a global option would be nice, it isn’t too bad.

  • @Wrlds2ndBstGeoshredr said:

    Midi mapping means the app assigns CC and midi channels, instead of the user choosing? (Dunno--just guessing...)

    No, the user sets them up with their preferred triggers.

  • @wim said:
    It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

    I haven't touched midi mapping any controls yet, but even if I save an empty drum kit with midi assignments, it forgets that I set it to midi only and the notes I wanted triggered. Would be nice to be able to save several drumkits with the right notes assigned for other apps.

  • wimwim
    edited May 27

    @espiegel123 said:

    @wim said:
    It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

    I set up a blank project with mappings i use and use it as a starting point. While a global option would be nice, it isn’t too bad.

    Yes, that is what I will do too. Needed to clarify though based on my earlier post before having checked. I'll upgrade from "no bueno" to "no es ideal". 😉

  • edited May 28

    @tyslothrop1 said:

    @wim said:
    It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

    I haven't touched midi mapping any controls yet, but even if I save an empty drum kit with midi assignments, it forgets that I set it to midi only and the notes I wanted triggered. Would be nice to be able to save several drumkits with the right notes assigned for other apps.

    Thanks, that sounds like a bug! There’s lots of little stuff like this, but I’ll get to it all. Thanks for your patience! We had a really good long beta period but things always get through the cracks which is to be expected.

    A feature that was in P2 but I haven’t had a chance to put back in yet is the ability to set a template project.

    But also - to clarify - the MIDI outputs belong to the drum kit. They are saved with a kit (except for this apparent bug). The MIDI inputs belong to the project. They remain the same when you change kits.

  • @benkamen Keep on Mister K, this is a brilliant piece of work...

  • Unless I’m missing it, I can’t find a way to select a global midi input channel ..
    Is using midi learn on each drum trigger the only way to select the midi input channel?

  • @benkamen said:

    @tyslothrop1 said:

    @wim said:
    It seems Patterning 3's midi settings are project specific - meaning you need to redo assignments for each project.
    No bueno IMO.

    I haven't touched midi mapping any controls yet, but even if I save an empty drum kit with midi assignments, it forgets that I set it to midi only and the notes I wanted triggered. Would be nice to be able to save several drumkits with the right notes assigned for other apps.

    Thanks, that sounds like a bug! There’s lots of little stuff like this, but I’ll get to it all. Thanks for your patience! We had a really good long beta period but things always get through the cracks which is to be expected.

    A feature that was in P2 but I haven’t had a chance to put back in yet is the ability to set a template project.

    But also - to clarify - the MIDI outputs belong to the drum kit. They are saved with a kit (except for this apparent bug). The MIDI inputs belong to the project. They remain the same when you change kits.

    Cool, thanks!

  • edited May 28

    What a wonderful interface. So happy it's AuV3, I skipped over the first two but i'm having a blast.

    Well worth the price of entry.

    Small report:
    Track Volume label gets cut off in standalone on 2018 11" iPad Pro

  • Following the MIDI assignment discussion here with interest. P3 looks decent.

  • @benkamen said:

    @Kashi said:

    @benkamen said:

    @Kashi said:
    Great stuff @benkamen ! Congrats.
    How do I import my own samples? I’ve pressed “open” in the drumkits page, but wav files are greyed out and don’t appear to be selectable

    Use the sample library instead of the drum kits one!
    https://docs.google.com/document/d/1OahHgkUCoPC9H92z68WxFTYudrvq9eYCMDaBGar_mP0/edit#heading=h.45jmnk3aq3v4

    Ah! Ok. I had issues accessing the manual yesterday, and then further problems saving the manual to my Books app, which is where I tend to put them....so I couldn't see that.
    Cheers!

    Were you able to save the manual to a pdf?

    Nope. Can’t figure out how to do this….

  • @Kashi said:

    @benkamen said:

    @Kashi said:

    @benkamen said:

    @Kashi said:
    Great stuff @benkamen ! Congrats.
    How do I import my own samples? I’ve pressed “open” in the drumkits page, but wav files are greyed out and don’t appear to be selectable

    Use the sample library instead of the drum kits one!
    https://docs.google.com/document/d/1OahHgkUCoPC9H92z68WxFTYudrvq9eYCMDaBGar_mP0/edit#heading=h.45jmnk3aq3v4

    Ah! Ok. I had issues accessing the manual yesterday, and then further problems saving the manual to my Books app, which is where I tend to put them....so I couldn't see that.
    Cheers!

    Were you able to save the manual to a pdf?

    Nope. Can’t figure out how to do this….

    To save the manual …

    • Click the link to the manual
    • Click on the three dots in the top right of the screen
    • Select “Share & export”
    • Select “send a copy”
    • Choose the format you want and click OK
    • Select the location where you want to save the copy to from the share sheet (Books app is an option)
  • @mikejohn said:

    @Kashi said:

    @benkamen said:

    @Kashi said:

    @benkamen said:

    @Kashi said:
    Great stuff @benkamen ! Congrats.
    How do I import my own samples? I’ve pressed “open” in the drumkits page, but wav files are greyed out and don’t appear to be selectable

    Use the sample library instead of the drum kits one!
    https://docs.google.com/document/d/1OahHgkUCoPC9H92z68WxFTYudrvq9eYCMDaBGar_mP0/edit#heading=h.45jmnk3aq3v4

    Ah! Ok. I had issues accessing the manual yesterday, and then further problems saving the manual to my Books app, which is where I tend to put them....so I couldn't see that.
    Cheers!

    Were you able to save the manual to a pdf?

    Nope. Can’t figure out how to do this….

    To save the manual …

    • Click the link to the manual
    • Click on the three dots in the top right of the screen
    • Select “Share & export”
    • Select “send a copy”
    • Choose the format you want and click OK
    • Select the location where you want to save the copy to from the share sheet (Books app is an option)

    Thanks @mikejohn , but I’m opening the manual from within the app itself and I can’t see 3 dots in top right of screen (?)

  • edited May 28

    @Kashi said:

    @mikejohn said:

    @Kashi said:

    @benkamen said:

    @Kashi said:

    @benkamen said:

    @Kashi said:
    Great stuff @benkamen ! Congrats.
    How do I import my own samples? I’ve pressed “open” in the drumkits page, but wav files are greyed out and don’t appear to be selectable

    Use the sample library instead of the drum kits one!
    https://docs.google.com/document/d/1OahHgkUCoPC9H92z68WxFTYudrvq9eYCMDaBGar_mP0/edit#heading=h.45jmnk3aq3v4

    Ah! Ok. I had issues accessing the manual yesterday, and then further problems saving the manual to my Books app, which is where I tend to put them....so I couldn't see that.
    Cheers!

    Were you able to save the manual to a pdf?

    Nope. Can’t figure out how to do this….

    To save the manual …

    • Click the link to the manual
    • Click on the three dots in the top right of the screen
    • Select “Share & export”
    • Select “send a copy”
    • Choose the format you want and click OK
    • Select the location where you want to save the copy to from the share sheet (Books app is an option)

    Thanks @mikejohn , but I’m opening the manual from within the app itself and I can’t see 3 dots in top right of screen (?)

    Oh .. I see . Here’s the link to the P3 manual from further up the thread:

    https://docs.google.com/document/d/1OahHgkUCoPC9H92z68WxFTYudrvq9eYCMDaBGar_mP0/edit#heading=h.45jmnk3aq3v4

    You can click it and then follow the steps I wrote ..

  • edited May 29

    @benkamen long time user going through first run through of 3 now. Is there no UNDO functionality?

    Parametric swing is legitimately genius. Groundbreaking potential for beat making in general. How does it integrate with midi clock (if at all)?

  • I'm curious about undo too :)

Sign In or Register to comment.