OK, don't know exactly what is going on but something is wanky since the BIAB 2018 update this morning. From warnings "drivers have been left open", to no sounds, to BIAB Lockups there is something strange going on. At this moment I have a locked screen of BIAB and no sound at all. Will reboot but this looks like it is going to take time. Anyone else?

Dan,

Set your audio driver to MME for the moment, after you reboot, and see if that helps.

Might also be coincidence. The staggered rollout of the Windows 10 Creators Update is causing the same problem.

Hi Matt

I agree the Creators upgrade has caused a lot of problems for many people
I have had four programs that worked perfectly well before causing problems
Solved the issues by installing Creators a second time
Evidently there are elements in it for changes later on
Brian

I had a problem with the winlive synth driver, but reinstalled it and no problems. I'm on the beta of the latest Windows 10 and have BIAB 18 installed. No problems so far for basic stuff.

Dan, let’s work on your problems and get more detail.

About the lockups, just checking, are you running BBW.EXE As Administrator?

What exactly do the driver warnings say?

Did you click on the Windows volume control (little speaker icon, lower right) to examine that? Make sure the right sound module is selected and make it the default device. Check that it’s 44.1 and not 48K. Windows updates keep flipping that.

First let me tell you this is a rock solid system. Yes, I have lots of drivers and lots of music apps - but this machine and I manage them well. I know I will fix this, but yiepps, sometimes I wonder why I spend so much time futzin with these darn computers.

Yes as administrator
See Picture
I am seeing issues with the rate. My MOTU is not reacting to BIAB and autosetting the rate as it did in the past. I am looking into this.
Yes, Windows updates are horrible. In fact I turn them off on this machine. But did update in the past week with that huge Creator updates.

Good detail. Yes, we all spend too much time on this nonsense.

I do have a memory of that error about another device open, but I haven’t seen it in many years. I think it’s in the BIAB FAQ. How about drivers: are you using ASIO or WAS in BIAB? If so, try MME for diagnostic purposes and I’ll bet the error disappears.

And while we are at it here, I googled "WAS Audio Driver" and Google's got nothing?? Is this a BIAB acronym for something it has created??

Try Windows Audio Service. It’s not from BIAB.

I am back up with sound. A good reboot likey.

Something going on with the rates. The WAS driver will not run. Error message "you audio device is set at 48K and BIAB is 44.1". Now in the past my MOTU Audio Express would always auto sense the app. For BAIB it would switch to 44.1 automatically. It is not doing that now? However, when I go back to MME in BAIB, the MOTU still says 48K (my system default), but it is playing fine. Go figure.

So for now all if fine. I just to focus on the music.

Oh by the way, last week I bought a new Music Machine. I have just plugged it in and booted it and it sits on the desk next to my current machine which is ~10 year old. But that is a whole nother story.

HI

On my Windows 7 build , my default soundcard is my AKAI EIE pro audio interface .
Providing it is switched on, otherwise it falls through to my onboard Realtech HD.if I am out and about without the AKAI.

By default my Akai is set to 24 bit 4800 this suits all of my music software.

When I run BIAB the Akai auto changes to 24 / 44100 I am using the dedicated Akai Asio driver all is fine.

But if I try to use the WAS driver in BIAB I get the error message about non matching in and out rates (so it seems that the WAS driver can not switch my Akai to 44 .1) as a result if I look at my Akai interface panel in this state it is indeed still set to 48.
All rather academic really as I want to use ASIO anyway and that works fine.

Have fun
Mike

Good observations. I ran into something similar with my Focusrite 18i20 (2) while testing BIAB 2018 with the WAS driver. I need to learn more about Windows Audio Service, but like you, I don't need it as my BIAB performance on MME or ASIO is fine.

If you read the PG Music News box, it's written there... BTW, it's WASAPI.

Well sure. API just means application programming interface. The WAS part is what’s important.

Try Windows Audio Service for the WAS search.
Ooops. Already answered.

