• SONAR
  • Issues with Sonar Home Studio
2018/01/17 15:11:51
JoeGBradford
Hi all
 
Since updating from Sonar 8LE to HS , installing a new SSD and updating to Win 10 I've had a few issues which have started to make me wish I hadn't bothered - though I do like the newer interface and features! I've sorted out previous issues I've mentioned on here related to Sampletank 2 based instruments by importing the libraries to ST3 - really glad that is now an option as I used Miroslav a fair bit.
 
I've been running through my library of VSTi's (mostly free or cheap ones it has to be said) and finding out which will work ok and which won't. I've removed those that don't appear to work at all (all 32 bit I think). I've done this testing partly by loading VSTi's into a test project which was working fine until yesterday. When I opened it I got a really loud awful noise so I turned off my speakers and noticed that the level meter was maxing out. After restarting the PC and the same thing happening I decided to delete this project. Any ideas why this may have happened? I use ASIO4All if that helps
 
I have two other issues:
Firstly some synths say they have not been installed correctly when I try to open them in one project but open fine in another. An example of this is Tone 2 Firebird which I was going to delete from my VSTi folder but then noticed I had loaded it successfully in an earlier test folder
 
Perhaps the most frustrating issue is that some synths do not seem to accept midi notes from my Roland A- Pro controller but will play if I use the synths own keyboard GUI or programme notes. Independence Free and Air Xpand2 seem to do this - though the latter did work for a while! Other synths work fine!  
 
If anyone can help me with the above I'd be very grateful. I can accept that some things won't work in HS but it is the inconsistency that really has me scratching my head!!
2018/01/17 16:10:54
Wookiee
What Audio interface are you using Joe, if it has its own ASIO driver remove all trace of that ASIO4All and install the OEM driver.  If not Try WASAPI as your driver mode.
2018/01/17 16:25:35
JoeGBradford
Thanks - I don't have an Audio Interface - just using the PC onboard sound which has been ok for me up to now with ASIO as I am purely a hobbyist
2018/01/17 19:35:18
Wookiee
I would still try the WASAPI mode, ASIO4all is not ASIO it is a wrapper around WMD driver to disguise it as an ASIO driver.
2018/01/17 19:59:15
JoeGBradford
Thanks I'll look at that. Is it something that is built into HS?
2018/01/17 21:11:09
Cactus Music
Actually I will say no don't use WASAPI. I use a laptop for pure midi work and ASIO4all is solid as a rock. It has come a long way and had a bad rap around here and for good reasons. But for me it is as smooth as using a real interface. 
I've been using it without issue for over a year. Loopback tests of audio come back bang on. WASAPI is late. 
 
It sound more like your just not setting up your input. One thing for sure is Air stuff is real weird about using obscure channels. I always have to use CH2. And I'm having issues with Mini Grand defaulting to a terrible patch with a ton of reverb. It seems to ignore Sonars patch assignments. Anyhow try setting the midi channel to Ch2. 
There is 2 places to set up a midi tracks ins and outs  notice the little tiny square icons. 
 
I= Input,  choose your controller and always use OMNI. 
O= Output  direct this to the VST instrument
C= Midi Channel-  this is where you would choose Xpand2  Channel 2   
B= Bank most I set to NONE, depends.
P= Patch set the patch
 

 
 
 
2018/01/17 21:18:49
chuckebaby
Windows 10 made major changes to WASAPI Windows API in April of 2017.
It is supposed to be better than ASIO4ALL. Not by much though. I haven't seen any loop back tests made within the last 7 months.
So if it were up to me, I would use WASAPI. It will prevent you from hunting down an ASIO wrapper and installing it when in reality you can use what it already there.
 
In Windows 10 using WASAPI in Sonar - The latency has been reduced to 1.3ms.
2018/01/17 21:20:35
JoeGBradford
Thanks I'll try Channel 2 tomorrow! I use Omni for input so that should be ok. Their other synths Hybrid & Vacuum Pro work fine but Xpand is hit and miss for no obvious reason!
2018/01/17 21:22:30
JoeGBradford
I'll try Wasapi as well. Presumably that'll be in the audio settings menu. Preume there will be no problems swapping between the two?
2018/01/17 21:27:27
chuckebaby
JoeGBradford
I'll try Wasapi as well. Presumably that'll be in the audio settings menu. Preume there will be no problems swapping between the two?


ASIO4ALL was always stable for me. But it occasionally crashed with my system and I also had to disable onboard sound. If you do end up getting an interface someday that requires an ASIO driver be sure to remove ASIO4ALL or it will cause driver conflicts and crash Sonar.
Another reason my vote for WASAPI. 1.3ms is un noticeable. Sonar worked exclusively with Cakewalk on the Windows API. Its solid. Good luck.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account