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.

AUM 1.3.9 update

1246

Comments

  • edited December 2020

    This is an amazing update - thanks!

    @audiblevideo

    Even better is the fact you can long press on the ‘MIDI Control’ button in the header and it takes you straight to the auto find feature!


  • auv3 push coming soon ?

  • edited December 2020

    @j_liljedahl Thanks for the update!

    The parameter find is a great addition.

    For the color picker, might be good to add a “Return to Default” button in case people want to revert to the original color, because once you start down the path of coloring there’s no way to get back.

    Thanks again.

  • Would be nice to get a video overview of the new features..😎

  • Updated
    Super smooth
    Good work
    Made tier 4 lockdown not so gloomy here in London

  • @j_liljedahl - you are amazing! Thank you for this great free update! You work your butt off and we continually get the benefit. It's like Santa's workshop except you're the only elf. Hardly seems fair, but I'm not complaining! <3

    A thread title update would be helpful for others who haven't been following up to now.

  • @RajahP said:
    Would be nice to get a video overview of the new features..😎

    Yes please!

  • ☝🏻 @Gavinski?????

    GAVINSKI!!!!! 🤗

  • Very nice update.

  • The changes were definitely improvements! One I really like is in the MIDI routing, which is being able to see not only the app instance name, but the label. I use multiple instances of Mozaic for certain purposes and used to have to count when connecting them. Now I can see their labels and don't have to guess.

  • @Dunamis said:
    @j_liljedahl Thanks for the update!

    The parameter find is a great addition.

    For the color picker, might be good to add a “Return to Default” button in case people want to revert to the original color, because once you start down the path of coloring there’s no way to get back.

    Thanks again.

    to return default uncheck customize node color

  • The control finder is awesome!

    Defer system gestures for all screen edges.

    Might be a minor thing to most but I highly appreciate it! :)

  • @j_liljedahl Bästa julklappen! Superbt jobbat, som alltid. Man tackar, bockar och bugar. :D

  • @Pxlhg said:
    @j_liljedahl Bästa julklappen! Superbt jobbat, som alltid. Man tackar, bockar och bugar. :D

    Translation:
    “Best Hulkmas wishes! Superb job, have some Altoids. Man tackle, my back is buggered. :D

  • Long tap to start and “Next” to map multiple parameters in one go is really smooth! Also, the Assigned is handy when refreshing what you have mapped in a template. Thanks!

  • @Emanresu said:

    @Dunamis said:
    @j_liljedahl Thanks for the update!

    The parameter find is a great addition.

    For the color picker, might be good to add a “Return to Default” button in case people want to revert to the original color, because once you start down the path of coloring there’s no way to get back.

    Thanks again.

    to return default uncheck customize node color

    I had a feeling there was a really easy way to do it that was right in front of my face. :p

  • @Liquidmantis said:

    @Pxlhg said:
    @j_liljedahl Bästa julklappen! Superbt jobbat, som alltid. Man tackar, bockar och bugar. :D

    Translation:
    “Best Hulkmas wishes! Superb job, have some Altoids. Man tackle, my back is buggered. :D

    OMFG. Thanks for the laughs 😂😂😀

  • @wim said:
    @j_liljedahl - you are amazing! Thank you for this great free update! You work your butt off and we continually get the benefit. It's like Santa's workshop except you're the only elf. Hardly seems fair, but I'm not complaining! <3

    Cubasis would have sold us an entire new version for $25 just to get a handful of new features. I will buy the new AU fx in gratitude, even though I don't really need them (have the old ones already).

  • @dobbs said:
    The control finder is awesome!

    Defer system gestures for all screen edges.

    Might be a minor thing to most but I highly appreciate it! :)

    Agreed - this makes a huge difference on iPhone

  • @Liquidmantis said:

    @Pxlhg said:
    @j_liljedahl Bästa julklappen! Superbt jobbat, som alltid. Man tackar, bockar och bugar. :D

    Translation:
    “Best Hulkmas wishes! Superb job, have some Altoids. Man tackle, my back is buggered. :D

    🤣

  • wimwim
    edited December 2020

    @Wrlds2ndBstGeoshredr said:

    @wim said:
    @j_liljedahl - you are amazing! Thank you for this great free update! You work your butt off and we continually get the benefit. It's like Santa's workshop except you're the only elf. Hardly seems fair, but I'm not complaining! <3

    Cubasis would have sold us an entire new version for $25 just to get a handful of new features. I will buy the new AU fx in gratitude, even though I don't really need them (have the old ones already).

    That's awfully harsh toward the Cubasis team. You have no basis to know the relative amount of effort behind those respective updates. Building software isn't like weighing out produce.

    Sorry, I just had to speak up.

  • @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

  • @moodscaper said:

    @j_liljedahl said: don't use contextName for short instance labels etc. Developers should go back to audioUnitShortName instead.

    moodunits update in the pipeline.

    Great! Note that if you want to change it dynamically you must emit a "didChangeValue" on it. But use with care because it will overwrite any custom short name & color set by the user.

    Be nice if this wasn't limited to 6 chars in the UI for the main source? I think that label could take 8 or even 10 chars, but we can probably ignore Apple's guideline of 16 chars for a short name :smile:

    6 char limit for inserts and fx, totally makes sense though.

    The thing is that I want it to be consistent across devices, and on iPhone there's only room for 6 chars.

  • @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

  • Huge thanks @j_liljedahl - Space/Dub just bought, at least part-way as appreciation :-)

  • @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

  • edited December 2020

    @arktek said:

    @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

  • @auxmux said:

    @arktek said:

    @j_liljedahl said:

    @0tolerance4silence said:
    @j_liljedahl
    small bug in AUM/Dub - if tempo sync is enabled in Dub, AUMs new parameter picker would automatically pick “Coarse Time” parameter.

    Ah, good catch. I can fix Dub to not emit a "parameter did change" for coarse time in sync mode unless the tempo actually changed, but it highlights a problem that might show up in other plugins as well: there's no way to differentiate between user wiggling a knob and the parameter being set by the plugin itself. I have some ideas to improve this though for the next update.

    Out of curiosity - is there a reason why the midi sync out port selection is not remembered on project reload, and ‘port allocation’ seems messier? It could be my interface (iCM4+), which have a mix of DIN ports and ?dynamically allocated USB midi?
    F.e - AUM would list all my ports in the same order (alphabetically) every time in the matrix, but not in sync out section.

    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    Oh my, still lots to look forward to.....thank you for all of your work...

    @j_liljedahl If you're looking into clock changes, one awesome update would be clock dividers built into AUM. This way different AU sequencers could be run at different speeds.

    Oh my, I LOVE this idea.

  • @j_liljedahl said:
    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    :star: :star: :star: :star: :star:

  • @AndyPlankton said:

    @j_liljedahl said:
    I'm planning a rewrite from the ground up regarding MIDI sync, adding clock slaving as well as bringing the MIDI clock in/out into the main MIDI matrix so it can be connected anywhere and to multiple endpoints.

    :star: :star: :star: :star: :star:

    5 star idea indeed!

Sign In or Register to comment.