Hi Larry,

Just came across your post. Since I'm probably going to upgrade to the latest Sonar, and I do currently use the 32bit TTS-1 in BB, it's of interest to me.

Just curious, did you (or anyone?) try registering the (renamed) 32-bit copy?

I'm guessing if we do that, then we could avoid the switcheroo you mention below. The idea would be to let the Sonar upgrade register the 64 bit, then manually register the saved & renamed 32 bit (using regsvr32.exe). Presumably, we could then point Sonar and BB to their respective versions. No later manipulation would be needed, and each program could load its TTS-1 while the other is open.

-Ron

Caution: Instructions for using RegSvr are readily online, but I don't recommend fiddling with the Windows registry to anyone uncomfortable doing so.

Originally Posted By: Larry Kehl
.................
9. Now within the current " ..\Shared DXi\TTS-1" folder (remember it's currently set for 64 bit) I

a. renamed the current (5,793 KB) .dll to "TTS-1 64 bit.dll"

b. Copied in the 32 bit TTS-1.dll (the 5,887 KB) from my "..\Cakewalk\Shared Dxi\TTS-1 32 bit" folder

c. Finally I ALSO made second copy of the 32 bit dll and called it, you guessed it, "TTS-1 32 bit.dll"


Without any other changes, BIAB, RB and PT can now use the TTS-1 (the 32 bit DXi), you have 64 bit Sonar but the 64 BIT SONAR cannot use TTS-1 (yet).

If you really need the 64 bit TTS-1 in Sonar just copy the "TTS-1 64 bit.dll" to "TTS-1.dll"

But now BIAB, RB, PT can’t use it - so back and forth you go.

...............