Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

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.