AZSlow

Also, I mentioned it HERE

OK I feel a bit dumb, but I cannot find the download file.
I'm just making a video teaching Cakewalk users about transferring CWP project to Studio one by using Midi , Stems and taking screenshots. At the end I mention your CWP  2 song tool which looks like something a lot of Cakewalk users should know about.
 
I see Ed talked you into this. 

Hi Alexey

It took some time but I got the PIC software code adapted to work with fader value inputs from both envelope and offset modes in Sonar.

The only compromise is that I need to always auto-switch Sonar into envelope mode when Sonar is in play, so that the dynamic fader envelope data is read during playback.

Thanks for all your help with this.  Mixing using both fader modes is a lot better!

Regards
Robert

I have uploaded b79. Nothing fancy, but some fixed.
EDIT: Envelopes for effects inside containers should work. Side-chaining into chain theoretically can work now (not tested).

For 2. MIDI FXes are not supported in general. Whatever is there is skipped.

As I have already mentioned, I am not parsing things which I am not converting (and not going to convert). And I will not do this just to print "it was there". In case of audio effects, some are converted, other are not. It make sense to give a hint what will be skipped and that is easy since I have to check what is "convertible". MIDI effects are completely different (in Cakewalk) and not "convertible".

Excellent progress.

1 - PROJECT PROPERTIES - TITLE - It's very good. It's already a big step forward, as you can now create a script that references the contents of this field for various automations.

2 - INSTRUMENT MIDI TRACKS - I use virtual instruments in my projects that I play on my MIDI keyboard. Since I'm not an expert on the instrument, I often use Cakewalk's native Cakewalk Fx TRANSPOSE . When migrating to Reaper, this plugin, or any reference to it, disappears. Because I'm familiar with the project, I'll go ahead and create a JS-MIDI TRANSPOSES, but it would be important to have this reference to the loss of the TRANSPOSE plugin in the process. I've attached a project to that share that contains all the issues I've described.

I'll run more tests on other projects I'm migrating. As soon as I have reports, I'll send them to you.

Quote from: miltonsica on July 29, 2025, 09:52:34 PM3 - Another thing I still don't understand, but it must be because there's some kind of tag in the SONAR project that informs me that some tracks are including empty takes.

At least in the first project I have opened (Always On My Mind), original CWP has empty take lanes. If I remove some, they are removed in REAPER.

But as I have wrote, there was something tricky there (but not exactly what). So if you have an example when empty take lane is not shown in Sonar, but appears in REAPER, please give me an example.

In CWP2Song I do tricky "auto comping", since that was the only way I could find to achieve reasonable result. In ReaCWP I convert lanes "as is" (since that is possible).

I have considered to "hide" lanes now (in following builds, not worse separate upload). I guess that is the view most people keep in Sonar and real projects can look disappointing for new users even with lanes hidden (especially in case of empty lanes, like in your projects). Probably I was just so proud I have finally managed to convert lanes reasonably in REAPER 7 (or it was just simpler to debug...). Proper solution could be convert that display option from Sonar (per strip), but I in general don't (try to) convert any display options.

I write b76M. But I have uploaded b77 (committed changes into versioning system  )

I have changed the behavior after your suggestions, but not the way you have suggested.

1. Title (and Author) are now set from Cakewalk project. Putting file name / directory there doesn't sound "right" for me. I guess most people expect original content there.
If you parse RPP, you can parse Notes.

2. I no longer show ReaCWP message in case there was no errors/warnings. But I mark Project Notes as "show on project load" in case there are "info" lines. So, if I have nothing to say, no dialog appear. If there is meaningful info, project notes are shown. If the tool knows something is fishy, the number of errors/warnings is shown.

I've used the 76 here in projects with an FX Chain, but I haven't seen any changes.

Title: Yes, I think it would be great, as it could be edited. I have a render preset that uses the information contained in this field to direct the rendered file's destination, which is invariably a folder I create within the folder where I place the project.

I have uploaded b76m which tries to convert Chains as Containers (with notes, when required).

I am almost sure there is a mess with side-chaining and automations which target containers (probably also strips which have them). Also chains in Clip FXes as not converted (separate code). But in my first attempt containers are created.

You want project directory as title? That is no a good idea when project is not in a separate directory.

If you have an example of "not working sends", please upload it.

Let's go. I'm sure many of these improvements you've made are incredibly important for the entire community looking to migrate from SONAR/Cakewalk to Reaper. You've probably noticed this by the number of downloads of the tool.
I've been spreading the word to the entire community I know who is interested in using it.
So, here are a few more considerations.

1 - PROCHANNEL - In my opinion, the current approach is completely correct.
2 - CONTAINERS/FX CHAIN - For me, the way you're doing it, removing the FX from the Chain and making them explicit in the track, is perfect, but I understand that purists will certainly appreciate having their Chains preserved.
3 - MIGRATED PROJECT NAME - I consider it important, within the possibilities, that you populate the Notes field of the Properties and the information about the name of the migrated project and its path appear in the TITLE field of the Project properties, as shown in the image below.

Place the information on the first line of notes

Converted from 'D:\Reaper Projects\0 - Milton Sica\MM_A chuva e a alma\MM_A chuva e a alma.cwp'

In the Title field as:

D:\Reaper Projects\0 - Milton Sica\MM_A chuva e a alma

This would make it much easier to execute the project rendering, where you can use marks in Reaper that automatically reference the content of these fields.


4 - SENDS - in some conversions the sending of some tracks, even though they are configured, I only get the sending if I delete and re-enter the sending.