> Alex, I was kind of hoping to get a reliable recent Sonar and running very soon, rather than wait for a demo to come out.
 
No point in testing anything at all now for bugs/features until X3D is out, which is next week, and I place bets the demo will be out within a month, if not this month... (just a hunch!).
 
Cheers...
 
BTW
 
After you review this I suggest creating one thread at a time for any specific missing features or bugs you would like to discuss. One step at a time or we will get overwhelmed. When you made the feature requests/bugs I hope you created one feature request per item, otherwise the chances are it may have been ignored as compilations are difficult to process in the land of software.... you may want to have another go if you did this (analyse one issue at a time, baby steps I suggest, adopting KISS)... To be honest the thread you pointed me towards isn't exactly what I call bite size and a discussion seems to have already taken place, which put me off somewhat (I am a bear of very little brain, trinkets need to be placed in front of me and I need a clear path and direction to follow) .

Yikes! Maybe that is what is wrong with my .CWB files opening with this message.
Is it that I used Audio Snap?

A CORRUPT AUDIO REGION WAS DETECTED AND PADDED WITH SILENCE.
 
I certainly used Audio snap, but after I was happy with the edit I would bounce the audio within the track.
Is there a way I can recover my .cwb files since the .cwp project files are long gone? I'm freaking out.
Hoping Noel Borthwick or someone here can give me a solution.

Here's what I posted in another part of the Sonar form.
I have a client that has been recording off and on for quite some time. I have saved his files as .CWB to an External Drive. I planned to open  and work on at a later date. I've done this for years and always had success opening .cwb or long before .bun

When attempting to open the files, It gives an error message that says.
A Corrupt Audio Region Was Detected And Padded With Silence
Seems all the drums come up as silence, some guitars? It varies.

The message makes me think I'm going to have the big one!


Is there any way to open these files or recover the files within the .CWB
BTW, The .cwp files are long gone.

Am I doing something wrong? Sampling or bit in Sonar? Do I have to check a little box somewhere?
Have I lost everything? I'm hoping there is an easy solution and I'm just overlooking something.
Help

This is still a BIG issue, unaddressed. Very disappointing. Here's what I've gone through:
 
http://forum.cakewalk.com/Sonar-X3-files-suddenly-get-too-large-m3342543.aspx#3342583
 

robert_e_bone

A V Man
Ah. I see the wheels are turning, albeit very slowly... 19 Months and 2 major releases of Sonar since I reported this problem and now someone has actually proposed doing something about it... instead of slagging me off for mentioning it.
Also, as I've mentioned here on the forum and in messages to Sonar Support, because Audiosnap on long and/or complex audio takes so much time to process there should absolutely be design feature (an "Are you sure?" dialog perhaps) to prevent audiosnap data being applied accidentally or unecessarily.  for the same reason, audiosnap should be available on a "per-clip" basis not "per track".  The amount of data created can be ridiculous and project files become unusable especially when the data is apparently multiplied by subsequent saves. I can't believe that two major releases of Sonar have come and gone without this major issue being fixed.
 
BTW If anyone with X2 or X3 has the time, I'd be interested to know if any of the functionality I listed in the post below is actually possible yet...
http://forum.cakewalk.com/Help-How-to-do-these-things-in-X1-m2577918.aspx  
forum.cakewalk.com/Help-How-to-do-these-things-in-X1-m2577918.aspx

I think what might have happened is that to the best of my recollection, there just have not been a bunch of occurrences of this kind of issue (I am not taking any sides on this issue - just speculating on the apparently reduced attention given to it).
 
I am glad some improvement to dealing with this kind of corruption is available, and I hope you and the OP don't have this crop up again in any case.
 
Best of all to you guys, 
 
Bob Bone