David?
My understanding such as it is is that control surface technology isn't
an accessibility solution as such, but smart folks have used it
to make things easier.
It is actually intended to make hardware connect to sonar, like the
mackie universal, and
act controlers for general on the fly connections,
where a protocol wasn't defined.
That's the problem with control surfaces, everybody does their own
thing, there are a few fairly well defined
protocols like mackie universal and hui for protools and such, but it's
up to the devs to write their own dll, and this is what Jamie and vic did,
defining controls for the transport and navigation and such.
Theoretically, one could define any control surface to do anything as
long as automatible parameters are exposed by the program,
and even with well defined protocols, there are areas that one has to
define themselves in .ini files if one want to change anything and not
have to go dig for the say 200 controls in a given synth or plug,
we've been having lots of discussion on the merits or not of surfaces on
midimag lately.
Someone correct me
if I'm wrong about how this works,
but we're basically using the same technology, but binding it to the
keyboard instead of a piece of actual hardware like a control surface unit,
but the way it talks to sonar
is through the same mechanism that any control surface would use.
On 5/5/2015 10:17 AM, David Engebretson Jr. wrote:
So Sonar doesn't provide a way for sighted folk to test the control surface?
I've dealt with software developers before who advertized their "control surface" has worked, but then found out that it wasn't working with their newer version of their software. After several weeks of frustrating debugging I was told, "we are sorry, we didn't realize it wasn't working."
So, even though sonar says their control surface works, are you sure it works?
It might save some frustration if you verify all of the functions can work - without JAWS in the middle of communication with the control surface and user.
Best,
David
*From:* John Martyn DoItBlind <mailto:John@xxxxxxxxxxxxx>
*Sent:* Monday, May 04, 2015 5:02 PM
*To:* sonarblindbeta@xxxxxxxxxxxxx <mailto: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> [mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] *On Behalf Of *David Engebretson Jr.
*Sent:* Monday, May 04, 2015 4:30 PM
*To:* sonarblindbeta@xxxxxxxxxxxxx <mailto: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 <mailto: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
