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.

LK - for Ableton Live & Midi by Imaginando - AUv3 Clip Launcher Finally Available in AUM!!

1108109111113114130

Comments

  • @tahiche said:
    Great! 🤟🙌🙌
    I also had the question about the similar “note bar” on the side of the chorder module. How does that bar work?. Can you set a scale for it?.
    Keep up the great work! 👏

    On the CHORDER module, those "note bars" on the left/right represent the notes of the current selected chord, in different octaves, in ascending order. Everytime you press a new chord, the notes are updated.
    Example. If you're playing a C Major chord, you'll have C1 E1 G1 C2 E2 G2 and so on.

  • @xglax said:

    @tahiche said:
    Great! 🤟🙌🙌
    I also had the question about the similar “note bar” on the side of the chorder module. How does that bar work?. Can you set a scale for it?.
    Keep up the great work! 👏

    On the CHORDER module, those "note bars" on the left/right represent the notes of the current selected chord, in different octaves, in ascending order. Everytime you press a new chord, the notes are updated.
    Example. If you're playing a C Major chord, you'll have C1 E1 G1 C2 E2 G2 and so on.

    Ohhhh. That was obvious, wasn’t it?. Not my brightest moment, I’m sure…
    Thanks for your patience!.

  • @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

  • @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

  • @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    That works properly now thanks!!

  • edited January 2022

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

  • @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

  • edited January 2022

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.
    Yes the problem is still present on the latest build released yesterday.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

    Yes the problem is still present on the latest build released yesterday.

  • @Jeezs

    Did this problem appear in these new betas (1.12.0) or was present before?

    What is causing the issue is the following. Scene trigger actions are only applied when a scene is triggered when the song is playing. If the song is paused and you press play, even if a scene with follow action plays, it will not occur since the play state of the song will clear the follow action status.

    The workflow you're reporting leads me to think that this is not a new issue. You're manually triggering a scene, but since the song is played afterwards, the follow action is not applied. If it was applied, when you press play, it would automatically triggered the follow action scene everytime instead of the scene you want to play.

  • It appears with 1.12.0, it always work before

  • edited January 2022

    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

  • @Janosax said:
    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

    Double tapping a keyboard key selects the notes in that pitch.

  • Such a great app… Looking forward to the update..

    Thank You.. ❤️

  • edited January 2022

    @sinosoidal said:

    @Janosax said:
    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

    Double tapping a keyboard key selects the notes in that pitch.

    Nice!! Isn’t it possible to implement simple taps to select directly on notes? Too difficult? Should be so simple and efficient. You don’t always want to change all velocities of a same pitched note (this almost never happens in real life except perhaps for drums).

  • edited January 2022

    @xglax said:

    Did this problem appear in these new betas (1.12.0) or was present before?

    I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I press a scene while it's already playing

  • @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

    Double tapping a keyboard key selects the notes in that pitch.

    Nice!! Isn’t it possible to implement simple taps to select directly on notes? Too difficult? Should be so simple and efficient. You don’t always want to change all velocities of a same pitched note (this almost never happens in real life except perhaps for drums).

    You use Shift button to tap-select multiple notes (double tap Shift if you don´t want to hold it down while selecting). When selected, you can adjust velocities individually, or you can change all selected velocities by again holding Shift. Works very well, I´d say.

  • ´

    @bleep said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

    Double tapping a keyboard key selects the notes in that pitch.

    Nice!! Isn’t it possible to implement simple taps to select directly on notes? Too difficult? Should be so simple and efficient. You don’t always want to change all velocities of a same pitched note (this almost never happens in real life except perhaps for drums).

    You use Shift button to tap-select multiple notes (double tap Shift if you don´t want to hold it down while selecting). When selected, you can adjust velocities individually, or you can change all selected velocities by again holding Shift. Works very well, I´d say.

    If I do that that will only duplicate selected notes. I don’t see how to do what I do in video in a alternative easier way:

  • Congrats on the new layout, buttons and specially on the automation improvements. It’s a lot clearer and easier to work with.

  • @RajahP said:
    Such a great app… Looking forward to the update..

    Thank You.. ❤️

    :blush:

  • @branis said:

    @xglax said:

    Did this problem appear in these new betas (1.12.0) or was present before?

    I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I press a scene while it's already playing

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.
    Yes the problem is still present on the latest build released yesterday.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

    Yes the problem is still present on the latest build released yesterday.

    The problem should be fixed in build 278

  • @Janosax said:
    ´

    @bleep said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Can you allow to select notes directly by single tap or drag over in that automation view? It’s necessary for now to toggle notes/automations views to do selections, it’s really not fast for change velocities for example. And because there is that message prompt to select notes, that is counterintuitive to have to toggle views just to be able to select something. Tools allow only to select all/deselect all.

    Double tapping a keyboard key selects the notes in that pitch.

    Nice!! Isn’t it possible to implement simple taps to select directly on notes? Too difficult? Should be so simple and efficient. You don’t always want to change all velocities of a same pitched note (this almost never happens in real life except perhaps for drums).

    You use Shift button to tap-select multiple notes (double tap Shift if you don´t want to hold it down while selecting). When selected, you can adjust velocities individually, or you can change all selected velocities by again holding Shift. Works very well, I´d say.

    If I do that that will only duplicate selected notes. I don’t see how to do what I do in video in a alternative easier way:

    I think a proper solution requires more time to mature. There are many edge cases that prevent us from implementing now a tap to select while in this mode. For now we simply updated the labels to instruct user that double tapping the piano roll key selects all the notes from that pitch

  • @tahiche said:
    Congrats on the new layout, buttons and specially on the automation improvements. It’s a lot clearer and easier to work with.

    Thanks for your feedback! :blush:

  • @sinosoidal said:

    @branis said:

    @xglax said:

    Did this problem appear in these new betas (1.12.0) or was present before?

    I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I press a scene while it's already playing

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.
    Yes the problem is still present on the latest build released yesterday.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

    Yes the problem is still present on the latest build released yesterday.

    The problem should be fixed in build 278

    Seems to be fixed. Thanks!
    I also must agree with tahiche, the new layout and icons are a big improvement!
    There are a few icons left that use a solid style instead of the new outlined style. When time permits these could be updated too:

  • @Janosax I see. I´m not on the beta, was referring to the current app store version, where it is easy enough to adjust multiple velocities in one go.

    The new layout looks good. Still quite many buttons to remember :-) If you find the time, @sinosoidal, would be nice if one could tap a ? to get small popups with short explanations of all of them. A nice example of this in use would be AudioLayer.

  • edited January 2022

    @sinosoidal said:

    @branis said:

    @xglax said:

    Did this problem appear in these new betas (1.12.0) or was present before?

    I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I presse a scene while it's already playing

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.
    Yes the problem is still present on the latest build released yesterday.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

    Yes the problem is still present on the latest build released yesterday.

    The problem should be fixed in build 278

    Scene chaining problem solved with latest beta!

    Thanks!

  • @Jeezs said:

    @sinosoidal said:

    @branis said:

    @xglax said:

    Did this problem appear in these new betas (1.12.0) or was present before?

    I can confirm that this is a new issue. In previous versions, when I would select a scene and press play in AUM, the scene would be launched with follow actions applied. Now it only happens if I presse a scene while it's already playing

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

    The latest build have a problem with scene chaining.
    When clicking on the the a scene, LK never trig the next one.
    If I double click the first scene then it work and then other scene are chained correctly

    The latest beta fixes this problem.
    Yes the problem is still present on the latest build released yesterday.

    @Janosax said:
    That works with AUM AppStore version, but not with latests AUM beta. Note that @j_liljedahl has implemented something new regarding midi mappings (presets), they are perhaps loaded at a moment on session load which cause an issue with LK? My other older templates sessions has no issues retrieving AUV3 midi mappings.

    Sorry for the work :D

    The problem with the midi assignments in AUM has been resolved in the latest beta.

    Any feedback regarding these two fixes is much appreciated =)

    I just tested latest beta of AUM and LK and had no troubles regarding the recall of the MIDI assignments.

    The problem I experience is not related to midi.
    Here is what I’ve done that produce the problem.
    First it only happen when Lk sync is set to host else it behave normally.
    I touch the scene I have want to be played then I hit AUM play button.
    The scene play but never trigger the next scene.
    If I touch the scene button while AUM is already playing then it work.
    Hope it’ll help.

    Is the problem still happening with the latest beta released yesterday? Can you please confirm? Because we have acted upon your feedback. :blush:

    Yes the problem is still present on the latest build released yesterday.

    The problem should be fixed in build 278

    Scene chaining problem solved with latest beta!

    Thanks!

    Thanks for the feedback! :blush:

  • @bleep said:
    @Janosax I see. I´m not on the beta, was referring to the current app store version, where it is easy enough to adjust multiple velocities in one go.

    let me know if you want to be on the beta.

    The new layout looks good. Still quite many buttons to remember :-) If you find the time, @sinosoidal, would be nice if one could tap a ? to get small popups with short explanations of all of them. A nice example of this in use would be AudioLayer.

    The suggestion is good but we have already a very long manual to keep updated and it is staying beyond for a long time. We have a complicated relation with LK documentation! :blush:

  • @sinosoidal said:

    @bleep said:
    The new layout looks good. Still quite many buttons to remember :-) If you find the time, @sinosoidal, would be nice if one could tap a ? to get small popups with short explanations of all of them. A nice example of this in use would be AudioLayer.

    The suggestion is good but we have already a very long manual to keep updated and it is staying beyond for a long time. We have a complicated relation with LK documentation! :blush:

    I know :blush:
    My suggestion would be to ditch the manual (too hard to maintain properly at this development pace), and rather have these small yellow help boxes always up-to-date as the UI is being modified. Maybe that's just me, but the forum knowledge is always here, should one need more in-depth help :)

  • edited February 2022

    @bleep said:

    @sinosoidal said:

    @bleep said:
    The new layout looks good. Still quite many buttons to remember :-) If you find the time, @sinosoidal, would be nice if one could tap a ? to get small popups with short explanations of all of them. A nice example of this in use would be AudioLayer.

    The suggestion is good but we have already a very long manual to keep updated and it is staying beyond for a long time. We have a complicated relation with LK documentation! :blush:

    I know :blush:
    My suggestion would be to ditch the manual (too hard to maintain properly at this development pace), and rather have these small yellow help boxes always up-to-date as the UI is being modified. Maybe that's just me, but the forum knowledge is always here, should one need more in-depth help :)

    That would break the fact that we have manuals for all apps. And there are many things that don't have changes at all. The only module that is constantly changing is MATRIX.

    We would need someone revising LK manual at every version. I don't think it would be an incredible amount of work after some catching up.

    Maybe we could have the help of the community in exchange of some exclusive perks. Don't know if there could be someone interested. It is not an exciting task. :blush:

  • edited February 2022

    Really like the refactoring of the layout, good job!

Sign In or Register to comment.