A corrupt audio region was detected and padded with silence

Look at the original project, if you still have it and see what is missing. Something in the conversion went wrong and sonar inserted silence in its place. It porbably is a clip.
Cj

Hi CJ. Ya, I was able to grab the clip from the original project and drop it into the new one (well, I exported it first to create a new file). But there too the single clip referenced two audio files -- I kind of expected that, but still I don't understand how a clip can consist of two files.

The help indicates this is normal, when it says that the properties dialog will show...

<< The audio file(s) that make up the selected clip
The pathname(s) the files are stored under >>

I don't think I've ever seen that before. Strange how it caused that particular error when I converted.

Hmmmm... I'm sure it wasn't ever frozen... though what you're saying makes sense....

When I go to the clip in the original file, slip-expand it, and then play it, I see that it was created by bouncing a piece of reversed audio in with normal forward audio, that was at one time part of the same wave as the reversed section before it was actually reversed. But it all appears to be a single clip as far as the wav form goes. Hmmm.... I dunno. Oh well. Everything seems to be working.

Thanks!

You'll get this message if the clip has been modified outside of SONAR in such a way as to change its length.

Any message with the word "corrupt" in it sends chills, but it's really not as scary as it sounds and is no cause for alarm.

But in some cases, the clips that are triggering these errors are playing back either silence or the wrong portion of the referenced clip. This is after a conversion from 96/24 down to 44/24 using r8brain

HCMG, I did a quick test with the free version of R8brain vs. Sonar conversion when this subject came up in your other post, and the first problem I encountered was that R8brain added about 2 seconds of silence to the front of the track. I don't know if this is what is causing your current problem, but it made R8brain a no-go for me right out of the box, regardless of any advantage it might have in sound-quality over SONAR, or the convenience of batch processing.

ORIGINAL: brundlefly

HCMG, I did a quick test with the free version of R8brain vs. Sonar conversion when this subject came up in your other post, and the first problem I encountered was that R8brain added about 2 seconds of silence to the front of the track. I don't know if this is what is causing your current problem, but it made R8brain a no-go for me right out of the box, regardless of any advantage it might have in sound-quality over SONAR, or the convenience of batch processing.

Brundlefly, that's interesting... that r8 adds so much silence to the front of the track. I can't say I've specifically noticed that.... that could be because I've not made any direct file to file comparisons of pre and post versions of the same file. But something like that would account for what I'm seeing in some of my post-conversion clips.

What I did was, I used r8 to batch convert all the files in the project, keeping the file names the same, and then opened an exact copy of the original cwp file (this was all in a new folder; I've still got my 96 audio intact.) Except for the handful of files that r8 complained about converting (which I posted about here: http://forum.cakewalk.com/tm.asp?m=1374926&mpage=2&key=� ),
the new project found all the files without any problem. But in a small number of cases, the clips played the wrong region of the referenced files... and the 2-second padding you mentioned could account for that. But in most cases this wasn't a problem. I haven't checked to see if all the problem clips referenced the same file, but some of them did. This was also when I encountered the problem I posted about at the top of this current thread. Other than that, the projects played fine... the clips were all positioned correctly and exposed the correct wave regions. But it wasn't as smooth a process as I'd hoped for... without batch processing it would have been way too tedious. And the return on investment -- in the form of reduced CPU load going from 96 to 44.1 -- was surprisingly slight.

Maybe we're just not supposed to tamper with such things?

bitflipper
You'll get this message if the clip has been modified outside of SONAR in such a way as to change its length.

Any message with the word "corrupt" in it sends chills, but it's really not as scary as it sounds and is no cause for alarm.

Hey Bit--
 
I know your reply was a million years ago, but do you know how to find which file is generating this error? I agree it's not a biggie, but it is a little annoying each time I open a project.
 
Thanks!

I do have a lot of tracks, and each track may have multiple take lanes--so, I guess it doesn't bother me that much. As I get to the end of the project and start cleaning up each track before mixdown, I know now to look for the no wave form track as the possible culprit.
 
Thanks!