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.

ID700 IS HERE

12345679»

Comments

  • crash fix is submitted to the app store, should be out today / tomorrow.

  • @modosc said:
    crash fix is submitted to the app store, should be out today / tomorrow.

    🙏🏻

  • @modosc said:
    crash fix is submitted to the app store, should be out today / tomorrow.

    Cool.

  • edited June 7

    I suppose I should @modosc this, although I’m also curious how others are faring with the UI on smaller iPads:

    I am liking this synth a whole lot. Imagine that in capital letters for the rest of what I have to say, because I mean it to be constructive criticism and, hopefully, productive of suggestions for making the UI more usable, especially on a regular (9.7”) iPad—the only screen size I have other than my iPhone 6s.

    Overall, it would really help to have a higher-contrast color theme. I prefer the light on dark UI, but either a true black background or a brighter value for the light gray foreground would help my aging eyes tremendously. And maybe there are places—I am thinking of the upper panel routing display in particular—where symbols would be more effective then text labels? Because the font has to be small to make all those labels fit; change to symbols where possible, and the font overall could be made larger and/or heavier.

    I am not a UI designer by any means, so I’m hesitant to make very specific suggestions. Just that upper panel is frustrating: having live controls in each of the very tiny modules means that, when I tap on one to see much larger controls in the middle or lower panel, more often than not I change a value I did not want to change. Those controls are so tiny! If they are there for quick live adjustment, I cannot use them that way with any precision on a 9.7” inch screen.

    My thought is that it would be more useful and legible to show the algorithm routing using smaller symbols, like those in the manual (and on the icon), perhaps with small meters to show the status of crucial parameters rather then live controls. Tapping a module to show the larger, live controls is practical enough for me. Maybe someone has better ideas. And/or experience designing this sort of thing.

    The rest of the UI works well enough for me, although sometimes I would like to hide the keyboard to get bigger versions of everything else.

    One non-UI related request: for custom tuning, the .scl files work as expected. They retune the synth with C as the default root note. But they don’t provide a way to designate other root notes. For equal-temperament scales this is less of a problem (usually), but with just intonation and other non-TET/EDO scales, it limits playing/performing to the key of C. Which I suppose could be the creative limitation I need? But I wish it were either B or Eb instead. :smiley:

    I have seen other apps approach this in different ways. The old-fashioned way is to also support .kbm mapping files. The venerable open source ZynAddSubFX does this, and you could look at the source code and, better, nip their .kbm files. It may be easier, though, to add a feature to designate the root note for any tuning. I know I have seen a couple of synths that do it this way. Wood Synth I think does this? Sunrizer tries, but post iOS 12, doesn’t do it very well (I have emailed beepstreet about it but got no response. In case you were wondering).

    So. That is, um, all? I truly am excited about this synth and want it to do everything as well as possible. I wouldn’t have taken the time to write this otherwise.

    And now that I have done so, I’m going to put on my reading glasses and play with it some more.

  • @erikjms i'm actually in the middle of adding .kbm support now.

  • @modosc said:
    i'm actually in the middle of adding .kbm support now.

    Sweet! I’ll just hang out in equal temperaments for now.

  • Sliders do need fixing Dev.

    A lot of times Algorythm selections dont respond, also.

  • @NoiseFloored said:
    @modosc I was wondering if you could tweak the sliders behavior or add an option for it. I think that the current way they work can be summarized as:
    1. If I tap a slider, the value immediately jumps to that position
    2. If I keep dragging after tapping, within the slider boundaries, I manipulate the value directly
    3. If I keep dragging, but go out of the slider boundaries, I fine-tune the value
    4. If I go back to the slider boundaries, the value jumps to the position I went back to

    One side-effect is that "flicking" a slider to make it go to the highest or lowest value requires one to be very precise to avoid leaving the slider boundaries.

    If possible, I'd like to be able to either fine-tune values by dragging further away (i.e., not the binary coarse/fine-tune mode we have right now), without values jumping if I go back to the boundaries, or not have fine-tuning at all, so I can see the value I'm dragging to by placing my finger a little outside the slider.

    Please let me know if this makes any sense at all.
    Thanks!

    this is exactly what i experience.
    the strange slider behaviour takes away most of the fun from this great synth.
    i think it was working way better in an earlier version!?

    please @modosc would you have a look at the sliders?

  • yup, looking into it.

  • @rototom said:

    @NoiseFloored said:
    @modosc I was wondering if you could tweak the sliders behavior or add an option for it. I think that the current way they work can be summarized as:
    1. If I tap a slider, the value immediately jumps to that position
    2. If I keep dragging after tapping, within the slider boundaries, I manipulate the value directly
    3. If I keep dragging, but go out of the slider boundaries, I fine-tune the value
    4. If I go back to the slider boundaries, the value jumps to the position I went back to

    One side-effect is that "flicking" a slider to make it go to the highest or lowest value requires one to be very precise to avoid leaving the slider boundaries.

    If possible, I'd like to be able to either fine-tune values by dragging further away (i.e., not the binary coarse/fine-tune mode we have right now), without values jumping if I go back to the boundaries, or not have fine-tuning at all, so I can see the value I'm dragging to by placing my finger a little outside the slider.

    Please let me know if this makes any sense at all.
    Thanks!

    this is exactly what i experience.
    the strange slider behaviour takes away most of the fun from this great synth.
    i think it was working way better in an earlier version!?

    please @modosc would you have a look at the sliders?

    +1 ...

    Especially the whole “jump immediately to tap position” thing makes fine adjustments frustratingly difficult, and it’s difficult to know how to manipulate the slider to get the adjustment I’m after given the behaviour described above.

  • @modosc said:
    yup, looking into it.

    Thank you!

  • for right now i'm adding a setting to disable the vertical fine mode. i'm looking into better solutions for the long term.

Sign In or Register to comment.