Bill Phillips

Might be a good question to ask Bandlab.

That makes sense and historically, I've taken the same approach. I think I'm softening up (or maybe getting more reckless) because I've become very comfortable with Windows 10 and am not so worried anymore about fatal flaws. I'm hoping that when I do have problems, I can provide feedback and then drop back to my last working build, like I did when 2004 blue-screened twice.

I just joined the Windows Insider Program. Is anyone else in the Insider Program? Any thoughts on whether or not it's worthwhile? I'm thinking as a Cakewalk user, I'll be providing info on Cakewalk performance to Microsoft which seems useful to Cakewalk users and I may get some tips on optimizing my PC for Cakewalk. Before making this post, I searched the forum for posts on the Insider Program and didn't find anything less than a year old. Looks like it's not that popular with Cakewalk users and might mean it's a bad idea. Also I recently tried to install the 2004 update but it failed twice. It appears a lot of people had that problem. So I figured I'd wait a few weeks to try it again.

I don't think that Cakewalk uses GPU processing, but some VST plugins use OpenGL, particularly for sophisticated graphical audio data displays. In my case my CPU is an older i7-6850K with 6 cores and 12 threads. I had an older AMD R7-250 video card. I use the iZotope Music Production Suite which has, what I consider, an awesome user interface using lots of sophisticated graphics. I've also verified that iZotope plugins use OpenGL. With my existing R7-250 video card I would get lots of pops and cracks anytime I opened certain iZotope plugins. Opening several iZotope plugins and interacting with the graphic displays would cause playback to stop even at the highest audio interface buffer size. I could see that the problem wasn't driving up or overloading my CPU and decided to upgrade my graphics card to a RX 580 to make more OpenGL processing capacity available for iZotope and any other processes that could use it. The result was a night and day improvement allowing me to drastically reduce audio interface buffer size in some situations and allowing Cakewalk to use more of my CPU's processing capacity. Here's a thread to the SoundonSound forum I used to get advice in addressing the OpenGL problem. The advice I received helped me understand the problem and select a replacement graphics card. At the end of the thread, I posted a summary of my conclusions from the graphics card upgrade. Hope you can open the link and read the thread. And I hope it's useful to you.

Sorry. I misspoke. I tried but there was nothing to select. scook's suggestion of selecting the orphaned envelopes using Shift+Click allowed the envelopes to be deleted using the Right-Click dropdown menu.

Try the test that @Noel Borthwick suggested to re-educate yourself.

I know, I've seen big improvements in working with envelopes over the last year or so.

Wow that works! How did you know that? Found it on page 1694 of the Reference Guide! Cakewalk has got to have the best DAW reference guide ever! When each of the "ghost" envelopes are "SHIFT+Click"ed the Edit Filter shows "Send Level" which is probably a remnant of a send level envelope that was deleted, probably without deleting the envelope first.

I don't think that will work. The two greenish "ghost" envelopes that I want to delete to de-clutter the display don't exist and can't be selected in the edit filter.

I didn't delete any automation lanes. Opening automation lanes was intended to make it easier to show that there was only one remaining automation envelope, but it appears to have caused confusion instead. The two greenish "ghost" envelopes don't exist and can't be selected in the edit filter. So I don't see how they can be deleted. Other than cluttering the track display they don't seem to be causing any problems. In the past, closing and re-opening Cakewalk has removed "ghost" envelopes. Hopefully that eventually happens here. I have since added two additional envelops to that track and will add more.

How do I remove the leftover automation envelopes shown in the image below. The only remaining track automation envelope is shown in the automation lane below the clip pane. The other automation shown in the clip is clip automation. The leftover envelopes don't seem to be affecting any controls but they do add clutter on a track that I plan to add more automation to.

I don't sync track and console views. I hide everything except active audio/midi tracks and track folders in track view. I'll also show buses and aux tracks when working on bus and aux automation. I only show anything with controls I want access to (all active tracks including aux tracks and active buses) in console view.

I don't know why that's happening. I think I followed the steps in you described in the 2020.05 Early Access 1 topic. I uploaded a GIF. However I've now noticed that BBCode option was missing for that GIF so I used the Linked BBCode option which probably converted my GIF to a mp4. Looking back I noticed that GIF is over 50 MB which may be to big to embed in the forum post so it was converted to mp4 and the BBCode option was removed. Thanks for getting my wheels back on the ground here. I'd gotten confused by the new "Inverse Link" feature in Neutron 3. A little more time reading Neutron 3 help documentation and watching videos cleared that up. Neutron 3's dynamic EQ sidechain input requires a send from another track like all other sidechain inputs.

