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…4647495152…130

Comments

  • gregsmithgregsmith

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    Best thing to happen in 2020 😉

  • sinosoidalsinosoidal

    @clowm said:

    @sinosoidal said:

    @tahiche said:
    Keep up the amazing work. Hope more follow your footsteps and make “problem solving” apps that open possibilities and new paths. It’s also brave cos you’re embracing a lot of functionality and with that comes a lot of work and risks. Really appreciate it. Bravo, Portuguese stars!!.

    Thank you for your warm words! :blush:

    So... now that 2020 is getting to an end, what do you desire for LK in 2021? You have only three wishes, use them wisely...

    Only one wish: more efficient screen space use on IPhones

    I believe we can save some space with margins. We will have a couple of reported issues. We will take a look! Thx

  • ronniebronnieb

    Man I love seeing developers who are so keen to hear our customer feature requests, it can often be the biggest invitation for headaches but it's so encouraging to see.

    A couple of quick Q's (possible future feature requests); I had a search in the thread but can only find it mentioned a couple of times but is it possible for the matric to record incoming MPE data?
    And somewhat related as would probably be more important if/when LK supports MPE playback, would it be possible in the future for LK to accept multiple (but separate, as opposed to the current global LK Input) midi inputs to allow more flexible midi routings?

    Anyway, killer work @sinosoidal, I'm new to the iOS world but LK is already proving to be a big piece to my puzzle :smiley:

  • sinosoidalsinosoidal
    edited December 2020

    @ronnieb said:
    Man I love seeing developers who are so keen to hear our customer feature requests, it can often be the biggest invitation for headaches but it's so encouraging to see.

    A couple of quick Q's (possible future feature requests); I had a search in the thread but can only find it mentioned a couple of times but is it possible for the matric to record incoming MPE data?
    And somewhat related as would probably be more important if/when LK supports MPE playback, would it be possible in the future for LK to accept multiple (but separate, as opposed to the current global LK Input) midi inputs to allow more flexible midi routings?

    Anyway, killer work @sinosoidal, I'm new to the iOS world but LK is already proving to be a big piece to my puzzle :smiley:

    Thanks for your feedback and support. :blush:

    Full MPE support on LK is not on our priority list but it could definitely happen in the next year. Lets see how it goes.

  • AletheiaAletheia

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

  • onerezonerez

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    @wim or whoever.... I must be dense... how are you recording the midi into LK??? I cant for the love of heck figure it out.

  • gregsmithgregsmith

    @onerez said:

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    @wim or whoever.... I must be dense... how are you recording the midi into LK??? I cant for the love of heck figure it out.

    I can’t get it to work either - I just posted this on the GR-16 thread:

    I’m currently trying to record midi from gr-16 into LK, hosted in AUM. Each gr-16 pad is output on its own midi channel so I’ve had iust ticked them all to route them into LK. I’ve got a track in LK that’s setup to receive all midi channels on the LK input. When I record it only records on c3 in the piano roll. I can’t work out if it’s because all midi channels output c3, or if it’s only recording one of the pads?

    Is this the same problem you’re having?

  • JanosaxJanosax

    @sinosoidal said:

    @clowm said:

    @sinosoidal said:

    @tahiche said:
    Keep up the amazing work. Hope more follow your footsteps and make “problem solving” apps that open possibilities and new paths. It’s also brave cos you’re embracing a lot of functionality and with that comes a lot of work and risks. Really appreciate it. Bravo, Portuguese stars!!.

    Thank you for your warm words! :blush:

    So... now that 2020 is getting to an end, what do you desire for LK in 2021? You have only three wishes, use them wisely...

    Only one wish: more efficient screen space use on IPhones

    I believe we can save some space with margins. We will have a couple of reported issues. We will take a look! Thx

    +1 everything is a bit too small even on 7 Plus. Some buttons could be a tad bigger perhaps.

  • onerezonerez

    @gregsmith said:

    @onerez said:

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    @wim or whoever.... I must be dense... how are you recording the midi into LK??? I cant for the love of heck figure it out.

    I can’t get it to work either - I just posted this on the GR-16 thread:

    I’m currently trying to record midi from gr-16 into LK, hosted in AUM. Each gr-16 pad is output on its own midi channel so I’ve had iust ticked them all to route them into LK. I’ve got a track in LK that’s setup to receive all midi channels on the LK input. When I record it only records on c3 in the piano roll. I can’t work out if it’s because all midi channels output c3, or if it’s only recording one of the pads?

    Is this the same problem you’re having?

    I can’t even get that far. But following same steps. @wim is vampire so we will have to wait till sundown to see what he thinks. 😂😂😂

  • AngieAngie

    @sinosoidal said:

    @Angie said:
    Is there a way to change the scale used for the notes on the pads. If not, is this in future plans? I’m really enjoying LK. It’s been a lot easier for me to get up to speed with than TouchAble.

    You can select chords but not change the scale. Sorry! I will add this as a feature request to our huge LK wish list. :blush:

    Thank you ❤️. There’s plenty else to enjoy in the app until then. 😃

  • gregsmithgregsmith

    @onerez said:

    @gregsmith said:

    @onerez said:

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    @wim or whoever.... I must be dense... how are you recording the midi into LK??? I cant for the love of heck figure it out.

    I can’t get it to work either - I just posted this on the GR-16 thread:

    I’m currently trying to record midi from gr-16 into LK, hosted in AUM. Each gr-16 pad is output on its own midi channel so I’ve had iust ticked them all to route them into LK. I’ve got a track in LK that’s setup to receive all midi channels on the LK input. When I record it only records on c3 in the piano roll. I can’t work out if it’s because all midi channels output c3, or if it’s only recording one of the pads?

    Is this the same problem you’re having?

    I can’t even get that far. But following same steps. @wim is vampire so we will have to wait till sundown to see what he thinks. 😂😂😂

    @wim never sleeps, it’s fine 😂

    Fwiw I’ve just tried the same setup routing into Xequence 2 and it does the same but on c5. It does seem that each channel outputs it’s ‘beats’ to the same midi note. I have no idea how to deal with this.

    Sorry @wim 🙏

  • gregsmithgregsmith

    @gregsmith said:

    @onerez said:

    @gregsmith said:

    @onerez said:

    @wim said:

    @gregsmith said:
    Thanks for confirming my assumptions @wim . I thought there might be something I didn’t know about - will have a look for an ‘immediate pattern change’ option but if not I think the best way is to send midi from LK to trigger the pads rather than the built in sequencer in gr-16.

    That is a great way to work with GR-16. If you like developing the ideas in GR-16, you can record the pattern out to LK, then launch it from there.

    This is similar to how I worked with Xequence 2 and GR-16, one of my favorite workflows. Whip up the ides in GR-16, record the midi into X2 to arrange songs.

    I'm looking forward to this approach with GR-16 and LK. B)

    @wim or whoever.... I must be dense... how are you recording the midi into LK??? I cant for the love of heck figure it out.

    I can’t get it to work either - I just posted this on the GR-16 thread:

    I’m currently trying to record midi from gr-16 into LK, hosted in AUM. Each gr-16 pad is output on its own midi channel so I’ve had iust ticked them all to route them into LK. I’ve got a track in LK that’s setup to receive all midi channels on the LK input. When I record it only records on c3 in the piano roll. I can’t work out if it’s because all midi channels output c3, or if it’s only recording one of the pads?

    Is this the same problem you’re having?

    I can’t even get that far. But following same steps. @wim is vampire so we will have to wait till sundown to see what he thinks. 😂😂😂

    @wim never sleeps, it’s fine 😂

    Fwiw I’ve just tried the same setup routing into Xequence 2 and it does the same but on c5. It does seem that each channel outputs it’s ‘beats’ to the same midi note. I have no idea how to deal with this.

    Sorry @wim 🙏

    I figured it out! You can change the notes in gr-16 that the sequencer is using if you press ‘edit’ then use the little screen to move them up and down. This then outputs those notes as midi so you just have to make them different.

    If you start with a c note for the first pad and go up a note for each pad, it’ll be the right notes when you feed the midi back in.

  • aratxtraratxtr

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

  • sinosoidalsinosoidal

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

  • hellquisthellquist
    edited December 2020

    @sinosoidal said:

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

    Aah. Somehow it feels good I'm not alone as that means I can abort my far-fetching plans for de-bugging. For sake of completeness: I'm using iPad Pro 12.9 (first gen) on the latest iOS (14.3). I have also un-installed LK (to ensure no beta stuff was lingering in system), rebooted and re-installed. I host LK and the other sound-source apps in AUM as AU's. I should possibly try to load LK stand-alone and do a couple of variants of hosts too, of both LK and sound-source-apps.

    EDIT: Oh, and yes, there has been times when the sound (and thus midi) comes "back" for a few seconds, only to go away again. Highly random though.

  • krassmannkrassmann
    edited December 2020

    @sinosoidal said:

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

    I have the same problem on both my iPads (iPad 6, iPad Pro 11 2020). I was a bit digging into it. The troublemaker seems to be my external keyboard (Korg nanoKey Studio). When I unplug it the problem goes away. The strange thing is that, as you can see on my screenshot, it is not even connected to LK, it only appears in AUM. Second strange thing is that there is absolutely no problem when I run LK standalone and use its virtual MIDI ports with the same setup in AUM. There is one thing different with the Korg nanoKey Studio compared to the other MIDI controllers I have connected (Launchpad mini mk2 and LauchControl XL): The nanoKey sends MIDI clock permanently because of its arpeggiator. I hope that helps to better locate the bug.

    For testing I created an AUM setup with DRC and Rozeta Bassline sending MIDI to LK. When the nanoKey is connected I get notes only sometimes. As soon as I plug it out and it disappears from AUM’s MIDI matrix then the sequence is playing fine.

    The nanoKey is also a Bluetooth device. If I connect it with Bluetooth it does not send MIDI clock. Then there is also no problem.

  • wimwim
    edited December 2020

    @gregsmith said:
    Fwiw I’ve just tried the same setup routing into Xequence 2 and it does the same but on c5. It does seem that each channel outputs it’s ‘beats’ to the same midi note. I have no idea how to deal with this.

    I know it works for Xequence from the standalone. Haven't tried from the AUv3 and not with LK.

    See https://patchstorage.com/xequence-2-grooverider-gr-16-patch/ for details on GR-16 Standalone > X2.

    I might have some time to look at this later tonight ... if I find a suitable victim soon enough after sundown.

    🩸🧛🏻‍♂️🩸

  • onerezonerez

    @wim said:

    @gregsmith said:
    Fwiw I’ve just tried the same setup routing into Xequence 2 and it does the same but on c5. It does seem that each channel outputs it’s ‘beats’ to the same midi note. I have no idea how to deal with this.

    I know it works for Xequence from the standalone. Haven't tried from the AUv3 and not with LK.

    See https://patchstorage.com/xequence-2-grooverider-gr-16-patch/ for details on GR-16 Standalone > X2.

    I might have some time to look at this later tonight ... if I find a suitable victim soon enough after sundown.

    🩸🧛🏻‍♂️🩸

    @wim Don’t worry about it!!! I was trying to do it all in AUM. You have better things to worry about I’m sure. 🤓

  • JanosaxJanosax
    edited December 2020

    @krassmann said:

    @sinosoidal said:

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

    I have the same problem on both my iPads (iPad 6, iPad Pro 11 2020). I was a bit digging into it. The troublemaker seems to be my external keyboard (Korg nanoKey Studio). When I unplug it the problem goes away. The strange thing is that, as you can see on my screenshot, it is not even connected to LK, it only appears in AUM. Second strange thing is that there is absolutely no problem when I run LK standalone and use its virtual MIDI ports with the same setup in AUM. There is one thing different with the Korg nanoKey Studio compared to the other MIDI controllers I have connected (Launchpad mini mk2 and LauchControl XL): The nanoKey sends MIDI clock permanently because of its arpeggiator. I hope that helps to better locate the bug.

    For testing I created an AUM setup with DRC and Rozeta Bassline sending MIDI to LK. When the nanoKey is connected I get notes only sometimes. As soon as I plug it out and it disappears from AUM’s MIDI matrix then the sequence is playing fine.

    The nanoKey is also a Bluetooth device. If I connect it with Bluetooth it does not send MIDI clock. Then there is also no problem.

    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

  • gregsmithgregsmith

    @onerez said:

    @wim said:

    @gregsmith said:
    Fwiw I’ve just tried the same setup routing into Xequence 2 and it does the same but on c5. It does seem that each channel outputs it’s ‘beats’ to the same midi note. I have no idea how to deal with this.

    I know it works for Xequence from the standalone. Haven't tried from the AUv3 and not with LK.

    See https://patchstorage.com/xequence-2-grooverider-gr-16-patch/ for details on GR-16 Standalone > X2.

    I might have some time to look at this later tonight ... if I find a suitable victim soon enough after sundown.

    🩸🧛🏻‍♂️🩸

    @wim Don’t worry about it!!! I was trying to do it all in AUM. You have better things to worry about I’m sure. 🤓

    What have you tried so far @onerez?

    All I did was click the 3 lines next to LK in AUM and click on all of the GR-16 midi channels. In LK then make sure the track your recording to is set to LK input and All channels. When you arm the track, press record, then press play in AUM, you should see some notes start to appear in the LK piano roll.

    I can make you a video if you want?

  • audiobussyaudiobussy

    @sinosoidal said:

    @sinosoidal What's the estimated date for releasing the support for Launchpad Pro MK3? Thanks

    We have ordered them, they are not here yet. Team is on vacations. Some updates to do to DRC and FRMS. Hopefully should be implemented by the end of January. :blush:

    Thank you! Agree that you guys are amazing developers — best wishes in 2021!

  • aratxtraratxtr

    @krassmann said:

    @sinosoidal said:

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

    I have the same problem on both my iPads (iPad 6, iPad Pro 11 2020). I was a bit digging into it. The troublemaker seems to be my external keyboard (Korg nanoKey Studio). When I unplug it the problem goes away. The strange thing is that, as you can see on my screenshot, it is not even connected to LK, it only appears in AUM. Second strange thing is that there is absolutely no problem when I run LK standalone and use its virtual MIDI ports with the same setup in AUM. There is one thing different with the Korg nanoKey Studio compared to the other MIDI controllers I have connected (Launchpad mini mk2 and LauchControl XL): The nanoKey sends MIDI clock permanently because of its arpeggiator. I hope that helps to better locate the bug.

    For testing I created an AUM setup with DRC and Rozeta Bassline sending MIDI to LK. When the nanoKey is connected I get notes only sometimes. As soon as I plug it out and it disappears from AUM’s MIDI matrix then the sequence is playing fine.

    The nanoKey is also a Bluetooth device. If I connect it with Bluetooth it does not send MIDI clock. Then there is also no problem.

    Hm, for me it also happens when i want to trigger LK with another AUV3 keyboard inside AUM and all my external gear disconnected.

  • aratxtraratxtr

    @sinosoidal said:

    @aratxtr said:

    @Aletheia said:

    @sinosoidal said:

    @hellquist said:
    @sinosoidal Hi! I'm having an issue with my external midi keyboard and LK, routed via AUM. Are there any known issues regarding that and I should passively await an update, or should I fill in a proper support request?

    I basically get very intermittent/random connectivity within LK. I can see the midi coming to AUM alright. My midi keyboard, which I've had for a couple of years, works just fine with all other apps/daws. I can't recall if I used it during beta testing of LK though I definitely had it already then (it is the one midi keyboard I've ever owned, an Alesis Vi-49).

    It works fine in LK too...for about 10 seconds. Then it stops. It appears like LK thinks notes are held that aren't, and it tries to record them to infinity unless I stop it, and that "feels" like it is using up all the resources including passing sound through to the test app. If I connect the keyboard directly to the test app (this evening it was Tines and then later Pure Synth) it works just as intended, but I can't pass the midi to LK -> other app (more than the initial few seconds).

    This is a know issue. It is not very frequent. I don't know the cause yet and I don't know how to reproduce it. Only happened to me once. This is what makes it hard to fix it...

    How many people here are having this issue? Is it intermittent? Or when someone has this problem, has it always?

    This happens to me as well since update 1.9.0. No matter if I send midi from my Launchpad or from a plugin like Fugue Machine I get this exact intermitent behaviour. And just like above, if I skip LK there is no problem in the midi flow. Before 1.9.0 it had no issue. Ipad 7th Gen, iOS 13.6.1

    Exactly the same here. IPad 6 Gen. IOS 14.1

    Does it ever go away or doesn't happen as a matter of luck?

    This is one of the most tricky bug I have ever been reported of. It happened to me once and since then couldn't replicate it. There is no pattern among users hardware and operating system reports.

    As with all problems, I'm sure we will find a solution for it...

    Unfortunately it occurs every single time. Maybe i should try to de- and reinstall AUM..

  • AletheiaAletheia
    edited December 2020

    @aratxtr said:

    I have the same problem on both my iPads (iPad 6, iPad Pro 11 2020). I was a bit digging into it. The troublemaker seems to be my external keyboard (Korg nanoKey Studio). When I unplug it the problem goes away. The strange thing is that, as you can see on my screenshot, it is not even connected to LK, it only appears in AUM. Second strange thing is that there is absolutely no problem when I run LK standalone and use its virtual MIDI ports with the same setup in AUM. There is one thing different with the Korg nanoKey Studio compared to the other MIDI controllers I have connected (Launchpad mini mk2 and LauchControl XL): The nanoKey sends MIDI clock permanently because of its arpeggiator. I hope that helps to better locate the bug.

    Hm, for me it also happens when i want to trigger LK with another AUV3 keyboard inside AUM and all my external gear disconnected.

    I can confirm this as well, @sinosoidal . If I unplug the Launchpad pro indeed it reacts normally to something like Fugue Machine or Cykle (any AUv3 midi sequencer). If I plug it back immediately the issues reappears, no matter if I use the Launchpad or sequencer plugins.

    I then have tried setting the "send midi clock off" on the Launchpad and it only seems to partly help, the AUv3 sequencers now work good - even with the controller plugged they play correctly via LK. But if I play notes on the Launchpad after some short time LK seems to "freeze" it doesn't receive anymore input. After some time it resumes and so on. So there's definitely something regarding midi clock from outside and external input.

    This happens in AudioBus as well, so clearly it doesn't have to do with AUM. Also, I did try reinstalling AUM and LK, @aratxtr and the same thing happens so there's no need to try it.

  • krassmannkrassmann
    edited December 2020

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

  • sinosoidalsinosoidal

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

  • WhiteWhite

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Happy new year 😊

  • gregsmithgregsmith

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Happy new year! Thanks for making 2020 a bit better with LK! 🙏

  • PxlhgPxlhg

    @sinosoidal said:
    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    Happy New Year!! :)

  • TatobxTatobx

    @sinosoidal said:

    @krassmann said:

    @Janosax said:
    You can try to play with those (global) settings in Korg Kontrol Editor desktop app, that could fix your issue:

    Okay, I did that. After turning MIDI clock off I could connect the Korg nanoKey Studio with an USB cable and the problem did not occur. I think that’s the proof that the MIDI clock is one reason for this issue when running as AUv3. I hope that helps to hunt down the bug.

    This sounds like LEAD!

    Can anyone else having the same problem relate with this report of midi clock being part of the problem?

    The year is getting to an end. Wishing you all an Happy New Year! :blush:

    a couple of times it happened to me too
    Launchkey Mini MK3

    Happy New Year

Sign In or Register to comment.