dubdisciple
Even older forms of cross DAW conversion rarely work seemlessly. When I transfer via omf or aaf, I strip project down to most base elements. What azlow achieved is amazing but must be treated in similar manner.
Exactly. It's simply not possible to translate a project using a DAW's proprietary functionality into some other DAW with incompatible proprietary functionality. What you CAN do is translate what those projects have in common, which can be a considerable amount of data and for many projects, may be all that's needed.
Maybe it's possible to map parameters among different proprietary processes designed to create the same end result, e.g., AudioSnap to however Reaper does stretching, but it seems that would be incredibly time-consuming. Or what about locked effects? Maybe it's possible to read all the parameters in the Adaptive Limiter and apply them to a different multiband limiting plug-in. Azslow would know that...I don't.
The MMA and AMEI (American and Japanese MIDI trade groups) are working on something along those lines so that, for example, filter cutoff is standardized. If your hardware controller adjusts filter cutoff, it will adjust filter cutoff in any software or hardware instrument with MIDI CI's Profile capabilities. But I don't think we have that kind of protocol yet for plug-ins.
Being able to open .cwp projects in Reaper is brilliant. It also sounds like a major improvement over OMF or AAF. Fortunately it sounds like joden's projects may be relatively simple; for example he thought it wasn't possible to cut and paste envelopes in Sonar, so he may not have gone too far into the deeper corners of the program.
Of course there's always the
100% perfect way to open a .cwp project in another DAW so it sounds
exactly the same: export all the tracks as stems, import them into the other program, make sure the pan laws are the same, and carry on from there