AZSlow

Excellent! The messages you posted are very enlightening for those who have worked with SONAR for many years and allow me to correct the original project for a better migration. I'd like to share my thoughts on the messages:

FX chain '0 - Bass Drum' in 'BUMBO', not supported -
CWP-specific module 'SMOOTHER' in '1-VOZ' is skipped - This is a constant effect from SONAR's ProChannel.
FX chain '0 - Reverb Room' in 'Room', not supported - This is a set of SONAR FX. A feature that allows me to create an effects chain. This allowed me to open the source project and move the existing effects in the chain into the track, allowing me to have the effects individually. This is a great improvement, as it's a feature widely used by SONAR users, and it would be a huge loss not to have it in the migration. In Reaper 7.42, if I'm not mistaken, this is what's being called a Container.
FX chain '0 - Reverb Hall' in 'Hall', not supported - Same.

In your migration process, these issues you started mentioning in the Reaper project notes are issues for the users who are migrating. So I think it would be important to report their existence in your Message Box at the end.

Only display this message (No problem occurred during conversion) if there were no warnings.
Something like: There were no conversion errors, but check the Notes for this project.

I'm migrating several projects and your implementation has already given me a tremendous recovery.

And now b75.

As I have written in other thread, errors and warnings are "logical bugs" and they are reported as such. Normally easy to understand for me from where it comes (and consequences), but will probably just confuse normal users (like "section N is not found for node M", "unexpected format of V", etc.).

In other words, warnings and errors mean converter hit something unexpected in the project, a good reason to contact the developer (me) for the explanation and possibly fix.


But I have introduced some info in b75, at the moment just which FXes are excluded from conversion (CW specific ProChannel modules and FX Chains).

I have tried TesteQuestao2020.CWP in Windows and Linux and it was converted as expected.
Note I don't have most plug-ins used in this project.

What you mean by "it crashed"? Real REAPER crash? If yes, does that happened after you see ReaCWP info dialog (where you see the number of warnings)? If you don't see ReaCWP dialog before crash, I have to try find the reason... If you see it, the conversion itself is over and the crash probably happens during plug-in(s) instantiation. In that case you need to troubleshoot using REAPER methods (it has way more then Cakewalk...).

In some of your example projects I see non-ascii characters in track names (and other places). And they seems like displayed correctly in REAPER. Cakewalk has switched to UTF-8 ~ in 2020. REAPER is using UTF-8. So that should work fine. For old projects with non ascii characters it make sense re-save in CbB/New Sonar, with hope that will convert these strings correctly.

In my quick check, old Sonar X2 doesn't display characters correctly if it is started with wrong OEM locale. I mean it can happened there is no codepage info in old projects. Theoretically I can try to use current OEM locale during conversion in case I detect non-utf8 characters, but that is tricky.

Please download b74 from the same place, it should be able load files with any name.



 

First, I'd like to thank you for your kindness in evaluating and implementing this version, and for sharing my checks on this. Since I live in Brazil, where Portuguese is the spoken language, I still have many projects that insert accent marks, not only in project names but also in tracks, which the code doesn't address.

1 - I tried to remove accented words from the names, and in some cases, it worked without any problems.
2 - In others, it crashed. I reopened it in SONAR and saved it without accent marks, after replacing all the accent marks in the tracks, but the error persisted. I'll make this project available to you in the same share.

Question:
Would it be possible to list the issues found in the warnings?

You mention that x warnings were found during the conversion. If these warnings could be included in the project's notes field, I believe they could improve the project's preparation in SONAR for a migration closer to the source.

Thank you very much.

Thanks Alexey, that works!
I'll do the work on the PIC software and let you know how it all works together.
Regards
Robert

Please try b73 test build of ReaCWP (https://www.azslow.com/index.php?action=downloads;sa=view;down=57)

It should be able convert projects with video (not converting video, just not breaking existing conversion).

Video conversion is theoretically possible (I have found related section in .CWP, when not empty it was breaking the converter since I had no idea what it is). But implementing that is not one minute task.

About your projects:
* FX chains are not converted in general, but in addition trigger warnings about preset format. So
* reverb FXes are not there (FX chains) and increase warnings counter
* not reported to the user (printed by debug version...) are skipped ProChannel modules

The rest should be fine, if the code works as desired.

Note that ReaCWP is not working properly with not ASCII characters in file names. CWP files have many strings in (old) Windows single byte encodings. What is correct encoding is probably also in the file, but I don't know where... so I don't "re-code". Most users are from US... many international users (like myself) try to avoid not ASCII when using "old style" programs. And so that was not a big issue. But it seems like in your case it can be, sorry for inconvenience. 

Reporting there is not converted video is a different thing (there are many features which are not converted, most of them are not even detected... I mean I don't know how they are defined in the project)

But the part of the project which can be converted should be converted, even in case it has video, so that I am going to fix.

A bit tricky, but...

Define "Offset" Set with "Off"/"On" States.

Create control "OffsetMonitor" with:
Set State Offset Off
Function Is Offfset Mode On
Last action:OK Set State Offset On
Text State of Offset
Monitor Command feedback

In the Monitor (feedback):
Set State Offset <Set to monitored>
... actions which send MIDI based on Offset On/Off

AZC works for me in new Sonar as well, thanks.

Hi,

I have discovered that Cakewalk allows me to right click on any channel and select "Move AZ Controller here" to shift the starting channel the AZC is mapped to.
But I do not know what feedback event to look for in AZC to be able to adjust WAI accordingly in AZC.

EDIT:

Answering my own question. There is no need to do anything, WAI is automatically adjusted as I move the AZ controller to another track.
It did not work for me as I was using absolute track numbers instead of WAI-related track numbers in my fader logic code.