Is anyone familiar with this message? I get it every time I open this one particular project. The project was recently converted from 96k to 44.1k. I can't find any clips that look or sound odd. But it's not really clear what I should be looking for.



I did a search, but didn't find anything.

Thanks!

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

Well I located the problem.

It was a clip that didn't have any audio data in it. That must have been the "padded with silence" part of the error message.

When I looked at its properties, on the Audio Files tab, it showed that if consisted of two files:

ProjectName etc, Edit (2).wav
ProjectName etc, Mix (16).wav

Both of those files are in the audio folder and can be opened in a new Sonar project and play fine. But when referenced for this particular clip in the project they belong to, they cause Sonar to detect "a corrupt audio region."

I don't understand how can a clip can have two wave files associated with it? I always thought a clip was either an entire wave file or some a portion of a wave file... but always just one file.

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.

The files may be due to because the clip was mixed or frozen atr one time. I'm just guessing, but it seems logical that if you freeze or bounce a clip, you would make another file for it. hope that helps
Cj

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!

Well bouncing it could do that also when reversing it. That probably explains it and its sounding correctly, so dont sweat it. Theres allot about sonar (the inner workings) that ill never understand
Cj

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.

Right. In some cases it doesn't seem to matter. 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 -- that's the "modified outside of SONAR" you mentioned.

Would be nice if Sonar had a smart conversion function, that would simply clone projects to your specified sample rate. Though I don't know how oftne that is actually done. It can be done manually... but it's a bit of a pain... and not entirely foolproof. (And I kind of like foolproof when it comes to these rarely-done processes.....)

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.