Jump to content

Jakub

Members
  • Posts

    22
  • Joined

  • Last visited

Posts posted by Jakub

  1. 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

    Quote

    Sampling rate is not simply dropping every other sample, etc. It's actuality done by taking the master clock rate (sampling rate like 88.2kS/s) and upsampling the data to over 30 MEGA samples per second. Once it is has been upsampled to that super high sampling rate, then it's downsampled to the appropriate sampling rate.


    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?

  2. 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?

  3. On 5/6/2019 at 5:35 PM, Base 57 said:

     If a tracks interleave is set to stereo then the pan knob . So it is important to change the interleave if you want the pan to behave as expected.

     

    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?

  4. 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) .

  5. 1 minute ago, scook said:

    The DAW can work with a mix of different bit depths.

    You can't do anything to improve pre-recorded clips but you should set the record and driver bit depths the same to maintain the best resolution available for your recordings.

    So in general - using higher resolution and dithering is better than using 16 bit resolution to avoid the dithering at all,?

  6. 4 minutes ago, scook said:

    As a rule,

    • Bring clips in to a project at their original bit depth.
    • Set record and driver bit depth to the same bit depth.
    • Use 32 or 64bit render depth.
    • Dither once on export when exporting to 16bit. Do not dither when exporting at the current render bit depth.

     

    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?

  7. 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?

  8. 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?

  9. 1 minute ago, scook said:

    The log shows it was previously scanned and determined not to be a plug-in.

    Subsequent scans will not rescan the plug-in unless running a VST reset or "rescan failed plug-ins" is enabled.

    If you perform a manual scan with "rescan failed plug-ins" enabled make sure to deselect the option after scanning.

     

    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?

  10. I just installed another VST instrument form this site that is also 32 bit and it loaded succesfully. So looks like the problem is with this plugin only but as I mentioned another person loeded it into cakewalk with out any problem. Running as an administrator did not help. Same thing in a log - "VSTSCAN: Previously scanned - NOT a VST plugin"

  11. Hello. I have problem with installing this plugin in cakewalk: https://plugins4free.com/plugin/189/?fbclid=IwAR0_mfQbgAliY1mpCVoaHgMLBBIQoy7pLbkY-OfEJahnM-ERsz3il7AsnwA

    Cakewalk scans it but according to genrted scan log thinks it is NOT a VST plugin. What's even weirder I just confirmed that another user downloaded it from the same source that I did and it was added to cakewalk without any problems. Any ideas what might be causing this error? I am pasting a fragment from a scan log below.


    VSTSCAN: ---- 29: c:\pluginy vst\SaxiPlayer\SAXi103beta8.dll ----
    VSTSCAN: [ShortPath] c:\PLUGIN~1\SAXIPL~1\SAXI10~1.DLL
    VSTSCAN: [RegKey] Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/pluginy vst/SaxiPlayer/SAXi103beta8.dll
    VSTSCAN: Previously scanned - NOT a VST plugin

  12. Does it differ or is this onyl anothe way of viewing the automation line? TBH i only discovered separate lanes for automation when i was trying to paste automation line from one track to another. Instead of being shown on the track itself (like in the source track) after using "paste special" it was pasted as sepratae lane. Is it any difference? Or can i use paste special to paste automation on the track and not as separate lane?

×
×
  • Create New...