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

I have just successfully rebuild MackieControl.dll (without changes, I am not so fast...). Thank you one more time!
 
I have made a post on my forum with step by step rebuilding instructions: http://www.azslow.com/index.php/topic,263.0.html
 

M@
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?)

 
This you could do with a MIDI Translator tool and virtual MIDI port. I did it using loopMIDI and MIDI Translator Pro as you need to intercept and remap MIDI msg before they hit the VS-700 and trigger key bound functionality in Sonar ...
 
It has some side effects, though. So I wouldn't use it while recording MIDI, it's OK to use in mixing with all MIDI biucned to audio ...

Hey can anyone direct me in the right direction/help me out with this VisualStudio.
Is there a way to "run/debug" the V700.DLL (within VS?) and have VS monitor which blocks/parts of the code get executed in realtime? Specifically when pressing certain buttons on the VS700Controller. Thanks

azslow3

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

I have just successfully rebuild MackieControl.dll (without changes, I am not so fast...). Thank you one more time!
 
I have made a post on my forum with step by step rebuilding instructions: http://www.azslow.com/index.php/topic,263.0.html
 

great news! (sorry for late reply)

M@
Hey can anyone direct me in the right direction/help me out with this VisualStudio.
Is there a way to "run/debug" the V700.DLL (within VS?) and have VS monitor which blocks/parts of the code get executed in realtime? Specifically when pressing certain buttons on the VS700Controller. Thanks

generally speaking, you can attach to one or more processes (the sonar exe in this case?) but you won't be able to step through code (see it executing) unless you have source code and/or pdb debug symbol files
hth

Hi pwalpwal,
 
thanks for the reply.

pwalpwal
..but you won't be able to step through code (see it executing) unless you have source code and/or pdb debug symbol files

In your reply you are referring to the source-code of 'sonar.exe' right?
I understand that i will not be able to see what's going on in Sonar...but will I see what is happening within the cakewalk-control-surface .dll?
(I am unfamiliar with Visual Studio/Debugging/ the term pdp debug files in general.)
If I understand correctly the control-surface-dll will intercept data (=buttons being pressed) from the controller and then the control-surface-dll will do something i.e. execute some code of it's own or call a function from sonar.exe / make sonar.exe do something -> that's what I'm interested in. I'd like to be able to make sonar do that specific thing even without pressing the buttons.
To be specific; If I press 'Control+ACT' on my controller what happens then?
If I could 'read' c++ I could just 'read' through the source-code of the control-surface and find out what part of the code gets run when I press that button combo. I did look through the code but it's just all greek to me....so I was hoping I could just 'monitor' what happens when I press the buttons.
------ Am I completely wrong  :)    ?  -------
 
 
 

M@
Hey can anyone direct me in the right direction/help me out with this VisualStudio.
Is there a way to "run/debug" the V700.DLL (within VS?) and have VS monitor which blocks/parts of the code get executed in realtime? Specifically when pressing certain buttons on the VS700Controller. Thanks

I guess you either have to start Sonar under debugger or implement "Sonar like" program yourself (these DLL are running as "inproc service", so they are a part of Sonar when working). I went the route number 2
 
In practice, I never had a need to really run under debugger. Just insert logging at required places. You can filter input/output yourself from the code (look for MidiInShort(Long)Msg and MidiOutShort(Long)Msg).

HI Azslow3,
appreciate your input as well!

azslow3
...may be you reconsider and finish some album instead

That one from a few posts above is especially true. In fact I do have a couple of recordings from our band that do need mixing, but I'll wait a little with that as we want to record a few more songs. Then when all the recording is done I'll get my mind set to mixing. So......as I have no important projects right now that need my PC running trouble-free I enjoy playing around a bit. I will gladly test your plugin as well soon.
 
I looked through the sourcecode a bit and found these passages:
// ACT Button
    pmsg = createMidiMsg( _T("ACT"), BID_Act );
    pmsg->SetMessageType( CMidiMsg::mtNote );
    pmsg->SetChannel(0);
    pmsg->SetNoteNum( 0x2b );
    pmsg->SetIsTrigger( true, 0x7f );
    addControlMsg( pmsg );
 
