AZSlow

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.

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.

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). 

Very good. I don't have many FX chains. My chains are very simple, but I know how to create them in Cakewalk and can help you test your version. If you want to send them to me, I can test them here, as I've already migrated all my projects. Now I'll only produce in Reaper, but there's a shift away from Cakewalk/SONAR. So we can help many users have much better preserved productions. You can leave it in the shared file we have and let me know when you're ready.

Since you have converted everything, not big use for you... but you have asked for and I have occasionally found relevant CWP section... I can start to print Info lines for missing MIDI FXes. I want finish that before uploading new version.

You will not believe how long I have spend to find where Sonar X2 is saving "MIDI FX Bin bypass", till I have understood it is NOT saving it at all (FX bin is simply re-enabled on project reload)   

EDIT: the latest "Cakwalk Sonar" Shareware is STILL not saving "MIDI FX Bin bypass"

I have PMed you the "bleeding edge" versions. Hopefully no big regression and at least something works on your system 
So, MFXes should be reported and whole functionality of FXChains should work (you can test with standard presets, f.e. "PC Style Dials").

Please don't be disappointer when something is wrong. I have testing the result just peace-wise.

No problem. I'll use the new version separately, keeping the last one that helped me complete the trip.

Can you send me a private message?

I have sent you PM (on this forum) yesterday.

BTW I am not sure in which build I have fixed that, can be you was using some version with problem: Container default "Mix" parameter is 50%. It is 100% when you create it in REAPER and in PMed ReaCWP (which set it explicitly).

Starting testing standard FX Chains presets from X2, I have already spotted 2 bugs in FX Chains... One of them can increase warning counter in the version you have, but that is not worse new build/upload. I have not checked if in current Sonar these bugs are fixed.

But I want mention them, so you don't count that as ReaCWP bugs:
1) some specified for FXChain controls can be NOT shown in Cakewalk. They are perfectly fine, converted and shown in REAPER. Editing the position of such control in Cakewalk (which for user appears as "not used") produce "ghost" control (with bad parameters). ReaCWP will ignore them silently, but till next build generate warning.
2) modulated parameters in REAPER can have "wrong" values (not the same as originally in Cakewalk) or the state of the control can be different from original (f.e. you see the button is "off" in Cakewalk, but it is "On" in REAPER). That can happened with parameters which have "custom range" (not default 0-100%) for the first parameter they modulate. Initially Cakewalk takes actual target parameter value as the value for macro control. The bug is with range, they don't apply "reverse custom range" to this value. F.e. if range is 20-40% and target parameter is 0.4, Cakewalk will NOT set button value to 1 (on), it will set it to 0.4 (shown as off).
In particular case where I have spotted that, the indication was wrong in Cakewalk but correct in CoControls. But that is case dependent, can go in any direction (both show wrong value, any set wrong value, etc.).
In practice, once control is "touched" in Cakewalk, correct value for it is saved and everything should work correctly (in Cakewalk and in REAPER).

I have published 0.0r5 version as new production version and updated installation instructions.

@miltonsica: I suggest you remove manually installed JSFXes (and corresponding lines in reaper-jsfx.ini) and upgrade ReaCWP. Test versions of ReaCWP and effects are NOT compatible with final versions (so it is good I have not published them... making them "compatible" could be challenging, I have understood that after defining ReaPack delivery method).