Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

Recent Profile Visitors

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

  1. It's been awhile. I haven't thought of turning it off until recently as I noticed my plugs scan was taking longer. So I went to where I remembered the tick box used to be and didn't find it. Thanks, I appreciate the replies.
  2. Looking for the on/off VST scan switch.....There used to be a tick box to turn off auto VST scanning upon startup in the Plug-in Mgr, but I haven't found it in CWbBL. I did find VST settings in the Edit/Pref menu, with 3 options - Auto Background Scan, Scan on Startup, and Manual Scan. Mine is set for Auto Background Scan, and there's a box ticked underneath for "Scan in Sandbox" (whatever that means). Every time I start CW it scans for all VSTs. I'd like to be able to turn off the automatic startup scan, and only do a scan when I add a new VST. Is this the only, and correct place for changing this setting?....and is it the Manual Scan setting in the drop list that I need to change it to? This would seem to make the most sense, just wanted to check with you guys in case I'm missing something. Thanks, much appreciated.
  3. Yes it can! I do the same thing, make an extra copy of any vocal tracks that I have slated for Melodyne, just in case, that way I always have copies of the originally recorded vocals. I will be working with 32 bit all the time now. For awhile I was using 24 for rendering, and not long ago I had changed my audio data render setting to 16 just because that day I wanted to export without mastering, and burn a quick CD to listen to the mix in my car, then forgot to change it back to 24! Now it's at 32 and that's where it's gonna stay.
  4. Fast. I don't remember ever doing a Real-time export. After listening more closely today, and isolating that vocal track with all FX plugs turned off, the glitch is there. Almost 100% certain it was something I did in Melodyne when I edited all the vox tracks. Sometimes Melodyne will garble a word or syllable if you edit with the modulation or pitch tool and go a little too far, I've had it happen before, and then had to back off a bit to get it to sound more natural. So what I did was go back to an older version of the same project and I grabbed the original piece of that vocal and brought it into the newest version of the project. A little repair job I guess you could say. So now it's a bit better, but I still have a little smoothing to do. At least I now know it's not anything to do with a plugin or a render issue. I had a feeling if it were a render or plugin issue, more glitches would have occurred, not just on one word. I did a draft mix as you had recommended at 32bit, then ran it through the mastering software. Still a few tweaks to do, but at this point in time it's sounding pretty good. 👍
  5. thanks for the links, I'll have a read through, much appreciated!
  6. I doubt it's a CPU issue, I have upgraded my PC and the CPU meter shows it's barely working, 12 threads in all and 32GB RAM (those are old specs on my post footer, I haven't revised that yet). I do have a lot of plugins going, it could be one of the plugs I have on the vox buss. Btw, thank you for taking the time to reply, always appreciated. The stutter was just on one word, the rest was fine. It's probably not an audio skip or drop from lack of resources, it sounds more like a glitch where the word I am singing gets a little garbled for a second. Going back just now and listening again, the original vox tracks were good. The glitch can be heard on both the final mixdown, and on the master, so whatever caused it happened within CWbB on the final mix bounce. I'll see what happens tomorrow when I bounce it all again to 32 bit. You almost can't notice it unless you really listen close. I do have that lead vox track doubled, so it is possible that one word is slightly out of alignment between the two tracks. Plus the word is "sleep", so it could be a sibilance issue. I'll check a few things more closely tomorrow, I'll find what's causing it.
  7. Interesting...So even if the setting in the Bounce to Tracks dialog box is set to dither, that function will automatically remain inactive unless it detects one or more tracks will be getting converted to a lower bit depth? According to what I've read, rendering at 32 bit will create a larger file size than rendering at 24 bit, but I would think the difference would be minimal, and probably would not outweigh the quality benefit that 32 bit would provide in comparison. Related thread: I have recently noticed there are also some plugins that also apply dither, like one of my limiters has two presets which include dithering, one preset is 16bit and the other is 24 bit. I'll have to remember not to use those presets. Scook, do you think that the way I had previously rendered and mastered, not using 32 bit and dithering twice could have caused that vocal stutter on the master that I had mentioned?
  8. Alright then, so the 32 bit setting covers everything I render without the need for dithering. Thank you my friend. Does that mean even if I just bounce a couple of guitar tracks to save space, just for example, that bounced/mixed guitar track is going to also be 32bit?...(or any other smaller groups of tracks I bounce for that matter?) Ok, then NO dithering at all at any time in CWbB, and only use dithering one time in the mastering software export. Got it. I wonder why CWbB Bounce to Tracks dialog always shows the dithering setting in the drop menu by default?
  9. Scook, I don't know tons about the bit depth and dithering. But I did watch a few videos on it from another thread awhile back. I seem to remember that going from a higher bit depth to a lower one....ie...24 to 16 it is recommended to use dithering. Yesterday I realized that I had my Audio Data settings at Record = 24 and Render = 16, and I think I had changed that Render setting from 24 to 16 a while back prior to this project, and then forgot to put it back at 24. So any tracks that got bounced automatically went to 16 bit, even if it was just a couple of guitar tracks and not a final entire mix bounce. As a result I now have a mixture of 16 and 24 ( so that's how I got here) The reason for my question is because I noticed on a project that I had mastered I had a sort of a glitch or stutter on one vocal part on the master but not on the unmastered mixdown. The only thing I could think of that may have caused it was maybe using dither to export the mixdown to wav file, then again using dither in my mastering software may have been too much. I had asked someone knowledgeable who told me they wouldn't recommend using dithering twice like that, only on the final master output. In this particular project I had bounced the mixture of 24 bit and 16 bit tracks down to a 16 bit mixdown track without dithering, then when I exported that mixdown to a 16 bit wav file I used dithering, then when I ran that through my mastering software I used dithering again upon exporting there. So I basically used dithering twice, once exporting the final mix out of CWbB to wav, then again exporting from the mastering software. So am I to assume the best way to do this as far as a step-by-step is to Step 1..... first render/bounce all my tracks ( a mixture of 16 and 24 bit) down to one 24 bit track final mix without using dithering, then Step 2.... exporting that final 24 bit mixdown track to a 24 bit wav file without dithering, then Step 3.... put that 24 bit wav file in my mastering software and export using dithering to 16 bit 44,100? (The end result if I want to say burn a CD is why the 16bit 44,100 final master)
  10. My goal is to try to get my final mix at 24 bit with no dithering, prior to using mastering software on that mix. The mastering software will apply dithering at the final stage, as it will be converted from 24 bit to 16 bit. When I looked at the bit depth of all my audio tracks, some are 24 bit, and some are 16 bit. My record bit depth in CWbB is set to 24, and I use drum loops that are mostly 24 bit, but sometimes I need to use some that are 16 bit. Plus there are other tracks at 16 as well, I'd say it's about 60% 24bit, and 40% 16bit. If there is always going to be a mixture of 16 and 24 bit audio clips/tracks, can I still bounce everything down to a final mix of 24 bit without dithering?. .. I'm trying to avoid applying dither more than once. I'd rather have a 24 bit final unmastered mix to put into my mastering software, and then dither down to 16 bit at the final master export. Is there any way to do this if my tracks are always a mixture of 16 and 24 bit? Are my 16 bit tracks negatively affected if I bounce all tracks to 24 bit mixdown?
  11. I haven't used the screensets function, I'll have to look it up, but that sounds like another good way to achieve this. Tried this, and it works as you said, as long as the screen availability is smaller than the number of tracks, they minimize all the way, regardless of whether they are each sized differently when opened, which is what I needed. After collapsing, I tried re-opening a few and they retained their original size they were prior to collapsing. Thank you. It seems the console view has a "widen all strips" and "narrow all strips" option, wonder why they don't have one for the track view. I guess the Shift + F is the closest thing. Thanks again, much appreciated.
  12. Ok thanks. I must have accidentally Ctrl Clicked on something. it was just strange that not only were all the Global on/off buttons lit, there were two or three modules in every track and sub that were lit as well. I know since beginning this project I never touched any of the pro channels or modules at all. I'm just glad I figured out what the issue was, and glad I had a backup just in case! Thanks guys, much appreciated
  13. Is there a shortcut to Collapse All Tracks at once in Track View? I know you can Ctrl+A to highlight all tracks, then Ctrl and resize all tracks at once, but can all the tracks be collapsed (and/or opened) at once, regardless if each one is sized differently? I haven't been able to find it in my searches. I know it's been asked before though, so I have a feeling it cannot be done.
  14. This thread caught my attention because of something that accidentally happened to me today. I was working in a nearly complete project today, just highlighting all the tracks that I wanted to bounce/mixdown to one track. When I played back the mix I just bounced the sound was way off from what it originally was before the bounce. For about fifteen minutes, I couldn't figure out what happened. I knew something was different. After looking closer, I noticed the ALL the prochannel Global on/off switches were all "on", in both the regular tracks, and in all my subix busses, plus, some of the prochannel modules had been turned on in ALL the tracks an subs as well. After going through and turning them all off one by one, my project sounded back to normal again. What a pain though! I know I didn't use any prochannel effects in this project at all, I only used 3rd party VST FX, so the prochannel FX somehow all got turned on at once. Is there some way this could have happened accidentally? I didn't think there was a switch that turned on ALL the prochannels at once, including sub busses, is there?
  15. Right you are scook! I did just figured that out a few moments ago and logged in to cancel the thread and saw your post. I guess I had a senior moment and the fog suddenly cleared! 🤔 Sorry to have wasted a thread here, but maybe someone else will benefit from the info. Thanks my friend, much appreciated.
  • Create New...