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.

DRAMBO 2.0 is LIVE!!!

15557596061

Comments

  • tbh I could just manually copy settings via screen if hassle sending presets across ipads and if Drambo dosent airdrop a track save containing the au fx and state save but Drambo maybe can. As you can download patches and airdrop entire projects.

  • Air drop cool now.

    Cpu conserver from 2049.

  • edited May 2023

    tbh. Its mainly for aum session stems plus aum midi controller stems where Drambo dosent map more than 16 parameters.

    So Thermos. Shooms etc.

    3rd ipad is for these original audio stems and sample sequencing.

    2nd ipad is for midi editing synths.

    1st ipad is for drums and sidechaining 2nd ipad ( plus obviously the background aum as needed )

    I probably have to polish a song, across 2 ipads as sidechaining across ipads complicates moving to another host but does obviously complicate mixing in general ( and obviously if you can complete via Drambo anyway )

    because of multi ipads and relying on original host sends.

  • Is there a bug in Drambo.

    I remapped the Drum ipad template because when i input a step via screen it would register as a chord.

    But noticed its on another ipad now.

  • I have noticed that Koala sampler behaves a bit weird in Drambo.

    I happens both on my iphone 12pro Max and Ipad pro 18 but in different ways. ( both ios 16.5)

    I am having this issue when i trigger samples in Koala from Drambo’s sequencer.

    Ipad behaviour: For the right notes to trigger I need to open Koala Sampler in an AU window.

    Iphone behaviour: The samples will be triggered correctly untill I open Koala sampler in an AU window. Then no samples will be triggered.

    Can anyone confirm this and if so, is it a Koala or a Drambo issue?

  • Hey folks, is there any way to know exactly what value I'm setting in a parameter in the automation? Or any way to monitor these values?

  • @Lorichs said:
    I have noticed that Koala sampler behaves a bit weird in Drambo.

    I happens both on my iphone 12pro Max and Ipad pro 18 but in different ways. ( both ios 16.5)

    I am having this issue when i trigger samples in Koala from Drambo’s sequencer.

    Ipad behaviour: For the right notes to trigger I need to open Koala Sampler in an AU window.

    Iphone behaviour: The samples will be triggered correctly untill I open Koala sampler in an AU window. Then no samples will be triggered.

    Can anyone confirm this and if so, is it a Koala or a Drambo issue?

    I checked and I'm seeing the behavior on my iPhone 13 that you have on your iPad: I need to open Koala's AU window before samples are triggered. After that it all works fine.

  • @Lorichs said:
    I have noticed that Koala sampler behaves a bit weird in Drambo.

    I happens both on my iphone 12pro Max and Ipad pro 18 but in different ways. ( both ios 16.5)

    I am having this issue when i trigger samples in Koala from Drambo’s sequencer.

    Ipad behaviour: For the right notes to trigger I need to open Koala Sampler in an AU window.

    Iphone behaviour: The samples will be triggered correctly untill I open Koala sampler in an AU window. Then no samples will be triggered.

    Can anyone confirm this and if so, is it a Koala or a Drambo issue?

    I get the same behaviour in NS2 on iPhone that you are getting on iPad in Drambo 🤷‍♂️

  • @attakk said:

    @Lorichs said:
    I have noticed that Koala sampler behaves a bit weird in Drambo.

    I happens both on my iphone 12pro Max and Ipad pro 18 but in different ways. ( both ios 16.5)

    I am having this issue when i trigger samples in Koala from Drambo’s sequencer.

    Ipad behaviour: For the right notes to trigger I need to open Koala Sampler in an AU window.

    Iphone behaviour: The samples will be triggered correctly untill I open Koala sampler in an AU window. Then no samples will be triggered.

    Can anyone confirm this and if so, is it a Koala or a Drambo issue?

    I get the same behaviour in NS2 on iPhone that you are getting on iPad in Drambo 🤷‍♂️

    Is the app opening in different portrait / landscape orientation in the two scenarios? I seem to remember pads being reordered depending on the layout. Are you maybe triggering the wrong pads because of this?

  • Uhh @wim. You are as sharp as a knife 😊. I have just tested on my iphone and i does make a difference. The samples are played from the sequencer when i’m in landscape mode but not in portrait mode. Thanks for your help.
    I’ll write Marek about this. 👍🏼

  • @wim said:

    @attakk said:

    @Lorichs said:
    I have noticed that Koala sampler behaves a bit weird in Drambo.

    I happens both on my iphone 12pro Max and Ipad pro 18 but in different ways. ( both ios 16.5)

    I am having this issue when i trigger samples in Koala from Drambo’s sequencer.

    Ipad behaviour: For the right notes to trigger I need to open Koala Sampler in an AU window.

    Iphone behaviour: The samples will be triggered correctly untill I open Koala sampler in an AU window. Then no samples will be triggered.

    Can anyone confirm this and if so, is it a Koala or a Drambo issue?

    I get the same behaviour in NS2 on iPhone that you are getting on iPad in Drambo 🤷‍♂️

    Is the app opening in different portrait / landscape orientation in the two scenarios? I seem to remember pads being reordered depending on the layout. Are you maybe triggering the wrong pads because of this?

    NS2 only displays in landscape mode - as Lorichs says though, open the Koala window and everything is good again.

    It’s not a dealbreaker for me as I tend to bounce Koala sessions out to audio asap and unload, so it rarely irritates me due to my normal workflow - I’m just noting it here to back up Lorich’s experience as it is something I have also observed.

  • edited June 2023

    Thanks for backing me up @attakk
    No it is not a dealbreaker at all 😊.
    Personally i am experimenting using drambo as a backup for live performing with accoustic instruments and in that context this issue is “one more thing to remember”.

  • @Lorichs said:
    Uhh @wim. You are as sharp as a knife 😊. I have just tested on my iphone and i does make a difference. The samples are played from the sequencer when i’m in landscape mode but not in portrait mode. Thanks for your help.
    I’ll write Marek about this. 👍🏼

    If I understood the issue correctly, it's just a matter of understanding how the pads get rearranged, or something like that. Each note plays the same pad. So, say you load a kick on a pad and C2 triggers it, that pad will end up in a different position, but C2 will still trigger it.

    Check the posts around here. They may shed some light.

  • @monomatik said:
    Hey folks, is there any way to know exactly what value I'm setting in a parameter in the automation? Or any way to monitor these values?

    I dont think so. You can kind of figure out from the horizontal grid, which is adjustable, but thats it. Someone correct me if I'm wrong.

  • @wim said:

    If I understood the issue correctly, it's just a matter of understanding how the pads get rearranged, or something like that. Each note plays the same pad. So, say you load a kick on a pad and C2 triggers it, that pad will end up in a different position, but C2 will still trigger it.

    Check the posts around here. They may shed some light.

    Yep that makes sense. But in this case the notes are triggered by the sequencer in Drambo. So i guess that the notes triggered should be the same.

  • @rvr said:

    @monomatik said:
    Hey folks, is there any way to know exactly what value I'm setting in a parameter in the automation? Or any way to monitor these values?

    I dont think so. You can kind of figure out from the horizontal grid, which is adjustable, but thats it. Someone correct me if I'm wrong.

    You could use the Oscilloscope module for CV signals and Midi Monitor for CC messages and midi notes.
    It does depend upon what you’re needing to know the value of.
    What are you automating?

  • @Lorichs said:

    @wim said:

    If I understood the issue correctly, it's just a matter of understanding how the pads get rearranged, or something like that. Each note plays the same pad. So, say you load a kick on a pad and C2 triggers it, that pad will end up in a different position, but C2 will still trigger it.

    Check the posts around here. They may shed some light.

    Yep that makes sense. But in this case the notes are triggered by the sequencer in Drambo. So i guess that the notes triggered should be the same.

    As dRambo is doing the sequencing then the notes being trigger should be the same.

  • @rvr said:
    You can kind of figure out from the horizontal grid, which is adjustable, but thats it.

    Thanks for the suggestion. I didn't think of it, but indeed I can make the Y grid of automation appropriately dense and recalculate for myself. If I set myself this grid of, say, 10 or 20 it is easy to divide. Thanks.

    @Gravitas said:
    You could use the Oscilloscope module

    I was thinking earlier about the oscilloscope, but its impossible to connect it to every parameter. My question came about because in the clip I was setting the automation of "mix" in Reverb (plate) from zero to some value. If in the next clip I set (e.g. using parameter lock) a different "mix" value than the final one from the automation in the previous clip, a slight pop is heard. It's not a major problem, but I thought there might be a way around it.

    But now as I was writing this answer an idea came to me - I can take a "knob" module that will control the "mix" parameter, and I can connect the oscilloscope to the "knob" and then I will see what the value is. I hope I described it clearly. Thanks for the idea with oscilloscope.

  • @monomatik said:

    @rvr said:
    You can kind of figure out from the horizontal grid, which is adjustable, but thats it.

    Thanks for the suggestion. I didn't think of it, but indeed I can make the Y grid of automation appropriately dense and recalculate for myself. If I set myself this grid of, say, 10 or 20 it is easy to divide. Thanks.

    @Gravitas said:
    You could use the Oscilloscope module

    I was thinking earlier about the oscilloscope, but its impossible to connect it to every parameter. My question came about because in the clip I was setting the automation of "mix" in Reverb (plate) from zero to some value. If in the next clip I set (e.g. using parameter lock) a different "mix" value than the final one from the automation in the previous clip, a slight pop is heard. It's not a major problem, but I thought there might be a way around it.

    But now as I was writing this answer an idea came to me - I can take a "knob" module that will control the "mix" parameter, and I can connect the oscilloscope to the "knob" and then I will see what the value is. I hope I described it clearly. Thanks for the idea with oscilloscope.

    You can long press any input and the Oscilloscope/spectrogram will appear, try that
    and look in the automation window top right hand corner and you should see smoothing.
    Try applying that and possibly the pop will disappear.
    Can you post up a screenshot?

  • @Lorichs said:

    @wim said:

    If I understood the issue correctly, it's just a matter of understanding how the pads get rearranged, or something like that. Each note plays the same pad. So, say you load a kick on a pad and C2 triggers it, that pad will end up in a different position, but C2 will still trigger it.

    Check the posts around here. They may shed some light.

    Yep that makes sense. But in this case the notes are triggered by the sequencer in Drambo. So i guess that the notes triggered should be the same.

    Yes, but if I understood it right, if you loading a sample on a pad, then change the orientation, the sample will move with the pad when it's rearranged so that it'll be triggered by the same note. It's only the pad position that has changed, not the mapping. Or that's how it sounded to me.

    I should just test this myself but don't have time right now. Will try later today.

  • @Gravitas said:
    Can you post up a screenshot?

    I don't know if it's worth explaining it all, because the problem is not that important.

    But all in all, I'll try to describe with screenshots anyway. And it's not about the pop in the automation, it's about the transition between clips.
    clip 1 the "mix" value at the end of the automation:

    clip 2 the "mix" value set via "clip parameter lock":

    Since they have different values during the transition this is what causes the audible pop. Of course, my example is exaggerated, just to show what I mean.

    It is possible to set these values more or less similarly, but I was thinking that maybe there is a way to check what the value is at the end of the automation and then enter this value in the parameter lock in the next clip. Hence my question.
    But as I mentioned it's not a significant problem, thanks for the help.

  • edited June 2023

    @monomatik Here’s an idea that might be worth trying: instead of automating the mix directly, automate a knob which goes into a lowpass filter (~10Hz) which then modulates the mix. This should hopefully smooth out the change of the Dry/Wet mix and remove the popping.

    Something like this:

    (There’s also the Slew Limiter which could be used instead of the filter.)

  • Hey @chrka, thanks a lot. I tried your method now and it actually works! Even when the values are very different the transition is smooth. Great, thanks!

    I think I'm about to try this way in other parts.

  • @monomatik said:
    Hey @chrka, thanks a lot. I tried your method now and it actually works! Even when the values are very different the transition is smooth. Great, thanks!

    I think I'm about to try this way in other parts.

    Excellent work, community!

  • @drez said:
    Excellent work, community!

    Ha, exactly! Thanks folks for being so helpful.

  • I can’t map Koala’s FX sliders to Drambo, although I have done it in the past.

    Usually I load Koala as an AU, tap the “map” button, and wiggle the sliders. The controls then show up in Drambo, ready to be p-locked and automated.

    Today, those knob controls do not appear in Drambo. I can map other AUs, just not Koala. Any ideas? I have restarted all apps.

  • wimwim
    edited June 2023

    @mistercharlie said:
    I can’t map Koala’s FX sliders to Drambo, although I have done it in the past.

    Usually I load Koala as an AU, tap the “map” button, and wiggle the sliders. The controls then show up in Drambo, ready to be p-locked and automated.

    Today, those knob controls do not appear in Drambo. I can map other AUs, just not Koala. Any ideas? I have restarted all apps.

    I never tried it before so I can't say if it worked for me before, but I can confirm that it doesn't work now.
    Learn for for the separate Koala FX app does work.

  • @mistercharlie said:
    I can’t map Koala’s FX sliders to Drambo, although I have done it in the past.

    Usually I load Koala as an AU, tap the “map” button, and wiggle the sliders. The controls then show up in Drambo, ready to be p-locked and automated.

    Today, those knob controls do not appear in Drambo. I can map other AUs, just not Koala. Any ideas? I have restarted all apps.

    Wasn’t Koala updated just a few weeks ago? Maybe new release bugs?

  • @mistercharlie said:
    I can’t map Koala’s FX sliders to Drambo, although I have done it in the past.

    Usually I load Koala as an AU, tap the “map” button, and wiggle the sliders. The controls then show up in Drambo, ready to be p-locked and automated.

    Today, those knob controls do not appear in Drambo. I can map other AUs, just not Koala. Any ideas? I have restarted all apps.

    In the meantime, until if/when it's fixed, you can still map parameters. Just hit Map, then tap the (0) that appears. That'll bring up a list of parameters that you can tap to add knobs for them.

  • @wim said:

    @mistercharlie said:
    I can’t map Koala’s FX sliders to Drambo, although I have done it in the past.

    Usually I load Koala as an AU, tap the “map” button, and wiggle the sliders. The controls then show up in Drambo, ready to be p-locked and automated.

    Today, those knob controls do not appear in Drambo. I can map other AUs, just not Koala. Any ideas? I have restarted all apps.

    In the meantime, until if/when it's fixed, you can still map parameters. Just hit Map, then tap the (0) that appears. That'll bring up a list of parameters that you can tap to add knobs for them.

    That’s a great workaround. 👍

Sign In or Register to comment.