Bill Phillips

Thanks. Glad it won't affect DX plugins. My processor is a 6850k. That's a little newer than the 4000 series numbers in the article. But it is too old for Win11.

The article I read was on Tom's Hardware. I mistakenly thought support was being withdrawn for new processors but it's actually older processors (4th gen) that are losing support. intel shutting down DirectX 12 support for some older processors

I saw something from Tom's Hardware or CNET I think stating that Intel might be dropping DX support because of security concerns for some processors.

Thanks. I guess I'll submit it to the Feedback Loop.

Thanks for looking, but the situation you're describing doesn't exist in the video and isn't causing my problem. I have "old eyes" too and am replying to you on my phone. To see the video clearly I tapped the video clip in landscape view and used two fingers to zoom in. I'll explain what's going on. I placed the cursor above the clip because the envelope is at +6 dB putting it at the top of the clip boundary and the cursor must be above the envelope and above the top of the clip frame. Once the cursor was above the envelope between two nodes and the level adjustment tool cursor (probably not the correct name) appeared. I clicked once to select the segment which shaded the clip area between the two nodes. I then clicked the tool again holding it this time. In the video clip the cursor turns yellow. Then I dragged down which should lower the selected segment but the segment doesn't move. I tried this several times. No luck. However I was able to click on one of the nodes defining the segment and drag it down to lower the gain for the shaded segment that way. Hopefully that clears it up for you.

I need some help troubleshooting a clip envelope editing problem I'm having that I'm guessing others might run into as well. I don't think it's new with 2021.11 though I only ran into it after I began using 2021.11 (build 010). I know that envelope editing has had a lot of recent improvements which have been very useful to me. And for the most part envelope editing works pretty well for me except for some things like selecting the whole envelope or a number of nodes to move as a group. In this case though something that's seems to be rock solid (selecting and dragging up/down a envelope segment between two nodes) works consistently intermittently for the audio clip shown in the video below. It's also occurred on other clips but not on all. At this point I'm generally making small changes to envelopes drawn earlier without this problem I think. It might have something to do with take lanes because the two BV clips both have two take lanes and the Bass DI clip below has a single take. I don't recall any issues making a couple of clip envelope adjustments on the bass clip. There are two takes of the clip. The shorter one is soloed. I've tried adjusting the automation both in the take lane and in the track. I seem to have the same problem in either case. Basically, I can move the cursor into the segment selection area at the top; click and release to select the segment; then click again and try to drag down but the selection is dropped frequently and doesn't move. When this happens I've learned that I can grab one of the highlighted nodes and drag the segment down. I don't think this contributes to the problem, but I'm learning to use a Kensington Expert Wireless Mouse (trackball). So I've tried this with both the trackball and a conventional wireless Logitech mouse. They are both active. In the video I'm using the mouse because I'm much worse at this using the trackball. As you can see in the video, the select and drag operation doesn't work. Sometimes it does. I've tried every combination of track or take lane being selected, having the focus, having the clip selected. None of that seems to make a difference. I'm using 2021.11. I ran into this on the Early Release (010) and for the video was using (015). I haven't worked on automation on these clips for a while (probably October) and don't recall having this problem before. I have clip automation on every clip and I've been working on this song for years on and off, though is is a new mix started back in September. In the online documentation under Using tools to perform common tasks I found this but nothing else: To raise/lower an audio Clip Gain envelope 1. Set the track’s Edit Filter control to Clips. 2. Select the Smart tool . 3. Hold down the CTRL key and drag the bottom part of the clip up/down. Tip: For greater control over clip gain envelopes, set the Event Filter to Clip Automation > Gain. Note: Clip envelopes can be adjusted in the parent track or in a Take lane

Why wouldn't you use versioning if you're looking for a way to recovery lost work after a crash? I don't understand the problem your describing. And I believe that Recent Projects are "recently saved projects." So if you never saved it, it won't be there.

Not minor. If you can reproduce that, you should submit it as a bug.

One of my concerns with auto-save has been what happens with auto-save during export/bounce. Turns out it could have been a problem but no more. Near the bottom of the Bug Fixes list for 2021.11 is "Disable project auto-save while File Export/Bounce to Track(s) dialogs are open." I'm leaving auto-save on and no longer worry about it impacting rendering.

Auto-save is not synced to what you're doing but I don't recall it causing me a problem though I suppose it might if it saved while I was recording or rendering. Well if you're using versioning, and go to File>Revert, you'll be able to select anyone of the saved version available. I'm not at Cakewalk so I can't verify the command.

Yes. You clarified the differences for me. Thanks.

