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.

Ridgewalk by Aqeel Aadam Sound (Released)

2

Comments

  • GrandbearGrandbear

    @Kewe_Esse said:

    @sevenape said:
    I think I like this more than SpaceFields. It’s less daunting that’s for sure, and less squishy space worm sounding.

    😂 agree

    I think that the modulation and chorus contribute the most to that sound, if you want to experiment disabling those :)

    Still, I really like the immediacy and direct access to the playhead of this one

  • cougarjonezcougarjonez

    Interested in the bundle, but what are the main differences/use cases between Ridgewalk and Zen Garden?

  • GavinskiGavinski

    .> @cougarjonez said:

    Interested in the bundle, but what are the main differences/use cases between Ridgewalk and Zen Garden?

    Do u mean between Ridgewalk and Weeping Wall?

  • abfabf

    @aqeelaadam said:

    @abf said:
    I bought the desktop version, it sounds beautiful. I haven't gotten the iPad version yet, so apologies for a desktop comment.
    This is a complex app, user error is probable.

    With the desktop version no matter the other settings, I can't change the Buffer size. It's stuck on "synced size two bars".

    Also I've had a crash take down Logic, the music was just playing, no tweaking going on, Pianoteq into Ridgewalk, simple settings- one loop, one layer.

    Edit: oh no it's crashing a lot. I didn't try the demo version, I should have!

    Hey @abf - I'm very sorry about this. I'm plowing my way through a bunch of bugs right now... Logic has proved to be by far the most unfriendly host for me as well, though it's no excuse. If you'd be willing to reach out via email ([email protected]) and provide a bit more info, it would go a very long way in helping me sort out these early issues. Furthermore, if you'd prefer a refund for now and would like to drop back to the demo version until you have more confidence, please let me know as well!

    @aqeelaadam
    No apology needed! I don't want a refund, I want to support your work. But thank you for the offer.
    I wish I could help sort it out, but I don't have any time off of work (and I am not technically inclined at all).

    I am usng Logic Pro 10.7.9 on an Macbook Pro Max M1 2021 64 GB memory, macOS monterey 12.7.1, no interface just listening through the headphone output.

  • colorsinspacecolorsinspace

    Still having crashes even with update.

  • skiphuntskiphunt

    I finally started getting some crashes. Tolerable, but not stable. Seems ok as long as I don’t change too many parameters while playing. Confident it’ll be addressed quickly

  • waka_xwaka_x

    releasing such complexe apps without betatesting (community or closed team) is quite silly but many/most are released like this nowadays:(

    amazing and creative take on looping
    just waiting for it to be stable.

  • GavinskiGavinski

    @waka_x said:
    releasing such complexe apps without betatesting (community or closed team) is quite silly but many/most are released like this nowadays:(

    amazing and creative take on looping
    just waiting for it to be stable.

    It was apparently beta tested, but clearly nowhere near thoroughly enough. Within minutes of first getting hands on the release version I had run into multiple crashes and even had 2 crashes while making my walkthrough video (using the latest version). I'm sure Aqeel will try to ensure that any future releases are tested more thoroughly. Lovely app nevertheless, one of the nicest releases of the year for me.

  • sevenapesevenape

    @Grandbear said:

    @Kewe_Esse said:

    @sevenape said:
    I think I like this more than SpaceFields. It’s less daunting that’s for sure, and less squishy space worm sounding.

    😂 agree

    I think that the modulation and chorus contribute the most to that sound, if you want to experiment disabling those :)

    Still, I really like the immediacy and direct access to the playhead of this one

    That’s interesting I will have a play around thank you!

  • anicktanickt

    FWIW - not a single crash…

  • aqeelaadamaqeelaadam

    Hey yall, working through the bugs as quickly as I can! I'm very sorry for the experience so far. I assure you that I tested to the best of my abilities, and had some really badass testers helping out as well, but there's always more things to learn and more issues to bump into. Some things are unfortunately just totally random chance and won't occur until a certain device tries a certain thing... for example, Ridgewalk has been pretty rock solid on my devices for around a month now, which is why I had confidence to release in the first place. I appreciate the info folks are providing in helping me diagnose and solve issues and updates will be coming soon.

    I'm planning to issue iOS updates on a fairly rolling basis as I patch issues and march towards stability; on desktop I'm going to commit to a ~weekly rollout process since the update process on desktop is a much heavier lift than updating through the App Store.

  • reasOnereasOne

    @aqeelaadam said:
    Hey yall, working through the bugs as quickly as I can! I'm very sorry for the experience so far. I assure you that I tested to the best of my abilities, and had some really badass testers helping out as well, but there's always more things to learn and more issues to bump into. Some things are unfortunately just totally random chance and won't occur until a certain device tries a certain thing... for example, Ridgewalk has been pretty rock solid on my devices for around a month now, which is why I had confidence to release in the first place. I appreciate the info folks are providing in helping me diagnose and solve issues and updates will be coming soon.

    I'm planning to issue iOS updates on a fairly rolling basis as I patch issues and march towards stability; on desktop I'm going to commit to a ~weekly rollout process since the update process on desktop is a much heavier lift than updating through the App Store.

    Thanks man! I’m looking forward to trying this one soon! I haven’t pulled the trigger yet simply due to the fact I’ve been trying to master some other apps, but loving the demos thus far

  • waka_xwaka_x

    thank you @aqeelaadam
    crashes here mostly in "classic recording" mode
    that seems very unstable...
    the rest seems fine and when its not crashing it is a sea of amazement:)

  • osc101osc101

    @aqeelaadam said:

    @osc101 said:
    Looks interesting.

    Can the “play head” be controlled via host automation?

    If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

    I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

    Perhaps I am doing something wrong?

  • PxlhgPxlhg
    edited July 15

    @aqeelaadam --Sorry, found answer for what I wanted to ask🙂

  • aqeelaadamaqeelaadam

    Hey all, just wanted to update this thread that I just uploaded a huge update to the App Store. I spent all weekend digging into the nooks and crannies and this version should have vastly improved stability, as well as some other nice updates. The manual and video manual will now be linked from directly in the app as well for convenience.

  • JumpercollinsJumpercollins

    -

  • IcoustikIcoustik

    @aqeelaadam said:
    Hey all, just wanted to update this thread that I just uploaded a huge update to the App Store. I spent all weekend digging into the nooks and crannies and this version should have vastly improved stability, as well as some other nice updates. The manual and video manual will now be linked from directly in the app as well for convenience.

    ❤!

  • ninobeatzninobeatz

    V1.0.2

  • waka_xwaka_x

    thanks @aqeelaadam
    much better now on my iPad 3.

    still- do you support iOS 12.5.7? (iPad air 1)!?
    there is a weird bug - the plug mostly works
    but Traversal "directions" popup doesnt respond. (forward, wander, etc)
    it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
    no problems if you don't...

  • SilentObserverSilentObserver

    @aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

    The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

  • waka_xwaka_x

    @SilentObserver and @aqeelaadam
    smth is broken in latest update...
    the loops fade and get quiet sometimes:(

  • aqeelaadamaqeelaadam
    edited July 16

    @SilentObserver said:
    @aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

    The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

    Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

    In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

    @waka_x said:
    thanks @aqeelaadam
    much better now on my iPad 3.

    still- do you support iOS 12.5.7? (iPad air 1)!?
    there is a weird bug - the plug mostly works
    but Traversal "directions" popup doesnt respond. (forward, wander, etc)
    it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
    no problems if you don't...

    I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore :/ But I would love to support them if I can. If not, I'll update documentation.

  • KrupaKrupa

    Really rather lovely in first use, nice and intuitive with a good amount of depth to the tweaks you can make. One thing that I immediately thought was would it be possible to have a setting that meant you could tap to set the position of the played even when it’s in one of the other modes? Setting a range with two fingers would be doubleplusgood 🤘

    Lovely work @aqeelaadam 🙌

  • aqeelaadamaqeelaadam

    @Krupa said:
    Really rather lovely in first use, nice and intuitive with a good amount of depth to the tweaks you can make. One thing that I immediately thought was would it be possible to have a setting that meant you could tap to set the position of the played even when it’s in one of the other modes? Setting a range with two fingers would be doubleplusgood 🤘

    Lovely work @aqeelaadam 🙌

    Really interesting idea! I'll think on that. I definitely like the idea to tap and override the position as a performative thing.

  • KrupaKrupa

    @aqeelaadam said:

    @Krupa said:
    Really rather lovely in first use, nice and intuitive with a good amount of depth to the tweaks you can make. One thing that I immediately thought was would it be possible to have a setting that meant you could tap to set the position of the played even when it’s in one of the other modes? Setting a range with two fingers would be doubleplusgood 🤘

    Lovely work @aqeelaadam 🙌

    Really interesting idea! I'll think on that. I definitely like the idea to tap and override the position as a performative thing.

    Groovy, I could definitely see this working when I’m playing with jam mates, a nice way to add spice to sessions…

  • aqeelaadamaqeelaadam

    @osc101 said:

    @aqeelaadam said:

    @osc101 said:
    Looks interesting.

    Can the “play head” be controlled via host automation?

    If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

    I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

    Perhaps I am doing something wrong?

    Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

    Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

  • osc101osc101

    @aqeelaadam said:

    @osc101 said:

    @aqeelaadam said:

    @osc101 said:
    Looks interesting.

    Can the “play head” be controlled via host automation?

    If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

    I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

    Perhaps I am doing something wrong?

    Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

    Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

    The update does seem to have lessened the amount of crashes…good work!

    As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

    I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

  • aqeelaadamaqeelaadam
    edited July 16

    @osc101 said:

    @aqeelaadam said:

    @osc101 said:

    @aqeelaadam said:

    @osc101 said:
    Looks interesting.

    Can the “play head” be controlled via host automation?

    If you mean playback being controlled generally - you can play/pause Ridgewalk via a param called "PLAY". If you want to control where the loopers are playing back from, yep, you can use the "External" Movement option and use the param "EXTERNAL MOTION" to control where loopers are positioned.

    I’ve loaded Ridgewalk as an insert fx in Cubasis 3 on an audio track playing a wav file. Ridgewalk seems to work, however, under automation, there are no Ridgewalk parameters shown at all. First time I tried this, Ridgewalk crashed. Second time and thereafter, no parameters shown under automation. Setting “External Movement” made no difference.

    Perhaps I am doing something wrong?

    Hey @osc101, sorry, just sitting down to look into this. Firstly, the latest update should really help with crashes and stability, so I'd make sure you're on that version.

    Secondly, I'm not super familiar with Cubasis so please correct me if I'm wrong, but Ridgewalk seems to be behaving as I'd expect in Cubasis. It seems that no AUv3s have their controls available in the Automation list at first, but if you manually record automation to an AUv3 control, it then shows up in the Automation section for further editing and manipulation. Here's a Jakob Haq video describing that behavior (he's demoing Cubasis 2 but this seems consistent on my Cubasis 3 as well). Can you confirm that same or is it still different for you?

    The update does seem to have lessened the amount of crashes…good work!

    As for my automation question, no luck. I understand how Cubasis works with automating parameters, the problem I’m having is that there is nothing to automate. Once movement is set to external, what parameter should I be tweaking for the automation setting to instantiate? Nothing in the UI controls the “play head” (other than the play, pause, reverse) and there are no other parameters selectable in the host automation channel.

    I think what I’m looking for is more like a source module via AU that allows for a file to be loaded, then granulated with a manually articulated playhead.

    Ahhh, I see what you're saying. I didn't realize you were trying to access the EXTERNAL MOTION parameter specifically - which is "headless" (no direct UI control).

    One thing I had been thinking about doing under the hood was tying the "Tap" position to the "External Motion" parameter, so that the Tap mode position would actually be reloaded when restarting a session. I think that would solve your problem as well, as you could use Tap mode to record some automation and then edit from there? But then it's getting fairly convoluted and I'm not sure where I'd even start with explaining that in the manual haha

    To be honest, IMO this is kind of strange behavior on the part of Cubasis; every other DAW I know of just gives you a list of params and lets you start editing or automating them. But I would like to support this use case of course

  • SilentObserverSilentObserver

    @aqeelaadam said:

    @SilentObserver said:
    @aqeelaadam I'm getting weird performance with Logic iPad. When a midi region, routed through Ridgewalk, finishes, the app stops playing the last loops, even though the track is still playing (and the hold time is quite long).

    The odd thing, is that this behaviour is not consistent - sometimes it will continue playing the last loops until the hold time runs out, other times it won't.

    Oh interesting. I think I know (roughly) what this issue might be - I'll take a look into it today and release a patch if it's simple enough.

    In testing on desktop, Logic seems to be the one DAW that really cares whether or not your "audio effect" is actually producing sound on its own. From Logic's perspective, an audio effect should only produce sound if it's receiving sound, and it'll shut down your plug-in's audio processing if nothing is actually being input to the plug-in. On desktop, loading Ridgewalk onto a software instrument's track at all seems to do the trick, but maybe Logic for iPad is further optimized and will shut down your plug-in's audio processing if input stops being sent. I think there's a way to declare your plug-in as having an infinite "tail" (e.g. like an infinite frozen reverb or self-oscillating delay).

    @waka_x said:
    thanks @aqeelaadam
    much better now on my iPad 3.

    still- do you support iOS 12.5.7? (iPad air 1)!?
    there is a weird bug - the plug mostly works
    but Traversal "directions" popup doesnt respond. (forward, wander, etc)
    it's dead- non-interactive. Would be cool if you can fix this... I still use that old iPad:)
    no problems if you don't...

    I'll try to investigate this - I think I have a similar device laying around. It's possible that the software framework that I'm using doesn't support such older devices anymore :/ But I would love to support them if I can. If not, I'll update documentation.

    Thanks @aqeelaadam - I guess it could be due to Logic shutting the processing. I can restart the internal play engine within the app to keep the remaining loops going, once Logic stops it, but I'd prefer to keep that processing running if possible. If you know that work-around for Logic, I'll give that a go! Strange that it's inconsistent though...

Sign In or Register to comment.