I can't open file...Please help me!!!

I can't open *.cwp file
I use to Sonar 4.02

it says the file you are trying to open is not campatible with this version of sonar..

Please any help would be much appreciated..thanks!!

That's an indicator something went wrong while saving the file for any number of reasons. You have 2 options:

1 - try to open the file in "safe" mode (shift-open)
2 - load the autosaved backup copy (provided you have the autosave option activated)

If you used per-project audio, all your audio clips associated with the cwp file should be easily locatable, they are not lost.

Did you try opening the file in Safe Mode? IIRC -- holding down the Shift Key while launching.

EDIT: A little slow today

oh...my god...

Also Safe-mode...can't open file
Different method??...Please~~~

Contact Cakewalk Tech Support. They might be able to open it for you.

Happened also to me! Nothing could be done.

As Mr. Loopjunkie said you can load the audio files if that is what you recorded. They will be somewhere on your HD. The project may be gone but if you recorded the audio then it may still be there. Open a new project and import the audio files into it. If you used per project audio folders then these files will all be in that folder. If you didn't they will still be on your HD. You will need only to fine them.

If you where using MIDI then it is gone.


Best
John

Hi and sorry , I don't speak english, but, i'll try .
I have a same problem,
it says the file you are trying to open is not compatible with this version of sonar
Why?
What I do?
Thanks for any help!
Cheers,
Theo.
Contact-me in Brazil!

I don't know about anybody else here in Sonarland, but I'm getting the "file not compatible" error more than ever with Sonar 4 (currently using 4.0.2). I've compensated by saving with a new file name (v. 1, 2, etc.) very frequently, but its troublesome nevertheless. Anybody else here see this error more often these days?

Best,

urock

