The files I recorded yesterday are 5 hours and twenty minutes long.
 
When I import them into Sonar, I only get 1 hour and 11 minutes.
 
What's up?
 
This is the file size of each WAV
5.15 GB (5,531,900,582 bytes)
24/96
 
When I play back the files in VLC Media Player, I can hear the complete files.
 
I can send the files to anyone who wants to help using Gobbler.

Only way I can find to deal with this issue is to play back the files 1 at a time and loop back the audio through the interface and re-record it into Sonar.
 
Can this possibly be true?
 
I've started recording the files into Sonar, I just can barely believe it. Maybe I should use Ardour to cut the audio up into little chewable bites for Sonar. That might work faster than playing it all back through the interface and lining it up again myself because Sonar chokes on the files.

Stereo files are easy to work with in a Wave Editor. I use Wave Lab. There are a few free editors that would work like Gold Wave or Wavosaur. 
 
http://www.wavosaur.com/download.php
 
If all your doing is editing the levels and chopping up a wave editor is a better tool. Most of mine will use Sonars VST plug ins too. 

@Sock Monkey
 
First, Thanks for replying! Second, I tried the 64 bit version of Wavosaur and I get an error 'Unable to Load File ...' then the file name.
 
These are mono files.
 
I could have easily saved the files at intervals during the day if I knew Sonar couldn't import files longer than an hour. I've been using Sonar a long time and I can't remember bumping my head on this constraint.
 
Or maybe I have. Hmmm. I remember one case where I had to open an RME file on a different computer and export it differently to get the 'whole' file. I remember reporting it to RME thinking that it was a bug between the two versions of DigiCheck, but now I'm wondering whether it wasn't Sonar all along.
 
 

I have found references to two wave file formats which support large files. RF64 and W64. I have read RME DIGICheck creates RF64 files. SONAR only supports W64 format. Not sure about Wavosaur. Waveshop lists RF64 as supported, I believe foobar2000 and Audacity do too. FWIW, I found the 64bit version of Wavosaur not as stable as the 32bit version but don't believe that is the issue in this case.

Thanks, Scook. I'll install Audacity on my windows box. I've had a little trouble moving the files to my Linux box b/c of file system incompatibilities for large files. I usually pass files like this using a Fat32 partition to the Linux drive, but that isn't working. I'll bet Audacity will support it.
 
Thanks for helping me through it!!

This list of file converters might help.

I've used digicheck with Sonar so many times. I guess I never noticed a need to convert the digicheck wave files before. I must have needed to. Perhaps, I was recording at lower sample rates and shorter sessions. So if I record at 48, maybe the session can be 2 hours and 20 minutes long before Sonar starts ignoring the extra data. I'm not sure. Strikes me as strange that Sonar imports of lots of the data without issue, but then stops before reading to the end of the file.
 
Currently, I'm trying to export the files as FLAC 24 from Audacity and import them into Sonar in this format.
 
Does Sonar have to pay extra to support RF64, kinda like MP3, where most people don't need it and it would bump up the cost of the program for everyone?
 
I haven't noticed a way in RME DigiCheck to export the files as anything more specific than single channel wav files.

W64 is the better of the two formats, which I assume is why Sonar supports it. From Bjorn Roche's blog:

• 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.

Sonar will not import the FLAC files I've exported from Audacity.
 
I went to install one of the apps in the list that Craig posted, but it wanted admin privileges, and it is my DAW. I'm starting to get nervous. I only record 2 files so in 11 or 12 hours, I play the audio into Sonar.
 
It will work and I don't have to worry about what strange things I've installed. I'm not worried about Audacity, but I just don't know... I'm a nervous nelly when installing stuff.
 
Thanks for the help. I'm going to take the long route and hope that Sonar supports RF wave files soon.