asked Mar 16 '17 at 21:03 by Gülkan (11)


Problem is as follows: When I try to route the audio of the different pads to Bitwig, theres no option where the assigned audio track can just get that kick pad e.g.sound. I hope u can understand what I mean... :/

You have to create additional audio tracks, as many as you need for individual outs, and put an audio receiver on each one to extract the sound from the output chains inside the Geist2 instrument group. Mute out the ones inside the instrument group, our mute the group altogether if you have extracted as individual outs all the chains you need. This is definitely a pain in the neck, time consuming process. So set up a project the way you want, and save it as a template. Keep the project you made the template from so you can go back to it. Otherwise you will spend the rest of your useful life setting up drum machine outputs. I originally complained about it too. But this is how it works, and the developers validated that I was doing it as they expected.


answered Mar 17 '17 at 03:57 by amg56 (717)

edited Mar 17 '17 at 03:58

Wow, this is not very great... I wonder why it doesn't work like in Ableton. There u just had to set the individual pad outputs to eg. S1 to S9 and define this as audio ins on your audio tracks in Ableton. Pretty disappointing solution I must say.

But thanks for your fast reply and the time you spent on the answer!


answered Mar 17 '17 at 06:33 by Gülkan (11)

Btw tried it. U dont need audioreciever, u can define the ins and outs in the audio track itself. But the rest sadly stays as u described

  — (Mar 17 '17 at 10:41) Gülkan

Btw u don't need the audio reciever, u can.just specify the ins and outs in the audio track itself. The rest is as described: mute everything except the sound u want to record. Do this with every tiny bit to get the tracks separately recorded in Bitwig. Very annoying and time consuming if u have many and long tracks :-/


answered Mar 18 '17 at 08:14 by Gülkan (11)

edited Mar 18 '17 at 08:15

Gulkan, I just realized you replied on this. If you got it to work without the audio receiver, I would very much like to know how you managed it, because that's what I was trying to do to start with, and it didn't work for me. In fact, I even complained about it to the developers, and when I said I had to use the audio receiver, they said that was the right way to do it. You can set a track to send audio to another track, but if you want to do it from the receiving track's perspective instead, it won't monitor an internal track, you have to get the audio receiver in there. See below from the developers:


you're doing everything correct, this is the specified behavior: in Bitwig Studio, only external sources can be monitored, not internal ones."


answered Mar 29 '17 at 01:17 by amg56 (717)

Hi! I think its a shame Bitwig isn't capable to monitor internal sources but ok...

I just set up an audio track, specified the Geist output as in for the audio, soloed just one track in Geist and recorded this to the audio track. Next I soloed another track and recorded this to another audio track. Did this until I had every geist track recorded to a seperate audio track in Bitwig.

I tried putting an audio receiver on the audio track before recording but this seems to be an unnecessary step since.the outcome seems to be exact same like with the method described in my second paragraph.

What do you think?


answered Mar 29 '17 at 06:44 by Gülkan (11)

edited Mar 29 '17 at 07:44

Oh I understand now, you are effectively bouncing the tracks. The goal of my setup was to not have to bounce. All the routing is set up in my template so each drum shows up on its own track that you can then route as you want, and everything plays out of Geist2 in real time on those tracks. This is definitely something that needs a templated approach. I could provide the template. It's got a ton of VST effects that are part of my standard setup that would need to be removed. It's actually set up with a disabled Bitwig drum machine in front of Geist. Its only purpose is as a tool to make drum names appear in the drum editor. The whole thing was a lot of work but it was worth it I have to say. I can load up the template and have drums and Vienna Ensemble all mapped and ready to slave 8 synths.


answered Mar 29 '17 at 19:21 by amg56 (717)

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Mar 16 '17 at 21:03

Seen: 1,800 times

Last updated: Mar 29 '17 at 19:21