What bit depth to change existing bundle files to?

Author
Post
Essentials Only Full Version
fableeq
Max Output Level: -90 dBFS
  • Total Posts : 7
  • Joined: 2011/10/27 08:26:19
  • Status: offline
2011/10/28 11:07:56 (permalink)

What bit depth to change existing bundle files to?

OK, thanks to the wonderful Cakewalk community I figured out the problem with the old bundles. Multiple bit depths rates on audio clips in the same bundle file is the culprit. Now the next question. If I have to go thru and change the bit depths on those files, what rate should I go for. The files will go on new I7 laps with MOTU Ultralite Hybrid mkIII interfaces. Just horn parts and back vocals to go along with midi tracks for use in live performance situation. Were originally recorded at 16 bit but did some processing on some of them and that is what changed them to 32 bit. Many thanks for any opinions on this matter.
 
Lee Q.
#1

4 Replies Related Threads
    Beagle
    Max Output Level: 0 dBFS
    • Total Posts : 50621
    • Joined: 2006/03/29 11:03:12
    • Location: Fort Worth, TX
    • Status: offline
    Re:What bit depth to change existing bundle files to? 2011/10/28 11:53:37 (permalink)
    Hi Lee,
    I didn't know it was possible to have multiple bit depths in a single project.  how did you discover that was the case?

    inside sonar projects, I always use the highest bit rate available.  for sonar 6 or 7 I think 32bit was the highest possible (though I could be remembering wrong).

    the bit depth for projects shouldn't be reliant on the soundcard interface, tho.  you can use internal bit depths of up to 32 (or 64 in later versions of cake).  the soundcard is only capable of recording at 16 or 24, but then sonar will automatically convert them to the bit depth you have chosen for projects as they are recorded. 

    if you're using these projects for backing tracks for live performances, however, I'd probably stick with 16bit or 24bit, depending on the output requirements for anything else you're using on that MOTU.  if you're ONLY using the sonar projects as output to the MOTU, then sending the LINE output of the MOTU to the FOH, then you probably can get away with 24bit projects sent to the MOTU.  however, if you're mixing any other inputs in the MOTU before going to FOH, I might go with 16bit, depending on what the other inputs are.  if they're analog, then maybe 24's OK, but if they're digital, (SPDIF) you'll need to match that.

    http://soundcloud.com/beaglesound/sets/featured-songs-1
    i7, 16G DDR3, Win10x64, MOTU Ultralite Hybrid MK3
    Yamaha MOXF6, Hammond XK3c, other stuff.
    #2
    fableeq
    Max Output Level: -90 dBFS
    • Total Posts : 7
    • Joined: 2011/10/27 08:26:19
    • Status: offline
    Re:What bit depth to change existing bundle files to? 2011/10/28 12:24:17 (permalink)
    I opened one of the old projects on the old computer and looked at some of the clip's properties and found out on the ones I processed with V-Vocal for tuning purposes, the clip was 32 bit. On a nonprocessed horn clip, it was at 16. So thats where I think all the problems came from. Of the 51 bundles, 17 were error free and when I loaded some of those, they had very few horn or vocal clips and had no processing done on them (sometimes I guess I can sing and play in tune LOL). When I load a bad file in safe mode on the Win7 comp, some of the clips looked like unrecorded clips (straight line no waveforms). When I checked these against the old bundles on the old computer, they corresponded exactly with the clips that had processing on them. I think I will drop all back to 16 bit. Any opinions on which dithering option to use?
    #3
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re:What bit depth to change existing bundle files to? 2011/10/28 12:50:19 (permalink)
    I'd be surprised if having mixed wordlengths was really the problem. More likely it was simply having a V-Vocal clip in the bundle. I know that having AudioSnap-enabled clips are (or used to be?) a problem for bundle files; maybe they have a similar issue with V-V clips. I'll bet you could just bounce those V-V clips to solve the problem.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #4
    fableeq
    Max Output Level: -90 dBFS
    • Total Posts : 7
    • Joined: 2011/10/27 08:26:19
    • Status: offline
    Re:What bit depth to change existing bundle files to? 2011/10/28 12:59:43 (permalink)
    All of the clips were bounced and for whatever reason, every clip that I had processed and bounced was at 32 bit. Any clip I didn't touch was at 16.
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1