In short. In case I will use the information from CWP file, in particular to open CWP files in Reaper, is that going to be legal?
 
In details.
We do NOT OWN CW software nor any part of it. And we are not allowed to RE/modify/etc. any bundled with Sonar code. That is in EULA and there is no questions about that part.
 
But WE OWN WAVS, MIDI, FLAC and other media files which Sonar produce. At the end, that is why we have payed for the license to use Sonar (plug-ins, etc). So we can do whatever we like with these files. We can use them in other DAWs, we can split them into bits, modify, sell, etc.
 
CWP files are also "media" files. They have the information how we have named out tracks, fade-in/fade-outs, automations, which settings we was using for the project and plug-ins, MIDI data, etc.
CWP files do not contain any CODE (at least it looks so).
CWP files are not "encrypted" (breaking any encryption is illegal).
 
But...
At least some "presets" from CW contain IP, as was mentioned in the forum before (f.e. FX chains from Craig).
There are many precedences that formats can be "protected" by something, f.e. mp3 not so long time ago.
 
So far, by deep Googling, I came to the conclusion that at least in Europe (and I am in Europe) file formats can not be patented. Restrictions can be on the DATA usage, but data in my case are solely made by users (using Sonar) directly or by Sonar on behalf of users. Restrictions can be on algorithms for using the data (like with mp3), but it seems like not the case with data in question.
 
But I am not a lawyer. In case someone has opinions (better with references...), please let me know.
 
As already discussed in several other threads, when a program development is stopped, people start to think about data preservation. While we can save WAVs and MIDI, there is a bit more information in our projects.

Edit- Post was not correct answer.  
 

More concerned about if can I open a Sonar Project in a couple of years so I can at the very least do an export. I don't want to see it deactivated.

I assume for a number of reason that we own our own project files.
But I don't get the reason for your post - it doesn't  much matter unless you can open them in other DAWs.
Owning the files is not the same thing as owning the format which is probably coperighted i.e. owning your own project files doesn't mean that Cakewalk is going to or is obligated to make the specification available.
 
The concept that some people hold about 'abandonware' has no legal standing - just because something is no longer sold or published doesn't mean it becomes public domain or negate the owner's rights (not considering copyright expiration dates).  
 

I'm gonna presume that you're looking into ways of harvesting the data from the CWP files so that you can recreate projects in Reaper? In other words, you're thinking about reverse engineering them? 
 
I guess it depends on whether CWP is a proprietary format or an open format? I suspect it's a proprietary format, and the details of it are unpublished. But while that might mean Cakewalk (or Gibson or whomever) could theoretically launch a legal challenge against you, I think there are probably enough legal precedents established that they wouldn't bother. In other words, the courts would probably deem it "fair use." 
 
You have to ask how, for example, OpenOffice is able to read and write .xls files despite .xls being a proprietary Microsoft format. Did OpenOffice get express permission? Do they pay a royalty? I don't think so. Have Microsoft tried to sue them? Definitely not. 
 
Would I release a program which converted CWP files into Reaper files, and charge money for it? Probably not. But I'm sure if you released a free app to convert the files, nobody would bother you. 

I still own all my old WordStar files, for all the good that does me. Although they do keep the WordPerfect files company in a shoebox full of floppies I can't read.
 
Which is not to make light of the OP's question. Though unlikely, the worst-case scenario is you cannot open CWP files at some point in the future. Best way to prepare for that would be to render all your projects to wave files.
 
Whether or not you own your project files is a moot point. You're not going to put them up on eBay. Nobody is going to sue you over them, any more than Borland is coming after me for my Turbo Pascal code.
 
Oh, and if you're thinking of reverse-engineering the project files, forget it. I've tried, with only limited success. There have been many different versions of the file format over the years, details hidden from users but that make it hard to figure out what's what in there.

I think it's a good idea also to save midi files. Also, make sure to save your vsti configurations, so you can load them into your project in another DAW.  If you save wave, midi and vsti's, you will pretty much have your project as it was in Sonar. At least I think this is true. the more knowledgeable folks here will correct me if I'm wrong.

Automation envelopes. Unfortunately that's a huge part of the mix you can't export. 

First of all, thanks for the answers.
 

Cactus Music
Hate to say this way, not meaning to sound nasty,, just a gut reaction,,  but your wasting a lot of brain cells worrying about nothing.

I know But that is quite some fun to refresh my old RE skills...
 

TheSteven
But I don't get the reason for your post - it doesn't  much matter unless you can open them in other DAWs.

Let say I am quite close to be able open them in other DAW...
 

Owning the files is not the same thing as owning the format which is probably copyrighted i.e. owning your own project files doesn't mean that Cakewalk is going to or is obligated to make the specification available.
 
The concept that some people hold about 'abandonware' has no legal standing - just because something is no longer sold or published doesn't mean it becomes public domain or negate the owner's rights (not considering copyright expiration dates).

The specification can be "deducted". I am not requesting anything from Cakewalk. Also I do not try to intrude Sonar. The file structure is probably copyrighted, but so are books and scores. That does not prevent you to read them. There there can be other implications for contained information use  (f.e. scores do not give you the right to play that music without extra fees), but the information in CWP is as yours as WAVs and MIDIs.
 

sharke
I'm gonna presume that you're looking into ways of harvesting the data from the CWP files so that you can recreate projects in Reaper? In other words, you're thinking about reverse engineering them? 

This.
 

I guess it depends on whether CWP is a proprietary format or an open format? I suspect it's a proprietary format, and the details of it are unpublished. But while that might mean Cakewalk (or Gibson or whomever) could theoretically launch a legal challenge against you, I think there are probably enough legal precedents established that they wouldn't bother. In other words, the courts would probably deem it "fair use." 

Reading (more cryptic then CWP and for me in "foreign" language) courts outcomes, that is how I have interpreted them
 

Would I release a program which converted CWP files into Reaper files, and charge money for it? Probably not. But I'm sure if you released a free app to convert the files, nobody would bother you.

Probably I will release the result as not open source donationware. But I have not decided yet.
Related project (AATranslator) is far from "free".
 

bitflipper
Oh, and if you're thinking of reverse-engineering the project files, forget it. I've tried, with only limited success. There have been many different versions of the file format over the years, details hidden from users but that make it hard to figure out what's what in there.

I normally try to avoid steeling peoples time by just creating a buzz... The format is not obvious at first, but once you understand its logic, it is not so difficult to extract the information. Also X+Platinum is what I target, any interface related parts are not relevant and I do not think the core had many changes, Platinum files till some degree can be opened in older versions.
 

sharke
Automation envelopes. Unfortunately that's a huge part of the mix you can't export.

FX chains, synth settings. Possible to save in each VST separately and reconstruct after, but boring and error prone. And many other details which can take time to put back in place. All that can be avoided in case "just open" can work.
Sure there are many things which can not be converted, ProChannel, RegionFX, not sure about step sequencer, not sure about AudioSnap.
 

do it until you're legally challenged and then stop doing it, seems to be the modern way