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.

Strange Stepped Dial behaviour

OlaRosOlaRos
in Loopy Pro

For every NEW inserted Stepped Dial, I get a strange response for the FIRST press of the Stepped Dial (see the picture for a simple setup):

The FIRST press will NOT move the Stepped Dial from position ONE to the next (second) step. BUT if I move back to the first position (after the first press), the Stepped Dial move to the next (second) position.

Is this a known bug? 👀

Comments

  • espiegel123espiegel123

    @OlaRos said:
    For every NEW inserted Stepped Dial, I get a strange response for the FIRST press of the Stepped Dial (see the picture for a simple setup):

    The FIRST press will NOT move the Stepped Dial from position ONE to the next (second) step. BUT if I move back to the first position (after the first press), the Stepped Dial move to the next (second) position.

    Is this a known bug? 👀

    What do you mean by 'press'? Is this the action for the press gesture of the widget?

  • wimwim
    edited August 1

    I tested in the latest Beta version and it's working as it should. I then reverted to the App Store version and it behaves as you describe. So, I'd say yes, this is probably a bug that will go away with the next update.

    nvm. I was mistaken. The current beta also displays this behavior. I'll report this over on Slack.

  • wimwim
    edited August 1

    @wim said:
    I tested in the latest Beta version and it's working as it should. I then reverted to the App Store version and it behaves as you describe. So, I'd say yes, this is probably a bug that will go away with the next update.

    nvm. I was mistaken. The current beta also displays this behavior. I'll report this over on Slack.

    @espiegel123 beat me to it, of course. 😂

  • espiegel123espiegel123

    It looks like the issue is only the very first tap after the dial is created.

  • OlaRosOlaRos

    @espiegel123 said:

    What do you mean by 'press'? Is this the action for the press gesture of the widget?

    Yes - it’s the action for the press gesture of the widget.

  • OlaRosOlaRos

    @espiegel123 said:
    It looks like the issue is only the very first tap after the dial is created.

    It is. And if you, for instance, put a “start-record” in the first step, the Stepped Dial will trigger record. But if you tap the Stepper Dial from the first position next time, the recording will NOT start.

    So this MUST be a bug… 👀

  • espiegel123espiegel123

    @OlaRos said:

    @espiegel123 said:
    It looks like the issue is only the very first tap after the dial is created.

    It is. And if you, for instance, put a “start-record” in the first step, the Stepped Dial will trigger record. But if you tap the Stepper Dial from the first position next time, the recording will NOT start.

    So this MUST be a bug… 👀

    Can you clarify? Are you saying that you are encountering an issue at some other time than the very first tap after you add the press action?

Sign In or Register to comment.