Danny Danzi


Thanks OB, but I don't have SD2. I think a few may have misunderstood me. On my old system, I had Sonar 5 through to 8.5 on it. Each time I bought Sonar, I always bought a full version. When 8.5 came out, it was way cheaper to buy the upgrade than it was to buy the full version. So I got the update, which stated it needed 8.0 installed in order for 8.5 to install.

Now, all the stuff above was on another machine that completely fried 3 weeks ago. This leaves me with install discs of Sonar's full version from Sonar 5 to Sonar 8. I don't want any of them on my new pc....all I want is Sonar 8.5. When the new machine I have here now was being built, I asked the DAW builder if he could put Sonar 8.5 on it for me using my codes that I have, to which we said "sure no problem".

Now all I want to do here is install SD3, but for me to use my upgrade install of 8.5, it needs Sonar 8 to be installed first. So I have no session Drummer 2 or 3 right now. SD 3 WAS installed on this new machine, but for some reason, I do not believe the .dll's are registered properly or something as they DO exist. See what my problem is now? :) Thanks for the suggestion though.

I just saw this after someone bubbled it back up...
 
I solved a similar problem on my new machine.  I migrated from a single core XP machine to a hex core Win 7 thing.  After I thought everything was installed and done, there were projects that refused to see Dimension Pro and Session Drummer 2...both of which ran fine when started in SaviHost.  (On a, perhaps unrelated note, I've installed SONAR as 32 bit...not yet having the courage to do the whole 64 bit thing.)
 
It turns out that these apps are confused as to where to find some of their registry settings.  The installer creates entries ("dp" and "SessionDrummer2" ) for these apps in...
 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cakewalk Music Software
 
...but it appears that, when instantiated in the 32 bit SONAR host, they look for these keys in...
 
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software
 
...instead.
 
Copying the reg info for those apps from the Wow6432Node tree down to the other one did the trick.
 
(This actually represents a bug that Cakewalk needs to take a look at.)
 
 
 

Cactus Music


Twaddle That was 2 years ago! Frugi, PM Danny, he has moved on to X1 so probably won't see your post.

Doh!!
Thanks cactus. Is that tumble-weed I see drifting past my profile?


Steve

Nice profile......

dantarbill

Danny Danzi


Thanks OB, but I don't have SD2. I think a few may have misunderstood me. On my old system, I had Sonar 5 through to 8.5 on it. Each time I bought Sonar, I always bought a full version. When 8.5 came out, it was way cheaper to buy the upgrade than it was to buy the full version. So I got the update, which stated it needed 8.0 installed in order for 8.5 to install.

Now, all the stuff above was on another machine that completely fried 3 weeks ago. This leaves me with install discs of Sonar's full version from Sonar 5 to Sonar 8. I don't want any of them on my new pc....all I want is Sonar 8.5. When the new machine I have here now was being built, I asked the DAW builder if he could put Sonar 8.5 on it for me using my codes that I have, to which we said "sure no problem".

Now all I want to do here is install SD3, but for me to use my upgrade install of 8.5, it needs Sonar 8 to be installed first. So I have no session Drummer 2 or 3 right now. SD 3 WAS installed on this new machine, but for some reason, I do not believe the .dll's are registered properly or something as they DO exist. See what my problem is now? :) Thanks for the suggestion though.

I just saw this after someone bubbled it back up...
 
I solved a similar problem on my new machine.  I migrated from a single core XP machine to a hex core Win 7 thing.  After I thought everything was installed and done, there were projects that refused to see Dimension Pro and Session Drummer 2...both of which ran fine when started in SaviHost.  (On a, perhaps unrelated note, I've installed SONAR as 32 bit...not yet having the courage to do the whole 64 bit thing.)
 
It turns out that these apps are confused as to where to find some of their registry settings.  The installer creates entries ("dp" and "SessionDrummer2" ) for these apps in...
 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cakewalk Music Software
 
...but it appears that, when instantiated in the 32 bit SONAR host, they look for these keys in...
 
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software
 
...instead.
 
Copying the reg info for those apps from the Wow6432Node tree down to the other one did the trick.
 
(This actually represents a bug that Cakewalk needs to take a look at.)
 
 
 

Thank you, thank you! 


Actually my problem was that the registry keys were pointing to the wrong location, so I just changed the path to where my Session Drummer files actually were. 

But if you hadn't told me about the registry keys I would have probably been too scared to go looking for them myself. 


I guess the paths in the registry were wrong because I moved the Session Drummer folder to another location. Would they have been fixed automatically if I had ran regsvr32.exe?


By the way I also had to copy "programs.lst" from a previous Session Drummer installation into Session Drummer 3\Contents\Programs. I don't know why it was missing, but after I copied the file, opened it, and fixed the path (it's a very strange file and somehow it seems that only the first path had to be changed)  I can now open programs from Session Drummer's Program Browser.

frugihoyi

I guess the paths in the registry were wrong because I moved the Session Drummer folder to another location. Would they have been fixed automatically if I had ran regsvr32.exe?

The regsvr32 stunt is only applicable to DX/DXi plugs.  It does a Windows specific thing where it registers the plug with the OS and identifies plugs via a CLSID that then is looked up in the registry and resolved to a path and a filename.
 
VSTs are handled by the host...which scans through specified directories looking for dll's that act like they follow the VST specification.  Each host then maintains their own list of VST's that they've discovered in this fashion.

frugihoyi

By the way I also had to copy "programs.lst" from a previous Session Drummer installation into Session Drummer 3\Contents\Programs. I don't know why it was missing, but after I copied the file, opened it, and fixed the path (it's a very strange file and somehow it seems that only the first path had to be changed)  I can now open programs from Session Drummer's Program Browser.

