Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello Rogerio. I tried to use Your scripts, downloaded both files into the same directory and when I run the main script I am getting such error: What am I doing wrong?
  2. Hello. I am looking for some tips about downsampling material recorded in 48 or 96hz sample rate to target CD 44.1hz. My interface does not work with 88.2hz sampling rate (has only fixed 44.1, 48, 96 and 192). I read some mixed information about integer vs non integer ratio with downsampling. As I do not have a possibility to record in 88.2 integer downsampling to 44.1 is not possible. However I also read that modern downsampling use complex algoritms so the integer vs non-integer thing is no longer relevant (one quote I found : So - can we generally say that in Cakewalk by Bandlab it is safe to downsample from 48 or 96 to 44.1 and we should not have any problems/distortion etc. due to ratio of two sampling rates being non-integer?
  3. Hello. I have some questions about the upsampling for plugins (x2) option in CbB. What exactly is the difference between Upsampling On Render and Upsampling on Playback . I suppose that vith VSTi that are generating audio tracks fro midi tracks it would mean that I will hear the effect of the upsampling only after freezing the midi track and generating audio track from it? But how does it go with plugins that are operating on already recorded/rendered audio tracks? Should I check Upsampling On Render or Upsampling Playback in such case. Another question is if the upsampling can cause conflicts with my interface. According to manual my interface supports 44.1, 48, 96 and 196 sample rates. I usually work with 44.1 so the x2 upsampling will result in 88.2 khz sample rate which my audio interface does not support. Does it mean that i should not use that option at all in 44.1 projects and need to use 48 projects?
  4. Hi, could You elaborate this topic a bit? what does "acts as a balance control" mean. What is the exact difference of how pan knob works with interleave button set to stereo vs set to mono?
  5. S o i think a final question for now :D. Should I dither multiple times? Consider such situation - I have a project made of different clips - some in 16 bit, some recorded in 24 bit and some from rendering in VST are 32 bit. What would be the best way to handle this: 1. Mix it down to 24 applying dither and then after mastering this 24 bit file export to 16 bit for CD with dither again? 2. Maintain the highest from all clips resolution for mastering, so mix down whole thing to 32 bit file, do a mastering on it and then export to 16 and only then dither. 3. Mix it down to 16 right away, with dithering, do a mastering and then export it to 16 again (of course no dithering this time as bit depth stays the same) .
  6. So in general - using higher resolution and dithering is better than using 16 bit resolution to avoid the dithering at all,?
  7. Ok, that helps a lot but about" Set record and driver bit depth to the same bit depth." I assume drvier depth can be higher? I often use 16 bit clips and as I said the driver depth is stuck at 24. Also - if my final master will be a 44/16 one can I record at 16 bit on low level to not exceed the headrom? Also- Did I get it right that when render depth is set to 32 it creates 32 bit wave files while freezing but later they are autho dithered during export, right?
  8. And let's assume that I have some pre recorded audio files in 16 bit as clips in a project and the target master should be red book 44/16 as well. If I plan to add to this pre recorded files some audio tracks rendered from vst instrument is it better to change the default render depth to 16 or leave it at 32 and dither when exporting the whole thing to single track for mastering to be done?
  9. With my interface (using its native asio driver) the driver bit depth is set to 24 and cannot be changed. Is it normal? What can be the problems if I record with different bith depth (either lower or higher)?
  10. Hello. By default in Cakewalk all rendering is done in 32 bit. So frozen tracks created with VST from midi will have 32 bit depth. Recording AFAIK always has the bit depth declared when creating project (the one that is shown in top panel under project sample rate). My question is - should I have all clips in project set to the same bit depth? And, if some have for example 32 bit and other 16 bit and the final depth of mixdown is going to be 16 should i use dithering?
  11. You are all right and although I found a subsitute what bothers me is that another user did run it so clearly something is wrong with my CW configuration.
  12. I'll try to dive into it more later. Maybe in the meantime some one will get another idea here. Will use another sax VST for while i guess. BTW here is a log from the guy that managed to load it: https://imgur.com/a/g4PU5wp
  13. I did the steps above but the result is exact the same. Log still says "previously scanned" although "rescan failed plugins" was checked.
  14. So to be sure - now i should: 1. Run Cakewalk as an administrator 2. Select "rescan failed plugins" in plugin manager options 3. Do a manual rescan?
  • Create New...