[Rwp] wav files and file size limits and things and stuff

[Patrick Perdue]

Not really. The only thing stopping a wave file from being larger than 2GB is the wav header itself, not the data. Reaper can just work around that. It’s cool like that.
I have opened huge contiguous files in Reaper before (accidentally once created a 28GB wave file) and it worked fine.

> On Nov 3, 2015, at 6:14 AM, Chris Belle via RWP <rwp at bluegrasspals.com> wrote:
> 
> Reaper must use a proprietary form of wav file when you render bigger wav files than will fit
> in the wav file limits.
> 
> I think that is just over 2 gigs.
> if I remember right.
> 
> Because I had a situation where I had a wav file which would not open in sound forge.
> Soundforge does the w64 format,
> but for some reason it wouldn't open a two gig plus something wav file,
> so there must be several ways of packing 64 bit wav files, other than w64.
> 
> Because the extension never changed, with sonar when you export a huge file they change to w64,
> and sound forge knows about that but reaper does something different.
> 
> Probably old hat for you
> old timer repaerarians,
> but this is new to me.
> 
> Reaper nicely records everything in 1 gig chunks,
> at default, so it's not a problem to use the pieces, but when you want to export a large hunk, then so far I've just exported in sections and stayed under 2 gigs.
> I'll have to dig through the manual to see if it says anything about this, I didn't see anything when I looked at rendering the first time,
> in the user guide I have there's surprisingly little about technical things like this,
> and the type of dithering and noise shaping used,
> other than yes they're there and you can use them or not 'smile'.
> 
> 
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp