• SONAR
  • [Solved] Mixing down error (getting .w64 rather than .wav
2016/11/27 10:40:34
Brian Johnston
Trying to find out what I did wrong (what I clicked).  I used Sonar for a few years and no problem.  This time, on a particular song, I mix down and it saves it with a .w64 extension (Sony wave).  This is NOT selected when I export... I am selecting a regular wave format.  I even de-select 64-bit (which was fine in the past) to make certain that was not the culprit.  Still no luck.
2016/11/27 11:05:33
scook
How large is the exported wave?
2016/11/27 11:14:46
Brian Johnston
I get two files... a wave file with 0 bytes... then a w64 file that's about 9 megs.
2016/11/27 11:23:49
bitflipper
So the file that's saved does not have the name you gave it in the export dialog?
 
That would seem to be impossible. If you type in "XYZ.WAV", SONAR will use that file name, verbatim, assuming you've also chosen "Wave" as the file type.
 
Even if the selected file type is incorrect, SONAR will use the file extension you entered and switch to the appropriate format. For example, if you intentionally select w64 as the file type, but enter "XYZ.WAV" in the file name textbox, SONAR will automatically change the type selection to "Wave". It does this so that the file extension always indicates the actual file format.


Here's a thought...are you sure that the .w64 file you're looking at is actually the one you just created? By that, I mean if you manually delete it before re-exporting, is the .w64 file then re-created? I have inadvertently exported files to the wrong folder before, and was then surprised when I listened to the exported file that it was an older version.
2016/11/27 11:36:06
Brian Johnston
I get two files... both with the same name... one with a .wav extension and the other with a .w64 extension.
2016/11/27 11:42:18
Brian Johnston
OK,forget what I said.  It not only takes forever to convert to wave (and there is no added file information past a certain point), but the finished product is 7.3 GB.  It's a massive file, whereas my other songs would convert to about 30 MB (for example).  This is only a 4.5 minute song...maybe 10 tracks.
2016/11/27 11:49:26
scook
There may be data beyond the "end of the song." Automation nodes and MIDI data are the usual suspects. Either use a time range selection for export or clean up the data past the end of the song.
2016/11/27 12:31:14
Brian Johnston
Scook, you are right.  I looked well beyond and there was nothing there... but 7 hours later (no kidding) there was something pasted. How the heck that got pasted way over there is beyond me, but it did.  That fixed that problem.  I then selected Microsoft Wave and it's OK.  Before I only had to indicate 'wave' when exporting.  Regardless, I got a finished product.  Thanks to those who replied.
2016/11/27 12:33:41
chuckebaby
Brian Johnston
but 7 hours later (no kidding) there was something pasted. How the heck that got pasted way over there is beyond me



You imported something without having Broadcast timestamp enabled.
2016/11/27 12:39:04
scook
Other way around, a file was imported with Preferences > File > Audio Data "Always Import Broadcast Waves At Their timestamp" enabled. This is the default setting.
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account