HI ALL

Just like to say that I have upgraded to the mew 2018 plus pack from my 2017 Ultra pack,

Downloaded and installed flawlessly very smooth (I do use all default locations)

Initial download build 502 + real tracks etc followed by update 503.
All seems fine here .

Yellow pop up at start up warns of windows audio session error input and output rates must match.

I assume this is to do with the new WASP driver thing which I wont be using anyway as I use a dedicated Asio driver for my AKAI EIE Pro.

So all in all a painless and straight forward logical procedure.
Thank you Pg for a pleasant upgrade experience.
Best regards
Mike

Yes, this is related to the new WAS driver.

Yes, use ASIO when your vendor has a good driver.

Yes, go into the Windows volume control properties to adjust the sample rate back to 44.1 if it was changed.

Glad everything went smoothly.

Even though you use ASIO driver, you might want to give the WAS driver a try, as (like with MME) it will let you run multiple applications concurrently. So you can run BIAB and RealBand at the same time, both using the WAS driver, with low latency. However, you may also find it doesn't work. On my laptop, the WAS driver works fine with the onboard RealTek sound chip, but it doesn't work (yet) with my (now out of production) M-Audio FastTrack Pro.

I'm going to put words in John's mouth to clarify what I think John said. I think by "run multiple applications concurrently' he meant that one audio program can use the WAS driver, and the other can use MME or ASIO.

HI Mat

Yes thanks for the clarification , it was my understanding that WAS is a one program/ app instance at a time driver.
In fact I am sure I saw a reference to this on here somewhere in the last few days highlighted in a please note box, but cant find it now.

Thanks ,
Mike

When I upgraded to 18 it selected WAS as the default driver but then no midi or audio until I changed back to MME again. I wonder does it select itself as default for all installs as this could well create problems for users, especially new ones.

I have messed around with settings in windows and sample rates but can't get it to work on its own, but funnily enough if I switch on my M-audio fast track pro it works then without error in windows 7 32 bit, haven't tried it in windows 10 as yet on same computer.

Initial reaction now that for a lot of people it may be more trouble than its worth.

Musiclover

Hi Music Lover
Yes mine also set automatically to WAS on installation had me going for a few minutes thought my controller keyboard was a bit sluggish and a tad down in volume??
Still all set back to my dedicated Asio driver and all is well.
BTW same went for Realband
Mike

Nothing but problems here. Seems my Avast is determined not to allow some of these executable files to run. Time for bed and will have to work on it tomorrow. Just wanted to let folks know life is not all rosy.

Actually, as long as I was using the onboard sound chip on my laptop, I could run both BIAB and Realband concurrently using the WAS driver. This is on Win7 Pro (haven't been able to test my Win10 computer yet).

Avast just notified me that the BIAB file was OK to install. Back on track now.

I have Avast as well. As far as I know PG music has notified Avast if I recall correctly, but Avast is continuing to stop the updates until they test it first.

Simple solution as Avast seemingly don't want to fix this,

Right click on Avast icon in system tray (Avast shields control) and disable for 10 mins. Then re-enable again.

Musiclover