// Command Modifier
    pmsg = createMidiMsg( _T("Command"), BID_Command );
    pmsg->SetMessageType( CMidiMsg::mtNote );
    pmsg->SetChannel(0);
    pmsg->SetNoteNum( 0x47 );
    addControlMsg( pmsg );
 
......and understand that they somehow generate midi-notes 71 and 43 but not more than that.
How or what happens then....no clue.
I'll try and search for the 'MidiInShort(Long)Msg' you mentioned.
 
 
 
 
 
 
 
 

M@
Hi pwalpwal,
 
thanks for the reply.

pwalpwal
..but you won't be able to step through code (see it executing) unless you have source code and/or pdb debug symbol files

In your reply you are referring to the source-code of 'sonar.exe' right?

no, i mean the code of the plugin v700 - i dont know this specific project so can't be any more specific sorry, but there will be a way to get sonar to load your "visual studio debug runtime" of the plugin

Meanwhile; let me give you guys the complete info on what I'm trying here.
I was actually hoping that I could somehow find out myself and get something working before I 'spill the beans': You know feel proud and all. But I rather put my ego back in line and try and find solutions together! That's the reason I joined the community in the first place.
 
Many times I have read here in the forum that people were aksing for the possibility of saving individual presets of each of the prochannel plugins; especially for the QuadCurve EQ.
Well there is a way to save presets individually.
 
If for example you open one of the SonitusFX plugins then they open in a 'classical windows' window. The header has the maximize, minimze, close buttons. The name of the plugin and below it has the dropdown menu in which you can save presets for the plugin. See screenshot here: https://www.dropbox.com/s...eter%20header.jpg?dl=0
 
This window or framework somehow is a placeholder for the Vst. In the background it keeps track of the controllable parameters (I think) Same is true for the Prochannel plugins.
There is a way to open this window but instead of showing the GUI of the plugin it's just showing the parameters as horizontal bars. You can see the parameters values in real-time as you are turning knobs in the plugin. This window also allows saving of presets for the plugin.
See screenshot for the GlossEQ (Quadcurve EQ) here:
https://www.dropbox.com/s/8k0mxddxssuwh7a/Prochannel%20EQ%20Preset.jpg?dl=0
 
Opening of this window only works with the older 2011 Sonar-X1 plugin (I have v1.3.0.18) in the shared surfaces folder.
(so I am not even sure if the v2011 of the open-source .dll is the same and we are able to find out what 'function' is called within Sonar to show this window.)
 
If you have the latest (2013) version of the plugin all works as it should:
On the VS700C if you press Command+ACT it will open the vst-plugin UI of the currently selected plugin in the FX-bin.
For the prochannel-plugins you have to press Command+EQ and it will give focus to the Prochannel section of the "Inspector" pane.

However using the older vs700.dll if you click/give focus to a prochannel plug and then hit Command+ACT! (Not Command+EQ) it will open this "ACT-Plugin-Parameter-Window" or whatever it is.
You can now save presets for the QuadCurve EQ independantly from any other plugs active and running in the Prochannel. Nice !!
(only small issue is that once you reload a preset, the plugin does not automatically 'refresh' it's state. You need to click/give focus to the plug to update the parameters)
 
For 3rd party prochannel plugs it doesn't work bug free; it causes display errors. Performace however does not seem to be impacted. It still allows saving of presets for those plugins and the display 'resets itself' once you close the window and reopen the prochannel. See screenshots here:
https://www.dropbox.com/s/kva6eoy3p91j85o/Prochannel%20load%20failure.jpg?dl=0
https://www.dropbox.com/s...oad%20Failure.PNG?dl=0
 
So bottom line is: I want to be able to open this window 'in a regular way'.
Say using the latest VS700.dll instead of the old one. Or.....without having a VS700 at all.
Is anyone willing to check the code and see if there is any clue as how to get that window open.
 
Final words: Maybe this is known for long time already. Maybe I'm completely missing something obvious. In that case I'm ready to laugh at myself: Just gotta let me know
Cheers, Mat