Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

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

1108109111113114130

Comments

  • @sinosoidal said:

    @branis said:

    @xglax said:

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

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

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

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

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

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

    Sorry for the work :D

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

    Any feedback regarding these two fixes is much appreciated =)

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

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

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

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

    The problem should be fixed in build 278

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

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

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

  • edited January 2022

    @sinosoidal said:

    @branis said:

    @xglax said:

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

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

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

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

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

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

    Sorry for the work :D

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

    Any feedback regarding these two fixes is much appreciated =)

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

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

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

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

    The problem should be fixed in build 278

    Scene chaining problem solved with latest beta!

    Thanks!

  • @Jeezs said:

    @sinosoidal said:

    @branis said:

    @xglax said:

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

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

    @Jeezs said:

    @sinosoidal said:

    @Jeezs said:

    @j_liljedahl said:

    @xglax said:

    @Jeezs said:

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

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

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

    Sorry for the work :D

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

    Any feedback regarding these two fixes is much appreciated =)

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

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

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

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

    The problem should be fixed in build 278

    Scene chaining problem solved with latest beta!

    Thanks!

    Thanks for the feedback! :blush:

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

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

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

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

  • @sinosoidal said:

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

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

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

  • edited February 2022

    @bleep said:

    @sinosoidal said:

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

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

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

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

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

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

  • edited February 2022

    Really like the refactoring of the layout, good job!

  • @MisplacedDevelopment said:
    Really like the refactoring of the layout, good job!

    Thanks for your feedback! :blush:

  • edited February 2022

    @MisplacedDevelopment said:
    Really like the refactoring of the layout, good job!

    I’ve been away from LK for a while and everything looks great but it seems like a whole new app now and I’ll have to learn and relearn what all the icons represent. Referring to the previous post about on screen help and a manual, maybe something like a quick start guide would be an easy place to start? This would be easier than a full blown manual. Even a screen shot of the main matrix view with icons labelled would be very helpful. Off to poke around in LK and try to figure out what’s going on. Edit: the icons on the piano roll could also be labelled in the screen shot too.

  • Yes! What an epic update! Love how you changed automations in this release. Displaying them large and over the pianoroll timeline. So cool. And CURVES editing!
    Wish more devs would implement automations like you did in this release. Epic.
    Thanks!

  • edited February 2022

    updating... Thanks..

  • Such a good update! Curved automation lanes that can be named and copied to other clips. Overall cleaned up UI looks nice. Still with some mysterious icons that one has forgotten the purpose of since last time around ;-)

  • @bleep said:
    Such a good update! Curved automation lanes that can be named and copied to other clips. Overall cleaned up UI looks nice. Still with some mysterious icons that one has forgotten the purpose of since last time around ;-)

    which icons? :blush:

  • edited February 2022

    @sinosoidal said:

    @bleep said:
    Such a good update! Curved automation lanes that can be named and copied to other clips. Overall cleaned up UI looks nice. Still with some mysterious icons that one has forgotten the purpose of since last time around ;-)

    which icons? :blush:

    The two icons to the left of Automation, what do they do? I suspect one is for displaying a ghost clip (?), but I have forgotten how to set it.

    Next to the left is crop, which can be a bit confusing. Is it an EDIT action sitting in-between icons for adjusting display? Maybe that's ok ... but would it be better if the zoom didn't change after cropping? I wonder if this crop edit would be better placed under the new wrench tab for editing.

    Next to the left of that is the "zoom to fit", which is easy enough to re-remember upon trying it. Perhaps it could act as a toggle, bringing you back to full length view if you tap it when already zoomed in to fit. If you understand my poor wording.

    At the bottom, I forgot what the tape icon is. The others are easy to figure out just by trying them (if you are in matrix view. If you try most of them out while being in piano roll view, you're out of luck). Seeing the online manual now, tape is for overdub recording. Makes sense. Must remember.

    Btw, when tapping Help in the plugin nothing happened.

    If you want to cut down on the number of UI icons, things like the headphone might as well be hidden in the settings menu (if its sole purpose is to say whether the vertical keyboard outputs midi when tapping).

  • edited February 2022

    The qwerty keyboard was not appearing to change LK track name or save session as.
    Updated iPad to 15.3 and it now works

  • edited February 2022

    @sinosoidal What's your opinion on live jamming with clips and quantisation?
    When global launch quantisation is 1/2 or one bar, launching the next triggered clip at 1.1 certainly makes sense.
    But with shorter LQ amounts or launch quantisation=off, wouldn't it make more sense if there was a clip setting that allows us to
    A: Launch the next clip at the beginning like now (good for one-shot phrases)
    B: Launch the next clip at the current playhead inside the clip. If the new launched clip is shorter than the previous one then just wrap the bars around (developers would say "mod 4") so the beat always stays in sync with the other tracks.

  • @rs2000 said:
    @sinosoidal What's your opinion on live jamming with clips and quantisation?
    When global launch quantisation is 1/2 or one bar, launching the next triggered clip at 1.1 certainly makes sense.
    But with shorter LQ amounts or launch quantisation=off, wouldn't it make more sense if there was a clip setting that allows us to
    A: Launch the next clip at the beginning like now (good for one-shot phrases)
    B: Launch the next clip at the current playhead inside the clip. If the new launched clip is shorter than the previous one then just wrap the bars around (developers would say "mod 4") so the beat always stays in sync with the other tracks.

    I'm definitely not the best person to discuss live performance usage at the time being! :blush:

    Maybe this is a good question for this community in general.

  • Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

  • @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

  • edited February 2022

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

  • @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

    Today while working on some bug fixes based on crash data we have been able to perform signifcant performance optimizations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submited for beta review. There is hope! :blush:

  • @sinosoidal said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

  • @sinosoidal said:

    @sinosoidal said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

    Thanks, so there is hope!!! One of my current live setup use several apps as you can see on my screenshot and LK has such good capabilities to record multiple instruments, so really I don’t want to try something else it’s perfect. I will let you know :)

  • @sinosoidal said:

    @sinosoidal said:

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

    You guys rock. Level of support and improvement on this application has just been amazing.

  • @cian said:

    @sinosoidal said:

    @sinosoidal said:

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

    You guys rock. Level of support and improvement on this application has just been amazing.

    Thanks for your kind words! :blush:

  • @Janosax said:

    @sinosoidal said:

    @sinosoidal said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

    Thanks, so there is hope!!! One of my current live setup use several apps as you can see on my screenshot and LK has such good capabilities to record multiple instruments, so really I don’t want to try something else it’s perfect. I will let you know :)

    Just wondering if you had any chance of using LK lately?

  • @sinosoidal said:

    @Janosax said:

    @sinosoidal said:

    @sinosoidal said:

    @Janosax said:

    @sinosoidal said:

    @Janosax said:
    Still have some crashes with my iPad M1, one today one yesterday, on total time 8 hours. Not a lot of crashes but unfortunately making LK not usable on stage for now :'(

    Can you please tell me what kind of crash is this?

    • Is it a grey screen when opening the AUv3?
    • Is it a host node getting crashed?

    What about the context in which it happened?

    • Were you doing things?
    • Was it just playing?

    Can you send us the AUM or Loopy Pro session?

    This bug is like a needle in a haystack, but the needle must be somewhere... :disappointed:

    The AUM host node itself is not crashed.

    AUV3 is on foreground and this is quite often while recording in LK, suddenly instance is frozen.

    LK still playing recorded notes but not recording anything new, nor routing midi monitoring to instruments.

    AUV3 is not greyed but there are no more graphics movements, everything in instance is frozen.

    Today just after that crash, after closing AUM and opening project again, LK node wasn’t loading. After second AUM closing/opening LK was loading properly in that project.

    That project is a template with tons of apps inside. I will send it to you. I have others templates even more complex and still with all AUV3 stable. I had LK crashes with simple projects too. iPad M1 is rock solid.

    Too bad as LK is best AUV3 for live midi looping on iPad.

    Today while working on some bug fixes based on crash data we have been able to perform significant performance optimisations, which seem to prevent one kind of freeze when a lot of midi input was being handled by the matrix.

    A new build has already been submitted for beta review. There is hope! :blush:

    The new beta is now available. Please let me know if you find in this new build anything better stability wise.

    Thanks, so there is hope!!! One of my current live setup use several apps as you can see on my screenshot and LK has such good capabilities to record multiple instruments, so really I don’t want to try something else it’s perfect. I will let you know :)

    Just wondering if you had any chance of using LK lately?

    Not yet this weekend sorry, but I will use it everyday this week, I will let you know today in the evening how stable it was :)

  • Hi @sinosoidal, I've been using LK on my iPad Pro in Live mode to control Live 11 on my M1 MacBook Pro. Generally, I far prefer LK to TouchablePro for reliability, note editing and clip control, but when it comes to device control I'm having some problems...
    1. Main is issue is that moving any parameter results in very jittery movement. See video
    2. In the user guide it shows how you can see and control devices in the drum rack chain, but in Live 11 it seems you get 16 macros and no way to access the chains
    3. Renaming a rack in Live shows up instantly in LK but renaming a macro control (or adding parameters to 3rd party plugins using configure) shows up eventually but not sure how to make it happen. The only reliable way is to toggle the script on/off

    https://photos.app.goo.gl/QzxBmxHrh4oTgo4W8

    I've double checked my midi settings in Live and have the latest ubridge running.

  • @soundtemple said:
    Hi @sinosoidal, I've been using LK on my iPad Pro in Live mode to control Live 11 on my M1 MacBook Pro. Generally, I far prefer LK to TouchablePro for reliability, note editing and clip control, but when it comes to device control I'm having some problems...
    1. Main is issue is that moving any parameter results in very jittery movement. See video

    This shouldn't be happening. We will see if we can replicate. Thanks for sending the video.

    1. In the user guide it shows how you can see and control devices in the drum rack chain, but in Live 11 it seems you get 16 macros and no way to access the chains

    You need to enable 'Include chain' option under 'Song Model' setting. It will be much slower to load because there will be a lot of information, specially if you have a large session.

    1. Renaming a rack in Live shows up instantly in LK but renaming a macro control (or adding parameters to 3rd party plugins using configure) shows up eventually but not sure how to make it happen. The only reliable way is to toggle the script on/off

    Maybe there isn't a specific property listener to report such changes and they will only be reported on the next full report for that device.x

    https://photos.app.goo.gl/QzxBmxHrh4oTgo4W8

    I've double checked my midi settings in Live and have the latest ubridge running.

Sign In or Register to comment.