[Solved] Dimension Pro not listed as softsynth in SONAR

Scan for changes? Preferences VSTs scan... something like that?

There are properties that allow VSTs to show up as synths. maybe This got changed by accident? I can't remember where it is right now, but there are like manage VST settings somewhere that allow you to check this.

chuckebaby

guitz

gswitz
Scan for changes? Preferences VSTs scan... something like that?

did that...weirdly, it shows up in the audio FX bin!...but obviously that's useless when wanting to select it as a MIDI instrument...what's the deal here?

I used Dim Pro yesterday, it is there. Did you try the Insert Tab: Insert / Soft Synths / Cakewalk / Dim Pro ?
When ever I have an issue inserting a soft synth, I take it back to basics and use the Insert Tab.
There was an upgrade to the plug in manager a couple months back. Maybe this is confusing you to which menus are now available.
 

 
Insert is how I too open softsynths half the time ....here's some screen captures showing it is installed and opens as a stand alone but is not listed anywhere in the insert>softsynth>submenus...am I looking in the wrong place maybe? ..I don't see it in any of the softsynth submenus...I have rescanned for plug ins multiple times
 

 

scook
If DPro appears in Audio FX, the plug-in did not scan properly. Try a VST Reset in Preferences > File > VST Settings.

that did it, thanks!

Ok, this is more information than you want since you have it fixed...
But here's what I was trying to say earlier today...
If you go to Utilities > Cakewalk Plugin Manager
You can go into VST Instruments and find Dimension Pro...
Next click plugin properties and uncheck Configure as Synth (this will mess you up like you were before).
Once done, Dimension Pro moves to the VST Audio Effects and out of the VST Instruments (VSTi)  category.
 
This was your case.
 
Now, to switch it back, you can go to VST Audio Effects, click on Dimension Pro and select Plugin Properties and check Configure as Synth > OK.
 
Now it moves out of the VST folder and back to the VSTi folder.
 
Why might you want this?? Good question!! Once you configure a VST as a VSTi you can send Midi to it. And you say, 'But I can just open the VST effect window and click on the VST3 drop down and choose 'Enable Midi Input'! True enough today, young Jedi... but in days long past before your father's father, this was not the way. To route Midi into a regular VST effect you needed to configure the effect as a VSTi. And so was born the option.
 
There were issues with the VST as a VSTi. One issue was tempo sync. As a VST, TH3 tempo sync works fine. Configured as a VSTi, Tempo Sync was disabled for the effect. At least that is my memory of the dark days before VST3. And so young warriors would switch their guitar amp sims between VST and VSTi depending on whether they were sending midi to the amp sim to manipulate effects or not.
 
Knowing all this, it may not have been necessary to reset/rescan. You could have just popped open this window and checked the box. 
 
 

I wasn't being critical, scook. I was meaning to be informative.

Respect to you as always.

You gave the right direction.

I had the same problem when upgrading to sonar platinum
i solved it by disintalling D-Pro completely and reinstalling from scratch using the old sonar 8.5 installer...

marciaferrell
So I added every Dimension Pro and VST folder to the list of scanned paths (this may come back to bite me).

It is not a good idea to add folders which are already included in the scan path. For example, by default the 64b8it DPro dll is in "C:\Program Files\Cakewalk\Vstplugins\Dimension Pro." By default, SONAR has "C:\Program Files\Cakewalk\Vstplugins" in the scan path. The default causes the scanner to search all the folders under "C:\Program Files\Cakewalk\Vstplugins" including "C:\Program Files\Cakewalk\Vstplugins\Dimension Pro." In the past adding redundant paths to the scanner caused problems.
 
It is also a really bad idea to add folders that do not normally contain VST dlls to the scan path. This can cause the scanner to open dlls which are not VST resulting the scanner hanging or crashing.
 
VST reset or one of the selective scan options above the reset button in preferences are the safest ways to correct scan problems. It is possible to perform surgical fixes with a combination of temporarily relocating VST dlls out of the scan path and removing partial entries in the VST Inventory in the registry. Manipulating the registry is not difficult but is not recommended for all.

In Preferences > File > VST Settings (where you should be maintaining the path) the defaults are:
C:\Program Files\Cakewalk\Vstplugins
C:\Program Files\Common Files\VST3

Cool sorted mine with a reset to Cheers