• SONAR
  • Wav file won't load (p.2)
2013/05/17 04:45:00
carlosagm79
OH MY GOD!!!

that was the weirdest issue ever I had with Sonar!!!!

so stupid (ignorance)

But obviously somebody at cakewalk have to fix or workaround that!!!
tons of wavefiles and samples simple wont load as you spected!!!!!!!!
2013/05/17 04:56:24
Kalle Rantaaho
OTOH,  it is quite logical, that an audio clip gets imported at the time stamp it includes. When you are assembling a project sent to you as separate wav-files from another DAW, it's the obvious way. Then again, I've never done that, so I have no first hand experience of the reliability of the stamps.
The key question, IMO, is, why does a commercial wav-sample have a time stamp that positions the file beyond the horizon?
No workarounds are needed, just uncheck the option.
2013/05/17 08:15:12
scook
I cannot see how this is a Cakewalk problem, this is the fault of a few loop vendors. Why would vendors ship loops as broadcast waves? The timestamps would be of no value.
2013/05/17 08:47:59
John
Chasmcg


 Kalle, looks like you were right about the "Import Broadcast wav at their timestamp." Thanks. 

jb101, thanks so much for showing me where the above is located.
 
One other thing, without your help on this matter, how would a person know to uncheck  "Import Broadcast wav at their timestamp?" This seems like an important issue that needs to be addressed by Cakewalk. Especially when FL Studio and Adobe Audition have no problem with the file. I could have looked for eternity for a solution without you guys.


The dots are telling you that something is there. 

Scook
I cannot see how this is a Cakewalk problem, this is the fault of a few loop vendors. Why would vendors ship loops as broadcast waves? The timestamps would be of no value.
I totally agree. 

2013/05/18 08:24:55
Guitarhacker
If you see dots in the track view... the file DID import but, it's much further to the right side of the track. 

Use the zoom function to zoom out on the track view and simply click it and drag it back to the start. 

I had that happen a few times importing waves and didn't realize the wave was waaaaaaaaayyyyy out on the time line.  Once you know about it, it just becomes a nuisance.... easy to remedy. 

This very thing happened to me recently on importation of several tracks for a remix from another studio.  Several imported just fine to the start of the time line, and the rest were way out on the time line. 
2017/07/23 09:06:56
lingyai
Thanks to those who posted the solution.
 
carlosagm79
OH MY GOD!!!

that was the weirdest issue ever I had with Sonar!!!!

....
But obviously somebody at cakewalk have to fix or workaround that!!!
tons of wavefiles and samples simple wont load as you spected!!!!!!!!



I totally agree, and wholly disagree with those above saying this is not a Cakewalk problem. How the hell is anyone supposed to know that the dots mean (in my case) mean that a 76 bar audio file (just a wav file rendered from Logic), inserted at time 0, like hundreds other wav files I've imported into Sonar previoulsy with no problem, is there, but this time, starts at bar 1795?
 
Don't blame Logic or loop vendors; Sonar looks like the odd man out here,  because Studio One, MuLab, Adobe Audution and even 10 year old Acid Pro know to import it at the designated point (i.e. time 0:00:00).   That is just incredibly non-obvious. One shouldn't have to turn to a forum to figure this out. This, four years after the original post. Gosh, what a thing to leave out of the "continuous improvment" agenda which is the basis of the SPLAT sales pitch.  
 
To say this is normal is to be in denial.
 
 
 
2017/07/23 09:56:13
Kalle Rantaaho
Yes and no... If there's a time stamp in the audio file, and SONAR is told to obey it, then it should be positioned according to the time stamp. How else?? That is how exported (broadcast)wavs of a project for example, can be automatically positioned correctly when transferring stuff between DAWs. 
 
Then again, the wav you rendered from Logic, how did it get a time stamp for bar 1795? Was it your original recording or an imported one (or partly imported)? Could it have (or one of its elements) a time stamp, and Logic
was set to ignore it as default, but it was included in the Broadcast Wav? Of course, there can always bve bugs...
 
"How the hell is anyone supposed to know that the dots mean..." I'm almost sure the manual tells most of those details.
2017/07/23 14:11:50
chuckebaby
lingyai
 
One shouldn't have to turn to a forum to figure this out. This, four years after the original post. Gosh, what a thing to leave out of the "continuous improvment" agenda which is the basis of the SPLAT sales pitch.  
 
To say this is normal is to be in denial.




If you want to bump a 4 year old thread at least come prepared.
 
Seriously,
This was changed/fixed over a year ago (Broadcast waves is no longer the default) 
Not sure what version you are using but obviously not the latest one.
 
Sonar Platinum: If you want SONAR to import Broadcast Wave files always at their timestamped location, go to Edit > Preferences > File - Audio Data and select the Always Import Broadcast Waves At Their Timestamp check box. Otherwise, set the Now Time and current track to indicate where the audio should be placed.
 
They even added a shortcut: Note: When importing Broadcast Wave files, you can hold down the SHIFT key to temporarily toggle the behavior of the Always Import Broadcast Waves At Their Timestamp global option.
 
Kind of sounds like "continuous improvement" to me.
Are you still on the Hopkinton update ? (I see in your Sig) That's an old update man.
Hope this helps.
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account