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.

Korg Gadget and AUM

Today was the first time that
I've opened up Korg Gadget since it's update.
There seems to be a timing problem.

I've got a session with iSpark, Gadget and Sector.
iSpark and Sector are playing perfectly in time and
Korg Gadget has suddenly developed a timing problem.

iSpark and Sector are syncing to host and
Gadget is being sent midi clock from AUM.

Switching off latency compensation in AUM does improve timing.

When using Ableton Link there is no timing problem the
only thing is Korg Gadget doesn't have Ableton Link start/stop.

Has anyone else had similar issues?

Comments

  • @Gravitas
    I was halfway shocked to hear that so I immediately tried how the latest Gadget syncs. 😉
    Digitakt hardware clock over USB > CCK2 > iPhone: Gadget syncs perfectly, turning BPM up to 300 then down again, not a single clock pulse lost, all good.

    Then in AUM, loaded Groove Rider as an IAA and Gadget as an IAA synced via MIDI clock.
    After switching between apps a bit, Gadget drifted back more and more.

    Then I've replaced Gadget with Electribe Wave, also synced via MIDI clock and that worked without any drift over time.

    I would say the problem is in the Gadget update.

    @davis_korgrd Would you please take this to your developer team? Thanks!

  • edited July 2020

    @rs2000 said:

    I would say the problem is in the Gadget update.

    Thanks for checking.

    I agree.

  • @Gravitas said:

    @rs2000 said:

    I would say the problem is in the Gadget update.

    Thanks for checking.

    I agree.

    Please also report on the KORG site:
    https://support.korguser.net/hc/en-us/requests/new
    Thanks!

  • @rs2000 said:

    @Gravitas said:

    @rs2000 said:

    I would say the problem is in the Gadget update.

    Thanks for checking.

    I agree.

    Please also report on the KORG site:
    https://support.korguser.net/hc/en-us/requests/new
    Thanks!

    Done.

Sign In or Register to comment.