AZSlow

I have a Sonar V-Studio Console (VS-700C) control surface  which has worked flawlessly with the old SONAR and Cakewalk by Bandlab under Windows 7.  But now with the new Sonar, I have to use Windows 10/11 and of course there is no Win 10 driver. I have read that the driver can be tweaked to work on Win 10.  Is there a script or anyone who has knowledge of how to modify the VS-700C driver to use with Windows 10?  I would love to keep the VS-700C if I can!!

I am still in "FX Chain" conversion. Complete FX Chain conversion, I mean with original "Macro controls" and all possible automations, happened to be not trivial task: REAPER has no build-in macro controls for containers, at least not at the moment (may be my activity will ping devs a bit, who knows).

There is a new (not uploaded!) version which does that. It needs custom JSFX effect(s) which I have developed.

The problem: both must be in sync to avoid mess. I mean if I publish some version of ReaCWP or corresponding JSFX effect which are incompatible, that will produce "incompatible" projects. I mean they will not be compatible with "right" effect. Probably triggering complains in the future 

If you have projects with "advanced" FXChains, I mean those with Knobs/Buttons, and you have time and willing to test, I can upload and PM you the link to current combination of ReaCWP + CoControls/CoGain.
I still have not tried to check a single tone, but technically things I slowly working as I want (GUI has knobs/buttons/sliders, positions seems like in original FX Chains, linking to effect parameters looks fine, automations for them look reasonable, parameters names seems like ok, I have just fixed the GUI so automation recording of these macro knobs / sliders in REAPER finally works as desired). 

For feedback on the over 100 project migrations I've made from Cakewalk to Reaper. Projects of the most varied styles and workflow models.

100% migrated.

1 - QuadEq - I've indeed found that the whole issue seems to be the use of ProChannel features at some point. So, on some tracks, the plugin remains, which I overcame by creating a script that ensures consistency and configures the project migrated to Reaper.

2 - MIDI FX - The fact that MIDI FX aren't recognized can be a major problem for those who use a lot of MIDI FX. In my case, I only used Cakewalk MIDI Transpose on tracks containing an instrument plugin. So, I overcame the problem with a script that inserts JS-MIDI TRANSPOSE NOTES into all tracks with instrument plugins, followed by another script that allows me to update the key preset in all instances where the plugin is inserted.

3 - ALERT AND WARNING MESSAGES - These are perfectly suited to inform you of conversion problems.

4 - INCLUSION IN THE TITLE FIELD OF PROJECT SETTINGS - With this information, I was also able to automate several operations via scripts, such as saving the project and rendering it.

Quote from: miltonsica on August 06, 2025, 02:45:20 PMFeedback on the migration of over 30 projects yesterday:

1 - EMPTY TAKES - I no longer have the insertion of takes without content.

There was no changes in related part of the code, probably these projects had no empty takes...

Quote2 - CAKEWALK MIDI FX - Wouldn't it be possible to reference the existence of MIDI FX on the MIDI tracks, or is this a problem with the information contained in the CWP project itself?

I am not parsing related part of CWP.

Feedback on the migration of over 30 projects yesterday:

1 - EMPTY TAKES - I no longer have the insertion of takes without content.

2 - CAKEWALK MIDI FX - Wouldn't it be possible to reference the existence of MIDI FX on the MIDI tracks, or is this a problem with the information contained in the CWP project itself?

Quote from: randro on August 05, 2025, 07:51:36 AMHi all, My Presonus Faderport 2 stopped working as soon as I installed Sonar a few weeks ago.I have tried all the usual setup with no luck. Has anyone else had any problems? Sure would appreciate some help!

Are you using it with AZ Controller? If yes, you can check there, in "Last MIDI event", which messages are sent my the device. Eventually you need to re-assign MIDI ports in Sonar preferences and/or checked MIDI messages are not filtered out (also in Sonar preferences).

Hi all, My Presonus Faderport 2 stopped working as soon as I installed Sonar a few weeks ago.I have tried all the usual setup with no luck. Has anyone else had any problems? Sure would appreciate some help!

Sorry, is QuadEq.

REAEQ - Yes, on the VOZ track a while back, I used some presets I'd created. It's no problem to add ReaEQ, as it comes flat.

I'm migrating several projects, and as soon as I find another one where there are no additional takes and the application is bringing them over, I'll let you know right away.

ReqEQ is (should be) instantiated in one single case: there is enabled EQ in ProChannel. As I have explained before, I can't detect something was enabled and then "de-instantiated". I am not even sure Cakewalk does that in case you disabled the module after enabling. So, I can't distinguish "not important" and "disabled at the moment". I had to make a choice and I have decided NOT put ReaEQ in case it is disabled, even when there is preset (so it was enabled at some moment, as I have mentioned that could happened in template).

You can expand takes in Sonar to check if empty exist in the original project.

So, if you think something is strange, please provide an example in which REAPER shows something different was.

BTW the last uploaded version is b80, from yesterday.