The programs.lst file is regenerated whenever you refresh the program list.  It's actually a better idea to not to copy the file.  Instead, open the program browser and hit F5.  This will rebuild the file based on all the programs it finds.  Admittedly, this is poorly documented.  Dimension, Rapture, Session Drummer 2 (and probably others) also use this gambit.
 
 

dantarbill

frugihoyi

I guess the paths in the registry were wrong because I moved the Session Drummer folder to another location. Would they have been fixed automatically if I had ran regsvr32.exe?

The regsvr32 stunt is only applicable to DX/DXi plugs.  It does a Windows specific thing where it registers the plug with the OS and identifies plugs via a CLSID that then is looked up in the registry and resolved to a path and a filename.
 
VSTs are handled by the host...which scans through specified directories looking for dll's that act like they follow the VST specification.  Each host then maintains their own list of VST's that they've discovered in this fashion.

frugihoyi

By the way I also had to copy "programs.lst" from a previous Session Drummer installation into Session Drummer 3\Contents\Programs. I don't know why it was missing, but after I copied the file, opened it, and fixed the path (it's a very strange file and somehow it seems that only the first path had to be changed)  I can now open programs from Session Drummer's Program Browser.

The programs.lst file is regenerated whenever you refresh the program list.  It's actually a better idea to not to copy the file.  Instead, open the program browser and hit F5.  This will rebuild the file based on all the programs it finds.  Admittedly, this is poorly documented.  Dimension, Rapture, Session Drummer 2 (and probably others) also use this gambit.
 
 

Again good to know. You're a mountain of knowledge.

I recently moved all plugins into one directory for ease of backing them up. Session Drummer 3 did what you guys discussed here. I found that the registry does not get updated as to the location of the Contents and Resources. @dantarbill -- Thanks for the heads up on that! After forcing a rescan, Session Drummer 3 still didn't show up, so I resorted to Resetting All VST Plug-ins and Re-scanning Existing Plug-ins. Now it shows up as Session Drummer x64 rather than the directory name "Session Drummer 3" -- which is strange, but it works. Thanks to all of you above who took the time to share your experience here!

bobbyprince
I recently moved all plugins into one directory for ease of backing them up. Session Drummer 3 did what you guys discussed here. I found that the registry does not get updated as to the location of the Contents and Resources. @dantarbill -- Thanks for the heads up on that! After forcing a rescan, Session Drummer 3 still didn't show up, so I resorted to Resetting All VST Plug-ins and Re-scanning Existing Plug-ins. Now it shows up as Session Drummer x64 rather than the directory name "Session Drummer 3" -- which is strange, but it works. Thanks to all of you above who took the time to share your experience here!

 
+1.
I got the same bug. I had to enter in the registry settings manually. I think it happens when you install Session Drummer 3 to a different location than the default. This thread was really useful thanks...
 
(BTW Old thread alert - thanks.).