Ah, I see. The project file keeps track of the details of the file, so when you modify it outside of SONAR you run the risk of confusing SONAR, which has no way of knowing what you've done to the file.

I'd think the only way to reliably convert the SR for a clip would be to import the modified clip, in which case SONAR would note the SR and log that information accordingly. Still not a convenient solution if you have a bunch of clips to convert.

Question: why did you need to SRC an existing clip in the first place? Couldn't you just leave it at 96/24?

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?

ORIGINAL: bitflipper

I'd think the only way to reliably convert the SR for a clip would be to import the modified clip, in which case SONAR would note the SR and log that information accordingly. Still not a convenient solution if you have a bunch of clips to convert.

Indeed. And again, that's why it would be nice if Sonar could do an automated project conversion based on the user's desired project specs.

Question: why did you need to SRC an existing clip in the first place? Couldn't you just leave it at 96/24?

Well that's the thing, I was trying to convert an entire project. Several of them, in fact... 96k was pushing my computer, and a conversion seemed the easiest way to ease solve that.

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!

Hey Razor, I'm not Bitflipper but...  
   I believe the only way to tell is to open each track tall enough to look at each clip one by one. The one(s) with silenced audio will show no wave, just a line.
   Hope you don't have hundreds of clips.
 All the best.

I often get this message when I edit project waves in Melodyne standalone outside of Sonar and haven't found that it always results in a flat lined wave pic.
 
I have found that once I resave the project the message does not reappear.

It happened to me when playing with comping editing. Sometime there is quite a bit of confusion, e.g. many lanes clips to erase or to cut and paste. Sometime something goes wrong and you  miss it and close the project. When you open the project again, here the message comes. You have to search the audio clip in your last version of the project and import it.

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!