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!!

1…8788909293…130

Comments

  • espiegel123espiegel123

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:
    LK 1.11.0 Beta (build 247) now also has custom song time signatures

    @espiegel123 @Janosax

    Now you can choose the song time signature. Created clips will automatically have the same time signature as the song (this include the created clips with recording). This setting is saved in your sessions and can be change from session to session.

    Remember that when changing song's signature, clip triggering timings will behave accordingly with the current selection. So, for instance, a song with 3/4 signature with a clip triggering of 1 bar, will trigger clips on a 3 beat basis instead of 4.

    Thanks for adding this. It makes things much better.

    I noticed a coulle of little details you might want to look it:

    • if not on the matrix page, the beat counter might not match the meter of the currently playing clip. For example, I set the project meter to 3/4 and then changed it to 7/4, but when on the MIDI Pads page, the beat counter treats the number of beats per measure as 4 (counts from 0 thru 3)
    • if i change the meter of the default empty clip, the number of beats per measure displayed remains at 4 unless I change the number of measures...at which point the number of beats per measure is displayed correctly.

    Thanks for reporting. I'll look at those issues!

    If you have any trouble reproducing them, let me know.

    The first issue is fixed, but could you tell me a little more about the second issue. I'm trying to replicate but can't find a way to do so. Maybe i'm misunderstanding the issue and not doing the right steps

    Create a new default project (master tempo 4/4 as is tempo of the default one bar clip).

    Open the piano roll for the default one bar clip.

    Change tempo to 7/4.

    The clip properties show the length as 1 bar but the bar only has 4 beats.

    The display will update if you re-enter a bar length for the clip or drag the loop end.

    This isn't major but did throw me for a loop when I first encountered it.

  • JanosaxJanosax
    edited July 2021

    @xglax

    Here are two minor issues:

    • when LK window is reduced, some info are superposed in upper right corner. An adaptative « … » or hamburger pop up menu could help here.

    • Also, Link display strange value in LK when an IAA app is also used. Here AUM and GroupTheLoop display correct value, but not LK. I don’t know if this translate to any drift.

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

  • rs2000rs2000

    @Janosax Are you sure LK as an AUv3 has direct access to MIDI ports?
    Isn't the selection reserved for the host (AUM) only?

  • JanosaxJanosax
    edited July 2021

    @rs2000 said:
    @Janosax Are you sure LK as an AUv3 has direct access to MIDI ports?
    Isn't the selection reserved for the host (AUM) only?

    No specific setting is made in AUM in this test in midi routing or midi control, every input/output is disabled (as default). LK midi setting only set midi inputs/outputs used in Matrix routing, not midi learn. Matrix built in midi learn seems to listen to all midi ports (from host?) but no filtering is possible to set in LK (nor AUM).

    Something like Voicerack FX allows to internal midi port selection for built in midi learn even as AUV3 hosted in AUM @xglax:

  • JanosaxJanosax
    edited July 2021

    @xglax is it possible to add AUV3 host state saving for Matrix Cell width/height? Sometime I use fullscreen and sometime more specific (smaller) visual arrangement, so I have to set those sliders quite often.

  • xglaxxglax

    @Janosax @espiegel123

    I'll look at your reported issue as soon as I have some time, and I'll get back to you =)

  • JanosaxJanosax

    @xglax said:
    @Janosax @espiegel123

    I'll look at your reported issue as soon as I have some time, and I'll get back to you =)

    Thanks 😊

  • xglaxxglax

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:
    LK 1.11.0 Beta (build 247) now also has custom song time signatures

    @espiegel123 @Janosax

    Now you can choose the song time signature. Created clips will automatically have the same time signature as the song (this include the created clips with recording). This setting is saved in your sessions and can be change from session to session.

    Remember that when changing song's signature, clip triggering timings will behave accordingly with the current selection. So, for instance, a song with 3/4 signature with a clip triggering of 1 bar, will trigger clips on a 3 beat basis instead of 4.

    Thanks for adding this. It makes things much better.

    I noticed a coulle of little details you might want to look it:

    • if not on the matrix page, the beat counter might not match the meter of the currently playing clip. For example, I set the project meter to 3/4 and then changed it to 7/4, but when on the MIDI Pads page, the beat counter treats the number of beats per measure as 4 (counts from 0 thru 3)
    • if i change the meter of the default empty clip, the number of beats per measure displayed remains at 4 unless I change the number of measures...at which point the number of beats per measure is displayed correctly.

    Thanks for reporting. I'll look at those issues!

    If you have any trouble reproducing them, let me know.

    The first issue is fixed, but could you tell me a little more about the second issue. I'm trying to replicate but can't find a way to do so. Maybe i'm misunderstanding the issue and not doing the right steps

    Create a new default project (master tempo 4/4 as is tempo of the default one bar clip).

    Open the piano roll for the default one bar clip.

    Change tempo to 7/4.

    The clip properties show the length as 1 bar but the bar only has 4 beats.

    The display will update if you re-enter a bar length for the clip or drag the loop end.

    This isn't major but did throw me for a loop when I first encountered it.

    Right now, changing clip's time signature doesn't affect the current length of the loop or length of the clip, it stays the same as before. Do you think that if a clip has a full bar of 4/4, and one change the signature to 5/4 for instance, the length should automatically change to a full bar of 5/4?

  • xglaxxglax
    edited July 2021

    @Janosax said:
    @xglax is it possible to add AUV3 host state saving for Matrix Cell width/height? Sometime I use fullscreen and sometime more specific (smaller) visual arrangement, so I have to set those sliders quite often.

    Aren't the matrix cell width and Height saved in your project? Just tested it right now and those settings were restored correctly.

  • xglaxxglax

    @Janosax

    Regarding the midi mapping routing issue, i was able to replicate the issue and will talk to @sinosoidal about this to see what we can do about this

  • espiegel123espiegel123

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:
    LK 1.11.0 Beta (build 247) now also has custom song time signatures

    @espiegel123 @Janosax

    Now you can choose the song time signature. Created clips will automatically have the same time signature as the song (this include the created clips with recording). This setting is saved in your sessions and can be change from session to session.

    Remember that when changing song's signature, clip triggering timings will behave accordingly with the current selection. So, for instance, a song with 3/4 signature with a clip triggering of 1 bar, will trigger clips on a 3 beat basis instead of 4.

    Thanks for adding this. It makes things much better.

    I noticed a coulle of little details you might want to look it:

    • if not on the matrix page, the beat counter might not match the meter of the currently playing clip. For example, I set the project meter to 3/4 and then changed it to 7/4, but when on the MIDI Pads page, the beat counter treats the number of beats per measure as 4 (counts from 0 thru 3)
    • if i change the meter of the default empty clip, the number of beats per measure displayed remains at 4 unless I change the number of measures...at which point the number of beats per measure is displayed correctly.

    Thanks for reporting. I'll look at those issues!

    If you have any trouble reproducing them, let me know.

    The first issue is fixed, but could you tell me a little more about the second issue. I'm trying to replicate but can't find a way to do so. Maybe i'm misunderstanding the issue and not doing the right steps

    Create a new default project (master tempo 4/4 as is tempo of the default one bar clip).

    Open the piano roll for the default one bar clip.

    Change tempo to 7/4.

    The clip properties show the length as 1 bar but the bar only has 4 beats.

    The display will update if you re-enter a bar length for the clip or drag the loop end.

    This isn't major but did throw me for a loop when I first encountered it.

    Right now, changing clip's time signature doesn't affect the current length of the loop or length of the clip, it stays the same as before. Do you think that if a clip has a full bar of 4/4, and one change the signature to 5/4 for instance, the length should automatically change to a full bar of 5/4?

    Since the properties displays length as whole bars, I think changing the meter of the clip should adjust the current loop length (and adjust what is visible so that when you change the meter of a 1 bar clip, you see an entire bar.)...particularly since if you are changing the length of an empty default clip, it isn't obvious what you need to do to see a whole bar. You can't zoom out to see the rest of it.

  • JanosaxJanosax
    edited July 2021

    @xglax said:

    @Janosax said:
    @xglax is it possible to add AUV3 host state saving for Matrix Cell width/height? Sometime I use fullscreen and sometime more specific (smaller) visual arrangement, so I have to set those sliders quite often.

    Aren't the matrix cell width and Height saved in your project? Just tested it right now and those settings were restored correctly.

    It works with AUM global session state saving and that’s the most important, I missed that thanks. But I initially found that it’s not saved in presets state saving (both LK and AUM presets systems). That’s less crucial but still can be useful to have presets with various Matrix size ratio.

    @xglax said:
    @Janosax

    Regarding the midi mapping routing issue, i was able to replicate the issue and will talk to @sinosoidal about this to see what we can do about this

    Very nice. LK midi learn is much faster to use than AUM in this situation.

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:

    @espiegel123 said:

    @xglax said:
    LK 1.11.0 Beta (build 247) now also has custom song time signatures

    @espiegel123 @Janosax

    Now you can choose the song time signature. Created clips will automatically have the same time signature as the song (this include the created clips with recording). This setting is saved in your sessions and can be change from session to session.

    Remember that when changing song's signature, clip triggering timings will behave accordingly with the current selection. So, for instance, a song with 3/4 signature with a clip triggering of 1 bar, will trigger clips on a 3 beat basis instead of 4.

    Thanks for adding this. It makes things much better.

    I noticed a coulle of little details you might want to look it:

    • if not on the matrix page, the beat counter might not match the meter of the currently playing clip. For example, I set the project meter to 3/4 and then changed it to 7/4, but when on the MIDI Pads page, the beat counter treats the number of beats per measure as 4 (counts from 0 thru 3)
    • if i change the meter of the default empty clip, the number of beats per measure displayed remains at 4 unless I change the number of measures...at which point the number of beats per measure is displayed correctly.

    Thanks for reporting. I'll look at those issues!

    If you have any trouble reproducing them, let me know.

    The first issue is fixed, but could you tell me a little more about the second issue. I'm trying to replicate but can't find a way to do so. Maybe i'm misunderstanding the issue and not doing the right steps

    Create a new default project (master tempo 4/4 as is tempo of the default one bar clip).

    Open the piano roll for the default one bar clip.

    Change tempo to 7/4.

    The clip properties show the length as 1 bar but the bar only has 4 beats.

    The display will update if you re-enter a bar length for the clip or drag the loop end.

    This isn't major but did throw me for a loop when I first encountered it.

    Right now, changing clip's time signature doesn't affect the current length of the loop or length of the clip, it stays the same as before. Do you think that if a clip has a full bar of 4/4, and one change the signature to 5/4 for instance, the length should automatically change to a full bar of 5/4?

    Since the properties displays length as whole bars, I think changing the meter of the clip should adjust the current loop length (and adjust what is visible so that when you change the meter of a 1 bar clip, you see an entire bar.)...particularly since if you are changing the length of an empty default clip, it isn't obvious what you need to do to see a whole bar. You can't zoom out to see the rest of it.

    +1 that give much faster workflow. Individual scene/clip tempo should be a must have too :-)

  • xglaxxglax
    edited July 2021

    @espiegel123 @Janosax

    New 1.11.0 beta (build 249) now updates clip's loop region when changing clip' signature.

    Ex: if you have a 1 bar clip with 4/4, changing clip' signature to 5/4 will update clip loop so it has 5 beats instead of 4

  • xglaxxglax
    edited July 2021

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

  • lukesleepwalkerlukesleepwalker

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Great problem to have—dividing time between two apps that are quickly becoming essential tools on iOS. Keep up the great work!

  • espiegel123espiegel123

    @xglax said:
    @espiegel123 @Janosax

    New 1.11.0 beta (build 249) now updates clip's loop region when changing clip' signature.

    Ex: if you have a 1 bar clip with 4/4, changing clip' signature to 5/4 will update clip loop so it has 5 beats instead of 4

    Works great! Thanks for the song and clip meter features. This is terrific.

  • tahichetahiche

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Regarding midi mapping… the “move your knob or play a note” approach is very handy but IMO you should always be able to specify the CC or note value manually, like you can in AUM. This is specially the case when you’re not mapping to a hardware device but to another app. To me “automatic” mapping should be an enhancement but not replace the possibility of setting a value manually.

  • JanosaxJanosax

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Thanks that’s perfect, we can wait for that improved system 😉

    Have you looked at two other minor issues I mentioned earlier?

    @Janosax said:
    @xglax

    Here are two minor issues:

    • when LK window is reduced, some info are superposed in upper right corner. An adaptative « … » or hamburger pop up menu could help here.

    • Also, Link display strange value in LK when an IAA app is also used. Here AUM and GroupTheLoop display correct value, but not LK. I don’t know if this translate to any drift.

  • JanosaxJanosax

    @tahiche said:

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Regarding midi mapping… the “move your knob or play a note” approach is very handy but IMO you should always be able to specify the CC or note value manually, like you can in AUM. This is specially the case when you’re not mapping to a hardware device but to another app. To me “automatic” mapping should be an enhancement but not replace the possibility of setting a value manually.

    +1

  • xglaxxglax
    edited July 2021

    @Janosax said:

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Thanks that’s perfect, we can wait for that improved system 😉

    Have you looked at two other minor issues I mentioned earlier?

    @Janosax said:
    @xglax

    Here are two minor issues:

    • when LK window is reduced, some info are superposed in upper right corner. An adaptative « … » or hamburger pop up menu could help here.

    • Also, Link display strange value in LK when an IAA app is also used. Here AUM and GroupTheLoop display correct value, but not LK. I don’t know if this translate to any drift.

    Tempo value was fixed and you can confirm that in the latest beta. I think the first problem was related to the tempo value text being too large, so that may be fixed as well

  • wimwim
    edited July 2021

    @tahiche said:
    Regarding midi mapping… the “move your knob or play a note” approach is very handy but IMO you should always be able to specify the CC or note value manually, like you can in AUM. This is specially the case when you’re not mapping to a hardware device but to another app. To me “automatic” mapping should be an enhancement but not replace the possibility of setting a value manually.

    +1

  • soundtemplesoundtemple

    @xglax When you do get around to refactoring the mapping manager can you also look at how mappings are saved?

    I think it's confusing how mappings are saved. It seems I can save them to an LK project in an AUM session, then switch to another LK project and save some different midi learn settings. Returning to the original project re-loads the original midi learn settings. This is great.

    However, if I open a new AUM session and load LK and open one of the saved projects the midi learn settings are gone. They are not saved in the stand alone version either.

    It seems like they are local to the instance in AUM but that instance can store midi learn settings for multiple projects.

    I think it would be better if midi learn settings were saved with the project and regardless of where you open the project (standalone, AUM or different AUM session) it should re-load the settings with last changes. This is how it is with everything else in the project. What do you think?

    Another issue for me is, even with LK all controllers off it seems LK responds to midi learn assignments from my Launchpad mini. See this video. Only Mozaic is receiving midi for logging purposes from the Launchpad. All Controllers and Midi inputs are off. There is no midi routed into LK from AUM, yet it’s responding to midi learn assignments on CH0. So, it seems like you cant disconnect the Launchpad from LK.
    https://photos.app.goo.gl/QnzpPRiGwsCkqttK6

  • xglaxxglax

    @soundtemple said:
    @xglax When you do get around to refactoring the mapping manager can you also look at how mappings are saved?

    I think it's confusing how mappings are saved. It seems I can save them to an LK project in an AUM session, then switch to another LK project and save some different midi learn settings. Returning to the original project re-loads the original midi learn settings. This is great.

    However, if I open a new AUM session and load LK and open one of the saved projects the midi learn settings are gone. They are not saved in the stand alone version either.

    It seems like they are local to the instance in AUM but that instance can store midi learn settings for multiple projects.

    I think it would be better if midi learn settings were saved with the project and regardless of where you open the project (standalone, AUM or different AUM session) it should re-load the settings with last changes. This is how it is with everything else in the project. What do you think?

    Another issue for me is, even with LK all controllers off it seems LK responds to midi learn assignments from my Launchpad mini. See this video. Only Mozaic is receiving midi for logging purposes from the Launchpad. All Controllers and Midi inputs are off. There is no midi routed into LK from AUM, yet it’s responding to midi learn assignments on CH0. So, it seems like you cant disconnect the Launchpad from LK.
    https://photos.app.goo.gl/QnzpPRiGwsCkqttK6

    Sure, we'll look at that. Makes sense having specific midi mappings according to each LK project.

    Yes, thats a problem. Right now, when you map something in LK, it will respond to whenever device that sends the same assign midi message. We aren't saving the device with the mapping information. Right now that fix isn't easy, we can't simply add that guard to out mapping system, but we will definitely take that into consideration when we make the refactor!

  • xglaxxglax

    @tahiche said:

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Regarding midi mapping… the “move your knob or play a note” approach is very handy but IMO you should always be able to specify the CC or note value manually, like you can in AUM. This is specially the case when you’re not mapping to a hardware device but to another app. To me “automatic” mapping should be an enhancement but not replace the possibility of setting a value manually.

    We'll take that into account. You're suggesting some kind of midi mapping system similar on what we have in the Controller Module. Thanks for your feedback =)

  • oddSTARoddSTAR

    Can you assign different modules in LK to different channels in AUM simultaneously? Like, can the pads be controlling Fractal Bits while the keyboard plays Agonizer within the same instance?

  • branisbranis

    @oddSTAR said:
    Can you assign different modules in LK to different channels in AUM simultaneously? Like, can the pads be controlling Fractal Bits while the keyboard plays Agonizer within the same instance?

    Yes, you can. You can set independent midi channels for each module

  • JanosaxJanosax

    @xglax said:

    @Janosax said:

    @xglax said:

    @Janosax said:
    @xglax

    A bigger issue for me concerning midi learn: how do you set midi input (for midi learn)? I use together Bluetooth pedalboard and MidiFire app to have various midi notes triggers on foot taps/buttons, but I want to use only MidiFire input and not BlueBoard. LK midi learn/trigger both BT input and MidiFire input, this gives dual notes and wrong triggering. I use AUM midi learn to control LK instead for now. It could be really useful to have a setting for midi learn midi inputs selection (physical and virtual).

    Our mapping manager needs some refactor to fix not only some issues (like this one you are reporting here) but also to accommodate some enhancements, like output range and so on. We're too busy right now with VS to make this kind of work, but as soon as we have some time we'll try to look at it and make a new mapping system. Doing this with time will also enable us to think of ways of migrating the mapping system to the other apps as well.

    Thanks that’s perfect, we can wait for that improved system 😉

    Have you looked at two other minor issues I mentioned earlier?

    @Janosax said:
    @xglax

    Here are two minor issues:

    • when LK window is reduced, some info are superposed in upper right corner. An adaptative « … » or hamburger pop up menu could help here.

    • Also, Link display strange value in LK when an IAA app is also used. Here AUM and GroupTheLoop display correct value, but not LK. I don’t know if this translate to any drift.

    Tempo value was fixed and you can confirm that in the latest beta. I think the first problem was related to the tempo value text being too large, so that may be fixed as well

    Tempo issue is fixed, display glitch not fully but this is a very minor issue.

  • KrupaKrupa

    I’ve just been trying to work out if I can have long clips playing that will control AUM channel volume parameters but I’m having little luck so far - did anyone ever manage this, or is it not possible? I’m thinking that I might set myself up with a nice template if I can as it’d be one way to push more long pieces out, and also any MIDI made at the awn’s time should mooch over to ableton with ease later...

  • branisbranis

    I just noticed that I get quite a huge bump in CPU usage when I switch the view to any of the controller compared to Matrix. Anyone seeing the same?

  • KrupaKrupa

    @Krupa said:
    I’ve just been trying to work out if I can have long clips playing that will control AUM channel volume parameters but I’m having little luck so far - did anyone ever manage this, or is it not possible? I’m thinking that I might set myself up with a nice template if I can as it’d be one way to push more long pieces out, and also any MIDI made at the awn’s time should mooch over to ableton with ease later...

    I think I kinda figured this out last night somehow - I think I needed to add an au to the track to get aum to sniff out the volume CC being sent. So, I’ve built up a little four track setup that has two LK tracks for each audio track; one long clip has volume in it (and potentially much else, pan, other cc days, or even notes) and then one alongside that can do clip building...

    I’ll see how it works, I could even share it as an aim file if anyone’s looking to do the same and is stuck.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024