I saw someplace on the Cakewalk support site about directions on how to
properly load a control surface and register it with Sonar. I believe they
wanted you to put the control surface DLL into the Shared Surfaces directory
under the Programs / Cakewalk / folder. Then when you open Sonar (and
perhaps scan for plug-ins) the control surface should show up in Sonar. If
it doesn't, then they give directions for perhaps putting in the correct
registry entries (don't remember).
Anyway, I don't have the time now to look further into it since I have a
commitment until later today. If you can't Google the Cakewalk support site
to find how to register a control surface with Sonar, let me know and I'll
try to dig up this info again.
Sounds like you're making lots of progress. I admire the effort you've been
putting into this. You will have a lot of grateful folks in the end.
Thanks.
--Pete
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of John Martyn
DoItBlind
Sent: Monday, May 04, 2015 12:33 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Sonar blind control surface issue
OK, got the DLLs for x64 and x86. Everything is correct in the registry when
registering either DLL. Power shell sees it, jaws sees it. The object
creates successfully in jaws script. This is true for both versions of the
DLL. The jaws script knows that the object was created successfully. But
there is an issue. The calls to the DLL are not communicating with Sonar
platinum in 32 bit or 64 bit installations. I make sure to unregister the
DLLs properly and it does nothing when I issue commands to the DLL. I have
the control surface loaded in sonar as well. I am so lost as to why it is
not working. I must be missing something.
Any help or outreach is greatly appreciated. I even looked at JSonar to see
how commands were issued and no luck. I get nothing from the DLL. I have
triple checked the registry settings and everything is good. Power shell
reports the object just fine. Perhaps I should issue a command in
powershell. Please, everyone reach out to other developers in this issue
because as soon as I get the program communicating to the dll we are in good
standing.
Thanks,
John
