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

  • sinosoidalsinosoidal

    @espiegel123 said:
    @sinosoidal : I just recorded a MIDI part and there is a note at the very beginning that plays the first time the loop plays but than doesn't sound on any of the repeats. This is with the latest beta. If I move the note a 32nd note later it sounds on the repeats but if it is right 1.1.0 or a little later it only sounds the first time.

    Can you send me a video showing how to reproduce the problem?

  • gregsmithgregsmith

    @sinosoidal said:

    @tahiche said:

    @Rodolfo said:

    @sinosoidal said:

    @branis said:

    @Rodolfo said:
    Sorry if this has been already commented (this is a long thread..) but I’d just would like to know if there’s a way to change the behavior of the Shift function as I find it not only counterintuitive and convoluted but also against all IOS UI/UX standards.

    The only purpose of holding the Shift functions is to enable new buttons with three dots which further enable new menus above them, overriding the column selections in the last row of clips.

    My point is:
    The Shift buttons and their behavior are redundant, counterintuitive, very uncomfortable to use and take precious space on the screen

    The shift has several alternate functions:

    • by default you edit a single note velocity, with shift press you change all at once
    • you can drag/copy selected notes with shift
    • you can drag/copy clips in the grid with shift

    The are probably more features I can't remember right now.

    In summary, shift isn't only used for activating the context menu for the tracks.

    Proposal:
    -Why not just add the three dot menus in all columns exactly the same way as the other combo menus for MIDI channels, IO, etc? They would use very little space and would be ready to tap without the need of a “Shift” function.

    That's redundant and wastes space in phone view.

    -If the two Shift buttons are removed then that space could be used to acomodate the other missing navigation functions that are only available after the tap and hold of the Shift button, avoiding redundant taps and speeding up the navigation workflow.

    Shift/alt operations are very common in many software/harware solutions in order to accommodate functions without spending space with extra buttons.

    Again, sorry if this has already been addressed. The app is really awesome, clearly the only and best clips sequencer on IOS, but I find the Shift functions very annoying and I know for sure that many other users think exactly the same.

    Hopefully this can be improved in a future update.

    We do hear users opinions and make improvements when we feel a common sense among the community.

    Long pressing clips opens a menu with extra functions, maybe the same could be applied to tracks and scenes.

    @branis the problem with this solution is that it conflicts with the track selection operation that occurs when we press the track label. Not relevant in midi mode (for now) but it will definitely mess with Live mode.

    @Rodolfo thanks for your feedback. We are always listening to the community and trying to improve the experience based on it. Merry xmas! :blush:

    Thank you very much for your comments!
    I just expressed my honest and transparent feedback on something that I consider could be drastically enhanced if the Shift function is eliminated. I know a lot of gear that uses the same approach, but no IOS app with this "hardware" concept, as far as I know.
    I also understand that it's not easy to modify a very complex (and awesome) app like LK, but I would kindly ask you to think out of the box just for a moment. You already know the reasons for keeping the Shift function, but maybe you discover that there are better options, who knows... I believe it's worth trying...
    Merrr xmass!!!

    I have to say I agree with @Rodolfo here about the Shift thing. Sometimes we feel guilty as if any criticism is going to offend our respected dev, I feel like that often. Constructive criticism on an app that you use and love shows implication and involvement. It also shows you hate the Shift function! 😂
    I did mention a while back various aspects of the UI that I find confusing. Thing they stop being confusing after some use, so those are hard to manage. You have to travel in time to see and trust your “I’m lost” moment.
    I remember a few:
    “M” for monitoring?. Thought it’d be “Mute”

    M stands for mixer actually because it hides Mute and Solo functions that are usually connected to the Mixer concept.

    Assigning cc’s on the midi control page is hidden below, extremely unintuitive.

    Agree! A better solution will take too much valuable time for now. Sorry!

    Opening up the midi sequence with the little bar, seems obvious now... but I remember it wasn’t.

    :smile:

    Double transport bar... this one still confuses me.

    Where is the duplicated transport bar? The one inside the composer is regarding the clip only.

    Overall these are all little details that only matter on the first hours of use, but those are crucial to newcomers. Specially ones with little patience.

    Tell me a complex piece of software that you are able to master in a day and get to know all its features. This days people are impatient about anything. They want to do everything in a snap because there is so much happening.

    LK is quite complex software with a lot of features and it is very hard to learn all this features just by looking at the screen. This happens with any other complex application.

    A few touches would go a long way IMO. I remember abandoning Modstep cos I kept getting lost, to me that was an amazing app ruined by weird design options.

    I experienced the same thing with Modstep. Full of options but it looked like a maze.

    BTW. I’d rather you leave the UI as it is, just change “Shift” to “Alt” and add audio clips instead! 😂

    It is impossible to please everyone.

    We are still working on features that have been asked here in the last couple of months. We prefer to implement this features than spending a lot of time changing small details that only people that haven't spend enough time with the app will complain.

    That doens't mean we are not hearing or getting offended with criticism. We usually have two options: we can ignore it or defend our point of view! :blush:

    I felt the same as @tahiche in all honesty but then I remembered I’m using your app on an iPhone a lot of the time and the amount of power you’ve managed to squeeze into an iPhone screen is phenomenal.

    Also a lot of my favourite ui’s on iOS (Xequence2, BLEASS apps) are doing things that we already know well such as piano rolls and filters, whereas LK is fairly new territory... for me anyway. I’ve also never used ableton so perhaps some of the ui elements are natural for ableton users?

    Despite all of this, LK is up there with Drambo and Atom 2 as most exciting app updates of the year.

  • batonbaton

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

  • onerezonerez

    @sinosoidal Just a reminder that you guys are doing a great job!!!!!!!!!! I know that it can be frustrating sometimes with the language anomalies at times, but you are terrific!!!!!! Thanks for all that you have done with this app!!!!!

  • GrimLuckyGrimLucky

    @onerez said:
    @sinosoidal Just a reminder that you guys are doing a great job!!!!!!!!!! I know that it can be frustrating sometimes with the language anomalies at times, but you are terrific!!!!!! Thanks for all that you have done with this app!!!!!

    +100, especially for it working great with APC key controller.

  • AngieAngie

    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.

  • sambosambo

    Personally I think that LK wins the prize for the most improved iOS app of 2020.

  • sinosoidalsinosoidal

    @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:

  • sinosoidalsinosoidal

    @onerez said:
    @sinosoidal Just a reminder that you guys are doing a great job!!!!!!!!!! I know that it can be frustrating sometimes with the language anomalies at times, but you are terrific!!!!!! Thanks for all that you have done with this app!!!!!

    Thank your for your feedback. We have done this because we have high interaction from the community which keeps us pushing us to the limit! Your guys rock too! :blush:

  • sinosoidalsinosoidal
    edited December 2020

    @sambo said:
    Personally I think that LK wins the prize for the most improved iOS app of 2020.

    Indeed! :blush: I would vote for that prize! :lol:

    LK has been updated 16 times since AUv3 support came out on 9 Jul 2020.

    1.9.1 - 22 Dec 2020

    • Performance improvements
    • Track arm button is now always visible
    • Fix XY and KEYBOARD midi cc to MATRIX
    • General bug fixes and improvements

    1.9.0 - 13 Dec 2020

    • Sample accurate midi events (playback & recording)
    • Clip drag and copy (with shift)
    • Notes drag and copy (with shift)
    • Fixes playback jitter
    • Fixes sample rate (AUv3)
    • Adds the ability to sync with host when hosted (status bar link icon)
    • Send MIDI clock start/stop events only when enabled
    • General bug fixes and improvements

    1.8.5 - 30 Nov 2020

    • Added note probability
    • Added another shift button to the left of the transport bar
    • Save track arm and global recording state on song model
    • Fixes crashes/freezes while handling midi input
    • Fixes crash on midi import to a clip while playing
    • General bug fixes and improvements

    1.8.4 - 12 Nov 2020

    • Fixed bug that would might cause LK to crash when disconnecting midi devices
    • Added Launchpad X support
    • Added APC Key 25 support
    • Added Launchpad Mini MK2 support
    • Added the ability to switch off controller via Menu->Midi menu item
    • Added grid to automations editor with snap support
    • Properties context menu for track and scene
    • Midi trigger for scene launch and track stop
    • Midi trigger can now be a note
    • Recording of clips without pre defined length
    • Allow undo/redo recorded notes
    • Clip notes now have clip color
    • Shift+tap to select/deselect notes
    • General bug fixes and improvements

    1.8.3 - 30 Oct 2020

    • Swing and humanize
    • Added Akai MPC Mini support
    • Midi Export
    • Ableton Live Export
    • General bug fixes and optimizations

    1.8.2 - 19 Oct 2020

    • New notes operations
    • Break down of clip inspector into sections
    • Added chord and melody generation tools
    • Fixed mute state on solo tracks change
    • Fixed recording to multiple armed tracks
    • Shift + Selection appends notes to selection
    • Note velocity is now independent for each note unless Shift is pressed
    • Improved restore state

    1.8.1 - 3 Oct 2020

    • Keyboard module: natural keyboard
    • Keyboard module: double keyboard on tablet
    • Matrix: Navigate through selected track and scene using the arrows in the transport bar
    • Matrix: Added move left, move right and add track to track options
    • Matrix: Added cut operation to clip context menu
    • Matrix: Fixed audio glitch on add/delete track/scene
    • Matrix - Composer: keyboard scale saved as clip property- Composer: custom scale
    • Matrix - Composer: fixed viewport navigation
    • Matrix - Composer: fixed automation loading bug
    • Matrix - Composer: removed selected pitch indicator
    • Matrix - Composer: Keyboard Scales
    • Matrix - Composer: Multi-Touch Piano Roll
    • Matrix - Composer: allow fully hide modulations section

    1.8.0 - 26 Sep 2020

    • MIDI CC automations
    • Visual review of all modules
    • Fixed AUv3 MIDI playback drift
    • Performance improvements
    • General bug fixes and optimizations

    1.7.6 - 9 Sep 2020

    • More clip follow actions (MATRIX MIDI Mode)
    • Clip play state saving (MATRIX MIDI Mode)
    • Aims to fix crashes

    1.7.5 - 7 Sep 2020

    • Aims to fixes some crashes that are being reported
    • Fixes imported MIDI clip length
    • Add scroll functionality to clip properties panel

    1.7.4 - 29 Aug 2020

    • Fixes bug in clip grid when using group tracks (Live Mode)
    • Fixes bug in selected notes move (Clip Composer)

    1.7.3 - 25 Aug 2020

    • Import MIDI files (MATRIX - MIDI Mode)
    • Bug fixes and optimisations

    1.7.2 - 14 Aug 2020

    • Add clip properties panel (MATRIX MIDI mode only)
    • Add clip copy/paste/delete context menu (MATRIX MIDI mode only)
    • Add move scene up/down options (MATRIX MIDI mode only)
    • Add clip follow actions & midi cc triggering
    • Performance improvements
    • General bug fixes and improvements

    1.7.1 - 17 Jul 2020

    • Fix Apple Pencil support
    • Fix note min length
    • Fix timeline disappearing
    • Fix notes delete on move and overlap
    • Fix quantized recording
    • Fix note off when track is muted while playing
    • Fix tempo when hosted (AUv3)
    • Fix host play state sync (AUv3)
    • Fix clock source label (AUv3)
    • General bug fixes and optimizations

    1.7.0 - 9 Jul 2020

    • Add AUv3 support
  • sinosoidalsinosoidal

    @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:

  • espiegel123espiegel123

    @sinosoidal said:

    @espiegel123 said:
    @sinosoidal : I just recorded a MIDI part and there is a note at the very beginning that plays the first time the loop plays but than doesn't sound on any of the repeats. This is with the latest beta. If I move the note a 32nd note later it sounds on the repeats but if it is right 1.1.0 or a little later it only sounds the first time.

    Can you send me a video showing how to reproduce the problem?

    I have PM’ed you a link to a video

  • tahichetahiche

    @gregsmith said:

    @sinosoidal said:

    @tahiche said:

    @Rodolfo said:

    @sinosoidal said:

    @branis said:

    @Rodolfo said:
    Sorry if this has been already commented (this is a long thread..) but I’d just would like to know if there’s a way to change the behavior of the Shift function as I find it not only counterintuitive and convoluted but also against all IOS UI/UX standards.

    The only purpose of holding the Shift functions is to enable new buttons with three dots which further enable new menus above them, overriding the column selections in the last row of clips.

    My point is:
    The Shift buttons and their behavior are redundant, counterintuitive, very uncomfortable to use and take precious space on the screen

    The shift has several alternate functions:

    • by default you edit a single note velocity, with shift press you change all at once
    • you can drag/copy selected notes with shift
    • you can drag/copy clips in the grid with shift

    The are probably more features I can't remember right now.

    In summary, shift isn't only used for activating the context menu for the tracks.

    Proposal:
    -Why not just add the three dot menus in all columns exactly the same way as the other combo menus for MIDI channels, IO, etc? They would use very little space and would be ready to tap without the need of a “Shift” function.

    That's redundant and wastes space in phone view.

    -If the two Shift buttons are removed then that space could be used to acomodate the other missing navigation functions that are only available after the tap and hold of the Shift button, avoiding redundant taps and speeding up the navigation workflow.

    Shift/alt operations are very common in many software/harware solutions in order to accommodate functions without spending space with extra buttons.

    Again, sorry if this has already been addressed. The app is really awesome, clearly the only and best clips sequencer on IOS, but I find the Shift functions very annoying and I know for sure that many other users think exactly the same.

    Hopefully this can be improved in a future update.

    We do hear users opinions and make improvements when we feel a common sense among the community.

    Long pressing clips opens a menu with extra functions, maybe the same could be applied to tracks and scenes.

    @branis the problem with this solution is that it conflicts with the track selection operation that occurs when we press the track label. Not relevant in midi mode (for now) but it will definitely mess with Live mode.

    @Rodolfo thanks for your feedback. We are always listening to the community and trying to improve the experience based on it. Merry xmas! :blush:

    Thank you very much for your comments!
    I just expressed my honest and transparent feedback on something that I consider could be drastically enhanced if the Shift function is eliminated. I know a lot of gear that uses the same approach, but no IOS app with this "hardware" concept, as far as I know.
    I also understand that it's not easy to modify a very complex (and awesome) app like LK, but I would kindly ask you to think out of the box just for a moment. You already know the reasons for keeping the Shift function, but maybe you discover that there are better options, who knows... I believe it's worth trying...
    Merrr xmass!!!

    I have to say I agree with @Rodolfo here about the Shift thing. Sometimes we feel guilty as if any criticism is going to offend our respected dev, I feel like that often. Constructive criticism on an app that you use and love shows implication and involvement. It also shows you hate the Shift function! 😂
    I did mention a while back various aspects of the UI that I find confusing. Thing they stop being confusing after some use, so those are hard to manage. You have to travel in time to see and trust your “I’m lost” moment.
    I remember a few:
    “M” for monitoring?. Thought it’d be “Mute”

    M stands for mixer actually because it hides Mute and Solo functions that are usually connected to the Mixer concept.

    Assigning cc’s on the midi control page is hidden below, extremely unintuitive.

    Agree! A better solution will take too much valuable time for now. Sorry!

    Opening up the midi sequence with the little bar, seems obvious now... but I remember it wasn’t.

    :smile:

    Double transport bar... this one still confuses me.

    Where is the duplicated transport bar? The one inside the composer is regarding the clip only.

    Overall these are all little details that only matter on the first hours of use, but those are crucial to newcomers. Specially ones with little patience.

    Tell me a complex piece of software that you are able to master in a day and get to know all its features. This days people are impatient about anything. They want to do everything in a snap because there is so much happening.

    LK is quite complex software with a lot of features and it is very hard to learn all this features just by looking at the screen. This happens with any other complex application.

    A few touches would go a long way IMO. I remember abandoning Modstep cos I kept getting lost, to me that was an amazing app ruined by weird design options.

    I experienced the same thing with Modstep. Full of options but it looked like a maze.

    BTW. I’d rather you leave the UI as it is, just change “Shift” to “Alt” and add audio clips instead! 😂

    It is impossible to please everyone.

    We are still working on features that have been asked here in the last couple of months. We prefer to implement this features than spending a lot of time changing small details that only people that haven't spend enough time with the app will complain.

    That doens't mean we are not hearing or getting offended with criticism. We usually have two options: we can ignore it or defend our point of view! :blush:

    I felt the same as @tahiche in all honesty but then I remembered I’m using your app on an iPhone a lot of the time and the amount of power you’ve managed to squeeze into an iPhone screen is phenomenal.

    Also a lot of my favourite ui’s on iOS (Xequence2, BLEASS apps) are doing things that we already know well such as piano rolls and filters, whereas LK is fairly new territory... for me anyway. I’ve also never used ableton so perhaps some of the ui elements are natural for ableton users?

    Despite all of this, LK is up there with Drambo and Atom 2 as most exciting app updates of the year.

    In case I wasn’t clear I LOVE LK. Exceptional and very, very needed. My comments are just my opinions, and my point was that pointing out things you’d do differently or not quite like is by no means a sign of less appreciation, quite the opposite. If I was to point out the things I do like it’d take me 56 posts.

    It is impossible to please everyone

    I know... but you only have to please me!! 😜

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

  • hellquisthellquist

    @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).

  • gregsmithgregsmith

    I have an issue that I can’t get my head round. It’s not a bug or anything - basically when I send a program change to drum sequencer app like gr-16 at the beginning of a clip, it doesn’t trigger a program change straight away, as gr-16 has just started playing the current pattern, so waits until it’s finished to trigger the program change. I’m sure there’s a good solution to this like sending the change at the end of the previous clip, but this doesn’t really fit the clip launching dynamic very well??

  • sinosoidalsinosoidal

    @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?

  • sinosoidalsinosoidal

    @gregsmith said:
    I have an issue that I can’t get my head round. It’s not a bug or anything - basically when I send a program change to drum sequencer app like gr-16 at the beginning of a clip, it doesn’t trigger a program change straight away, as gr-16 has just started playing the current pattern, so waits until it’s finished to trigger the program change. I’m sure there’s a good solution to this like sending the change at the end of the previous clip, but this doesn’t really fit the clip launching dynamic very well??

    We need to review those mechanics. Can you please make a video showing the minimal steps to reproduce the problem? Thx!

  • sinosoidalsinosoidal
    edited December 2020

    @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...

  • wimwim
    edited December 2020

    @gregsmith said:
    I have an issue that I can’t get my head round. It’s not a bug or anything - basically when I send a program change to drum sequencer app like gr-16 at the beginning of a clip, it doesn’t trigger a program change straight away, as gr-16 has just started playing the current pattern, so waits until it’s finished to trigger the program change. I’m sure there’s a good solution to this like sending the change at the end of the previous clip, but this doesn’t really fit the clip launching dynamic very well??

    That isn't really an LK issue. In some ways it's not the target app issue either. It's just the reality that a program change can't always be enacted instantaneously. If it's a program change to the patch of a synthesizer, having it kick in slightly after the beat might not be a big deal. But when it's launching a pattern, the target app is likely to quantize the pattern launch to the beginning of a bar. But if the sending app is sending it right at the bar, then it's already too late for the target app.

    You've already discovered the solution: launch the PC just before the bar for apps that need it. I don't think LK can know when it might need to send a program change earlier than when you've sequenced it because of the behavior of a target app.

    Some apps have an "immediate pattern change" option setting, meaning the app will change patterns mid-pattern if needed, most don't.

  • clowmclowm

    @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

  • gregsmithgregsmith

    @sinosoidal said:

    @gregsmith said:
    I have an issue that I can’t get my head round. It’s not a bug or anything - basically when I send a program change to drum sequencer app like gr-16 at the beginning of a clip, it doesn’t trigger a program change straight away, as gr-16 has just started playing the current pattern, so waits until it’s finished to trigger the program change. I’m sure there’s a good solution to this like sending the change at the end of the previous clip, but this doesn’t really fit the clip launching dynamic very well??

    We need to review those mechanics. Can you please make a video showing the minimal steps to reproduce the problem? Thx!

    Thanks for replying @sinosoidal - as wim says below, this isn’t your problem to solve so won’t take up your time on it.

    @wim said:

    @gregsmith said:
    I have an issue that I can’t get my head round. It’s not a bug or anything - basically when I send a program change to drum sequencer app like gr-16 at the beginning of a clip, it doesn’t trigger a program change straight away, as gr-16 has just started playing the current pattern, so waits until it’s finished to trigger the program change. I’m sure there’s a good solution to this like sending the change at the end of the previous clip, but this doesn’t really fit the clip launching dynamic very well??

    That isn't really an LK issue. In some ways it's not the target app issue either. It's just the reality that a program change can't always be enacted instantaneously. If it's a program change to the patch of a synthesizer, having it kick in slightly after the beat might not be a big deal. But when it's launching a pattern, the target app is likely to quantize the pattern launch to the beginning of a bar. But if the sending app is sending it right at the bar, then it's already too late for the target app.

    You've already discovered the solution: launch the PC just before the bar for apps that need it. I don't think LK can know when it might need to send a program change earlier than when you've sequenced it because of the behavior of a target app.

    Some apps have an "immediate pattern change" option setting, meaning the app will change patterns mid-pattern if needed, most don't.

    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.

  • wimwim

    @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)

  • 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.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024