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.

Gadget accepting midi ccs on all channels

Don't get too excited - it's a bug, I think, but certain apps (like TC Data and also StepPolyArp) do this 'thing' where they fire:

  • CC #1 0

  • CC #7 127

  • CC # 10 64

  • CC #11 127

  • CC #64 0

when a new patch is loaded (or a new pattern in the case of SPA).

I've had Gadget pick up on this on every single Gadget track and it ends up turning every instance of Abu, Bilboa and London's master sound level to 0 (that's cc1) and the filter cutoff to 0 in Chiang Mai and other weird stuff etc... (Miami gets effected).

Anyone else experienced this?

It's pretty annoying because you have to go back and re-set all the parameters in those Gadget's effected...

But I'm also curious as to how those midi messages are getting through to all Gadget instances... I wonder if it's a sneaky loop hole that could be exploited somehow?

Comments

  • Too deep for me man, but you're amazing at this midi stuff. I almost wanna get TC11 cause of you. But, saving for Auria pro. :-)

    Keep the good work man!

  • Because Gadget does not allow you to designate a channel for it to listen to, my guess is that it probably automatically responds to any CC messages it receives. The CCs you mentioned are often used for common across devices, such as volume and panning. See the chart here: http://nickfever.com/music/midi-cc-list

    Begin rant***
    If Korg maybe gave a damn about proper midi implementation in anything they did, this wouldn't be an issue, but Korg seems to think that tossing any old midi something-or-other into a product is sufficient. It's a piss-poor approach to understanding connectivity, and it's the reason why the only things I own from them are a couple apps I rarely use and a KP3...which they've never bothered to fix the midi timing for. I doubt that anything midi related in Gadget will get better than it is now, which is a shame because it could be the best thing ever as a multitimbral module.
    End rant***

  • ^^^ what he said

  • ^^^ a slightly less ranty version of what he said :)

    I still love Korg (they're streets ahead IMO) but I wish they'd open up on Midi a bit more!

    Its a strange thing i'm describing in my OP... I know that the gadget you have enabled for midi listens on all channels... But what i've found is that occassionally, ALL gagdet's seem to pick up those cc's being reset. I think it's probably some kind of weird bug that's crept it. It's not always repeatable either...

    It's a common "reset" thing to send reset those common midi cc values I believe...

    Anyway - doesn't really matter. As you were :).

    @Musikman4Christ - thanks man! You're too kind. I'm gonna listen to the track you posted recently - and will report back. TC-11 is fabulous for certain things. And playing it is out of this world. But Auria Pro is probably an essential buy.

Sign In or Register to comment.