thegeek
menu->global options->audio data->UNTICK "always import broadcast waves at their original timestamp"

Just came across this old thread as I was having the same problem. Had some violin tracks I had a musician record for a song and Acid and FL could open the files but not Sonar.

I tried a 'Save As' just saving again as 44.1 at 24bit like the originals but suddenly those worked. I read up a little on 'broadcast waves', still don't fully understand why these files would be recognized as them, but unticking that option made it work, cheers.

I love this forum!  
 
Had the same problem, too.  A friend/drummer just sent me his percussion tracks recorded in PT, saved as 48/24 WAVs.  For the life of me, couldn't get them to play in Sonar.  Ran across this thread, and this suggestion: menu->global options->audio data->UNTICK "always import broadcast waves at their original timestamp".  Worked beautifully, and now I'm back up and running with my project.

Thank you!!

Broadcast Waves include their original timestamps, so if a clip started an hour into the original PT session then that's where it will be placed in the SONAR project.
 

stevec
Broadcast Waves include their original timestamps, so if a clip started an hour into the original PT session then that's where it will be placed in the SONAR project.
 

Makes total sense now, had no idea what was meant by a "timestamp". Cheers.

What causes even more confusion is that if the files are placed like an hour into the Sonar timeline, when you go to "select all" to bounce something to a track, you are now going to bounce an hour's worth of not very useful silent audio.
 
A question about this crops up at least once a month in the forums. I recommended to the bakers that they make NOT import at timestamp the default. People who don't know about Broadcast Wav won't know what's wrong or how to fix it, but people who do know about Broadcast Wav will look to see if there's a way to import at timestamp.