Problem Importing Wav Files

• Wave64, aka Sony Wave64, originally developed by Sonic Foundry before 2003, is an open standard and a true 64-bit format: all 32-bit fields are replaced with 64-bit fields, and all chunks are 8-byte word aligned. Instead of the dreaded FourCC it uses GUID. Other than that, it is pretty much the same as WAV, so the spec is barely 4 pages long, although in my opinion it could stand to be a bit longer, as many aspects of WAV are so poorly devised it really wouldn't hurt for someone to put it all in one place. Some people have criticized the use of GUID on the grounds that there will never be that many chunks, but this misses the point: the point of using GUIDs is that anyone can define their own chunk without having to check with Sony or register a chunk ID. It's actually rather clever.
• RF64 was proposed in 2005 by the EBU with full knowledge of Wave64. Although the proposal stated basic requirements that could have easily been met by a few minor extensions to Wave64, and they stated a desire to "join forces" with the developers of Wave64, they made no effort to do so other than to say they hoped they'd be involved. Moreover, the same document proposes RF64 as an alternative, incompatible 64-bit extension to the WAV format. Unlike Wave64, RF64 is not a true 64-bit format. All existing "chunks" remain 32-bit, so, for example, markers, regions and loops will no longer work past a certain number of samples. Even EBU's levl chunk will not work with RF64 because it uses a 32-bit address for pointing to the "peak-of-peaks" in the raw data. RF64 offers the much made-of promise of backwards compatibility via a "junk chunk", but, of course, this is possible with Wave64 as well, as pointed out in the Wave64 spec.

gswitz
 
I'm just bummed that I can't even import the files because Sonar isn't reading to the end of the file. It imports a bunch of it. It just bags out before it gets to the end.
 

Anderton
So basically, the reason why Sonar isn't reading to the end of the file is because the RF64 specification can't communicate to Sonar that the end exists.

scook

Anderton
So basically, the reason why Sonar isn't reading to the end of the file is because the RF64 specification can't communicate to Sonar that the end exists.

This is a little backward. The reason SONAR is not reading to the end of the file is because SONAR does not understand the format, not because the RF64 specification or the audio file has failed in any way. At least from what I can tell from the info in this this thread.

scook
Rather than confuse the issue with a discussion of the merits of W64 vs. RF64, determining EOF does not appear to be a problem for programs supporting RF64. Maybe someday SONAR will support RF64 import. Until that time, a third party utility is necessary for converting RF64 files to W64.