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

Comments

  • sinosoidalsinosoidal

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

  • JumpercollinsJumpercollins

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

  • auxmuxauxmux

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

  • sinosoidalsinosoidal

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

  • branisbranis

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

  • sinosoidalsinosoidal

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

  • auxmuxauxmux

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

  • JumpercollinsJumpercollins

    @sinosoidal said:

    @Jumpercollins said:
    @sinosoidal in the new beta with the controller if I set it up to control the volume of my first track ch1 cc3 as shown hit midi learn in AUM nothing happens when I press learn then touch the volume control inside LK Controller?

    Is there anyway we can use the controller to learn and control on different channels inside AUM like midi mixer does from 4 Pockets. Hope so as LK could be a all in one controller for AUM.

    It’s great you can match the colours now inside the controller to AUM new colour nodes.

    It seems you are not selecting a output device in status bar. The midi is not being sent at all.

    @sinosoidal Cheers took a while but finally got it working.

  • sinosoidalsinosoidal

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

  • JumpercollinsJumpercollins
    edited March 2021

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    @sinusoid That looks a lot cleaner and stops you losing screen estate when trying to map. I like it👍

  • gregsmithgregsmith

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    @sinusoid That looks a lot cleaner and stops you losing screen estate when trying to map. I like it👍

    Yeah looks better! I know you’re adding the ability to colour each control, but it’d be great to have a global option to set the accent colour of the app - I’m not a huge fan of yellow 😂

  • auxmuxauxmux

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    Awesome! Dig it!

  • branisbranis

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    Looks great - very clean and informative

  • WhiteWhite

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    It looks very good.

  • CarnbotCarnbot

    That looks much better, currently it's not very intuitive :)

  • sinosoidalsinosoidal

    @Carnbot said:
    @White said:

    @sinosoidal said:

    @auxmux said:

    @sinosoidal said:

    @branis said:

    @sinosoidal said:

    @auxmux said:

    @Jumpercollins said:

    @sinosoidal said:

    @auxmux said:

    @auxmux said:

    @Jumpercollins said:
    @auxmux Did you try on the Controller page drag up. under Functions hold down Properties it turns white then press the control you want edit to bring up the settings menu.

    Yup, tried and nothing is coming up in AU or standalone.

    Actually, didn't realize that long press was necessary. Somewhat confusing. I figured since last touch on top of the screen shows which control was last selected, it would toggle Properties right away.

    I want to remove the bottom bar from the midi controller page. One idea is to move the banks and the assign function to the status bar.

    @sinosoidal That would make for better work flow and more sense.

    Same, agree, that would be better. Also, a vote of one touch configuration. 🙏

    My biggest doubt is how to trigger the assign dialog for a certain parameter:

    • long press - but it will not work on sliders and knobs because it acts immediatelly.
    • status bar edit checkable button - when enabled it pops the assign dialog for any parameter

    I would love to hear your and others thoughts about it! :blush:

    The second option sounds good to me, with some visual indication that you are in edit mode, like outlining the Controller page or turning all controllers to red, or something similar.

    Cool, next beta will have this modifications so you can all try them out! :blush:

    That works for me too. Thanks @sinosoidal and @branis

    Preview:

    It looks very good.

    Thank you all for your feedback. We should publish a new beta build soon. I think we are ready to close 1.10.2 changes.

  • AlmostAnonymousAlmostAnonymous
    edited March 2021

    Wow. Did we really go a whole day with no one posting in this mega? Impressive.

    Not to keep harping on the LPP color not matching thing (which this thread is full of), but I have a suggestion that might be a compromise between making users happy and time spent coding it.

    Have you thought of implementing a toggle switch is settings to offer a simplified color palette with a smaller number of colors to choose from? Call it something like “Use Novation Color Palatte” or something?

    My think here is this. Of the 32 default colors in the clip properties pane, there’s only 10 colors that are truly different enough from each other.

    In this picture, I set the top 4 scenes to exactly how the color palate is laid out. All the reds on track 1, all the yellows on track 2, etc top to bottom:

    I can identify only 10 distinct colors from the pallatte that the launchpad display differently on its own:

    Assigning them to the bottom 4 scenes according to the numbering above (9 and 10 are extra), you can see there is enough unique colors to use without even implementing any of novations programmers mode for colors:

    So by limiting LK to these 10 colors via a toggle, you could make colors match without implementing any new code. You would use the existing color codes and just “paint” the colors correctly in LK. Have LK match what the surface does on its own without having to deal with sending code to the novation.

    I don’t know if in the world of programming if this is “cheating” by not using novations programmers mode, but in theory you can get the colors to match on a limited basis with very minimal changes to LK. The color palate from the novation programmers reference is the same for the ProMk3, X, and MiniMk3 (and also for the mk2’s and originals I believe).

    Do we really need 128 colors to choose from? 10 is probably enough to make people happy that the colors match and be able to color code drums from bass from whatever.

    I dunno if the akai apc’s also have color mismatching, but in theory you could do the same.

    Anyway, was just a thought I had, and sorry for the ridiculously long boat about it, but thank you for continuing to make LK awesome for us. It’s been much appreciated here.

    You guys need a vacation at the rate you were squashing bug fixes the past couple weeks!

    (Edit: I’m sure you can tell from my crappy photos I don’t have a nice lidar camera on my iPad.....)
    (Edit 2: I don’t know if everyone else’s launchpad displays the same colors as mine for the default colors, but I assume they do. If not, you can disregard all of the above.)

  • AlmostAnonymousAlmostAnonymous

    I also have this weird issue where my launchpad doesn’t display which clip is playing, it’s just slightly dimmer, and track 8 and on won’t turn red when armed to record, but I’ll save that for another day......

  • sinosoidalsinosoidal

    @AlmostAnonymous said:
    Wow. Did we really go a whole day with no one posting in this mega? Impressive.

    Not to keep harping on the LPP color not matching thing (which this thread is full of), but I have a suggestion that might be a compromise between making users happy and time spent coding it.

    Have you thought of implementing a toggle switch is settings to offer a simplified color palette with a smaller number of colors to choose from? Call it something like “Use Novation Color Palatte” or something?

    My think here is this. Of the 32 default colors in the clip properties pane, there’s only 10 colors that are truly different enough from each other.

    In this picture, I set the top 4 scenes to exactly how the color palate is laid out. All the reds on track 1, all the yellows on track 2, etc top to bottom:

    I can identify only 10 distinct colors from the pallatte that the launchpad display differently on its own:

    Assigning them to the bottom 4 scenes according to the numbering above (9 and 10 are extra), you can see there is enough unique colors to use without even implementing any of novations programmers mode for colors:

    So by limiting LK to these 10 colors via a toggle, you could make colors match without implementing any new code. You would use the existing color codes and just “paint” the colors correctly in LK. Have LK match what the surface does on its own without having to deal with sending code to the novation.

    I don’t know if in the world of programming if this is “cheating” by not using novations programmers mode, but in theory you can get the colors to match on a limited basis with very minimal changes to LK. The color palate from the novation programmers reference is the same for the ProMk3, X, and MiniMk3 (and also for the mk2’s and originals I believe).

    Do we really need 128 colors to choose from? 10 is probably enough to make people happy that the colors match and be able to color code drums from bass from whatever.

    I dunno if the akai apc’s also have color mismatching, but in theory you could do the same.

    Anyway, was just a thought I had, and sorry for the ridiculously long boat about it, but thank you for continuing to make LK awesome for us. It’s been much appreciated here.

    You guys need a vacation at the rate you were squashing bug fixes the past couple weeks!

    (Edit: I’m sure you can tell from my crappy photos I don’t have a nice lidar camera on my iPad.....)
    (Edit 2: I don’t know if everyone else’s launchpad displays the same colors as mine for the default colors, but I assume they do. If not, you can disregard all of the above.)

    Thanks for this detailed post and suggestion. This goes in line with my idea of not spending much time with this and finding a solution very quickly. I can't provide an ETA for this at this point.

    Honestly, I find Novations decison of not providing RGB in other mode than DAW mode really strange. I don't know if there is any technical constraint that I'm not aware, but it sucks.

    Thanks for your feedback in general. :blush:

  • lukesleepwalkerlukesleepwalker
    edited March 2021

    @sinosoidal I have a couple of questions after about a week's worth of playing with LK:

    1. Clip launching with the trigger quant set to "none" mostly does what I'd expect, which is cool. But a couple of observations: (1) there's a bug where the clips will sometimes revert to playing all the way through to the end of the clip before retriggering even when the selected clip shows a trigger quant set at "none". Selecting the note and moving the trigger quant to any other value and then reselecting "none" again always fixes this problem but is quite annoying when one has many clips and just wants to play music! (I can send you a video that shows this bug.) (2) When the retrigger does work as expected, the first note on retrigger doesn't play unless the note off message is received first. So, I play a clip and it plays a note. If the note off is reached, retrigger works as expected (so short notes generally work well as a result). If the note off is not reached the clip does retrigger as expected but the first note doesn't actually play as expected. Is that on purpose?

    2. Is it possible to set the trigger quant for a scene launch? Or does it follow the trigger quant of each clip in that scene? I have found that it sometimes works great to trigger a scene without waiting for the quantization to roll through to the next quanta, but in other cases, I trigger a scene and it counts off as if it's waiting for the next quanta (even when all the clips are set to none).

  • gregsmithgregsmith

    The latest beta is great. The app feels slick - love the new comboboxes.

    Also ‘declare LK as a midi processor’ will save me constantly going into the wrong menu!

  • JumpercollinsJumpercollins

    @gregsmith said:
    The latest beta is great. The app feels slick - love the new comboboxes.

    Also ‘declare LK as a midi processor’ will save me constantly going into the wrong menu!

    @gregsmith Agreed having fun mapping the controller in AUM. Haven’t found the combo boxes yet what are they ?

  • gregsmithgregsmith

    @Jumpercollins said:

    @gregsmith said:
    The latest beta is great. The app feels slick - love the new comboboxes.

    Also ‘declare LK as a midi processor’ will save me constantly going into the wrong menu!

    @gregsmith Agreed having fun mapping the controller in AUM. Haven’t found the combo boxes yet what are they ?

    The combo boxes are the ones when you long press and get add track, add scene etc. At least I think they are!

  • JumpercollinsJumpercollins

    @gregsmith said:

    @Jumpercollins said:

    @gregsmith said:
    The latest beta is great. The app feels slick - love the new comboboxes.

    Also ‘declare LK as a midi processor’ will save me constantly going into the wrong menu!

    @gregsmith Agreed having fun mapping the controller in AUM. Haven’t found the combo boxes yet what are they ?

    The combo boxes are the ones when you long press and get add track, add scene etc. At least I think they are!

    Ok that makes sense yes been using them very useful for workflow. Didn’t know they were called that though.

    LK is near enough the perfect clip launcher now for AUM.

  • sinosoidalsinosoidal

    @Jumpercollins said:

    @gregsmith said:

    @Jumpercollins said:

    @gregsmith said:
    The latest beta is great. The app feels slick - love the new comboboxes.

    Also ‘declare LK as a midi processor’ will save me constantly going into the wrong menu!

    @gregsmith Agreed having fun mapping the controller in AUM. Haven’t found the combo boxes yet what are they ?

    The combo boxes are the ones when you long press and get add track, add scene etc. At least I think they are!

    Ok that makes sense yes been using them very useful for workflow. Didn’t know they were called that though.

    LK is near enough the perfect clip launcher now for AUM.

    ComboBox aka Dropdown menus are those that for example are used to select the midi input/outpu on a track. They were looking pretty bad for a long time! :) Those have been uniformized along the UI.

    The menu @gregsmith was talking is usually refered as context menu. :blush:

    We should continue the housekeeping, revisiting module by module, detail by detail, in order to make the app smoother and prettier. We are keeping the number of new features low in order to give us time to do the maintenance work.

    We still have a long list of little bugs and request that this awesome community posts here and many others that reach us by email, YouTube comments and app reviews.

    If no one reports a several problem with 1.10.2 we should send it for App Store review to be sent to production. :blush:

  • auxmuxauxmux

    @sinosoidal The new beta update is great, esp the controller layout. Thanks! But one quick request, is it possible to have all 4 banks buttons shown in top right, rather than a dropdown? Since that requires two taps, in a performance setting, switching banks as quickly as possible would be super helpful. Plus there is enough room to have 4 switches for the banks in the new layout.

  • branisbranis

    @auxmux said:
    @sinosoidal The new beta update is great, esp the controller layout. Thanks! But one quick request, is it possible to have all 4 banks buttons shown in top right, rather than a dropdown? Since that requires two taps, in a performance setting, switching banks as quickly as possible would be super helpful. Plus there is enough room to have 4 switches for the banks in the new layout.

    I was thinking the same

  • ArtvargArtvarg

    @sinosoidal did you secretly sneak in a fix for the Launchpad timing issues? 🤔 Yesterday I was able to record (quantized) some patters from the LP sequencer and they seemed to be identical.
    Have to do some more testing though.
    I switched from AUM to Drambo btw. Works really well with notes, have to check CCs next.

    One thing I’d wish for is multi-channel recording.

  • sinosoidalsinosoidal

    @branis said:

    @auxmux said:
    @sinosoidal The new beta update is great, esp the controller layout. Thanks! But one quick request, is it possible to have all 4 banks buttons shown in top right, rather than a dropdown? Since that requires two taps, in a performance setting, switching banks as quickly as possible would be super helpful. Plus there is enough room to have 4 switches for the banks in the new layout.

    I was thinking the same

    It can be done. But I'm still a bit unsure. The status bar is usually reserved for things that are indicative, that can be toggled or have multiple options. It has never been used for buttons.

    Let me think about this and more feedback from the community. It will keep it like this for 1.10.2

  • sinosoidalsinosoidal

    @Artvarg said:
    @sinosoidal did you secretly sneak in a fix for the Launchpad timing issues? 🤔 Yesterday I was able to record (quantized) some patters from the LP sequencer and they seemed to be identical.
    Have to do some more testing though.
    I switched from AUM to Drambo btw. Works really well with notes, have to check CCs next.

    No, I didn't. I believe that issue is kind of random. We didn't had the time to look at that yet.

    One thing I’d wish for is multi-channel recording.

    Isn't that possible already by arming several trakcs at once (shift + arm track)?

Sign In or Register to comment.

© Vanilla Keystone Theme 2024