Samuel540
 
Well, I've already settled it. It's definitely the bit rate.
I've experienced this issue a couple times before in the past but never knew why. I've recently ran into the problem again so, I decided to experiment with it. The confusing and very frustrating part of it was trying to understand why the audio file was being imported as a loop in SONAR, but when dragged into FL Studio and Ableton Live, the audio file was imported as normal. No weird, sped-up tempos etc.. 

Something is telling the file to have transient markers, and SONAR sees them. Perhaps other programs convert on the way in, or don't "see" that data so it gets stripped off.

Anderton
Something is telling the file to have transient markers, and SONAR sees them. Perhaps other programs convert on the way in, or don't "see" that data so it gets stripped off.

I wish SONAR did the same as the other DAWs and saved me the stress. #NoMoreStressFromSONAR

Samuel540

Anderton
Something is telling the file to have transient markers, and SONAR sees them. Perhaps other programs convert on the way in, or don't "see" that data so it gets stripped off.

I wish SONAR did the same as the other DAWs and saved me the stress. #NoMoreStressFromSONAR

I don't know for sure where the issue lies, but the header on the file you have appears to be different from a typical Acidized file. This reminds me of the thread where someone complained about SONAR having a "serious bug" because it couldn't export floating-point files into the FLAC format without artifacts...and then someone pointed out that FLAC doesn't support floating-point. 
 
Only SONAR and Acid Pro allow creating and editing Acidized files from scratch. Maybe one man's stress is another man's flexibility . 

Anderton 
Only SONAR and Acid Pro allow creating and editing Acidized files from scratch. Maybe one man's stress is another man's flexibility . 

Touché!  

Actually I agree that SONAR's "you can do anything" philosophy presents its share of difficulties. For example consider how many people find the Export dialog confusing...which it is. But, it also means you can handle all kinds of export scenarios, including esoteric ones. One could counter "but doesn't saving presets solve those kinds of issues?," however, you need to know what a preset should be...which means you need to know what all the export options are anyway.
 
Ultimately I think something like Lenses is moving in the right direction. All DAWs have increased their capabilities to the point where many (most?) people find them difficult and confusing to learn. I think the "final frontier" for DAWs will be how to simplify them and also, "suggest" to the person what to do instead of depending solely on the user knowing exactly what it is they want to do. Artificial Intelligence could be of tremendous help here...but we're not there yet. 

User friendliness is kind of a subjective thing. Personally, I don't find the Export dialog confusing, but the "gotcha" for me has been having a section of a track selected (usually off-screen) because of an edit or looping a part. Not really a big deal, since it's obvious what the problem is when my export only takes a few seconds. But I do think there's room for improvement there, and I believe Noel said they're looking at some changes.
 
To the OP's problem, I'm seldom surprised when an export from any program doesn't work as expected in another program. It's a pretty rare occurrence, though.
 
Not sure it would make a difference, but I would have turned of the 'Save ACIDized' and 'Save slice markers' options (as I mentioned in post #10) and re-exported. Dunno why you would leave those on if you don't want your file to time-stretch/loop.

I hadn't noticed that "Save Slice Markers" was a separate entry. I'd bet that's the source of the problem. Saving an Acidized file automatically saves any needed slice markers. Perhaps the "Save Slice Markers" option is for those who want to convert the WAV into a REX file or something...

Anderton
Actually I agree that SONAR's "you can do anything" philosophy presents its share of difficulties.
 
Ultimately I think something like Lenses is moving in the right direction. All DAWs have increased their capabilities to the point where many (most?) people find them difficult and confusing to learn.

 
Maybe SONAR can work on that a teenie bit?! The die-hard users are pretty much here to stay but what about the new users?! I wonder how the other SONAR skews like Artist and Professional compare to Platinum beyond the typical track limitations or plugin limitations... maybe certain other technical aspects of the program can be omitted as well, and some of those discouraging quirks can leave along with them.

telecharge
Not sure it would make a difference, but I would have turned of the 'Save ACIDized' and 'Save slice markers' options (as I mentioned in post #10) and re-exported. Dunno why you would leave those on if you don't want your file to time-stretch/loop.

The thing is, I didn't have those options (Save slice markers or Save ACIDized) turned on when I exported the wave file because I was going to use the file in Ableton Live and that's where I will do all my looping and time-stretching.
As it turns out, it seems the issue of the clips being embedded with slice markers, comes from Edison (FL Studio's audio editor). It seems as though Edison embeds slice markers by default.