AZSlow

BTW may be I manage to add "Containers" soon instead of "flat unrolling" chains. I mean in case you plan "final" export, it make sense postpone it a bit. If something prevents quick Container implementation, I will let you know.

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.

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.

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

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.

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.

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

Buenas (a cordial greeting used by Brazilians from the South), here are the reviews on the 79:

1 - The project properties screen is always displayed at the end of the verification process, and there are some warnings. Excellent.

2 - In the VOZ track, especially where I know there is no equalization plugin, a ReaEq plugin is being added ().

Today I tested at least 30 projects, and all of them migrated the content.

For 2. In the project "MM_A melhor..." (from upload): there is no EQ in "VOZ" track, but there is (enabled) EQ in "1-VOZ" bus. I have hard time to notice when ProCh module is enabled in new Sonar (what a bad color choice...), but EQ line is lighter when it is enabled. Are you sure EQ is really disabled in your case? In what I have checked so far, the result is consistent.

"Warnings" with b79 have uncovered somethings I (and probably many CW users...) did not know: "Style Dial FX" (single knob, "MAX", "SMOOTH", etc.) ProCh modules are in practice "FXChains" with standard CW effects They have a bit "special" format, different from "normal" "FXChains", so my converter is confused. I will try to adjust to convert them as Containers (not sure I will/can reproduce "One Knob" modulation link, but at least they should work with original knob position).

I don't actually have an equalizer on the VOICE track, but I do have one on the 1-VOICE track/bus (FAB C3), so it's strange that a ReaEq appears there. I only understand it because the ProChannell, even though it hasn't been instantiated, never lets itself be completely removed, but even if it has been instantiated once, it remains there. Unlike other tracks where there was never any mention of its use.

I'll test it further here with other projects. I've had projects with various layouts and configurations over the long time I've used Cakewalk.

I'm still "pursuing" the understanding of the continuity of empty takes. I think this is something that comes from some design flag. Since I rarely use "chopped" tracks from separate takes, I always paste them all so that a single track/single reference wav remains, so I think it could be that. Cakewalk leaves references to previous takes that, since they no longer exist, were not "emptied" from the flags.

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.

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.

Sorry, is QuadEq.

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?