foobar2000 claims to read RF64 and write W64. So does Waveshop. Both are free and I believe they do not require elevated privileges. foobar2000 is primarily a playback tool, Waveshop is an audio editor. While I have used both program I have no experience with RF64 to W64 conversion.

Anderton
W64 is the better of the two formats, which I assume is why Sonar supports it.

Craig, I totally understand that Sonar has to pick it's battles and for it's own recording it makes sense that it uses W64.
 
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.
 
The hassle for me is non trivial, although similar to exporting files from my old Tascam recorder. It's basically a real time export, one file at a time.
 
If it really starts to bug me, I'll find another way. I'll bet there are other ways to do this. Right now, I just want access to my recordings.
 
And yes, I'm disappointed that I'm inconvenienced by this. I'm not usually. In the future, I'll just stop and save progress at short intervals.

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.
 

It appears to be importing the initial 32bit chunk of the file and has no idea there is more data.

scook

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.
 

It appears to be importing the initial 32bit chunk of the file and had no idea there is more data.

That's the problem with RF64. It's not a true 64-bit standard; as it says in the blog post quoted above:
 
"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."
 
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. Why the EBU chose RF64 over the Sony format, which is open, free, works better, and was introduced prior to RF64 remains a mystery...other than the usual "not invented here" syndrome.

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,
Using Wave Shop I've managed to convert them to W64.

Thanks for your help (and Everyone Else)!
 
I'm back working way sooner than I would have been otherwise.
 
I'm very grateful.

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.

You could very well be right, but what I got from Bjorn Roche's post is that the 32-bit format for the chunks limits the ability of the format itself to express markers, levels, loops, etc. past a certain number of samples. It seems that might be related to Sonar being able to work with only a certain number of samples. 

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.

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.

Agreed, but I do think it's important to mention that if you work with large files and have a choice between W64 and RF64, you're probably better off choosing W64. I've been using it since it was introduced for Sound Forge and have found it to be a pretty universal answer.

My bad. I thought DigiCheck could export W64 files because I got a lot of google hits on W64 export RME. But on closer inspection, they were threads by people who were looking for ways to export W64 files from DigiCheck, or had written format translation routines because they couldn't open files in Wavelab, Nuendo, etc.