richardl Posted August 17, 2005 Report Share Posted August 17, 2005 I have a Hi-MD MZ-RH910 which will record about 7hrs 3min on a disk. I've been trying to use SonicStage 3.2 to upload these recordings to my PC. (Sometimes the transfers fail after about 50% is transfered and give me an internal error. But usually they eventually work.) SonicStage can convert the uploaded OMA file into a WAV file. But, for example, a 5 hour (Hi-SP) recording results in a 3+ GB WAV file.My Sony Vegas 6.0 audio editing software will not open the resulting 3GB+ WAV file. According to the Vegas support forums WAV files can not be larger than 2GB due to built-in limitations of the WAV file format. Sonic Foundry (now Sony) developed an extended WAV file format called Wave64 to address this limitation. But it doesn't seem that SonicStage supports Wave64. What gives? How does Sony expect you to use the huge files that you can record and upload from a Hi-MD disc? Why don't the WAV fles created by Sony SonicStage work with Sony Vegas or Sony ACID software?Thanks for any insight into this.- Richard Lawler Quote Link to comment Share on other sites More sharing options...
ROMBUSTERS Posted August 17, 2005 Report Share Posted August 17, 2005 as mentioned WAV files cannot be larger than 2GB, however what you could do is use SonicStage (or the recorder) to split the track so that the resulting two files are each under the 2GB limit, and then edit these files as you see fit, before placing them back into SonicStage to combine Quote Link to comment Share on other sites More sharing options...
ozpeter Posted August 17, 2005 Report Share Posted August 17, 2005 In fact the correct limit for a wave file is 4gb - the chunk sizes in RIFF are defined as unsigned 32-bit integers, but many RIFF handling programs (such as SonicStage sadly) considers them as signed, hence the 2GB limit instead of 4GB. FWIW. Total Recorder or Audition will handle 4Gb for instance. Quote Link to comment Share on other sites More sharing options...
richardl Posted August 17, 2005 Author Report Share Posted August 17, 2005 (edited) In fact the correct limit for a wave file is 4gb - the chunk sizes in RIFF are defined as unsigned 32-bit integers, but many RIFF handling programs (such as SonicStage sadly) considers them as signed, hence the 2GB limit instead of 4GB. FWIW. Total Recorder or Audition will handle 4Gb for instance.←But what about converting longer recordings to WAV files? Has anyone done this successfully? My MD-RH910 can record for 7.5 hours or even 35 hours. But it's useless if I can't split up those recordings when converting .OMA files to WAV files.edit:Never mind. I missed the information on dividing tracks posted above. (They really should say something about this limit in the manual or in a FAQ rather than forcing people to figure it out.)Thanks. Edited August 17, 2005 by richardl Quote Link to comment Share on other sites More sharing options...
richardl Posted August 17, 2005 Author Report Share Posted August 17, 2005 as mentioned WAV files cannot be larger than 2GB, however what you could do is use SonicStage (or the recorder) to split the track so that the resulting two files are each under the 2GB limit, and then edit these files as you see fit, before placing them back into SonicStage to combine←Thank you for the suggestion. I found the information on dividing tracks in the recorder using the T-Mark button as well as the Edit->Divide option in SonicStage. A bit clumsy, but it should work. Quote Link to comment Share on other sites More sharing options...
tommypeters Posted August 17, 2005 Report Share Posted August 17, 2005 Best would be if the suppoerted formats weren't "hard coded" so you could use FLAC (for example) that uses less space and has no 2/4GB limit. Quote Link to comment Share on other sites More sharing options...
greenmachine Posted August 17, 2005 Report Share Posted August 17, 2005 If i'm not mistaken, himdrenderer can convert directly to FLAC. Quote Link to comment Share on other sites More sharing options...
bug80 Posted August 20, 2005 Report Share Posted August 20, 2005 If i'm not mistaken, himdrenderer can convert directly to FLAC.←Are you sure HiMDrenderer doesn't decode to WAV first? It probably uses flac.exe which expects WAV files as input.By the way, I've heard a special WAV header extension exists that allows for files > 4 GB. Historically, the limit was set to 4 GB, because that's the greatest file size the FAT32 file system supports. As soon as the WAV header is altered to allow for larger files, it is no longer "standard", so I don't think himdrenderer writes it or flac.exe reads it. Quote Link to comment Share on other sites More sharing options...
marcnet Posted August 20, 2005 Report Share Posted August 20, 2005 no. The data is decoded to PCM, yes, but my program supplies the mp3/ogg/flac/whatever DLL with the PCM data as it gets it. There is no saving of wav file first. Whatever the OMA decoder returns get input directly into the mp3/ogg/flac/whatever DLL Quote Link to comment Share on other sites More sharing options...
bug80 Posted August 20, 2005 Report Share Posted August 20, 2005 no. The data is decoded to PCM, yes, but my program supplies the mp3/ogg/flac/whatever DLL with the PCM data as it gets it. There is no saving of wav file first. Whatever the OMA decoder returns get input directly into the mp3/ogg/flac/whatever DLL←Ok, thanks. Quote Link to comment Share on other sites More sharing options...
richardl Posted August 21, 2005 Author Report Share Posted August 21, 2005 (edited) By the way, I've heard a special WAV header extension exists that allows for files > 4 GB. Historically, the limit was set to 4 GB, because that's the greatest file size the FAT32 file system supports. As soon as the WAV header is altered to allow for larger files, it is no longer "standard", so I don't think himdrenderer writes it or flac.exe reads it.←Actually the FAT32 limit has nothing to do with the limit in WAV files. WAV is based in IFF and uses a 32 or 31 bit value (unsigned and signed int) to store file size and data chunk size. AIFF suffers from the same limitation.Sonic Foundry (now owned by Sony) developed the Wave64 format that they support in their apps: Vegas, SoundForge and ACID. Those programs will produce a W64 file if the file exceeds the limits of WAV.Here's the spec:http://media.vcs.de/download/content/show/04345113457(Wouldn't it be nice if other Sony audio software also supported this format?)Sony Wave64 File Format Specification Edited August 21, 2005 by richardl Quote Link to comment Share on other sites More sharing options...
bug80 Posted August 21, 2005 Report Share Posted August 21, 2005 Actually the FAT32 limit has nothing to do with the limit in WAV files. WAV is based in IFF and uses a 32 or 31 bit value (unsigned and signed int) to store file size and data chunk size. AIFF suffers from the same limitation.I know, but I've heard that, since files could not be larger than 4 GB anyway, it was decided to not change the 32-bit file size parameter. Could be wrong information, though.Sonic Foundry (now owned by Sony) developed the Wave64 format that they support in their apps: Vegas, SoundForge and ACID. Those programs will produce a W64 file if the file exceeds the limits of WAV.Here's the spec:http://media.vcs.de/download/content/show/04345113457(Wouldn't it be nice if other Sony audio software also supported this format?)Sony Wave64 File Format Specification←Ah thanks, I was looking for that. Quote Link to comment Share on other sites More sharing options...
richardl Posted August 21, 2005 Author Report Share Posted August 21, 2005 I know, but I've heard that, since files could not be larger than 4 GB anyway, it was decided to not change the 32-bit file size parameter. Could be wrong information, though.Ah thanks, I was looking for that. ←Not to beat a dead horse, but WAV was defined long before FAT32 was even a glimmer of an idea.I believe WAV's was based on the IFF file format which originated on the Commodore Amiga. WAV inherits its file size limit from the data structures defined by IFF. That dates back to the early-to-mid 1980s. FAT32 was developed as an alternative file system for Windows 98 that would be able to deal with the large hard drives that had become prevalent. Its predecessor FAT has a 2GB file size limit and a small maximum partition size. NTFS has no maximum file size limit and existed on Windows NT since the early '90s. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.