[sonarblindbeta] Re: Sonar Blind control surface issue

  • From: <ptorpey00@xxxxxxxxx>
  • To: <sonarblindbeta@xxxxxxxxxxxxx>
  • Date: Tue, 5 May 2015 14:05:23 -0400

Do you at least see the JSonar surface appear as one of the options in sonar
after registering the DLL with Windows and putting the DLL in the Shared
Surfaces directory?



--Pete





From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of John Martyn
DoItBlind
Sent: Tuesday, May 05, 2015 11:27 AM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Sonar Blind control surface issue



Thanks, but no brackets. The JSonar surface doesn't even work. Not sure what
to do at this point but I'm working at it.

John



From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of TL
Sent: Tuesday, May 05, 2015 6:44 AM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Sonar Blind control surface issue



Hi John, don't know if you've found the solution yet, but perhaps this could
be something to look at. If the name of the surface appears in brackets
within Sonar, then according to the following article it indicates a problem
with the registration. This comes from a community for a gaming platform
which Cakewalk seems to be a part of ... I took the excerpt from:



http://steamcommunity.com/app/241070/discussions/0/630800442990465622/



Of course, if the name doesn't appear in brackets, then this likely doesn't
apply ... and the directory names will be slightly different because we
aren't using STEAM.



Control Surface Problems in x64?[Instructions for Resolution]

Is your control surface name in brackets? This happens in certain conditions
with how the Control Surface files get registered within Windows. We haven't
nailed the exact reason that causes it, but we do have a solution. It just
takes a few easy steps.

1. Close SONAR
2. On your system go to 'C:\Users\[Your Windows user
name]\AppData\Roaming\Cakewalk\SONAR X3' (or producer/studio)
3. Delete the file called ctrlsurface.dat
4. Now open up a command window with administrator rights.
Windows 7: Type CMD in the start search. Right click on cmd.exe and select
'Run as Administrator'
Windows 8: Open up Metro, type CMD, rightclick on Command Prompt and select
'Run as Administrator' at the bottom of the screen.
5. In the prompt type "cd C:\Program Files
(x86)\Steam\SteamApps\common\Cakewalk\x64\Shared Surfaces" and/or
"C:\Program Files (x86)\Steam\SteamApps\common\Cakewalk\Shared Surfaces"
without quotes and press [Enter].
Note: If your STEAM directory is not on C: or in a different path you'll
need to change that accordingly.
6. Your prompt should now read that you're in the above directory.
7. Next type "Regsvr32 ACTController.dll" without the quotes and press
[Enter].
8. You should receive a message stating that the .dll was registered
successfully.
9. Repeat this for any of the other control surface .dll files you need to
utilize and are having issues with.

Now you should be able to go back into SONAR x64 and the ACT control surface
will keep your MIDI port assignments. If you have any issues with following
along, please contact our phone support reps and they can walk you through
this.

Note: We've used ACTController.dll as an example, but you can apply these
instructions to any .dll file in those 2 different control surface folders.

<http://steamcommunity.com/app/241070/discussions/0/630800442989546462/>
More Info on Contacting Support here



_____

From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of John Martyn
DoItBlind
Sent: Monday, May 04, 2015 8:02 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Sonar Blind control surface issue

Well, no. Sonar has to be running and the control surface loaded.

I could probably try this with power shell really quick.

Nope, nothing returned but errors. Same with jSonar plugin.

John



From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of David Engebretson
Jr.
Sent: Monday, May 04, 2015 4:30 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Sonar Blind control surface issue



If you take JAWS out of the picture, will the methods return anything? Does
Sonar have an application to test their methods in the control surface?



Best,

David





From: John Martyn DoItBlind <mailto:John@xxxxxxxxxxxxx>

Sent: Monday, May 04, 2015 3:19 PM

To: sonarblindbeta@xxxxxxxxxxxxx

Subject: [sonarblindbeta] Sonar Blind control surface issue



I am writing to you because I need help with the control surface. I made my
own control surface and all the reg entries are good. Power shell sees the
object, JAWS sees the object in 64 and 32 bit DLLs. I have implemented the
control surface in the preferences, and all seems fine until I make a call
to one of the methods. Nothing speaks. The registry entries mimic what
JSonar does in the registry with different GUID CLSIDs. All seems fine. I
even tried installing JSonar and switched everything to
JSonar.controlSurface and made the control surface active in Sonar
preferences. I also placed the appropriate DLLs in the shared surfaces
folder. I have Platinum 64 and 32 bit installed and nothing is speaking. Is
this issue correctable? Is there some secret I am missing? I'd be glad to
send you the DLLs to work with. It uses a SonarBlind.ControlSurface hook. I
made everything look the same in the registry, but alas nothing is working.
I even tried this in X3 and nothing helped. I compiled with Visual studio
express 2013 and all went fine building the DLLs. Any help would be greatly
appreciated. This is the key to making Sonar work. I am wondering if there
is some setting in the registry I am missing.

I sent this out to Victor and Jamie and hopefully gordan hears me too. I
think there is some setting in the registry that will enable the control
surface to speak. I was amazed at the jSonar DLL because it says control
surface active when you load it in the preferences control surfaces. I'll
take a better look at the code to see if there is anything missing, but I
mimicked the JSonar entries with my own identifiers. Seems that things are
working, but not quite yet. There is probably some silly setting somewhere
that I need to enable.



Thanks so much for your time.

John Martyn

505-507-3054

Mountain Time





Other related posts: