[Solved] Sonar importing audio file in wrong key. It's nuts!

Is biab using the same audio driver? You may have a sample rate conflict.

And a lurker (that's me) learns something new!

And just as an aside to this,, isn't it better to import BnaB as midi and use Sonar's better quality midi playback synths??? Last time I messed with BinaB it used sort of wavetable style synths... 

Noel Borthwick [Cakewalk]
I've imported waves from bb and never had this issue.

But Noel - did you sign up for the BIAB membership? I think in their "Toronto" update, they added acidization metadata to WAV files. 
 
[kidding!]

Cactus Music, if you haven't tried BIAB for a while take another look. They have some pretty fantastic real audio tracks that are played by great players incorporated, not just midi files and wavetables. It's impressive and I'm glad I took another look after all these years. Wish I had looked sooner. It's those real audio tracks that I was importing, and it would be a giant step backwards to convert it to midi to use soft synths. Take a listen some time.

EFaaT
Noel, I've never had this problem importing audio ever. And I've never used groove clips so why is the default key C, instead of "none?" Seems like something the user should set.

I can't speak for Noel, but I'm pretty sure Project Pitch relates only to Groove Clips/Acidized files. If it's set to "none," clips will import at their native pitch so regardless, Project Pitch will need to be set to something. With a default of C, given that many loop libraries are in C, the odds are somewhat better that the groove clips will work as expected than if none is selected.

Wow, this happened to me yesterday and I thought I was going mad!  I didn't even feel confident to post about it! Thanks to Thom, the OP!
 
Since BIAB introduced RealTracks and the facility to drag WAV instrument parts - either straight into Sonar with both BIAB and Sonar open, or by first dragging to BIAB's parking area then to desktop - this transposition has NEVER happened to me and I've done it scores of times. It happened to me this week and I couldn't understand what the heck was going on. There is absolutely no doubt in my mind that this problem has only just arisen, either through a change/fault in Sonar recent update(s) or BIAB's latest 2016 release. BIAB's WAV files are not groove clip files by default when brought into Sonar, they are straight WAVs.
 
When this first happened yesterday I went to my Desktop and played the WAV in Windows Media Player to check it. Unsurprisingly it was ok, so BIAB is not at fault. As soon as I dragged it into Sonar it was automatically re-pitched. And I say again, this 'feature' never existed previously in Sonar.  Why should it? Surely, when dragging a WAV file into a track the default MUST be to not change it in any way?
 
Am I missing something? How can I stop this wrong behaviour?  If I have to always in future re-pitch all clips by going into the Inspector then this is in my mind an unwanted feature at best or a bug at worst.
 
 
   

Skyline_UK
BIAB's WAV files are not groove clip files by default when brought into Sonar, they are straight WAVs. When this first happened yesterday I went to my Desktop and played the WAV in Windows Media Player to check it. Unsurprisingly it was ok, so BIAB is not at fault.

 
Unsurprising yes, but the correct reason for it being unsurprising is that Windows Media Player does not recognize metadata and will not transpose files. That experiment tells us nothing about BIAB or SONAR, only Windows Media Player. However the BIAB web site does tell us something about BIAB's new features for 2015:
 
"You can now write Acidized information to the audio file." 
 
FWIW it now supports Apple Loops too.
 
Your problem is not with SONAR, which is simply following instructions given to it by the BIAB file. Your problem is figuring out how not to write Acidized information to your BIAB audio files. Until you do, in SONAR set Project > Set Default Groove Clip Pitch to "none" so SONAR will ignore whatever you're accidentally telling it to do.
 

As soon as I dragged it into Sonar it was automatically re-pitched. And I say again, this 'feature' never existed previously in Sonar.

 
Absolutely not true, the ability to recognize Acidized metadata and transpose pitch as instructed (as well as conform to tempo) has ALWAYS existed in SONAR, starting with version 1.0. Later it did the same for REX files. It's BIAB that's changed, with a 'feature' that at least according to their own web site never existed previously.
 

Craig, Noel, and everyone in between, this is all brand new to me. I'm glad to learn this. I don't think this can be classified as a "fault" of either program. Now that I know this, I like it. At least I know it can be corrected in Sonar. I'm going to investigate with the BIAB folks whether exporting with metadata can be turned off. Or not. But either way, knowing that Sonar has the feature flexibility to deal with it is comforting and all is well.
 
Thanks to everyone for the comments...