AZSlow

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.

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.

2.

I will start with an example for MIDI tracks. MIDI tracks have "parameter controls" which send particular CC, f.e. volume, chorus and reverb. When "Chorus" is at (default) 0, should Sonar technically "send" corresponding CC? If you have never "touched" it, logically you probably don't want it is set. But what should happened if you has touched it? It can happened that was a mistake, you reset it back to zero and "don't want it". But it can also happened you have explicitly set it to zero. For that reason there is a separate "Disable" option for all these controls, Sonar "enable" them whenever you touch them. But you have an option to "disable" at any time.

But such parameters "always exist", there are not created "on the fly".

ProChannel modules are complex and dynamic (unlike "filters" in old Sonar they replace, which was fixed). You probably don't want instantiate every module initially visible on every strip. But what happens if you touch any parameter? Sure, you can "disable" it as for MIDI parameters. But unlike MIDI parameters, which are "always there", you have already "instantiated" the module. And so, to be consistent, you need something else to "de-instantiate". In any case, you have to keep "preset" for changed parameter. The same in case your "default" preset is not "empty".

And now to ReaCWP. CWP is a binary format, any flag/parameter has to be deducted. There is no "de-instantiate" GUI control and so I don't know when (and if) a module is "not loaded" in case there is "preset".
ReaCWP instantiate ProChannel module (currently ReaCWP EQ only, but can happened FX Chains are also there, I have not checked yet) in case: ProChannel is not disabled for the track and there is preset for it.

By default, Sonar name them as "Proxy" and don't include presets. So there will be no ReaEQ. But templates and touching something in ProChannel change that. And I don't know what else I can use to decide.

3. lanes mapping is tricky, especially with comping, I guess I have not added "deleting" into the logic. There was some difficulty with empty lanes (I don't remember what exactly). There is "Delete lanes with no media items" Action (and other) for quick "fixing" the result. 
 

Thank you, and I'll definitely revisit your implementations.

I was a Visual Basic, VB.Net, C++, and other developer for several years, and I know exactly what you're saying.

I'll send you a few more.

1 - The Preset Chain conversion was perfect, as it alerts you in project notes and separates the plugins on the track. With the previous version, I was opening the project in SONAR and inserting the plugins outside the chain. This is now perfect.
2 - In the SONAR project, many tracks appear to have no ProChannel input, even if I configure it with an "empty" preset, it's never empty. So I understand you're including a ReaEq instead.
3 - 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.

BTW I forgot to write: big thanks for the communication. Most "users" try it... get frustrated... years later write somewhere "this thing doesn't work" 

I have just uploaded b76....

It happened unrolling FX Chains was relatively simple.
I know, putting them into REAPER 7 Containers is better. But that requires more coding, so not for today.
Also REAPER Containers have no separate Input/Output levelers, so conversion can't be exact in any case.
For that reason I still put note about unrolling.

Well, there are MANY things which (can) exist in CW project and are not converted / not detected / etc. ReaCWP teleports way more then any other cross-daw converters/formats, but I still can't write "everything except <short list>". I mean it make little sense to write in Notes what is not converted (in most cases I don't even know things are in the project).