sonar 6 and plugins .. not all of my plugins show up.

Audio Plugin Hosts and other audio software applications discussion
RELATED
PRODUCTS

Post

kp wrote:Does that mean Disable8Dot3 is set to 1? It needs to be set to 0 (and a reboot) for the VST Scan to work properly.

EDIT: whoops, re-read your post .. thanks, i'll try that!

Post

... and sorry ;P

Post

For some reason i found in previous versions that i had to delete a bunch of the crap out of my VST folder to allow Sonar to see the plugs i wanted to use.
It seemed as though the scanner would not pick up everything if you had too much in the VSTi folder.

Once i got rid of the crap then Sonar saw the stuff i wanted it to see.

Just a suggestion. (I know it has been talked about here before at KVR also if you search the archive)

Paul
Image

Post

kp wrote:There's an option (registry setting) that stops NTFS generating 8.3 filenames when creating/renaming a file - it improves performance especially on directories with large numbers of files (and especially if the filenames start similarly, because of how file sorting/searching works).

For backwards compatability, the VST code in SONAR 6 uses the 8.3 filename of the dll, so if 8.3 has been disabled, you'll have problems.

But if you don't know, then probably you haven't disabled it :-)
OH MY GOD!!! YOU ARE TEH BESTEST!!!!!!

IT WORKS NOW, PERFECTLY!!

I'M SO HAPPY!! :D

sorry for shouting but this is incredible! how on earth did you know that fix??

Post

It worked for me too!

Post

I'm sad and found out ages ago when I broke the VST Adapter by changing that setting :-)

Post

don't be sad ,)

Post

hmh. still having trouble. at least nicfits lfo plug doesn't show up ..

http://www.asseca.com/nicfit/cc_mod_ldev.html

Post

That looks like a VST effect that works on MIDI data, yes? They're not supported (yet).

Post

yeah not per se, but it should still show up at least as an instrument "with midi out" - thus can be routed to another midi track .. did that with its lighter version:

http://www.asseca.com/nicfit/cc_mod.html

that one works perfectly ..

Post

Ah, OK, didn't realise it was an "instrument". In which case, there's a bug that Cakewalk have acknowledged, so it's registry editing time again to fix it.

Run the VST Scan
Select the LFO Plug and open its properties
Tick "Configure as Synth" (if it isn't already ticked like this); click OK
Add it to a plug-in menu if you want to use a custom one and save the plug-in layout and close the scanner
Open regedit (and the rest I'm doing from memory, so the registry path may be slightly wrong)
Navigate to HKLM\Cakewalk\Cakewalk VST\<plugin pathname>
Find the value labelled isSynth and change it to 1
Run SONAR and check it appears as an instrument and can be inserted as one

Post

no but you see, it doesn't show up in the plugin manager at all ..

Post

hm, the weirdest thing is that when i make a new vst directory, and put ONLY those plugs there, they show :o

i mean, normally my vst dir is c:\vstplugins and i have a good collection of vst:s there, including a bunch that won't show up in the plugin manager.

now i tried making c:\vstemp, and put a few plugs that don't show up in the manger there. i removed c:\vstplugins from the manager and replaced it with c:\vstemp

now the plugs show and work ?!? tried it again, checked that the settings are the same for both dirs etc ..

.. reverted to vstplugins dir, and they don't show

.. back to vstemp only, and they show up.

weird, huh?

Post

even weirder: when i scan /both/ dirs for plugs, they only show up in vstemp

.. but i think i can live with this now .. i just have to have a "specialized" dir for some plugs that don't show up in the normal plugin dir ..

Post

I'll give it a whirl here and see what happens.

Post Reply

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”