scook
SONAR has settings to run a project at 64bit depth. I have never tried.

Indeed. Never paid attention to it, as audio-interfaces that I knew of are only capable of 24-bit.
Last time I checked there were no interfaces that supported 32-bit audio resolution. The times have changed, 32-bit ADCs now are easy to find, and there are some audio interfaces with 32-bit resolution. Yes, they exist. ) Sorry for some rigidness in previous statement.

The double precision (64 bit) option for the engine is for higher precision and headroom, not to read/process 64 bit audio samples.
 

BobF
The double precision (64 bit) option for the engine is for higher precision and headroom, not to read/process 64 bit audio samples.
 

I was not referring to the 64bit DPE but the "File Bit Depth" settings in Preferences > File > Audio Data

scook
SONAR has settings to run a project at 64bit depth. I have never tried. Some audio drivers are fixed at 32bit. I suspect this is due to software mixers and effects supplied with the interfaces. Of course, this does not mean the hardware is running at 32bit.

My bro and I did some math based on the specs of the km 184 SDC microphone. Basically, there was a pretty wide range of levels for the RME UCX where all of the sound delivered by the Mic could be reproduced entirely. You can leave a ton of headroom without losing anything the Mic captures.

Thanks guys. It is misleading and hard for an analog man to understand. I'm not sure I'll ever understand MIDI. I'll just use what I can and not worry about it. BTW, I wasn't thinking of recording 64/96 or anything like that, just using 64bit VSTs. I usually try to run 24/48 but sometimes this or that says I am limited to 16/44.1
It doesn't really seem to matter.
 
Julien

scook

BobF
The double precision (64 bit) option for the engine is for higher precision and headroom, not to read/process 64 bit audio samples.
 

I was not referring to the 64bit DPE but the "File Bit Depth" settings in Preferences > File > Audio Data

Got it ... seems the 64 bit DPE would be req'd for 64 bit deep samples.  Otherwise everything gets chopped to 32 for processing.  Just trying to make sense for myself

 
Has there been anything written on Rapture Pro's folder structure ?  I've pieced together an idea from my experience installing and uninstalling Rapture Session (for instance I've seen its registry paths to various sound libraries and I presume it does something very similar to RPro as far as folders go) but it would be nice to know the finer details specifically related Pro.  Especially locations that can and can't be specified by the user.
 
What I'm most interested in is how the Rapture Classic and DimPro programs/samples/etc are merged to be used by RPro.  Does RPro copy their programs as does Rapture Session ?  If it does, then I think that you really wouldn't want to use DimPro or RClassic for any new sound development because their browsers would get out of sync with RPro's.
 
I've come to the realization that Cakewalk's intent must be to leave RClassic and DimPro behind after having merged their functionalities and program structures.  However, RSession left RClassic and DimPro's multisample folders alone, it didn't copy them like it did their programs.  Is there a way to move their multisamples into RPro's folder structure to bring everything under RPro ?  (just edit the registry, for example ?)
 

Paul P
What I'm most interested in is how the Rapture Classic and DimPro programs/samples/etc are merged to be used by RPro.  Does RPro copy their programs as does Rapture Session ? 

Yes, RPro performs the same copy process for DPro and Rapture Programs
 

Paul P
 Is there a way to move their multisamples into RPro's folder structure to bring everything under RPro ?  (just edit the registry, for example ?)

Yes. there is a registry entry for RPro
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Rapture Pro
and RSes
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Rapture Session
In these are paths to the legacy Multisample folders called "Dim Multisamples Path", "Rap Multisamples Path" and "CSC Multisamples Path"
 
IIRC, you converted everything to wave in DPro. All factory samples in RPro/Ses are flac. If the legacy libraries are installed for RPro, copying the existing DPro/Rap wave multisamples into the new location will duplicate all the factory samples.
 

scook
IIRC, you converted everything to wave in DPro. All factory samples in RPro/Ses are flac. If the legacy libraries are installed for RPro, copying the existing DPro/Rap wave multisamples into the new location will duplicate all the factory samples.

Thanks Steve.  My DimPro and Rapture Multisamples folders have more than the "factory samples" (is what that comprises, exactly, listed somewhere) since I've added to them.  Also RPro has apparently modified the factory samples ("remastered content") ?  So I'm guessing RPro has it's own Multisamples folder.  How are original and remastered versions of the same program kept separate, or are they ?
 
I can see myself acquiring DPro in the not too distant future and I would then go about merging and cleaning up everything since I don't like pieces scattered all over the place (and I'd forget about ever using Rapture or DimPro again).  Having to reconvert anything to wav isn't a big deal for me, it's just figuring out how everything fits together that's interesting me for the moment.
 
 

Paul P
Thanks Steve.  My DimPro and Rapture Multisamples folders have more than the "factory samples" (is what that comprises, exactly, listed somewhere) since I've added to them.  Also RPro has apparently modified the factory samples ("remastered content") ? 

Other than converted Rapture samples to flac, I do not believe the legacy content was altered in any way. The remastering was to address new content issues.
 

Paul P
So I'm guessing RPro has it's own Multisamples folder.  How are original and remastered versions of the same program kept separate, or are they ?

It looks like the two legacy synth multisample folders merged together with added folders for new content. FWIW, I did a full RPro install. It is possible to skip the legacy installers if you wish. The advantage to installing the legacy content included with RPro are the reorganized program folders.