if you restart your PC (and i mean using the "Reset" Button ) While SONAR is running
or
if you close SONAR using Task Manager
or
if SONAR crashes (very often with VSTi's using lots of CPU on a low resource PC)

All These WILL cause your file to display this message... and i would be (NOT) glad to say : Kiss your file Goodbye

ORIGINAL: crash_3210

if you restart your PC (and i mean using the "Reset" Button ) While SONAR is running
or
if you close SONAR using Task Manager
or
if SONAR crashes (very often with VSTi's using lots of CPU on a low resource PC)

All These WILL cause your file to display this message... and i would be (NOT) glad to say : Kiss your file Goodbye

Yes, I experienced the crash scenario. However, at least with me, that doesn't always result in a "file not compatible." Also, it still seems like Sonar 4 is more vulnerable to this than prior Sonar versions.

Since Cakewalk sometimes offers to fix those files if you send it in, maybe Cakewalk could come up with a little stand alone utility that one can use to try to repair the project enough to open it.

I've become really paranoid about saving again and again with Sonar 4. It didn't use to always be that way (and I've been a Cakewalk user since before PA9).

Best,

urock

I lost a couple tracks due to this...Now, I keep Windows Explorer open while I am recording and copy and paste a copy of the project file. I can use the copy to open the project in the event the original project file gets corrupted.

hey all...

this happened to me as well. luckily i had a backup that hadn't been updated in a couple of days.

But...........

THIS IS ABSOLUTELY UNACCEPTABLE.

I'm really sorry cakewalk... you do soooooo much right for us, but this isn't a problem that should ever happen. Nothing says "unprofessional" like a project file not opening.

everybody should keep this thread going and **** until it gets fixed.

-brett

This happened to me too. I finished for the night, everthing was fine until I tried to open the file the next day!!!

I always back up my work, but this kind of error just shouldn't happen. I never experienced this with Sonar 3...

I love working with Sonar, but Cakewalk needs to come up with a fix for this!

Hi!
I agree absolutely with Soldan!
Anybody speak with Cakewalk?
And what they says?



(Sorry my english)

ORIGINAL: crash_3210

if you restart your PC (and i mean using the "Reset" Button ) While SONAR is running

I had an odd crash yesterday and had to start my pc with the reset button, but the project loaded fine after the re-boot. Actually, I've never lost a Cakewalk project ever.
Knock on wood...

I am a programmer, and I recently had this happen to a very important file. It would help me alot if anyone who has had a file become currupted, but had it backed up recently, could send me the bad file and the good file so that I can compare them, the more files I get to compare, the closer I can come to making a program that can fix the broken files. Including mine.

Email it to:

goblinking [AT] echoexperiment [D0T] com

I just had the same problem. Alot of midi is lost. Jaireth I would love to send you both but I only have the corrupted file. Sorry!

Yep. Happens to me too. I lost a whole day of work the other day. Cakewalk - please stop this happening!!

I've also experienced this terrible problem. For me it was about 7 hours worth of MIDI sequencing lost. :(

Hi all:
This is a very strange report. I work with Cakewalk products since version 5 in my Home Studio, where I work more than 10 hours/day, 7 days/week, and I never had problems opening files, either .cwp or .mid.
I hightly suggest all you write to Cakewalk support with a detailed info about your problems. They can to request more info and after a study to send you suggestions or a fix.
Good luck!

This is strange! It just happened to me last week. I thought I had lost my project because I didn't have a back up and it was a .cwb file. I thought this was a problem that was unique to that file when I found two more in my archives that gave me the same message ("... the file you are trying to open is not compatable with this version of sonar!"). Now I'm thinking there is a problem with my DAW, possibly in the registry so I removed and reinstalled S4 and the updates. Still nojoy! Now I'm pissed! But I was able to recover the file and finish my project in time to meet a deadline. I loaded S4 on my lap top and opened the file via lan off of my desk top's hard drive. For about a day or so I was still thinking that my desk top had some issues but after reviewing the frustration level in post and several others on this and other web-sites, it's obvious that Twelve Tones has got a major problem in S4 that needs to be address immediately! I'm still scratching my head about being able to open the very same file on another computer of off the same hard drive. After resaving it with my laptop and renaming it I still was not to open the file or a renamed file on my desk top. I read in another post that this problem is more common with bun files. This worked for me maybe some of you should give it a try if you have the resources.

Hi Keith:
Reading your post I believe the problem is in the registry of your desktop OS. The simple fact you uninstall and reinstall Sonar 4 and updates didn´t alter the corrupted area of the registry, because probably the problem isn´t in the Sonar area of the registry but in other general area (relationed with DLLs and INIs). For a corrective procedure I believe you need to format the partition where your OS is installed, a fresh OS and programs install.
The file itself isn´t corrupted (you opened it in your notebook, via LAN, from the desktop HD, right?) and Sonar also isn´t with problems (I presume the version you installed in the notebook is the same and from the same CD you installed in your desktop, right?).
In a simple exercise of logic I believe we can to conclude wich the problem is in the OS of your desktop, probably a corrupted registry.
Only my modest opinion and conclusion. If you can, make the format/fresh install procedure and I can to bet you´ll can to open the same file normally in your desktop. If the problem is solved, please post here for other guys wich the same problem to know.
Take care.
Greetings.

Hi:
Could all other guys with this problem try to open the corrupted file in other computer and to post the result?
So we can get a final conclusion in this problem (I believe, but nothing is definitive in software/hardware area, eh eh).
Greetings

I agree with everything that you have said accept for one thing Juca. There is a problem with SONAR. If this problem was isolated to my system then I would conclude that it was in just mydesk top's OS registry. (BTW I am running windows 2K on my destop.) But the fact still remains there are several other people that have reported similar issues with this problem if not the same on this site and other bulletin boards and that's not accounting for the people who haven't reported this on the web. Yes, reformating my OS will most likely fix this problem but I shutter to think that I'm going to have to go through this everytime I see that error. SONAR is a great product but this problem is clearly in the program code that Twelve Tone Systems Inc. has sold to us and they need to fix it ASAP!!!

Hi KGB:
I can undertand your point, but if it was right my machine (and of hundred of other guys around the world wich haven´t this problem) also couldn´t to open regular cwp files. And I believe we can´t to condemn Sonar without a major investigation.
Because this, in my last post I did suggest other Sonar users wich had this problem for to initiate an investigation and to post the results. If the files can to be regularly opened in other systems by various users, will be proved that some corruption was present in these systems where the same file didn´t open.
In a sequence, this users will can to post what other softwares they have installed in the problematic machines, what OS are using, what Sonar version are using, etc etc etc.
Comparing the posts, we´ll can to detect common points between the users and establish one relationship wich permit us to arrive at one conclusion.
We already had strange cases related in this forum. One example: Arturia´s synths and Kompakt based synths not producing sound for various Sonar 4 users. The initial reaction was the users to blame Sonar 4, because the same synths was sounding very well in Sonar 3. Are you remembered?
Could you to accept that as a logical conclusion and to condemn Sonar 4? I no. After particular investigation and changing info with Ron Kuper, wich did change info with the Arturia Team, Ron Kuper did discover the problem was: as Sonar 4 was UNICODE coded because the multilanguage options implemented only with Sonar 4, and Arturia´s synths no was UNICODE coded, under WinXP versions other than English the problem was present and only because of the decimal division symbol used in these OS versions.
Simply to blame Sonar isn´t the correct way of to solve the problem. If after a major investigation the conclusion is "the problem was caused by Sonar", then yes, blame Sonar and send a report for the technical support. Better, send a report now, but ever trying to encounter the problem and fix it.
This is my personal opinion and I have experience in this scenario from that mentioned episode.
Only my .2 cents.
Greetings.

I am wondering how many people experiencing this problem might have write caching checked. Just a guess. I haven't had this problem in a long while. I suspected PACE but I have no evidence to back it up.

Problem solved

i wanna share this for anyone with similar problem in the future. I autosaved my tracks every 10 minutes. Sonar save this to a differnt file. So i went and open that file. It works.

That or you could "save as" twice everytime into 2 version A and B for example. This way, if one file is corrupt, the other identical file still openable