Steve,
I sent the URL to John and this list some time ago for accessing the
Cakewalk SDK tools, samples, and resources, so I believe that this is what
he has been digging into. Here is the URL where one can download the
repository:
https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK
From there one can download a zip file which contains sample source code for
various control surfaces. As John noted, and the latest documentation I
have indicates, some of the surfaces may not compile because of a missing
link, but others seem like they should work (like the Mackie control
surface). The documentation I downloaded is rather sparse on some details.
When one downloads and unzips the repository one can view the source code
for various control surfaces.
From the documentation that comes with the SDK download:
"We have published the source code for several production control surfaces
that ship with SONAR to the open source Cakewalk community. The code can be
found in the Surfaces folder. This software is distributed in the spirit of
open source sharing under the MIT license (MIT) below. "
Looks like the last update to any of this from Cakewalk was in December of
last year, so it isn't something Cakewalk works on actively. But I believe
it was only in the last year or two that Cakewalk updated this SDK (well
after the JSonar team put together the JSonar control surface and had been
begging Cakewalk to update it with better functionality).
Anyway, I don't envy anyone having to slog through this since it is a lot of
code, poorly documented, and apparently is a "work in progress" with not
everything working as well as one might like.
My only suggestion was that one should probably put a fair amount of thought
into which sample to start with to make sure one gets the functionality one
is looking for in the end and have the best chance of success. But I'm sure
John already knows this and has obviously confronted many of these issues.
--Pete
-----Original Message-----
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Matzura
Sent: Thursday, May 21, 2015 1:50 PM
To: sonarblindbeta@xxxxxxxxxxxxx
Subject: [sonarblindbeta] Re: Update from John
Pete,
I'm not quite sure what you're talking about here, but I think what
you're saying is that there should be some publicly available code for
control surfaces that already exist for the new software--X3 and
Platinum to be specific. If that's what you're talking about, that now
makes me wonder why John didn't look into those possibilities first,
and that maybe he should. Let me know and I can pass this back to him
and see what he says.
On Thu, 21 May 2015 13:05:24 -0400, you wrote:
Just one suggestion - Cakewalk did provide several sample projects - Somesure
thought might be given to choosing one of those sample projects to start
with as a base. I believe that the VS700 sample project may offer the most
feature set rich of Mackie compliant functions to start with but am not
about that. Hopefully John will be able to leverage some of these samples
to best use so that he doesn't have to build everything up from the ground
floor.
Good luck. What a mammoth task!
--Pete
-----Original Message-----
From: sonarblindbeta-bounce@xxxxxxxxxxxxx
[mailto:sonarblindbeta-bounce@xxxxxxxxxxxxx] On Behalf Of Steve Matzura
Sent: Thursday, May 21, 2015 12:31 PM
To: sbb
Subject: [sonarblindbeta] Update from John
Just got off the phone with the man himself. Two major things to
report:
One, Visual Studio Express cannot be used to develop this program
because it lacks support for certain components required in order to
build a dynamic link library of the type we need, so he went out and
got himself a full-blown Visual Studio Ultimate. Luckily he doesn't
actually have to pay for it for ninety days! I got it, too, on his
recommendation.
Two, most of the original source code, written in C, had to be
scrapped because the conversion to C++ (that C plus plus for those of
you without punctuation turned on) was problematic and full of dynamic
code rewrites thanks to Visual Studio Express. There were also
problems with pre-compiled headers using old Microsoft Foundation
Class files which are non-redistributable and which won't work in
Windows 7 and beyond anyway, another reason why VS Ultimate is
required. For those interested in learning what MFC's and ATL's are,
consult https://msdn.microsoft.com/en-us/library/hh967573.aspx for all
the gory glories, as they say. It's more Microsoft convolution for
sure, but if you want to play in their sandbox, you can't even bring
your own sand! LOL.
John is pretty confident that now he's decided to rework the thing
from the ground up without trying to bend the old wheel to the new
frame that he'll have something by the weekend, and it'll be a lot
easier to make happen than it was by doing it the old way, by
rebuilding rather than converting.
