Quote:
Originally Posted by bblue
Why would you want to use RF64 (or whatever) just for large files? Shouldn't it be settable as a default for all files of that project? There's no size penalty, whether wav, w64 or rf64 they occupy the same space for equivalent amounts of time. Just set the type you want to use and go. Maybe you could have a fallback mode if set to wav and a track goes over the limit... something like that.
I just found that if FORCE RF64 is set in Project settings, basic tracks of any size WILL be recorded in RF64, but with the standard WAV extension. If you also specify Recording Format for Format for Apply/Glue, it will maintain RF64 in the new file. However, it still fails to join the items together.
Why are Markers+Regions (in Project Settings) broken out separately? How is that used?
My head hurts.
|
Some audio handling software (esp in the consumer world) can't deal with the Sony Wave64 or the EBU RF64 wav format, so you might want to only use 64-bit address-space formats for files that need it, ie very long, multichannel, or both -here you tend to be only using specialist software anyway (eg DAWs) that can handle it.
"Auto wav/RF64" is that mode for recording, it just doesn't work for glue and consolidate yet...
The standard setting for RF64 files is ".wav" RF64 is a wav file, it's just an extended address-space version of one with a 64-bit integer chunk and file size system internally.
It's not failing to
join the items together, it's failing to
not create a new file at each 2GB limit when it
doesn't need to 
Justin is on it, it'll appear in the next update or so...
Not sure what your question is about on markers and regions. They can be included in recordings and renders as cue markers and cue regions. This is entirely separate from the ones in the DAW, they are embedded into the new wav files from the REAPER positions. REAPER can read and display them as dotted lines in the items, and create new markers and reqions based on them. You get the choice whether or not they are created.
Shout back if you need this bit further explaining (I can do pictures)
>