asked Jun 21 '17 at 23:15 by rickyshair (21)

edited Jun 21 '17 at 23:25

First off, I just upgraded from 8-Track to 2.1 and I'm loving it. Fantastic software.

However, my research around these parts has led me to believe that Bitwig used to support recording inputs with the WASAPI sound engine, but removed it.

Why is that? I have yet to find anything that explains why it was removed. While I do have an audio interface that provides good performance with its ASIO driver, it's a slight inconvenience to have to grab the interface and switch my audio device whenever I want to record something that isn't MIDI, even just some reference vocals through my Surface Pro's cheap, built-in microphone. I've recorded through WASAPI in other DAWs, and I'm always pleased by the low latency and how easily I can take down ideas/record quick clips of audio, even if I'm just talking into the microphone to guide myself through production ideas.

I've also read that Bitwig apparently doesn't intend to restore this feature. Consider this my humble suggestion that those in charge please reconsider.

Thanks for the great software.

I still have Windows WASAPI as an option Picture of my options


answered Jun 27 '17 at 08:48 by SaturnAudio (11)

Hi, the above question and reply touches on some problems I'm having.

I'm new to Bitwig, but not completely new to DAWs, however I've been using only hardware for the last couple of years and recording directly into a hd sound recorder as its so much fun and spontaneous to jam on synths, and I get very easily frustrated with software problems.

I got Bitwig to be part of a hybrid set up as I own a number of soft synths and I have a surface pro 4 and it looked great.

I'm finding Bitwig to be excellent if i just stick to using its internal modules and my vsts, however they seem to be using more cpu, but that's a separate issue. l'm loving the note effects etc. Getting the hang of the surface interface too, and all that side of it seems great,

My problem is with integrating and recording hardware / external audio. I have a UR22mk 2, I got it as it was supposed to be the best in class, however i was concerned about the lack of stereo monitoring, but I thought it would be OK as I could always monitor through Bitwig.

Seems like I can't. I don't know if its my being stupid. If it's problem with Bitwig or the interface, or what.

I'm spending hours unplugging and rerouting different things, messing about with wasapi and asio. inputs and outputs in Bitwig. I didn't make any music for a couple of months because i was so frustrated early on.

SO should it be possible for me to play a soft synth or drum machine in Bitwig, and record and monitor my hardware simultaneously? As it seems marketed as the DAW for hybrid systems I assumed it wouldn't be a problem. Am I crazy? Should I resign myself to the fact that i Just got the wrong audio interface, or DAW?

I can monitor both (DAW and hardware), through the UR22mk2 simultaneously but in Mono,. As I make ambient music and play with stereo effects, real time stereo monitoring is very important to me.

BTW last time i regularly integrated hardware with a DAW, I was using ableton 8 and an ancient creative zen sound card and I don't remember having any problems at all.

One work around I've considered is using my surface as a soft synth going straight into my mixer, then recording through that through the UR22 into my desktop and collecting and saving the projects, transferring through dropbox or something, but jeez...

Also, bouncing seems to take a long time and cause crashes

Any help would be greatly appreciated.

I'll try the fl thing too.


answered Jul 13 '17 at 10:09 by Fremder (11)

Purchase the 'Dante Via + DVS bundle' for $59 and your driver/ routing issues will be a thing of the past.

It's basically a digital patchbay, that unifies all hardware and software on the local computer and across the network to other computers using a custom Asio driver.

I can route audio between Bitwig and Reaper, whilst watching a movie and surfing the net.

Pro Tip: It will expose every audio capable piece of software/ hardware on the computer so before starting to route stuff, disable everything that wont be used (via Device Manager in the case of Windows)

There is a learning curve, but by also using their 'Dante Controller' app you cane fine tune all the routing and see exactly what is sending and receiving signals locally and across a network.

If you have questions after installing, start another topic 'Dante Via' and ping me here so I know it's active.


answered Jul 14 '17 at 03:52 by chrisfostertv (19)

Thanks! That looks really useful!

I have to admit it was me being stupid.

I'd got into such a mess of cables and switching between drivers and routings on the computer that I'd failed to notice that my line outs from the UR22 were no longer going into my mixer. So sorry Bitwig and Steinberg. I can now monitor and listen and play at the same time, (CPU allowing). To be fair my higher than expected CPU could be to do with temperature issues with the Surface as, its hot here and I have a cover on it.

BTW anyone else having excessive CPU issues with your VSTs set them as bit bridge only, I saw that on another thread here. Also the internal sequencer on Aalto seems to use less CPU than controlling through my SQ1. Apologies for getting off topic, but this is all stuff that I've learnt painfully, and I hope it can help any other musicians and noodlers.

I'm still surprised at how complicated it is to get things working smoothly, but I gather that it is just difficult, (analogue to digital). Robin Vincent of Molten Music technology has some useful advice on Surface related audio stuff, for anyone who might be interested.

Anyway thanks again, I'll definitely check Dante Via out.


answered Jul 14 '17 at 07:49 by Fremder (11)



answered Jun 29 at 06:30 by estebanaraneda (11)


hey man :) i totally agree on your point of view ,

i found a solution :) but first i want to say how i feel :)

i find it very frustrating that they dont support WASAPI anymore, it fills very silly and i dont think they achieve good customer experience with this decisions. They say its not meeting their requirements, but it doesnt matter. It worked perfectly in bitwig 1.1.11. In the end Bitwig doesnt ship with a working driver for windows and this makes it a horrible Program for Beginners and Pros on the Road, so basically for 50% of the customers.

Im always thinking about the new customers, they install bitwig and cant record any audio at all. Man this is a huge fail :D They might just give up and try ableton or fruity loops, where everything works right out of the box :D

to be honest ... I feel very ashamed for Bitwig :D lol Bitwig is such a cool program, but this is like.: "meeeeh I dont want to eat my broccoli"

Anywaysss there is good news for you my friend. I was gonna write a big, evil email to bitwig till i luckily found this :

!!!!!!!!!!!!!!!!!!!! Huge tension Here ... What will it beeee ????????!!!!! :)

Dude ! Install Flstudio demo and it will install FL ASIO Audio Driver !

This thing is a non Blocking ASIO Driver which behaves like WASAPI :) Its like 3ms slower than WASAPI but still its better than messing arround with ASIO4All.

Bitwig Team is messing up, but FL team solved the Windows Driver trouble :) so actualy lets give them a huge THANKS !!!!!

THAAAAAAAANNNNKKKKKSSSS Fruity Looooops :) :) :) :) :) :) :) :) :) :) :) :) :) :)

good luck and have fun ;)


answered Jul 11 '17 at 18:43 by rat010104 (19)

edited Jul 13 '17 at 11:46

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: Jun 21 '17 at 23:15

Seen: 3,525 times

Last updated: Jun 29 at 06:30