Just wondering ... did anyone of you ever do anything serious with the published sourced for legacy control surfaces?
 
Actually I had downloaded the source myself and successfully built it on a demo developer studio license, but never got around to dig into it while the demo license was active ... now it's expred and I still have no clue as whether I would even be able to understand it well enough to "fix" some its issue ...
 
My current view is that just paying for developer studio license to mess around with it is too expensive.  I haven't worked as software dev in a few years so all my tools are outdated - the costs for updating basically get me half way to a RME interface or half way to another CS once VS700 set stops working ... and that estimate doesn't even account for time & effort yet...
 
When I checked out the source from the reporsitory in summer it listed me as 5th ... so I don't really expect anyone to have done much ... but I'm curious ...

If you mean the source as the reference, I have used it to build by plug-in (www.azslow.com).
 
If you mean bug fixing of original plug-ins, than I guess the answer is no (expect more compatible devices friendly MCU, not from me). But there is a change that happens in the future.

what do you mean by developer tools? there's a free, fully functional "community" version of visual studio these days...

pwalpwal
what do you mean by developer tools? there's a free, fully functional "community" version of visual studio these days...

If you know where to find free and legal version of tool chain required to build these plug-ins (I mean the part which use MFC), I am interested

https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx
https://msdn.microsoft.com/en-us/library/hh967573.aspx
 
"You can create MFC or ATL programs with Visual Studio Community Edition or higher" :-)

pwalpwal
https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx
https://msdn.microsoft.com/en-us/library/hh967573.aspx
 
"You can create MFC or ATL programs with Visual Studio Community Edition or higher" :-)

OK. That's interesting because previously I just had the express version and that did not include MFC/ATL which you need to build Cakewalk source ... hence I demoed the full version and wonder why I missed that community version.
 
But I do wonder where the catch is ... because they seem to be giving everything away for free while charging big time for the actual dev studio licenses ...
 
 

FreeFlyBertl
But I do wonder where the catch is ... because they seem to be giving everything away for free while charging big time for the actual dev studio licenses ...

the catch is your app using their framework/platform :-)

pwalpwal
https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx
https://msdn.microsoft.com/en-us/library/hh967573.aspx
 
"You can create MFC or ATL programs with Visual Studio Community Edition or higher" :-)

Thanks!
That rapidly increase the chance that MCU plug-in will work with ProChannel EQ/Compressor at any place, other wished can be also accepted in case that toolchain is working

...well. I am a dreamer
Even though I only have minutest knowledge about coding I downloaded all the files hoping I could "find" something.
After downloading the express version of visualstudio and opening some of the source-code files my little dream-bubble burst 
Waaay too high above my knowledge level (Did I just say waaay to high? Uh, I meant waaaaaaay to high!)
 
I really wish for a 'personalized', 'updated', and 'improved' VS700 control surface!
I'm going to start taking notes of the things that I would like to see improved or which seem not to function well-
Some things that come to mind immediately:
1)     Would like the 16 buttons of the user assignable access-panel to be programmable with a second (or even third & fourth) function using one (or more) of the modifier buttons. See table 28 from the SONAR_VS-700_Control_Surface.chm
https://www.dropbox.com/s/hv3rig818naveam/VS700C-4.jpg?dl=0
(More of the "reserved" button combinations should be programmable)
2)     Would like to be able to programme "shift", "strg" and "alt" buttons. Either onto the acces-panel buttons (or onto the modifier buttons?)
3)      Be able to disable the LED-strip showing the values of the faders/knobs each time I move them. I'd prefer the channel-name just remains in place.
 
...to be continued
 

M@
...well. I am a dreamer
Even though I only have minutest knowledge about coding... I downloaded all the files hoping I could "find" something.
After downloading the express version of visualstudio and opening some of the source-code files my little dream-bubble burst 
Waaay too high above my knowledge level (Did I just say waaay to high? Uh, I meant waaaaaaay to high!)
 
I really wish for a 'personalized', 'updated', and 'improved' VS700 control surface!
I'm going to start taking notes of the things that I would like to see improved or which seem not to function well-
Some things that come to mind immediately:
1)     Would like the 16 buttons of the user assignable access-panel to be programmable with a second (or even third & fourth) function using one (or more) of the modifier buttons. See table 28 from the SONAR_VS-700_Control_Surface.chm
https://www.dropbox.com/s/hv3rig818naveam/VS700C-4.jpg?dl=0
(More of the "reserved" button combinations should be programmable)
2)     Would like to be able to programme "shift", "strg" and "alt" buttons. Either onto the acces-panel buttons (or onto the modifier buttons?)
3)      Be able to disable the LED-strip showing the values of the faders/knobs each time I move them. I'd prefer the channel-name just remains in place.
 
...to be continued

With such background and wishes, you can download my plug-in and start from scratch. But before you begin, look at BCR2000 thread (and the preset) and Mackie preset. While BCR does what MarCo wants, the time he spent to achieve that is enormous. May be you reconsider and finish some album instead