So I need some education here. I have a few different setups one of which is my surface pro 3 with ableton and BIAB installed on a Samsung external ssd. I have always just used MME or if I am in my shed using my novation keyboard I will use ASIO with a Berigner q802 USB mixer. I have never really used the USB audio connection but decided to try it toay. With the new windows 10 creator update ASIO was really having issues. I used MME with the windows USB codec/(which I did not know even existed) Ableton said my latency was about 63ms but I truly could not hear any at all. buffer was set to approx. 3700, which seemed high. Once I tried to go below that I had issues.

Set BIAB (2017, latest build) to the same and again no latency at all with both programs running. I can usually notice some latency around 30 to 35ms.

So my question is did something change in the way that windows handles audio? I was really surprised that performance was so good.

From the release notes for 2018:
Windows Audio (WASAPI) driver format support. This allows for low latency audio recording/playback without requiring ASIO. Note: this supports 1 stereo input plus 1 stereo output at a time.

For multiple inputs/outputs, you should continue to use either MME or ASIO.

Yes, WAS was introduced with Win 10 and now it's backwards compatible to Vista or at least it is with PG products. WAS is Microsoft's answer to Apple's Core Audio. Since it's native to Windows no more third party software (ASIO) needed in many cases but it's still not good enough for live recording piano into a DAW with a midi keyboard. You need the latency down to 15ms or less for that. ASIO can get it below 10 on a good system. WAS is still a big deal though.

Bob

Totally agree, and besides I WAS so happy with ASIO i tell ya', Paddy ...........

My MOTU audio drivers are down again this morning. Something strange is going on!

I even got a Win10 error message saying the "Windows Audio Service is not running". Now if you recall from the start of this post just days ago, I didn't even know what WAS was?

Now when I tried to open BIAB, it crashed, saved a Log File and asked be to send the log file to Support and reboot.

So I rebooted and tried BIAB, this time it opened, BUT LOOK WHAT IS BACK.

This is NOT due to a NEW Win10 update as I turned it off last time I had this problem. There is some ghost in the code and given the timing of the BIAB 2018 update I can only suspect it is involved.

My first thoughts are to re-enable Win Updates. When I do this a very large list is found and its starts to download. Remember I only disabled this a couple weeks ago...

Hmmm. This isn’t directly to your problem but general advice: use ASIO if you have it - it’s better than WAS. Use MME to diagnose system problems.

After Windows does an update, check through all audio driver settings and Windows volume control properties. You may have to reinstall your audio device.

Dan, I’m sure this error message is described in one of the BIAB FAQ posts.

Matt, just to be clear, I only use MME in BIAB. I tried WAS for a few minutes on day 1, didn't like it. I have used my MOTU ASIO with BIAB when I use my keyboard input - work fine. But 99% of my time in BAIB is MME.

Yesterday was a big session of recording work. I am working on my grand OPUS. Lots of BIAB use and Reaper and recording. All went well. I turned off the DAW last night and this morning no joy. Right now massive downloads of Win10 Updates.

Today I am off the day job till next year. So I will let you know (likely more than anyone cares) how this plays out.


...Win10 updates just told me to "restart".

HI

The audio service not running thing that pops up down the bottom is normally accompanied by a cross on the little speaker in the task bar/
If you click on this and bring up the vol control and move it a bit it should clear.
Also you could instead evoke task manager cntr alt del and tab to services and start there .
Pretty certain that this is a false message anyway. it is in fact running, just that windows reported it as not before it got up and went late in the start up routine

The above is for W7 as I don’t run W10 but I suspect it is the same.
Best Regards,
MIKE

Uninstall MOTU Asio drivers, reboot, Reinstall ASIO drivers. Set new drivers as default. Test, test (yes BIAB back to normal with MME default). All is now fine again.

I will send the "error log" to BIAB support.

I am not pointing fingers here, but...

I wish someone would stop breaking my ASIO drivers!

thanks Mike for the input.

Yes, the little red circle was there as you state. But it would not go away by adjusting vol.

And Yes, the WAS was still "enabled" according to the Services page. But no message said it was not running. BIAB error message said it could not be opened. All sounds were dead until I reinstalled the ASIO from my audio device.

Maybe just me with this system. If I find time I will tell you about the new DAW I am currently building. It is sitting right next to the older one and up and running now. It will take a bit of time to transfer software over with all the licencing requirements. I am working on that now in between writing, producing and recording my OPUS.