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.

Klevgrand OneShot CC midi mapping

Hi everyone.

I watched the OneShot ‘Overview’ video on the Klevgrand YouTube channel with Sebastian and Noah demonstrating the app’s functionality with a drum controller.

I am curious if the app has an option to implement CC4 for continuous hi hat position control. Has anyone who is using the app with a controller as shown in the video investigated the extent of hi hat control possible? The ‘Overview’ video only mentions open/closed hi hat implementation by way of choke groups i.e. simple open/closed.

The acoustic samples sound great and given the storage size of the app I am not surprised. I’m just hoping we may finally have an AUV3 app on iOS that offers proper variable hi hat control.
Poly aftertouch would be icing on the cake in midi mapping to implement choked cymbals.

This app definitely shows lots of potential.. fingers crossed.

Comments

  • @GrnEgz_N_Hm said:
    Hi everyone.

    I watched the OneShot ‘Overview’ video on the Klevgrand YouTube channel with Sebastian and Noah demonstrating the app’s functionality with a drum controller.

    I am curious if the app has an option to implement CC4 for continuous hi hat position control. Has anyone who is using the app with a controller as shown in the video investigated the extent of hi hat control possible? The ‘Overview’ video only mentions open/closed hi hat implementation by way of choke groups i.e. simple open/closed.

    The acoustic samples sound great and given the storage size of the app I am not surprised. I’m just hoping we may finally have an AUV3 app on iOS that offers proper variable hi hat control.
    Poly aftertouch would be icing on the cake in midi mapping to implement choked cymbals.

    This app definitely shows lots of potential.. fingers crossed.

    I'm not sure of the definitive answer to this, but I think there's a way that you could make something like that work mapping cc4 to the AUv3 parameters for level on each slot and reversing the direction. So, the level of one hat would be increased by cc4 and the level of the other decreased. That coupled with the flexible settings for percentage of Amount, Time, and Velocity choking might give you what you need.

  • @wim said:

    @GrnEgz_N_Hm said:
    Hi everyone.

    I watched the OneShot ‘Overview’ video on the Klevgrand YouTube channel with Sebastian and Noah demonstrating the app’s functionality with a drum controller.

    I am curious if the app has an option to implement CC4 for continuous hi hat position control. Has anyone who is using the app with a controller as shown in the video investigated the extent of hi hat control possible? The ‘Overview’ video only mentions open/closed hi hat implementation by way of choke groups i.e. simple open/closed.

    The acoustic samples sound great and given the storage size of the app I am not surprised. I’m just hoping we may finally have an AUV3 app on iOS that offers proper variable hi hat control.
    Poly aftertouch would be icing on the cake in midi mapping to implement choked cymbals.

    This app definitely shows lots of potential.. fingers crossed.

    I'm not sure of the definitive answer to this, but I think there's a way that you could make something like that work mapping cc4 to the AUv3 parameters for level on each slot and reversing the direction. So, the level of one hat would be increased by cc4 and the level of the other decreased. That coupled with the flexible settings for percentage of Amount, Time, and Velocity choking might give you what you need.

    Oh that’s clever as heck!

  • @wim said:
    I'm not sure of the definitive answer to this, but I think there's a way that you could make something like that work mapping cc4 to the AUv3 parameters for level on each slot and reversing the direction. So, the level of one hat would be increased by cc4 and the level of the other decreased. That coupled with the flexible settings for percentage of Amount, Time, and Velocity choking might give you what you need.

    Considering AUM for example, that would mean two separate instances of OneShot just for the hi hat the way I am visualizing your suggestion. One for increasing cc4 and the other for decreasing cc4 and all other non-hi hat slots muted per each hi hat specific instance of OneShot. The 3rd AUV3 instance of OneShot could be used for the rest of the drum parts minus hi hats. So a total of three AUV3 instance of OneShot for the full kit. I don't see any other way I could isolate cc4 to just the hihat slot. It doesn't appear I can assign a slot within the app to it's own midi channel to isolate cc4 to the hi hat specific slot(s) that way.

  • @GrnEgz_N_Hm said:

    @wim said:
    I'm not sure of the definitive answer to this, but I think there's a way that you could make something like that work mapping cc4 to the AUv3 parameters for level on each slot and reversing the direction. So, the level of one hat would be increased by cc4 and the level of the other decreased. That coupled with the flexible settings for percentage of Amount, Time, and Velocity choking might give you what you need.

    Considering AUM for example, that would mean two separate instances of OneShot just for the hi hat the way I am visualizing your suggestion. One for increasing cc4 and the other for decreasing cc4 and all other non-hi hat slots muted per each hi hat specific instance of OneShot. The 3rd AUV3 instance of OneShot could be used for the rest of the drum parts minus hi hats. So a total of three AUV3 instance of OneShot for the full kit. I don't see any other way I could isolate cc4 to just the hihat slot. It doesn't appear I can assign a slot within the app to it's own midi channel to isolate cc4 to the hi hat specific slot(s) that way.

    No, it would only require one instance. You wouldn't be filtering channels to OneShot. You would instead route the midi in parallel to AUM's midi control system. There you would make mappings to both AUv3 parameters. In one of them you would reverse the direction.

    Before going further into details, can you tell me if you're familiar with AUM's midi control system and with AUv3 parameters?

  • _ki_ki
    edited November 2024

    Perhaps one also could archive a mixing between several HH types with the following setup:

    Each of the slots could contain several samples for velocity layers.

    The script could activate two of the slots if the control CC is in an inbetween value - the midi note velocity of both these slots could be adapted to the control the mix result of the two hh slots beeing triggered.

    One drawback is that there are no mutes, ie a still playing long open HH, won‘t be cut off by a new arriving closed HH. The slots itself ‚mute‘ their own type of HH, but not between HHs. If one would put all three HH slots into a mute group, only one of them would play and one can‘t mix between them with the CC

  • @wim said:

    Yes, I am familiar with the control system and I get what you are saying now. An interesting solution. Thank you for that.
    After trying it out, this method does work and it’s pretty easy to set up.
    However it definitely sounds like cross fading without the variable textures that are typical as the symbols separate and sizzle/ring out in different ways from touching lightly, slightly or not at all etc.

  • @_ki said:
    Perhaps one also could archive a mixing between several HH types with the following setup:

    Each of the slots could contain several samples for velocity layers.

    The script could activate two of the slots if the control CC is in an inbetween value - the midi note velocity of both these slots could be adapted to the control the mix result of the two hh slots beeing triggered.

    One drawback is that there are no mutes, ie a still playing long open HH, won‘t be cut off by a new arriving closed HH. The slots itself ‚mute‘ their own type of HH, but not between HHs. If one would put all three HH slots into a mute group, only one of them would play and one can‘t mix between them with the CC

    I’ll definitely try this when I get some time and share what results I get. Wow, another very cool concept.

  • @GrnEgz_N_Hm said:

    @wim said:

    Yes, I am familiar with the control system and I get what you are saying now. An interesting solution. Thank you for that.
    After trying it out, this method does work and it’s pretty easy to set up.
    However it definitely sounds like cross fading without the variable textures that are typical as the symbols separate and sizzle/ring out in different ways from touching lightly, slightly or not at all etc.

    I guess what you really need is a well crafted sound font. I know it's possible to do things like that with the SFZ format. You can have certain other sounds mixed in during a cross fade. Writing your own SFZ file is a steep learning curve though.

    Does Drum Perfect Pro do pretty much what you want? It sounds as though it might come closer. It's coming as an AUv3 at some point.

  • @wim said:

    @GrnEgz_N_Hm said:

    @wim said:

    Yes, I am familiar with the control system and I get what you are saying now. An interesting solution. Thank you for that.
    After trying it out, this method does work and it’s pretty easy to set up.
    However it definitely sounds like cross fading without the variable textures that are typical as the symbols separate and sizzle/ring out in different ways from touching lightly, slightly or not at all etc.

    I guess what you really need is a well crafted sound font. I know it's possible to do things like that with the SFZ format. You can have certain other sounds mixed in during a cross fade. Writing your own SFZ file is a steep learning curve though.

    Does Drum Perfect Pro do pretty much what you want? It sounds as though it might come closer. It's coming as an AUv3 at some point.

    I’m not familiar with the SFZ format but I’ll at least look into it.

    The prospect of DPP as a AUV3 sounds really good.

    I tried DPP in the past but couldn’t get the hi hat functionality to work properly following the straight forward directions in the manual. It just triggered in a very strange way that sounded like stuck midi notes or something like that, but everything else was great. Just wished the hi hat issue was resolvable. I’ll definitely look at it again as an AUV3.

Sign In or Register to comment.