Bill Phillips

@tonemangler thanks for the clarification and insights.

Thanks, the filter toggles work for me but the right-click drag moves don't work with the smart tool. Did you mean to say left-click drag to select and left-click drag up/down to adjust volume?

Thanks. That's it. I should have read more carefully. I was looking for "Bus Compressor" syntax used in the Master Bus instance.

See the screenshot below. I'm trying to add a send in a vocal track to the PC4K-S compressor in an acoustic guitar track. As the Send target list shows the Bus Compressor in the Master Bus is available but the AccGtr MF50 and Mix track Bus Compressors are not available. Any suggestions on a way to resolve this? I've read through a couple of earlier threads. In one case a driver update solved the problem. My Focusrite 18i8 1st gen drivers are up to date. In the other the project was forwarded to Cakewalk support but the results of that effort are not in the thread. Thanks.

When selecting multiple nodes or all nodes on an envelope, Ctrl + Click-Dragging with the Smart Tool seems to move all selected nodes reliably, but, I didn't find that option in the documentation. Did I miss it? Is that expected behavior or a bug? Should it be documented? OTOH, the documented method (as described by text in the red box in screenshot below), Click-Dragging Up/Dn in the top center, does not always move all selected nodes Up/Dn. Sometimes it will create a node below the mouse pointer or highlight the envelope segment between the nodes on either side of the mouse pointer.

Thanks for the clarification. I was using SHIFT + Right-Click and Drag which was doing strange things like changing the edit filter.

I can't get lasso (SHIFT + RIGNT-CLICK) works with the edit filter but drag select does and DELETE does work. I just know that I've tried that before and it didn't work but looks like I was wrong.

I agree and am using it.

That works. This one works too and I don't need to make a tool change. Thanks to all. I'll be using these suggestions to speed up my automation envelope development. After reviewing these responses I went back and reviewed Creating and editing automation envelopes in the online help document and found much of it misleading. I wasn't able to identify either @Nigel Mackay 's or @Lord Tim's suggestions on that page. Also since there are multiple ways to do the same thing, I find the documentation confusing. Also, one thing I'd really like but can't find is a way to delete a group of selected nodes. I often accidentally create a number of nodes and have to delete them one at a time because anything I try deletes all nodes not just the selected ones.

Do you have an easier/faster way of doing the operation shown in the GIF below? I do this a lot for clip gain and other automation envelopes like the PC EQ HMF Gain envelope shown in the GIF and my way of adding sloped transitions is time consuming. One issue that might not be obvious is setting the envelope level since for things like this unmasking operation I like to make the cut level consistent. But, dragging it down in each instance is tedious and the level increments easily hit vary depending on vertical zoom. One thing that would be helpful for my workflow is eliminating the duplicate nodes created by the envelope drag up/down operation.

My daughter has one with only a USB interface. Is that what you have? I haven't had to deal with it yet, but will. So I'll be following this thread. She likes the mic but the USB interface and the 16 bit depth are a concern for me. If there is an ASIO driver for it and I can record her vocals solo, then I'll probably use that. Otherwise, I'm hoping I can use WSAPI. Then I'll just have to remember to switch back to 24 bit depth when I switch back to my audio interface, something I've forgotten to do before.

I'm no expert but this seems to work for me. I use Melodyne 5 or iZotope RX for any plosives that I can't handle with clip automation. For everything else associated with normalization I use clip gain automation which is time consuming but tames lumps while maintaining dynamic range. I've been using clip gain automation for a long time.

So true. Thank you Bakers!

Thanks for sharing the 30 year old video. I moved from Colorado to Florida 35 years ago and have been really enjoying the snow (lack of) in Florida ever since. Once in a while I do miss snow this time of the year and your video cured me.🤣

Thanks, does "delete muted clips" delete clips from the audio folder (in addition to deleting them from the project)?

FWIW, I used to use CCCleaner all the time but uninstalled it this year. Win10 doesn't like it and flags it as malicious software, IIRC. I always liked the idea that it identified hundreds of registry entries and with my permission deleted them with no noticeable impact on performance. But now, rightly or wrongly, I've grown more trusting of Win10 and am hoping that Win10 is taking care of the mess I used CCCleaner to clean up.

In my experience, Cakewalk doesn't present much of a graphics processing load and may not benefit much from graphics acceleration. But the iZotope production suite I use does causing dropouts at max buffer size anytime I opened to many iZotope plugins while mixing. I upgraded my graphics card to a AMD RX 580 (not latest model or very expensive but has considerable OpenGL capacity). AFAIK the OpenGL (graphics acceleration) capacity is only used when the calculation intensive iZotope plugins are open and updating graphic displays in real time. This made a big difference. Now I can have several iZotope plugins open at once while working at lower buffer sizes. If you have plugins that can use OpenGL, they should gobble the capacity of your 3090 when their displays are open.

Thanks.

Not everybody will be familiar with command line programs. Do you use it? Will it work on Windows 10 2004 64-bit?

The folks that have been responding to you understand the difference between fixed and floating point and they understand Cakewalk. That should be clear from their responses. In answer to your OP, they've also stated multiple times that Cakewalk has been capable of recording at 32 & 64 bit floating point since 2005. This link to Cakewalk Online Documentation lists recording bit depth options including 32 & 64 bit. At the time it was last updated no 32 bit audio interfaces existed. Looks like there is one now. This link explains 32 & 64 bit floating point recording capability. If you have a 32 bit floating point audio interface, set the Cakewalk record bit depth to 32 bit and record some audio and take a look at the recorded bit depth.

Faulty cables are a common problem. Hardware tech support will often ask you to try different cables first. Thanks for the monitor recommendation.

I'd like to know how this works out. I've been looking for a curved 3840x1200 as close to 40" as I can get. I have 36" between my monitors and a 40" curved monitor should fit. I have a AMD RX 580 video card which may solve the flakiness problem for me but I'd still like to know how you solve the problem.

Thanks for explaining that. I don't recall ever seeing those. Thanks. I upgraded to M5. I'm a novice Melodyne user and only used M5 a little on one project so far but M5 seems a lot better integrated with Cakewalk and have a lot more features than M4.

Sorry. I'm not at my DAW & don't think those .nff files have anything to do with Melodyne or Cakewalk. I use region FX which bounces clips to the project audio folder and, at least in my recent experience, places at least some of them in take lanes. I believe that when I decided to undo changes made and rendered using Melodyne, I muted the rendered clip and re-edited and rendered the recorded clip.

It shouldn't be hard to find it will be in the same folder than the other project audio files. Also don't forget to look in take lanes.