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.

ANALOGyKIT - Virtual Analog Drum Kit / Module for iOS & macOS

Rob_Jackson_MusicRob_Jackson_Music
edited May 27 in General App Discussion

Hi Folks,

iOS version is now available, macOS version will hopefully be approved soon - $4.99 Universal Purchase.

https://youtu.be/RKVpcQ7yPtY

https://apps.apple.com/us/app/analogykit/id6770343050

ANALOGyKIT (“analog-ee kit”) is an AUv3 virtual instrument plugin that can run standalone, or in any AUv3 compatible host such as Logic Pro, GarageBand or AUM. Please note that the standalone version does not include a built-in keyboard - you need to connect a suitable MIDI device to play the synth.

Please also note that ANALOGyKIT is not a drum machine, so does not have a built-in pattern sequencer. It has been designed as a virtual drum kit / drum module controlled via MIDI, using a separate sequencer plugin or piano roll in a DAW.

ANALOGyKIT currently runs on iOS (iPad & iPhone) and macOS (Intel & Silicon) and is available as a Universal Purchase from the Apple App Store.

If you’re planning on using ANALOGyKIT on Mac / desktop, please ensure that your favourite DAW / host supports AUv3 (not just AU). Note there is also a known issue beyond my control relating to Ableton Live, so if you only use Live on desktop, sadly I can't recommend you purchase ANALOGyKIT.

NOTE - ANALOGyKIT uses the same synthesis engine as ANALOGyDR so you can think of ANALOGyKIT as 8 x ANALOGyDR, plus dedicated per-voice effects and a master / mixer section.

Design Overview

ANALOGyKIT is an 8 voice virtual analog drum synthesizer, i.e. it does not use samples. The design is based on the sound engines in early analog drum machines for the late 1970’s and early 80’s. Each voice comprises two tuneable pitched oscillators, two noise sources and a variable mode filter with envelope. All eight voices have their own dedicated tempo-sync delay and reverb with gate effect. The master output section includes an 8 channel stereo mixer and simple one-knob controls for compression, limiting and clipping.

Presets

ANALOGyKIT comes with factory presets for Kits and individual Drums, and user presets can be saved or loaded using the OS file system browser. New Kits can be generated automatically by combining sounds randomly from existing factory Drum and Kit presets.

«1

