I sure hope he takes breaks, for his own health and sanity!
We've waited a few years for some action on the X
series, an extra month or two won't hurt anyone.
At 07:27 PM 5/7/2015, you wrote:
I spoke with John a few hours ago and he has been working tirelessly on the control surface for us. At one point, he spent 36 hours non-stop working on compiling and taking out old code; just so that we can have a one of a kind sonar experience like none before these scripts. Sometimes, John would spend 18 hours a day working on improving the scripts and compiling a DLL so that it can interact with the Jaws scripts. Be assured people, that when the scripts are released, they will have been worth the wait. Not only will there be excellent documentation to support the scripts, but there will also be audio demonstrations of the features as well put together by yours truly. So, stay tuned, you wonât regret it.
Regards,
Ernest A. McCullough JR.
> On May 7, 2015, at 7:14 PM, John Martyn DoItBlind <John@xxxxxxxxxxxxx> wrote:
>
> Basically I learned C++ in a hurry to make this thing compatible with the
> new sonar.
> LOL
> John
>
> -----Original Message-----
> From: sonarblindbeta-bounce@xxxxxxxxxxxxx
> [mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Roy Shtupler
> Sent: Thursday, May 07, 2015 2:46 PM
> To: sonarblindbeta@xxxxxxxxxxxxx
> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>
> that's real frustrating indeed.
> will ask John about the scrubbing feature , since it's done via the surface.
> thanks very much for sharing
> Roy.
> http://elephant-dolphin.bandcamp.com
> ----- Original Message -----
> From: "Steve Matzura" <number6@xxxxxxxxxxxxxx>
> To: <sonarblindbeta@xxxxxxxxxxxxx>
> Sent: Thursday, May 07, 2015 8:53 PM
> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>
>
> Hi, Roy:
>
> Of course I'm not John, and I'm certainly not here to answer for him,
> but maybe I can save you some time by telling you what John told me in
> this regard. He calls me a lot and we get into the nuts and bolts of
> the thing sometimes, so maybe teling you a little of what he's told me
> might help. He says he can connect to the surface with PowerShell,
> issue commands to it, but when he tries to get stuff back from it, it
> returns garbage and doesn't pass anything on to Sonar itself. The
> thing compiled correctly and everything, JAWS can talk to it and get
> stuff back from it, but something else unknown is going on which may
> or may not hav anything to do with the header information in the .h
> files. We shall see. John's really banging his head against the wall
> on this one, but without sufficient documentation or even a glimmer of
> an idea of how to hook the thing up with Sonar so it responds to
> methods and members and all the other things having to do with DLL's
> and stuff, we're kind of clueless for the nonce. I even got onto an
> IRC channel with folks that do this stuff for a living, and they said
> the same thing--it's just supposed to work. Well, it doesn't, and
> that's what's so frustrating.
>
> On Thu, 07 May 2015 19:41:32 +0300, you wrote:
>
>> probably in the *.h , which are the header files; there you can find all
>> declarations for the various properties , methods and events for the
>> control
>> surface.
>> will check the latest version of the sdk to see where exactly this resides.
>> cheers
>> Roy.
>> http://elephant-dolphin.bandcamp.com
>> ----- Original Message -----
>> From: <ptorpey00@xxxxxxxxx>
>> To: <sonarblindbeta@xxxxxxxxxxxxx>
>> Sent: Monday, May 04, 2015 4:11 PM
>> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>>
>>
>>> I think the surfaces provided by Cakewalk are examples and one can
>>> customize
>>> them as one wishes to include the functions one wants. I don't know
>>> where
>>> one finds out what other functions one might include and what the format
>>> should be. I never got a chance to look that deeply into it. The
>>> documentation seems to be pretty sparse - Not an easy job to dig it all
>>> out.
>>> Probably a lot of what I call "experimental programming".
>>>
>>> Anyway, good luck with it. Again, I'm glad to help if and where I can.
>>>
>>> One more suggestion, you might be able to get some ideas on how the
>>> surface
>>> was implemented in the JSonar scripts - that might give you some ideas.
>>>
>>> --Pete
>>>
>>>
>>> -----Original Message-----
>>> From: sonarblindbeta-bounce@xxxxxxxxxxxxx
>>> [mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of John Martyn
>>> DoItBlind
>>> Sent: Sunday, May 03, 2015 11:27 PM
>>> To: sonarblindbeta@xxxxxxxxxxxxx
>>> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>>>
>>> Yes, but the source is problematic and a lot of things needed changing
>>> even
>>> though it is up to date. Still trying to figure out the commands.
>>> John
>>>
>>> -----Original Message-----
>>> From: sonarblindbeta-bounce@xxxxxxxxxxxxx
>>> [mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of
>>> ptorpey00@xxxxxxxxx
>>> Sent: Sunday, May 03, 2015 8:46 PM
>>> To: sonarblindbeta@xxxxxxxxxxxxx
>>> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>>>
>>> David,
>>>
>>> Yes, the Cakewalk control surface SDK is open source and available to
>>> anyone. Here is the link I sent to John with all of the information to
>>> get
>>> one started:
>>> https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK
>>>
>>> This is the latest SDK from Cakewalk. The JSonar scripts used an earlier
>>> version. I believe that you can compile the control surface into a DLL
>>> using Visual Studio 2013 (which Cakewalk recommends) and then grab all of
>>> the methods and properties of the control surface through objects via the
>>> JAWS scripts.
>>>
>>> --Pete
>>>
>>>
>>> -----Original Message-----
>>> From: sonarblindbeta-bounce@xxxxxxxxxxxxx
>>> [mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of David
>>> Engebretson
>>> Jr.
>>> Sent: Sunday, May 03, 2015 4:50 PM
>>> To: sonarblindbeta@xxxxxxxxxxxxx
>>> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>>>
>>> Is this control service open? Does Sonar make it available for all of
>>> its
>>> customers? It would be nice if everyone had access to it and its
>>> documentation. Especially if the UI is being defined.
>>>
>>> I'd be willing to get my hands dirty in a UI wrapped around Sonar's
>>> API.Let
>>> me know what you need help with.
>>>
>>> Best,
>>> David
>>>
>>>
>>>
>>> --------------------------------------------------
>>> From: "Steve Matzura" <number6@xxxxxxxxxxxxxx>
>>> Sent: Sunday, May 03, 2015 1:43 PM
>>> To: <sonarblindbeta@xxxxxxxxxxxxx>
>>> Subject: [sonarblindbeta] Re: Liftoff! Control Surface Operational!
>>>
>>>> There aren't any scripts to test yet. John's just getting the ins and
>>>> outs of the control surface under his hands now. That's the JAWS
>>>> scripting part of it. He's trying to get straight what to tell the
>>>> control surface, and how to understand what it's telling him back when
>>>> he gives it things to do. So far there's literally nothing to test.
>>>> It's the equivalent of him designing the tool which will help him
>>>> design the scripts.
>>>>
>>>> On Sun, 03 May 2015 14:52:19 -0500, you wrote:
>>>>
>>>>> That's wonderful
>>>>>
>>>>> I wish I could test these scripts out, I can't seem to get an answer
>>>>> from anybody, here I sit with my fully appointed test machine, but
>>>>> with no demo code, I can't do a thing till I get my jaws.
>>>>>
>>>>> I mean, I have my code for my serial number, and I was under the
>>>>> impression I could test with the demo, I've written to rishi and John,
>>>>> but I guess everyone's too busy.
>>>>>
>>>>> Or maybe my messages aren't getting through, is there ir is there not
>>>>> a way to test with a demo copy of jaws till my jaws gets here?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 5/3/2015 2:12 PM, Steve Matzura wrote:
>>>>>> John reports the 32- and 64-bit control surface DLL's are ready for
>>>>>> use! Now all he has to do is figure out the interface between us and
>>>>>> the functions the control surface library can call, and the data
>>>>>> which these functions return and how it should be
>>>>>> displayed/presented to us verbally. The concept of a control surface
>>>>>> is the basis of the old CakeTalking product, and it's where a large
>>>>>> portion of the development and testing for X3 and Platinum access
>>>>>> will occur. In fact, many of the things John has already worked on
>>>>>> will be rewritten because the control surface makes performing those
>>>>>> functions easier and more reliable, so there will be less actual
>>>>>> script
>>> code needed.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