I'm like you but working hard to use more keyboard shortcuts. I've now got a mouse and a kensington trackball, both active. I want to use the trackball to eliminate arm motion but I'm under impressed with kensington. I think the software is flaky. Initially I couldn't get it to work using the latest software version. Kensington tech support had be revert to an older version which definitely help. But, sometimes it won't start and I have to pull the USB fob and re-insert it. Sometimes the pointer becomes really sluggish for no reason and then it gets better. Even though it's less than a month old (and cost $95) I've cleaned the cradle several times but that doesn't seem to make a difference. And then there's my ability to point accurately with it. I tend to use my index finger or the index finger and ring finger. Both will start to wobble when I'm trying to hit a small target. Using the ALT key slows that down some. Sorry about venting the sob story.

Thanks for the reminder about the menu keyboard shortcuts. I'll start using them while it's fresh in my memory.

Thanks for the comprehensive response. What I'm seeing is that auto-save doesn't create multiple versions. Each auto-save overwrites the existing one. So the latest auto-saved copy is the only one. Now that I understand that, I like it. If I forget to periodically save, auto-save might save my butt as it did on this most recent crash. I do all three. I have auto-save enabled every 10 minutes or 10 changes. I keep 20 versions and I File>Save>Copy As in the same folder so that there's no need to copy audio files. Over time I'll collect 20 versions of various Save-As versions. My plan is to periodically delete versions of now outdated Save-As versions.

Thanks. I can live with it. One of the plugins causing this problem in vx-64.

How does ALT-F-S work?

Thanks. I've got a much more haphazard process that I need to refine. ?

Thanks for the analysis.

I changed Exception Handling Severity to 7, restarted Cakewalk, opened the project and began toggling the FX Chain power buttons on the three plugin bars (vx-64, W.A. Production Vocal Limiter and Klanghelm IVGI2). When I do that playback becomes garbled and additional toggles can ungarble and regarble playback. After doing this a number of times, Cakewalk exited but didn't generate an error message This also happens on any of the plugins and in the same position on the adjacent identical track, and to some degree in FX Chains in other tracks.

Me either until yesterday with 2021.11. That's what got me into looking into the differences between auto save and versioning. Auto save saved me some tedious work but it's awkward. Seems like it was an afterthought and not integrated into versioning.

Not sure this is related to the new build but, I'm consistently seeing Cakewalk close when I click of the power button of a plugin in a PC FX Chain. So far I've noticed it with two plugins for sure: VX-64 and Klanghelm IVGI2 version 2.3.0. There may have been others. This seems recent or seems to occurring with more regularity with 2021.11 Build 010 which I installed this morning.

Up until now I'd thought that the auto saved versions were added to the revert list but they are apparently not. Shouldn't they be or why not? Otherwise, using auto save appears to be more awkward that using the revert option which includes only manually saved versions, something that isn't clear to me in the documentation (see copy in screenshot of pdf RG version 27.04.00). I've been using Cakewalk for a long time (since SONAR 4), but obviously haven't needed to use project recovery very often recently, which is good; but now that I am using it, I'm finding that my understanding of advanced file save options is wrong. My Cakewalk Preferences>File>Advanced options are shown in the Preferences screenshot. Here's what happened: I was just tweaking settings on VX-64 plugins on duplicate channels in Cakewalk 2021.11 Build 010 and it crashed preceded by some audible hissing then blink gone. I reopened the project after the abrupt exit and it seemed fine except recent tweaks weren't included. So I closed it with the idea of reverting to the most recent auto saved version since I hadn't manually saved during this session. As luck would have it Cakewalk auto saved less than a minute before the crash. So I wanted to use that auto saved version. It's visible in the file list in the upper left corner of the Cakewalk screenshot. However, when I selected File>Revert, the last available version was on 10/31 as shown in the Revert screenshot. And if I just open the recent auto saved version that includes most of my lost work, it's name includes the auto save text. I'd thought that the auto saved versions would be added to the Revert list but that's apparently not true. From my experience just now and what's somewhat vaguely described in the documentation: I opened the auto saved version and saved it as the current version that had crashed. That worked and added the current version to the revert list. The last screenshot shows the project folder after I'd opened the latest auto save version and manually saved it as the project (ends in TEMP3) that crashed. I checked and the new manually saved version was also added to the revert list confirming that only manually saved versions make it onto the revert list.

Mine is FW (Firewire) not USB.

Anecdotally I've noticed iZotope getting bogged down on Mac support and leaving Windows uses hanging. I've also heard that they sold out to a venture capital company. So it won't surprise me to see Windows users taking on second class users status.

They're on my s--t list too. I have an old 828 mkll FW. I've updated the FW card a couple of times as Windows evolved and it's continued to work well until now. Now when I'm using it for mixing, the audio output will become garbled and I'll have to restart Cakewalk to correct. I checked for new drivers and found that my 2015 drivers were the latest. I asked MOTU about that and was told that they dropped support of that product in 2015 which apparently isn't true. I saw a couple of 2021 Mac driver updates. So it looks like it's Windows that they dropped support of in 2015. The fact that Windows 10 doesn't support is a complication but the FW card makers seem to have a way of keeping FW working.