I had a look at the Cakewalk repository at Github.
 
Does anyone know what it takes to build the 64 bit versions from the source code at Github? I could not find any documentation on requirements or build instructions.
 
Just recently I encountered some issues in the VS-700 control when it comes to adjusting/saving/restoring direct monitor mixes on the linked Octa-Capture ... and I wonder if I would be smart enough to understand the code ...
 
However, I haven't done any C++ coding in the past 3 years so my dev environment is probably outdated (Visual Studio 2010 Express is what I found when I fired up the old coding work horse) ...
 
 

OK, found it at https://github.com/Cakewalk/Cakewalk-Control-Surface-SDK/wiki/Requirements
 
It's right there in my face and I didn't see it :-)

azslow3
I think the version requirement comes just from included project files, the code is many years old and I guess can be build by old compiler.

I don't feel like splashing out on a new compiler / dev environment just now as it's not cheap and I have no idea whether this will get anywhere ...
 
So, I've got one machine with Visual Studio Express 2010 (hence probably no ATL/MFC) and older machine dusting away in the corner with an older Visual Studio that includes MFC (and probably dates back to when the VS-700 dll was actually coded) which may be good ... and bad as it is probably all 32 bit and never been ported to 64 bit ... oh, boy, that'll be another issue to deal with ... if I even get it to compile ... fiddling with compiler settings and things to link against has never been my specialty ...
 
Anyway, I'll give it a try ... it may be an interesting venture ... it's not my top priority, but something for slower days like Easter weekend maybe ???

robert_e_bone
I have the full Visual Studio 2013 Ultimate program, and a programming background, but most of that was doing a bunch of mainframe languages.  
 
I have built some C# Windows utility programs for myself, and don't mind jumping in to help in any way I can, but I also do not have the hardware on which I could test anything out.  But I do have 38 years of serious programming experience, if it can be directed at this.
 
If there is any way I can assist, I would be happy to try - I just don't know what I could do.
 
Bob Bone
 

Hi Bob, that sounds great! Thanks for your offer to help. As I said above I want to give it a try. It's not top priority. I got several recording sessions scheduled this week and an album to finish ... but Easter may be slow and there's rain on the forecasts, which may give me time to try those compilers I still have ...
 
I may be so impertinent and contact you directly via PM if I need help and will only document the relevant stuff here (sort of hiding my incompentence ;-) )
 
Thanks again,
 
Rob

It has been a LONG time since I wrote anything in C, but I'd be willing to assist as well if you need more hands.

As to what the community longs for featurewise, here is an old list:
http://forum.cakewalk.com/VS700-feature-request-master-list-m2676731.aspx
 
 
Maybe a good small and potentially easy start (for the experts among us) would be to check, why the OFFSET-Button light is not lighting up.
 
 
 Just to pick out a few things I dearly miss:
 
7- OFFSET button should light when engaged
That' a bug obviously. Makes it easy to forget, which mode you're in.
 
11- While in "Layer view", +8/-8 buttons scroll through layers of a channel in bank of 8
When you want to mute/unmute Layer No. 9+, there's no way to get there via the VS700c.
 
2- ALT+ Jog temprarily disengage snap settings to allow the Now Time cursor to scroll faster through the project
SHIFT+Jog works fine (scroll slower), but a "scroll very fast"-option would be awesome. I need the mouse for that frequently.
 
3- Allow zooming in the PRV with the console
Another thing where I have to fiddle with the mouse frequently.
 
1- Remember last selected prochannel modules when changing channels selection
You can't go through your project channel by channel and check e.g. the EQ on each channel. You need to press SEL and EQ, next channel SEL and EQ, next channel SEL and EQ. Because every time you select a new channel, the first Prochannel-Item is shown. That feature would be very nice.

 
 
Of course there are many other inconsistencies, esp. with the Channel Strip Controls. Often you don't know, where you at or which channels parameters you're adjusting... the following three bugs fall in that category:
 
4- When clicking on an open window with the mouse, keep the focus on the currently selected prochannel module
Clicking on any window (like a random VSTi) changes the actually selected Prochannel-Module of your actually selected channel back to the first one (eg. from EQ to Compressor), for no sensical reason.


5- When the EQ button is lid, double-clicking a VSTi in the rack should lit the "ACT" button while displaying the ACT parameters on the console 
Double-Clicking on an VSTi in the rack instantly shows you the ACT values in the channel control strip. However the EQ button keeps being lid.

6- When the SEND button is lid on the console, double clicking a VSTi in the syth rack should display the ACT parameters and light the ACT button on the console
Double-Clicking on an VSTi in the rack while in SEND-Mode in the channel strip control simply blanks out the display. SEND keeps being lid.
 

azslow3
"The experts among us" claiming so in this forum can be counted by fingers... on one hand... and you do not even need all 5 fingers

:D There might be some silent experts though. ;)
 
Thank you for your work regarding that matter!
 
 
There's another thing I just figured out:
Keyboard "B" toggles the Browser/Synth Rack (open or hide).
The SYNTH RACK Button on the vs700c opens up the Browser/Synth Rack. It does NOT, however, toggle it. So you cannot hide the Synth Rack by pressing the SYNTH RACK button again.
To hide it, you need to press SHIFT+SYNTH RACK.
 
The funny thing is ... SHIFT+SYNTH RACK can also open the Browser/Synth Rack. :D
So basically, SHIFT+SYNTH RACK does, what SYNTH RACK should be doing in the first place.
No need in wasting that SHIFT-Function.
 
So, this could also be an easy task potentially, to implement the correct toggle-behavoir to the SYNTH RACK button on the vs700c.

azslow3
And update to my post about Visual Studio Community 2015.
Unlike ACT MIDI and MackieControl, VS700 plug-in is build using some closed source libraries. These libraries was not compiled with VS2015 and so VS700 plug-in can not be easily rebuild with it.
  

 
Thanks az, for sharing ... so no chance unless you buy the developer studio license?