bitflipper
Ozone probably can't deal with 64-bit audio, but you don't want to go all the way down to 16 bits. Export it at 32 bits, no dither. Then just check the MBit+ box in Ozone to use its own dither algorithm.
 
BTW, there is no benefit to rendering at 64 bits within SONAR. You're just burning up twice the disk space for no benefit. Set your render bit depth to 32.

That would probably explain my diminishing disk space.... Thank you Mr.

keneds
What My initial approach was before I opened this post was to open a fresh project and call it "masters". Each track (or song, wave file) would have its own instance of Ozone loaded into it because each song has its own needs ( let's just say it's a ten song project ). I would solo the song I'm working on and mute the others. Once all are done......I would bounce all songs to a single stereo track, gap accordingly, and convert that "Album" track to a wave file @ 16 bits. Is this a suitable way to do this? I just want to start out in the right direction from the start, that's why I come here to pick up pieces of the knowledge that is here.

That is what I do. I have a project with a single track for importing audio to master. On my master buss. I have a bunch of plugins for mastering and for analysis that are bypassed unless I think one or another is needed.  For example the LP 64 is the very first plugin but its bypassed. If I need it its there in what I think is the proper position. I also use the Pro Channel modules.
 
The list of plugins includes T-Racks and stereo enhancers and BBE modules and the like plus Ozone 4, 5 and now 6. Its simple to use but is also versatile.  
 
 

It can't actually record at 64 bits. All recordings are 24-bit (or 20-bit plus 4 bits of noise if you want to get picky about it) but is converted to 32 bits within SONAR by simply tacking on some zeroes. If you specify 64 bits, it just tacks on a bunch more zeroes.

Made the bit rate adjustments to 24, Nextly........final output levels between songs ( I'm doing this in stand alone mode ) the wave files are being imported @ -6 dB. With my output being set at 0 dB, I am averaging all the final output volumes between songs around -9.5 to -10 RMS with no clipping on the input and output channels. It's seems to be coming together fine, assuming I'm on the right path.

Be sure to post your results in the Songs forum when you're done, Ken. Lots of experienced songmakers there who'll happily offer advice.
 
BTW, bit RATE refers to the sample rate, how many samples per second, e.g. 44.1 KHz. Bit DEPTH, or wordlength, refers to the number of bits in each sample, e.g. 24 bits. So it's bit DEPTH that you've adjusted, not bit rate. Not to nit-pick (bit-pick?), but getting the terminology straight will help in future conversations.

Got it. Thanks for your help.

Question, Let's say I have all twelve songs completed in ozone 6. How do I send all tracks to disk ( using stand alone mode ) can I preview all of the songs from start to finish without having to manually start each song to check for proper spacing?

WOW!  You guys answered sooooo many questions I had in this thread!   Who'd of thunk it... was just curious about ozone!

After all is good at the end of working with my songs in Ozone, what are the benefits of Sony cd architect? Is it a wise purchase?

CDA can't do anything that most generic CD-burning programs can also do. However, because it's oriented specifically to audio CDs some things are more convenient. Whether or not it's worth spending a hundred bucks on depends on how often you create CD compilations.