Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Drambo is an AU host now / the new Drambo mega thread

191012141564

Comments

  • edited December 2020

    Perhaps there’s a more minimalistic solution. Perhaps each track device located in main could eventually have an audio recorder built in. Kind of like ‘record track’s session’ or something. That way we wouldn’t need to add extra modules to the interface.

    A bit similar in practice to how you can record the output of each channel in Aum. Just that the utility would be accessible as a red button (or anything) on the actual track device itself. Or have a small “R” button beneath the MASTER, A, B, Pan knobs at the right side of an open track @giku_beepstreet

  • @cuscolima said:
    Is it possible to record the output of Drambo? I mean, I don't want to make a song export but just record what is happening in the master bus (for example if I play on my keyboard)? Probably a stupid question, sorry for this

    I have just been placing 4 pockets multi track on the master right after enso for some live looping. It’s been working well to record live.

  • wimwim
    edited December 2020

    .

  • @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    I can also record individual audio tracks within standalone Drambo by putting an individual instance of 4Pocket's Multitrack Recorder at the end of each track. Multitrack Recorder uses an Audio Pool that collects stems from all the instances.

    But I completely agree... that having the Midi and Audio track recording as a built-in features of standalone Drambo would make it the perfect App. :)

    But for now I'm astounded by what I've been able to do!!! :)

  • @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

  • @wim said:

    @sigma79 said:
    Whats the dealio with the wave packs? Still using aum for now but with drambo synths as tracks + a few auv3 ( in aum )

    See they are linked to serum but is the oscialtor a generator or does it affect serum waves? I mean if you added serum waves, then you are just then adding the wave effect maybe. Or does the oscilator work with the drambo modules, then effect?

    Plus the wave effect. Whats that like on any sound. Maybe to create unusual sounds for drums?


    Hi wim. So Continua for instance. Is it wavetable or just a display that seems similar ( digital )

    This ( continua ) has a lot of oscilator variation for a synth? How and is it what its about? To create my own wavetables on ios say from continua or any app for drambo?

    Or wave tables on internet are fine because modulation in drambo warps the original wave table order, so much it isnt worth creating an order.

    Whats the gist of a good wave . Your own sequence of oscilators ( if drambo goes by how you originally sequenced ) or if sequence order dosent matter or because theres different sound in every oscilator even if its same shape?

    So essentially your own order of oscilators if order matters and or if its also for gaining a diferent or better oscilator and if its easy to achieve through ios from apps, or if just better to find on internet.

    I may as well buy though if its good for synths and decided to not host auv3's.

    Thanks.

  • @aleyas said:

    @auxmux said:
    Thanks @aleyas I appreciate it. I'll try this tomorrow.

    2nd the request from @rs2000, it would awesome if there was no time limit on flexi for master or individual tracks performance recording.

    Putting in another request for the standard Recorder Module to save WAV files also. With record synced by p-lock, its a small and lightweight module to use, especially if you wanna record like 16 stems.

    I was wondering, if one wanted to set up multi out and record it into a computer like a hardware mpc or something, what would be the best way to do this? Realistically it should be able to pipe it digitally over usb c but Mac is limited to one channel natively iirc. Seems illogical to buy another 8 out interface for my iPad and wire it all back in to an 8 input interface for my Mac. I imagine there would be ground loop hum along with a huge mess of wires. Is there a better solution other than exporting and dragging them into DAW? I hate that workflow it’s a real drag for me. Call me old school but I just like to record hardware that way lol

  • If im correct and you can gain an original oscilator from any synths. Then will it be ideal to add auv3 to drambo to gain oscilators for the wave oscilator module? directly.

    Forgive if Im being silly.

  • @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

  • @J_B said:

    @aleyas said:

    @auxmux said:
    Thanks @aleyas I appreciate it. I'll try this tomorrow.

    2nd the request from @rs2000, it would awesome if there was no time limit on flexi for master or individual tracks performance recording.

    Putting in another request for the standard Recorder Module to save WAV files also. With record synced by p-lock, its a small and lightweight module to use, especially if you wanna record like 16 stems.

    I was wondering, if one wanted to set up multi out and record it into a computer like a hardware mpc or something, what would be the best way to do this? Realistically it should be able to pipe it digitally over usb c but Mac is limited to one channel natively iirc. Seems illogical to buy another 8 out interface for my iPad and wire it all back in to an 8 input interface for my Mac. I imagine there would be ground loop hum along with a huge mess of wires. Is there a better solution other than exporting and dragging them into DAW? I hate that workflow it’s a real drag for me. Call me old school but I just like to record hardware that way lol

    Multi out in standalone for use with audio interfaces is planned for the future, I believe.
    It will all come in time.

  • @horsetrainer said:

    @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

    Oh right, I think I know why the Miditools routing trick doesn’t work correctly - it’s because each track on Drambo can only output on a single channel. For instance, you couldn’t set up 3 midi output modules on 3 different channels on the same track - it would still only output on a single channel. So multi channel midi from apps like LK is being bottlenecked to a single output channel on the way out of Drambo. It’s a current limitation.

  • The auv3 apps with midi multi-out work very well with Drambo. Hopefully @sinosoidal can implement it so that we can use our LK projects in whatever host we wish.

  • Beginners question, I want to use Drambo as a sound module In a project, recording the midi in Xequence. How do I turn off Drambos transport button during replay to avoid double hearing of the recorded midi?

  • @horsetrainer said:

    @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

    This is what I need, the ability to record with kb-1, chordbud etc into the step sequencer. Not multi out so this app would meet that need?

    Is it a suite with other midi apps? Are the others apps worthwhile?

    Spent so much recently on apps really didn't want to buy another lol

  • @mikewb said:

    @cuscolima said:
    Is it possible to record the output of Drambo? I mean, I don't want to make a song export but just record what is happening in the master bus (for example if I play on my keyboard)? Probably a stupid question, sorry for this

    I have just been placing 4 pockets multi track on the master right after enso for some live looping. It’s been working well to record live.

    Thanks, that’s a good idea. 4pockets multitrack is however expecting a 48khz input signal and Drambo is 44khz. How can I change this?

  • @auxmux Have tried Multi-track Recorder from 4pockets? That should work I think.

  • @aleyas said:
    Perhaps there’s a more minimalistic solution. Perhaps each track device located in main could eventually have an audio recorder built in. Kind of like ‘record track’s session’ or something. That way we wouldn’t need to add extra modules to the interface.

    A bit similar in practice to how you can record the output of each channel in Aum. Just that the utility would be accessible as a red button (or anything) on the actual track device itself. Or have a small “R” button beneath the MASTER, A, B, Pan knobs at the right side of an open track @giku_beepstreet

    Implementing in the standalone host seems appropriate to me.

    Most of the hosts, incl. AUM, provide a separate record enable latch for each track; these are armed first before pressing the master record button. apeMatrix has a simpler implementation, where the user chooses in global settings between only recording the master vs recording separate outs.

  • @aleyas said:

    @horsetrainer said:

    @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

    Oh right, I think I know why the Miditools routing trick doesn’t work correctly - it’s because each track on Drambo can only output on a single channel. For instance, you couldn’t set up 3 midi output modules on 3 different channels on the same track - it would still only output on a single channel. So multi channel midi from apps like LK is being bottlenecked to a single output channel on the way out of Drambo. It’s a current limitation.

    Unfortunately I don't have LK to work with.

    But I did discover a way to route multiple Midi Channels from a single AUv3 App in Standalone Drambo.
    (I used one instance of the Drambo Midi AU to output on multiple channels, by hosting it in Standalone Drambo)...

    I sent the Midi out into Audiobus, and set up Audiobus to send the Midi back into Drambo... Each midi channel was then received by it's own individual track by setting each track to a different input channel.

    To make it work I had to put a Midi Channel Filter for each midi channel after the multi-channel Audio Unit. I used the MidiTools Midi Filter AU for this purpose.

    It worked like this:
    Multi-Channel-Audio Unit output to the following modules in parallel----->
    ----> Midi Channel Filter set to Ch 1 ----> Midi Output Module set to Ch 1
    ----> Midi Channel Filter set to Ch 2 ----> Midi Output Module set to Ch 2
    ----> Midi Channel Filter set to Ch 3 ----> Midi Output Module set to Ch 3

    Apparently the Drambo Midi Output Modules don't act as filters, so I'm assuming that trying to send multiple midi channels into one or more Output Modules just cause each module to convert everything that gets sent into it into the same Midi Channel (making a big single channel midi mess).

    Adding a Midi filter before each Output Module seems to solve this issue.

    I'm not sure if this was the sort of thing you guys were trying to do, or if it will help get LK working, but it does appear to be a workable solution for separating midi channels so they can each be output on their own channel.

    I was able to record the separated incoming midi onto Drambo's internal sequencer, one channel per track, all in one take, just by starting the Drambo transport in rec mode.

    Let me know if this works with LK. I'm curious.

  • @aleyas said:
    @auxmux Sunvox works for recording stems. Kind of involved, but I don’t think there are any recording length limits.

    -Load Sunvox as an AU processor
    -Open a new project.
    -Add an input, and sampler module.
    -In the sampler options select ‘start recording on project play” and “stop recording on project play”
    -When you press play in drambo, recording in SunVox will begin immediately, and end when you stop the transport. (Optional)

    To save the file
    -once file is recorded, press EDIT in the sampler
    -there’s a hamburger menu which will allow you to save and name the file. Save it wherever.
    -go to Main Menu at top left, select IMPORT/EXPORT
    -select COPY FILE TO SYSTEM PASTEBOARD, select the file you just saved. You will be notified ‘“file has been copied”
    -Open AudioShare (or another app or DAW, dunno) and go down to the green pasteboard icon. Your file can be added now, and will be renamed to ‘pasted audio’.

    Now the Stem is ready to be used anywhere.





    Thanks, it works great! A little bit complex but a good workaround for the moment.

  • @muzka said:

    @horsetrainer said:

    @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

    This is what I need, the ability to record with kb-1, chordbud etc into the step sequencer. Not multi out so this app would meet that need?

    Is it a suite with other midi apps? Are the others apps worthwhile?

    Spent so much recently on apps really didn't want to buy another lol

    Do you already own Drambo? If so do you enjoy the challenge of the modular workflow?

    I've been able to accomplish all the things you've mentioned... BUT it requires using workaround solutions that may not meet the ease of use needs for all users.

    Also, the Drambo internal sequencer has recording length limitations that require some pre-planning. Some users might be bummed to discover this after buying Drambo. But I believe I heard that improvements to Drambo's sequencer are in the works.

    For me Drambo is the most fun iPad App available. But I'm the sort that likes technical challenges, and building musical creations in the modular workflow.

    If your cash strapped, you may want to watch a bunch of Drambo youtube videos, and make sure you like what you see before purchasing. :)

  • @horsetrainer said:

    @muzka said:

    @horsetrainer said:

    @wim said:

    @horsetrainer said:

    @rs2000 said:
    @horsetrainer I should have added that the routing is about the standalone Drambo version which can also host AUv3 plugins and have "its own" audio and MIDI interfaces attached.
    You can host Drambo inside AUM or Audiobus, no question, but you lose all AUv3-related features inside Drambo if you do.

    I'm confused. I'm able to do all this Midi recording from within standalone Drambo.

    The problem comes when you have an app like LK that sends on multiple midi channels. In LK, each track outputs on a separate channel. You would think that sending the midi out and back in, and filtering on the channel at the input like you say, would work, but it doesn’t.

    Single-channel AU Midi plugins aren’t a problem. LK isn’t a problem if you only set up one track. But if you set up more than one track, routing by midi channel doesn’t work right - at least not in my tests.

    Gotcha. :) Now I understand the issue being discussed.

    I've only been working with one Midi channel. I'm Just really happy to be able to record using Atom 1 first, and then be able to transfer Atom's midi into the Drambo sequencer for easy all in one sequencer project storage.

    This update rocks!

    This is what I need, the ability to record with kb-1, chordbud etc into the step sequencer. Not multi out so this app would meet that need?

    Is it a suite with other midi apps? Are the others apps worthwhile?

    Spent so much recently on apps really didn't want to buy another lol

    Do you already own Drambo? If so do you enjoy the challenge of the modular workflow?

    I've been able to accomplish all the things you've mentioned... BUT it requires using workaround solutions that may not meet the ease of use needs for all users.

    Also, the Drambo internal sequencer has recording length limitations that require some pre-planning. Some users might be bummed to discover this after buying Drambo. But I believe I heard that improvements to Drambo's sequencer are in the works.

    For me Drambo is the most fun iPad App available. But I'm the sort that likes technical challenges, and building musical creations in the modular workflow.

    If your cash strapped, you may want to watch a bunch of Drambo youtube videos, and make sure you like what you see before purchasing. :)

    Been using drambo for a while now and happy with its sequencing etc.

    Before I ran it in aum, I'd have all my midi generators on a aum channel and I'd send them to each track in drambo via different midi channels Then I'd hit record in drambo and the midi would record into each drambo track in the step sequencer and I could delete the aum midi tracker and work in drambo

    I'd hoped for a similar workaround, hist my midi apps such as rozetta and chordbud in a midi channel and send to auv3 tracks and record or have midi generator and synth on same track and record

    To get round it I've been adding a flexi sampler at the end and recording as audio, make 3 or 4 variations then open eg pulse on a track and use it as an audio clip launcher.

    Its actually similar to how I work in ableton with bouncing midi patterns down to audio

  • @muzka said:

    Been using drambo for a while now and happy with its sequencing etc.

    Before I ran it in aum, I'd have all my midi generators on a aum channel and I'd send them to each track in drambo via different midi channels Then I'd hit record in drambo and the midi would record into each drambo track in the step sequencer and I could delete the aum midi tracker and work in drambo

    I'd hoped for a similar workaround, hist my midi apps such as rozetta and chordbud in a midi channel and send to auv3 tracks and record or have midi generator and synth on same track and record

    To get round it I've been adding a flexi sampler at the end and recording as audio, make 3 or 4 variations then open eg pulse on a track and use it as an audio clip launcher.

    Its actually similar to how I work in ableton with bouncing midi patterns down to audio

    Here's an example setup. It can be done in multiple ways, but the principles are the same.

    Step one.
    Set up your AU's and connect each to a MIDI OUTPUT.
    All these AU's will be receiving from the KB1.
    Notice that all the MIDI OUTPUTs will be pointed to AUM (After AUM is setup)

    This is where you setup the KB1.
    Notice you are not connecting the KB1 input, only the output.
    The KB1 is outputting on Ch 1.
    In this example we'll be using AUM as the Midi loopback App.
    AUM will receive each Midi Ch, and bounce it right back into Drambo.

    In this photo you can see that Track one is set to receive on Ch 1 (The KB1's loopback Midi)
    All the other AU's are connected to Track One's main midi in (The KB1's loopback Midi).

    Setting up AUM is simple.
    You don't have to create any channel at all.
    Just go into the routing grid and send "AUM virtual" to "Drambo virtual".
    Make sure you start AUM's transport playing or it won't work.

    This shows how I set up the tracks.
    I set each track Ch to correspond with it's track number.
    "Receives Midi" is set to "always" on each track used.

    With this setup, I'm able to record the Midi from the Audio Units directly into Drambo's Sequencer.
    This last pic show that you can turn off any of the MIDI OUTPUTS by deselecting AUM and changing it to "- -".
    Do this after recording to stop the loopback.

    Note that you can change midi Channels on the MIDI OUTPUTS too. This way you can configure which track to send the Midi.

    Hope this is helpful. :)

  • @horsetrainer said:

    @muzka said:

    Been using drambo for a while now and happy with its sequencing etc.

    Before I ran it in aum, I'd have all my midi generators on a aum channel and I'd send them to each track in drambo via different midi channels Then I'd hit record in drambo and the midi would record into each drambo track in the step sequencer and I could delete the aum midi tracker and work in drambo

    I'd hoped for a similar workaround, hist my midi apps such as rozetta and chordbud in a midi channel and send to auv3 tracks and record or have midi generator and synth on same track and record

    To get round it I've been adding a flexi sampler at the end and recording as audio, make 3 or 4 variations then open eg pulse on a track and use it as an audio clip launcher.

    Its actually similar to how I work in ableton with bouncing midi patterns down to audio

    Here's an example setup. It can be done in multiple ways, but the principles are the same.

    Step one.
    Set up your AU's and connect each to a MIDI OUTPUT.
    All these AU's will be receiving from the KB1.
    Notice that all the MIDI OUTPUTs will be pointed to AUM (After AUM is setup)

    This is where you setup the KB1.
    Notice you are not connecting the KB1 input, only the output.
    The KB1 is outputting on Ch 1.
    In this example we'll be using AUM as the Midi loopback App.
    AUM will receive each Midi Ch, and bounce it right back into Drambo.

    In this photo you can see that Track one is set to receive on Ch 1 (The KB1's loopback Midi)
    All the other AU's are connected to Track One's main midi in (The KB1's loopback Midi).

    Setting up AUM is simple.
    You don't have to create any channel at all.
    Just go into the routing grid and send "AUM virtual" to "Drambo virtual".
    Make sure you start AUM's transport playing or it won't work.

    This shows how I set up the tracks.
    I set each track Ch to correspond with it's track number.
    "Receives Midi" is set to "always" on each track used.

    With this setup, I'm able to record the Midi from the Audio Units directly into Drambo's Sequencer.
    This last pic show that you can turn off any of the MIDI OUTPUTS by deselecting AUM and changing it to "- -".
    Do this after recording to stop the loopback.

    Note that you can change midi Channels on the MIDI OUTPUTS too. This way you can configure which track to send the Midi.

    Hope this is helpful. :)

    Excellent, thank you

    Going to grab my ipad and read over this :smile:

  • Great idea @horsetrainer! 👍🏼

  • edited December 2020

    @horsetrainer said:

    @muzka said:

    Been using drambo for a while now and happy with its sequencing etc.

    Before I ran it in aum, I'd have all my midi generators on a aum channel and I'd send them to each track in drambo via different midi channels Then I'd hit record in drambo and the midi would record into each drambo track in the step sequencer and I could delete the aum midi tracker and work in drambo

    I'd hoped for a similar workaround, hist my midi apps such as rozetta and chordbud in a midi channel and send to auv3 tracks and record or have midi generator and synth on same track and record

    To get round it I've been adding a flexi sampler at the end and recording as audio, make 3 or 4 variations then open eg pulse on a track and use it as an audio clip launcher.

    Its actually similar to how I work in ableton with bouncing midi patterns down to audio

    Here's an example setup. It can be done in multiple ways, but the principles are the same.

    Step one.
    Set up your AU's and connect each to a MIDI OUTPUT.
    All these AU's will be receiving from the KB1.
    Notice that all the MIDI OUTPUTs will be pointed to AUM (After AUM is setup)

    This is where you setup the KB1.
    Notice you are not connecting the KB1 input, only the output.
    The KB1 is outputting on Ch 1.
    In this example we'll be using AUM as the Midi loopback App.
    AUM will receive each Midi Ch, and bounce it right back into Drambo.

    In this photo you can see that Track one is set to receive on Ch 1 (The KB1's loopback Midi)
    All the other AU's are connected to Track One's main midi in (The KB1's loopback Midi).

    Setting up AUM is simple.
    You don't have to create any channel at all.
    Just go into the routing grid and send "AUM virtual" to "Drambo virtual".
    Make sure you start AUM's transport playing or it won't work.

    This shows how I set up the tracks.
    I set each track Ch to correspond with it's track number.
    "Receives Midi" is set to "always" on each track used.

    With this setup, I'm able to record the Midi from the Audio Units directly into Drambo's Sequencer.
    This last pic show that you can turn off any of the MIDI OUTPUTS by deselecting AUM and changing it to "- -".
    Do this after recording to stop the loopback.

    Note that you can change midi Channels on the MIDI OUTPUTS too. This way you can configure which track to send the Midi.

    Hope this is helpful. :)

    That's pretty slick! Gonna have to give that a shot.
    I thought that a track couldn't output more than on multiple midi channels though? In your example could you have arpbud, Rozeta cells and KB-1 all sending out simultaneously, and looping back to separate tracks? Or do you need to disable the midi output of the apps you're not currently looping back to record?

  • @Spud said:

    @rs2000 said:

    It seems like what many of you want now is audio and MIDI routing for all available inputs, outputs, plugin inputs and outputs, and sequencer MIDI I/O, correct?
    What do you think about the way it's done inside AUM?

    AUM with a decent sequencer would probably meet all my needs - Atom 2 might be the final piece of the puzzle when that is launched. Drambo with AUM-like midi and multi-channel audio routing would probably also work.

    The familiar iOS frustrations...

  • Is it right that with a lot of auv3 synths and fx I can’t see or access preset menu?

  • @horsetrainer said:

    @muzka said:

    Been using drambo for a while now and happy with its sequencing etc.

    Before I ran it in aum, I'd have all my midi generators on a aum channel and I'd send them to each track in drambo via different midi channels Then I'd hit record in drambo and the midi would record into each drambo track in the step sequencer and I could delete the aum midi tracker and work in drambo

    I'd hoped for a similar workaround, hist my midi apps such as rozetta and chordbud in a midi channel and send to auv3 tracks and record or have midi generator and synth on same track and record

    To get round it I've been adding a flexi sampler at the end and recording as audio, make 3 or 4 variations then open eg pulse on a track and use it as an audio clip launcher.

    Its actually similar to how I work in ableton with bouncing midi patterns down to audio

    Here's an example setup. It can be done in multiple ways, but the principles are the same.

    Step one.
    Set up your AU's and connect each to a MIDI OUTPUT.
    All these AU's will be receiving from the KB1.
    Notice that all the MIDI OUTPUTs will be pointed to AUM (After AUM is setup)

    This is where you setup the KB1.
    Notice you are not connecting the KB1 input, only the output.
    The KB1 is outputting on Ch 1.
    In this example we'll be using AUM as the Midi loopback App.
    AUM will receive each Midi Ch, and bounce it right back into Drambo.

    In this photo you can see that Track one is set to receive on Ch 1 (The KB1's loopback Midi)
    All the other AU's are connected to Track One's main midi in (The KB1's loopback Midi).

    Setting up AUM is simple.
    You don't have to create any channel at all.
    Just go into the routing grid and send "AUM virtual" to "Drambo virtual".
    Make sure you start AUM's transport playing or it won't work.

    This shows how I set up the tracks.
    I set each track Ch to correspond with it's track number.
    "Receives Midi" is set to "always" on each track used.

    With this setup, I'm able to record the Midi from the Audio Units directly into Drambo's Sequencer.
    This last pic show that you can turn off any of the MIDI OUTPUTS by deselecting AUM and changing it to "- -".
    Do this after recording to stop the loopback.

    Note that you can change midi Channels on the MIDI OUTPUTS too. This way you can configure which track to send the Midi.

    Hope this is helpful. :)

    This is great thank you. I could only get one midi generator to work in the chain but that's no problem as I'll just use one at a time

    Thanks again

  • The AU parameter mapping is really good in Drambo and essentially the same workflow as Ableton :)
    But yes, a midi matrix routing visualiser like AUM and apeMatrix would be nice, I wish all hosts did this including Ableton.

Sign In or Register to comment.