Yes. You can press "H" to open the console view track manager, scroll to and "un-tick" the strings folder and click OK to hide them all; and repeat the process to "tick" the folder to show the string tracks. You need to be careful to make sure that the console view is selected when you press "H" if both the console view and any portion of the track view are visible. There are separate track managers for the track and console view as long as the "Keep track/console views in sync" option on the track manager is un-ticked.

This probably is a problem to refer to Izotope but wanted to check here first to be sure that it's not a Cakewalk related problem. The GIF below shows a vocal track Neutron EQ plugin (left) and acoustic guitar EQ plugin (right). I mouse through the EQ curve selections for each plugin and the masking meter dropdown for the guitar EQ. I have a dynamic EQ set up in the Guitar EQ for Band 3 that is sidechained to Band 3 for the vocal. Once the music starts, it's clear that the dynamic EQ is not responding. Is there something I need to do in Cakewalk 2020.05 to make this work? Any suggestions. http://i.imgur.com/VNCctKm.gifv Not sure what's going on with the GIF. Clicking the link opens it in a separat imgur tab but doesn't show up in the forum post. Maybe it's too big.

Using the media browser preview usually does it for me

@msmcleod, thanks. I used save as to create the project so the clips were already nearly the correct length, but I "Applied Trimming" to be safe. That didn't solve the problem. I use aux tracks, not buses for FX these days so, I hadn't really looked at buses. When I did I saw bus automation that stretched out across the whole tracking session. Deleting the bus automation solved my problem. Now "Shift + F" stretches the project to fill the screen. I think I'd originally added the bus automation to do a rough mixdown of the whole session. It looks like you get all the bus automation with each song when you use "Save As" to create a single song mix project from a multi-song session with bus automation. That probably also means that the bus automation is not in sync with the song. Not good, but ok if you don't use bus automation or don't mind recreating it manually for each song.

Thanks @Promidi & @msmcleod. That's it! I moved the left selection boundary to 6:02 and was able to move all the clips left. I also noticed that the selection extends to measure 903. So when press Shift + F to display the project which ends at measure 219, I get the display in the screen shot. I looked at the event list and there are no events after measure 219. Any idea what's out there? Dashed lines for track automation envelopes extend out there but nothing else I can see. As a note the clips for this project were cut from a recording session that most likely extended to measure 903.

Why can't I drag the 18 tracks in a project to the left? The attached GIF shows me trying to drag move 18 clips left. The clips won't drag left and the gray shapes shown show up while I'm trying. I then dragged one clip left with no problem. There are also white dots in the empty space to the left of most of the clips. What's the significance of that?

@MediaGary, are you using a 100% display scale factor?

Focusrite has a floating buffer size popup that you could leave open but using it several times in a session is about the only way I can BSOD Cakewalk

Are you saying that using Workspaces makes Screensets obsolete? I've been trying to use them together on a single project with no luck. I'll worry about other projects once I've got one working. Right now I've got a Workspace definition with the Screenset box not checked that loads one of the screensets that I want to use for mixing, but I have several other screensets I'd like to be able to easily toggle to. With the Workspace Screenset box not checked, Screensets are unavailable in that Workspace. If I check the box, I can't get the Workspace to load that screenset that it will load with the screenset box not checked. I've tried defining a screenset (1) that matches the one I want, but have been unsuccessful. Is there some trick I'm missing? Or should I abandon screensets, which wouldn't bother me, and define more Workspaces for the other screensets I'd like to have available. I just want to take advantage of the workflow tools Cakewalk offers to move around as repeatably and quickly as possible.

Yeah. I think the same thing would happen to me. I have 1st gen 18i8. I don't disconnect audio interfaces when Cakewalk is running so I don't know for sure. I do have a similar problem, when I change ASIO buffer size which is usually dodgy after the first attempt which works flawlessly. But if I'm searching for the smallest buffer size possible, I'll change the buffer size multiple times. Using the buffer size is always iffy and the Focusrite buffer size popup stays under Cakewalk after the first change. And once in a while, I'll get a BSOD. Both Cakewalk and Focusrite have made software updates to resolve this problem. But not there yet.

+1

I haven't used it yet but this one may have more features than LICEcap, but seems a little scary to me. Install took longer and once installed a capture launch dropdown was added in the top center of my screen that I couldn't immediately determine how to remove. So I uninstalled it which required a reboot that took considerably longer than usual to get rid of the capture launch dropdown.