[Replied] No sound; Plugins not detecting; Help would be Appreciated!!!

[Vaughann722]

Dear readers; I have reinstalled Sonar X3 on a new laptop. A Toshiba Satellite S70. I’m using a UR22 interface. I’ve done as customer service suggested – installed asio drivers, installed my Korg Krome as a midi device… I’ve also installed all the Applied Acoustics Systems plugins into the following path:

C:\Program Files\Applied Acoustics Systems\VSTPlugins

I had bought about six or seven plugins so its extremely frustrating that they still don’t detect.
Firstly – I cannot get any sound out of any of the plugins via Sonar X3.
Secondly most of the Applied Acoustics Systems plugins still aren’t even detecting.

My Korg Krome no longer produces music on its own; But when I run it with my Krome Editor I can play the synthesiser – though with some background buzzing…

I had these problems with an older computer – but upon buying a laptop to dedicate to music I’m getting the same problems again…

Seth: if you read this maybe you could contact me with advice? Thought I'd try the forums too...

Help would really be appreciated.

[Vaughann722]

nb: I'm also getting a messsage about "assigned to silent hardware output'. that mmight be part of the problem but doesn't explain the plugins still not detecting...

[Aztec]

Vaughann - you certainly are having a bad run ... but hang in there, these seem like solvable things.

1. AAS Plugins should work because Lounge Lizard and Strum Acoustic are part of Producer! (Do you still have Producer ... I recall you have a cracking setup).
Is the path on your VST Scan Path?
Edit>Preferences>File>VST Settings
Where possible you should install your VSTs to a common location (split out to 32bit / 64bit is a common setup).

2. Sound assigned to silent hardware is likely the issue for all the others.
Probably best to start with:
- Master output to UR22 speakers
- Track output to Master.
You'll have to have you Audio IN/OUTs checked in:
Edit>Preferences>Audio>Devices
You can set you track IN/OUTs a number of different ways:
- Perhap most easily seen in Console View ( or simply the Inspeector window)
- Another way - You'll see a drop down option ('Custom') at the top off Track View. Choose 'All" and it'll give more info/controls in the track header.
i = input - should be your Krome
o = output - should be your UR22 speakers.
(you may have to stop/start Sonar after reassigning input/outputs).

[Jon Sasor [Cakewalk]]

To expand on what ShellstaX was saying, you basically need to break this problem down to it's separate components to effectively troubleshoot and get back running again.

First, make sure your UR22 is up and running properly with SONAR- make sure you're running ASIO and make sure the Playback and Record Timing Masters are set to the interface drivers in the Preferences. Test that your audio playback is working properly by opening a project (or creating a new one) with a simple audio file on a track.

Once the audio is squared away, you'll want to take a look at your MIDI input. Make sure the device appears and is enabled on the Devices tab of the MIDI category in the Preferences. Once enabled, create a new project and click onto a basic MIDI track. Play your controller and verify that the MIDI input meter registers properly.

If everything is okay at this point, insert one of the stock synths that comes with SONAR (like the Sound Center). Double-check your Insert Soft Synth Options dialog when doing this, generally, you'll want to make sure you have the boxes for Simple Instrument Track and Synth Property Page are both checked (have synth track folder unchecked). Once the synth then comes up, play this track with your controller and it should output normally.

From this point, you can then take a look at your third party plugs. SONAR is not going to see them until your third party folder is added to its VST scan list in the Preferences. Once this folder is in the list alongside the defaults, hit the Scan button and you'll see the scanner window appear at the bottom of SONAR. At this point it should pick up the new plugins. If it doesn't initially, try checking the boxes for rescan failed and rescan existing plugins, then scan again and the plugs should be added.

At this point everything should work as it should, just repeat the insert soft synth process with your new plugins.

[Vaughann722]

The Strum Acoustic and Lounge Lizard the come with the program detect; But the improved versions that I upgraded to don't... Trying to work the rest out now..

[Vaughann722]

All the AAS plugins are down in the VST scan path: C:\Program FIles\Applied Acoustics Systems\vstplug-ins

[Vaughann722]

I try Edit - Preference - Audio Devices - USB ASIO UR22.... - I have that ticked - but don't same to have any more choices in that window...

[Vaughann722]

ok down the bottom I changed one of the tracks from Master to uSB22 -I can get noise via the VST window now but not via my Korg Krome - which works ok when I use VSTs in stand alone mode. Apart from continued problems detecting there must be some universal setting i can use to stop all the tracks being silent...

[Vaughann722]

ok Now I have the hardware synth working but for some reason it doesn't work with one track - Track 26. And there's still the problem of most of the AAS plugins not detecting... Later on I will try and get addictive drums working too...

[Aztec]

You likely have to switch "Input Echo=ON" on the track (icon to the right of Arm Record).

[Aztec]

Further VST Install / Scan Path info:
http://steamcommunity.com/app/241070/discussions/0/540739861236700695/#c540739861285794625

[Aztec]

I believe we sorted out sound IN/OUT issues today, in a chat session, with a closer look at Track input and output channels (?).

Still some issues with VSTs ... which I think there's still plenty of things to try.

[Jon Sasor [Cakewalk]]

When the VST Scanner runs, do you see it scanning the plugins? Also, make sure that if the plugins are 64-bit, you're using a 64-bit version of SONAR or they won't appear. Rescan Failed and Rescan Existing Plugins generally should get anything in your scan path to show properly. One further thing to try is launching Steam as Administrator from Windows, then run SONAR (sometimes the plugs may not like a host without admin privileges).

[Vaughann722]

yes I see the VST scanner scanning the plugins; I have all the necessary paths included; though it goes by very quickly; Despite the paths being included I'm not sure the specfic AAS paths are actually being scanned. BTW I am using the 64 bit version. BTW how do I run Steam as adminstrator?

[Aztec]

Hi @Vaughann,

As we finished up yesterday ,,,

Steam as Admin - Right Click the icon > Run as Administrator.

If that doesn't work our next steps were:
1. Check your VST Scan Paths thouroughly for e.g stray spaces etc.
2. Remove all but the Standard VST locations. make sure they work, Then add the others one by one, ensuring they work along the way. (pref cut/paste location from Windows Explorer to avoid potential mistakes). Add the AAS path last as the seem to be giving the most grief (although Tassman did work).
[UPDATE: You should only need one entry for AAS Plugins a Scan search the tree beneath e.g, C:\Program Files\Applied Acoustics Systems\VST-Plugins ... sub-directories will be presented in the Instrument Browser].

Another thing we may have covered (?). During AAS installs did you get the option of install both or either 32/64 bit VSTs? I know you would have likely installed the 64 bit ones ... but this can easily be tested by launching Sonar 32bit mode and seeing if the VSTs are there (suggesting they are 32bit) (assuming the VST Scan Path is set correctly / persists in the 32bit mode).
(I recall you only had one set of dirs/dlls - suggesting one of either 32 or 64 bit).

[Vaughann722]

I will post this in my other thread too; Running Sonar as Admin had all the Applied Acoustics Systems plug ins detect. But the cost seems to be no more detection of VST3. Also: Z3ta+2 isnt working or detecting anymomore. NEITHER is Cakewalk Sound Center - which I had upgraded too.... Hoping someone can help me finish fixing this..... So I can have one without losing the other... Deleted all the Z3ta+2 files I could find... Trying a fresh install again..