Your problem maybe that SONAR dfoesn't know where the Dim Pro sounds are.

Unlike many soft synths you can't just move Dim Pro Multisample folder to another palce after its been installed. It will mean a reinstall or a simple registry edit to Point Dim Pro at its Multisample folder.

That's if I understood your last comments correctly.

Backup your registry before touch anything,

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\dp

You'll find the multisample entry. just edit it to reflect the actual Multisamples location and close regedit. You'll need to restart SONAR and Dim Pro

I remember when X1 came out there were a couple of demo tracks that you could download as well as X1. There were various people here (myself included) who couldn't get the Dim Pro tracks to play in one of the demos. The way around it was to make a note of the patch name and then load a fresh instance of Dim Pro and then move the midi to it and load the patch.
Just a thought.
 
Grum.
 
P.S. When I went to 64 bit from 32 bit it junked just about every track with a plugin so if you are just having Dim Pro trouble you are lucky.

mudgel, I did reinstall Dim Pro again, rather than move any files. And thanks for the registry edit option, but I'd prefer to try and find a less technical alternative first if I can - I'd prefer not to touch the registry so soon after purchasing the PC and installing Sonar. Last resort, maybe.

Grum, I already attempted your workaround but since the synths won't load, I can't open Dim Pro to find out which patch it is, so I can't reload the patch.

The actual error message I get when I try to load a project on either the 32- or 64-bit version of X1 says: "The following plugins are referred to by this project but could not be found. They may be missing or improperly installed on your system.  Dimension Pro (Synth Rack)."

Grum: "P.S. When I went to 64 bit from 32 bit it junked just about every track with a plugin so if you are just having Dim Pro trouble you are lucky."

I thought I'd remembered some discussions on similar problems myself, but had trouble finding any when I tried a search. Anyway, I anticipated that there'd be some teething problems (I'd already had months of experience with X1!). It seems to work okay with new projects, at least.

Yep, that error was what I was talking about. That project uses DimPro 32 bit, so that's all Sonar will look for. It doesn't regard DimPro64 as the same thing.

I've got X1 seeing both, but unfortunately I can't recall how. Sorry.

This is semi-related...I have both 32- and 64-bit programs on my computer, so I usually install both 32- and 64-bit plugs, if available. What I've found with 64-bit programs (including Sonar) is some will see the 32-bit plug and assume that's the right one.

What works for me with 64-bit Sonar is after installing the plug-ins, but before running Sonar, I move the 32-bit one out of its x86 VST folder. Then I scan, and Sonar finds the 64-bit plug. When I put the 32-bit plug back in, Sonar has already "committed" to the 64-bit plug so that's what loads.

I just installed the 64 bit version of Sonar X1 Producer on my new computer as well, and several DirectX audio effects I used in multiple tracks of previous songs are no longer available.  So if I install the 32 bit version too, I assume I have to open a song in 32 bit to use these effects?  And this means I cannot use these effects going forward unless I flip the song back and forth between 32 & 64 bit programs?

John T


Odd.

Actually, I seem to recall a lot of people reporting a bit of pain getting their DimPro installations up and running. It was okay for me, but there were definitively some issues. Maybe someone will pop up who knows about this, but if you have a search for DimPro installation threads, you'll get plenty of results I'm sure.

Tell me about it!

I still haven't managed to get DP 1.5 running on my DAW yet.
I can run it stand alone but can't get the vsti to show up in Sonar, either 8.5 or X1

This is mainly due to running both 8.5.3 and X1 on the same pc.

On the laptop which has only got X1 on it, DP 1.5 installed perfectly.

I learned more about this subject here in four minutes than I have in four years.
 
Thank you

Concerning plugins I create own plugin folders (and subfolders) for each DAW/version and use those ones as scan target. I do not copy the plugin DLL's into those additional folders, but instead I just create links to the original plugin DLLs (mklink <link name> <original plugin path>. Like this I have full control which plugins are visible for each DAW/version and because I only defined links a new plugin version is automatically visible to the DAWs that have a link defined to it. This works great and it makes plugin scanning faster if you do not define all the plugins for each DAW (what I did of several reasons). The only plugins that can not be handled like that in each DAW are VST3 plugins, because some DAWs do not allow to choose a VST3 folder (or subfolder), but have a fixed defined one (default VST3 path).
 
Marc