Comments

  • catherdercatherder
    edited May 27

    This was an instabuy for me. I was looking forward to have a simple drum kit plugin for a long time. And it sounds great! Thanks @Rob_Jackson_Music
    Two improvement suggestions:

    • Maybe it's there, but I have not found it: I think it would be good to have some kind of preview / audition buttons that allow manual triggering of the drums. Specially for drum sound design. It's not always convenient to use the hosts built-in MIDI keyboard etc. for this.
    • I find DSP load fairly high: On my iPad 9 the plugin uses over 30% DSP in AUM - all the time, playing or not. Here is an interesting observation: When I load the plugin it uses 16-17% DSP with the default setting. The same goes when loading "Compu Kit -Dry". However, the moment I load "Compu-Kit Reverb" I get the high DSP usage and it will not return to lower levels - even when I load the default or "Compu Kit Dry" again. So something seems to get stuck at high DSP.
  • Rob_Jackson_MusicRob_Jackson_Music
    edited May 27

    @catherder - many thanks.

    There isn't a trigger function currently, but I can add that to the list of feature requests - usual deal, they all get considered and prioritised.

    And yeah, that CPU load is quite high, even for an A13. Does it come down if you turn off the fx? I'll look at any further optimisation possibilities. Thanks for the heads-up.

    Edit: I'm seeing 5% CPU on an iPad M1 11" (2021) in AUM when playing with the Compu Kit - Dry preset. Goes up to around 8-9% CPU with the FX version.

  • catherdercatherder

    @Rob_Jackson_Music said:
    @catherder - many thanks.

    There isn't a trigger function currently, but I can add that to the list of feature requests - usual deal, they all get considered and prioritised.

    And yeah, that CPU load is quite high, even for an A13. Does it come down if you turn off the fx? I'll look at any further optimisation possibilities. Thanks for the heads-up.

    Edit: I'm seeing 5% CPU on an iPad M1 11" (2021) in AUM when playing with the Compu Kit - Dry preset. Goes up to around 8-9% CPU with the FX version.

    The CPU load is not coming down. Switching effects off or loading the “dry” kit does not result in the expected DSP drop. Only reloading the plugin helps.

  • Rob_Jackson_MusicRob_Jackson_Music
    edited May 27

    @catherder - thanks for the additional info. There is some cpu optimisation around fx, and handling tails gracefully when toggling fx on or off - it sounds like that code needs looking at...

    I've just added a dedicated Trigger / preview button :smile: (also visible in the effects view)

    There will also be a new "sweep" up / down parameter for both tuned oscillators in the next update. PEW! PEW! :smiley:

  • wimwim

    @Rob_Jackson_Music said:
    There will also be a new "sweep" up / down parameter for both tuned oscillators in the next update. PEW! PEW! :smiley:

    Cool. I found myself always wishing for that in ANALYGyDR. Also that I didn't have to load a separate plug for each hit. Win, win. 😎

  • FizzyLizzy27FizzyLizzy27

    Cool. You got my support ✌️

  • egobeatsegobeats

    Awesome price point!

  • SchmotownSchmotown

    I may have missed this, but do the kits follow a standard mapping scheme? General MIDI doesn’t seem like the one.

  • Rob_Jackson_MusicRob_Jackson_Music

    @Schmotown - the kits are mapped by default from note 24 to 36 (white notes only) for Drums 1 to 8. So that's C0 to C1 in Apple octaves.

    Typically, I assign kick to drum 1, snare to 2, hhc / hho to 3 and 4, but it really depends on the types of the drums.

  • SchmotownSchmotown

    @Rob_Jackson_Music said:
    @Schmotown - the kits are mapped by default from note 24 to 36 (white notes only) for Drums 1 to 8. So that's C0 to C1 in Apple octaves.

    Typically, I assign kick to drum 1, snare to 2, hhc / hho to 3 and 4, but it really depends on the types of the drums.

    Thanks, Rob.

  • catherdercatherder
    edited May 27

    @Rob_Jackson_Music said:
    @catherder - thanks for the additional info. There is some cpu optimisation around fx, and handling tails gracefully when toggling fx on or off - it sounds like that code needs looking at...

    I've just added a dedicated Trigger / preview button :smile: (also visible in the effects view)

    There will also be a new "sweep" up / down parameter for both tuned oscillators in the next update. PEW! PEW! :smiley:

    That’s great. Thanks a lot. One more question/idea about saving CPU: You say that ANALOGyKIT is basically 8 x ANALOGyDR plus effects and mixer. What happens when you turn one drum off, does that disable the associated synth/effects chain or is this just a mute? I’m asking because I often don’t use all 8 drums and not having the additional synth engines running might result in further CPU savings. The on/off buttons on the mixer page could act as mutes and the ones on the Drumkit page switch the engines on and off.

  • Rob_Jackson_MusicRob_Jackson_Music
    edited May 27

    @catherder - yes, the mixer toggles just ramp down / up whatever's coming out of that drum voice into the summing bus. You kinda have to do that, because say you mute and unmute a cymbal sound with a long decay. You still need that decay to ring out, whether you're muting or un-muting, otherwise it will be "frozen in time" if you don't do the processing for that voice.

    However something you can do, is look at the state of the envelope for that voice. If it's below "silence", there's probably a lot of processing you can avoid doing. So you get the bonus there of reduced CPU load when the voice is not playing, not just when it's not being used at all. This is a CPU thing I do in pretty much all my stuff.

    It gets more interesting with reverbs and delays... If you're familiar with "trails mode" in effects, you'll get the idea. In "trails mode", if you toggle the effect off, you want to stop sending to the effect, but still receive what's coming out - say a really long reverb tail. While this is deemed a cool feature, it comes at a cost, because you always need the reverb / delay to be doing its thing - basically regurgitating its buffers! :) Or rather, it's challenging to decide if it doesn't need to be doing its thing... :smile:

    I thought I'd come up with a new clever way of handling that in ANALOGyKIT.

    Turns out, it's a very thin line between clever and stupid :smiley: (Spinal Tap)

    So for now, I'm not supporting trails mode at all in the KIT reverbs and delays. I think it's different if it's a dedicated delay you want to switch on and off during a performance - you really need that I think. All my other delays and reverbs do it, in fact.

    I did see some other stuff that had low risk optimisation potential, so I'm in the midst of testing those things too.

    Cheers! -Rob

  • Rob_Jackson_MusicRob_Jackson_Music

    Very quick update on performance...

    With the proposed v1.1 update, I'm now seeing 3% CPU on the dry kit, and 6% on the reverb version when idle - single instance in AUM. This increases by 2-3% depending on how many voices are active. I struggled to get it over 8% on my M1 iPad tapping the keys as fast as I could - very scientific, I know... :smile:

    Sadly, most of this improvement comes at the expense of ditching trails mode.

  • PxlhgPxlhg
    edited May 27

    There's quite the catalogue now from our dear Mr Jackson. There's also the Scaper apps beside these 40. Pretty impressive.

  • egobeatsegobeats
    edited May 27

    Might be my favorite developer, I tell everybody I know (that's into music) about his apps. Poly delay is a one of the coolest AU effects I have and Dinasinth is literally on all my tracks.

    I only lack AnalogyKit and the scaper app.

  • anicktanickt

    @Rob_Jackson_Music Nicely done Rob! 😎✌🏼

  • KaptkraychKaptkraych

    @egobeats said:
    Might be my favorite developer, I tell everybody I know (that's into music) about his apps. Poly delay is a one of the coolest AU effects I have and Dinasinth is literally on all my tracks.

    Far out do you actually know people in the real world that do ios music? Thats encouraging !

    ‘Rob Jackson’ and ‘Insta buy’ are becoming synonymous.., i hear theres a growing cult of personality surrounding RJ? Where do i sign up?

  • GavinskiGavinski

    @Kaptkraych said:

    @egobeats said:
    Might be my favorite developer, I tell everybody I know (that's into music) about his apps. Poly delay is a one of the coolest AU effects I have and Dinasinth is literally on all my tracks.

    Far out do you actually know people in the real world that do ios music? Thats encouraging !

    ‘Rob Jackson’ and ‘Insta buy’ are becoming synonymous.., i hear theres a growing cult of personality surrounding RJ? Where do i sign up?

    It’s not even just a question of where to sign up. You have to know which letters of your name to capitalise and which to leave lower case. And then you have to pronounce the damn thing correctly! Many are called, few are chosen…

  • Rob_Jackson_MusicRob_Jackson_Music
    edited May 27

    If cult of personality was at play here, I'd be doomed... :D

    Thanks for the kind words folks. Much appreciated.

  • AnalogMatthewAnalogMatthew

    Video sounds great, nice job! 🥁

  • Rob_Jackson_MusicRob_Jackson_Music
    edited May 28

    Many thanks @AnalogMatthew - much appreciated!

    And just to let you know that v1.1.2 for iOS has just been approved. This update has the manual trigger button, oscillator sweep and some small CPU improvements.

    The macOS version was still waiting for review (after almost a week...), so I've re-submitted a new macOS build for approval this morning with the v1.1.2 updates.

  • egobeatsegobeats
    edited May 28

    *removed.

  • wimwim

    @Rob_Jackson_Music said:
    Many thanks @AnalogMatthew - much appreciated!

    And just to let you know that v1.1.2 for iOS has just been approved. This update has the manual trigger button, oscillator sweep and some small CPU improvements.

    The macOS version was still waiting for review (after almost a week...), so I've re-submitted a new macOS build for approval this morning with the v1.1.2 updates.

    Thanks for the trigger button! It's awkward that it triggers on release rather press tho.

  • wimwim
    edited May 28

    Sweep is so very helpful, thanks!

    I'm tempted to suggest a sweep rate control too, but I don't see how that would work with the UI. Since there are two oscillators, it's not super necessary anyway ... it's just something I'm used to.

  • wimwim

    Here's an idea: When in the kit presets selector is present, perhaps the drum buttons could function as a toggle to remove pads from the Generate function. That way individual hits could be locked in as you go.

  • wimwim
    edited May 28

    Love the reverb gate! That is such a useful thing.

    You nailed it with this plugin @Rob_Jackson_Music. 😎

  • wimwim
    edited May 28

    meh. Sorry for all the spam. I'll shut up now.
    Long press copy/paste for the drum pads would be great too.

  • wimwim
    edited May 28

    I lied.

    It's a little hard to browse in the preset file dialog. I can think of a couple of ideas to help:

    • Reduce the font size? I don't know if that's even possible in the dialog options. **
    • Enable collapsing the side bar when not needed. I think that's a standard option.
    • Hide the long (though helpful) file extension, in favor of filter out, rather than greying out, non applicable files.
    • Increase the percentage of the plugin window width used by the dialog, or just maximize it since there's an X to close button anyway.
    • Also, it would be very helpful to be able to delete presets in that dialog. Rename too if that wouldn't break anything.

    ** [edit] I found the View Options for Compact Icon and List Size. That helps.
    Interestingly, `Show All Finename Extensions is OFF, but the extensions still show, so I guess you're overriding that?

    I gotta say, you nailed preset management with leveraging the file system, IMO. I wish all plugins did that and that this legacy sandboxed garbage that complicates everything could just freaking go away.

  • catherdercatherder

    @Rob_Jackson_Music said:
    Many thanks @AnalogMatthew - much appreciated!

    And just to let you know that v1.1.2 for iOS has just been approved. This update has the manual trigger button, oscillator sweep and some small CPU improvements.

    The macOS version was still waiting for review (after almost a week...), so I've re-submitted a new macOS build for approval this morning with the v1.1.2 updates.

    Thanks a lot. Great update. Thanks for the trigger buttons, and there is now much more control over CPU usage with no hanging.

  • Rob_Jackson_MusicRob_Jackson_Music

    Sorry for delayed reply, and thanks @catherder and @wim.

    Trigger on release is standard button behaviour I'm afraid.

    Also, I'm using the JUCE wrapper around the OS / native "file dialog", and there are limitations as to how much control you have due to cross-platform / lowest common denominator stuff I'm afraid. I've made a note to check if it can be refined further though.

    Also, just a heads-up, I managed to introduce a regression bug in v1.1.2 that resets the MIDI note trigger and choke assignments back to their default values when you load a file or factory drum preset, which is kinda annoying. There's a fix in for review today (v1.1.3) for that - apologies.

Sign In or Register to comment.