Olaf

Thanks, @Noel Borthwick, I've tried the latest update, and both features work, including the mass/group bypass, regardless of the position of the fx in the chain, which is just great. Yeah, that will be great to fix in the future. Thanks for the advice, I'll try that test, and see what it says. Aha, it's good that the differentiation between EA and final is made in the DAW. 11 final release was notified correctly in the DAW, so that was good. I've seen that you've made the full installer available, so that everybody can use it, which is great. Downloaded it, installed, replaced my 3 piece puzzle installer to the latest version I've had before. Usually I look for the full installer on other sites that provide it, but it was hard to find lately, and I also suspect having it done in one piece should be more reliable, so that's all great. Thanks for everything, and looking forward to the next batch of fixes and improvements!

Very happy about this update. Finally!! 🥳 solves some things that I've asked for since I was two (not really, but for a really long time). I can confirm these work on my system Browser collapsed state fails to persist when opening project Incorrect docked view order after project load and I've checked on every open so far, almost in disbelief. Call me low expectation, but seeing that actually behaving correctly makes me really happy. You learn to appreciate the simple things ☺️. Now, connected to that - all that remains, afaic, is for the Arranger Track show/hide setting to be saved and recalled correctly with the project, cause it's not, just like the Brwoser and Synth Rack weren't before this update, and the Show Velocity setting in Track View>MIDI, too - cause the Arranger Track show/hide is remembered on and off, and Show Velocity, never. I think the new Replace FX function is useful, not so much cause it removes deleting the old one manually, for a single instance - not that much effort - but it really comes in handy when you do mass replace. And so I agree with @Milton Sica that mass delete should also be possible (since mass insert and replace already are), following the same principles, and ALSO mass On/Off of rack FXs - that's a big one. That's really useful for a quick comparison across the board, to see what a plugin does, and is impossible for now. So that option added would be consistent behavior, and a very seful feature. I would argue that if we had mass Delete, combined with the already existing mass Insert, you wouldn't even need Replace at all, it would just be one extra click across the board - but having Replace, too, is a plus, not a minus, so no complaint there. However mass Delete and mass On/Off would be useful functions in themselves, not only in connection with Replace. On this topic, you should be able to click-select an Insert FX and delete it by pressing "DEL" - obviously, also for mass Delete (+Ctrl). Doing that doesn't work now, and I've had the experience - this I believe should be checked - of trying that, while in the Console View, and have it do nothing, only to find later on, that my pressing "DEL" DID do something, which was delete an audio clip that was selected in the... Track View, which is an major no-no. So, first of all, pressing anything should not do things you don't know about, in other views that are not selected, and secondly deleting FXs should be possible via pressing DEL, which would be an intuitive and common sense option. You can now optionally send "All Notes Off" messages to all VST plugins when the transport stops That seems like a good idea, I've had a synth with a somewhat longer release amp envelope setting, and it had this droning note throughout the exported song, even though the synth only came in in the last part of it - and obviously the release wasn't THAT long. So that was 😳... spooky action at a distance, to quote someone with bad hair. I don't get this, though - not the point of it, but how to interpret the behavior: Note: If the tooltip shows "Time Critical" when MMCSS is enabled in ASIO mode, it's possible that the driver is not using MMCSS, or has set up MMCSS incorrectly. On my Audient ID4 mk2 - haven't tried the Evo - when Enable MMCSS is toggled off, I get "Time Critical", and when it's on, I get "Realtime" - in ASIO, obviously. Does that mean that the audio driver CAN manage MMCSS on its own, or that it CAN'T? For this, Bouncing with selected aux tracks alone doesn't automatically include sources routed to the aux track, leading to silent output I've had the opposite happen, which is, if I select a MIDI clip for an Export Selection operation, and for some reason the output tracks for the respective synth, and/or the bus (Aux Track) summing those outputs, is/are not selected, the output of that synth is not exported, which is weird. Once you select clips to be included in a bounce, the signal path for it should be included by default, with no selection, since otherwise the bounce is not possible. Last, but not least, the automatic update within Cakewalk - which is really nice to have - doesn't work well with EA releases - there a mismatch there, which complicates updating - particularly since no links are provided for the official releases, for a reason I don't understand. The EA releases are not notified by CW update, which is OK, maybe not everybody wants to be involved, and bothered with those toasts - although, if I know anything about audio nerds, EVERYBODY can't wait for a new update, EA or not - but the problem is, if you install the EA release manually, then CW DOESN'T notify you of the final release - it treats it as being already INSTALLED - so there's absolutely no way of getting it. Basically there's no way of getting the final release anywhere - no links, and no notifications - if you've got the EA installed. I think that should be sorted out. Either the EA releases not be considered by the update notifier - like now - in which case it should notify you of the final release, even if it's the same version as the EA - or EAs be considered as a proper update, in which case you should be notified of them. Cause this way is neither here, nor there, and leaves you with no path to get the final release - or even know about it, if you've already got the EA installed manually. By the way @Noel Borthwick, if you've gone through the trouble of signing all the .dlls - which is really useful, cause Windows Defender is an absolute bitch, and there's no way of fully getting rid of it, it even blocks itself, Windows components, full installations, EVERYTHING portable, so on - I don't think I've ever had a virus that was so damaging to the computer as this "antivirus", in the most proper sense - it never remembers any permissions, so on, many times it doesn't ask, doesn't even inform, anyway, complete and utter dementia - why not provide the link to the full installer, so that we can actually make full use of the signed dlls? What's the point in making that improvement, if people can't have access to it? Anyway, really like this update. And can't wait for the next improvements.

This is an older issue I've reported several times. It's very often when you move automation segments that random nodes are generated automatically along the envelope - or a node will move from a lower inflection point, in jump mode, that was set up in linear mode. And, seemingly without connection, on a couple of projects the play head will keep playing well after the end of the project, with no event listed in the Event list, or present on any audio or automation lane. There are a few other things, too, with automations, that behave weirdly. I hope these behaviors get fixed in a future release.

It would be user preference if you had the choice. Otherwise it's more like a user must. As for the cost, it's probably the exact same. Regardless of how you access the installers, the bandwidth involved is the same. It's not about getting the full installer every time, instead of the update, it's about having both available, for when you need each. Like for now, when you would want to update all your dlls. I like having automatic updates in CW, don't get me wrong, I like to be notified, having the update available at a single click, that's all good. Question is what do you do when you need the full installer, or need some extra options. It's not a question of either or, but rather having both, as needed. In the end, it's just a link to the resources.

It will, but, from what I understand, only those involved in the new/modified features. So why not just get the full installer instead of all this process?

Doing that only replaces the dlls targeted by the update, doesn't it?

It would be nice if, in addition to the automatic update available in CW, the release posts would include a link to the update installer, just like the early access posts, and also a link to the full program installer updated to the latest release. For instance, now, if you want to update all the dlls to the new signed versions - which are a good idea - there's no option provided to do it. The only option is to uninstall CW completely, and reinstall, with losing all the customizations and settings - and I'm not doing that.

Ah, OK, that explains it. I had remembered 2017.

I don't think that's what this is, cause even live I've never seen these problems in their shows. No, the problem in most likely the VSTs. Older generation VSTs always had that problem in the top, and so did guitar amps and everything else. They also sounded flat, bloated and sluggish, which I was noting in the sound before. There are some good plugin synths out there now, but not all of them are, and probably 5 years ago, when the show was recorded, they weren't even out.

I grew up with Jean Michel Jarre, Vangelis, Klaus Schulze, Yanni - back whan he was playing synths - Kitaro, Tangerine Dream, so on... But that never seemed to be a problem on their records. The frequencies were more well balanced. I guess it was the hardware, going to tape, etc. That being said, I prefer a good drum kit over a drum machine any day, myself, but there are some genres where it would be harder to make them gel. JMJ started to use real drums from Rendez-Vous to Chronologie, then electric guitars, and made it work well.

I agree with you, sound wise, but I wouldn't go as far as to just call it a controller - even though I've thought about that myself - because it actually generates its own sound. Just that it's not that good. And the pickups you choose - and the pickup height, that often gets overlooked - do matter for the tone, albeit not as much as the amp, the cab, and the miking, I agree.

Interesting to see, but, to be honest, that's exactly what it sounds like. The roundness and the definition are gone, and those transients... I had to shut it down after a few minutes, just cause I couldn't take those clangy hi-hats.

I agree with you, good modulation, great space, and a little saturation could have saved the Roman Empire, if they had had any. Good effects are everything to a tone, in electric instruments. The best example is the electric guitar, which is nothing - if anything it's a blank, not an instrument yet, sound wise - without effects. It sounds like a bad acoustic guitar, until you add the effects - amp saturation and compression included. And then it becomes an instrument, in fact, dozens of instruments, any instrument you like. It's one of the things I love about it. One thing most people miss when they shape their tone is that they don't choose what instrument that is, before thinking about miking and the rest of it.

They've updated EZ Drummer to 3.0.3, so try that one to see if it helps. I've had the same problem with the first version, and I had to do a lot of dancing around to be able to assign different outs to separate CW tracks, and managed to do it with rerouting to unused outs, internally, route the intended ones to CW, then reroute back to them internally, so on. But I believe the latest release solved that problem.

I've got a very strange problem that's been plaguing one of my projects for a long while now - always in the same project. Waves H-EQ bands jump randomly either when you press play, or when you move the playhead along the timeline, like in this example. In this case it happens with 4 instances at once, on repositioning the playhead. It only happens when there's an undo/redo history in the plugin, and it doesn't happen to all the instances. Anybody else ever got this? 4 Waves H-EQ Jumping on Playhead Move.mp4

Absolutely, and also horizontal scrolling on mouse hover over the horizontal slider. I suggested this over three years ago. Edit: now that I'm thinking about it, the drump map menu in the channel out section, and the plugin category list in the plugin browser, could use scrolling over, too.

This is something that is greatly annoying to me, as well. And I fail to see the utility behind it. If I have the clips already drawn up, every time I add new notes, or copy-paste content, it makes a mess of all the clips involved, and I have to waste time just trying to make sense of what it did, and rebounce the clips to what they were. Can this behavior be removed?

The standalone loads in less than 3 secs on my Threadripper 5800X machine (16 GB RAM, NVme drives). I've tried to replicate your experiment, and the results are as follows: Default preset, idle: 1.1-1.7% After switching to the parallel double routing, and back to single: 0.4-1.1% But after switching to the "forked" double route, and back to single: 0.2-0.7%. Massive difference. Why is that? From what I've noticed, the first switch you do sets the CPU load range, if you try different ones afterwards, when you go back single the CPU use will stay at the same values as after the first switch. I swear the behavior of these digital recreations, with mathematical precision, 1s and 0s, is just as finicky and unpredictable as on the real thing. The same thing happens when you do the switch in a VST instance, in a project. CW's CPU use decreases by 0.5-0.6% for one instance of Amplitube. I wonder if you have to do the switch with every amp instance in your projects, after every open (or maybe just doing it one will suffice?). Could it be made so that it goes straight to the post switch-reswitch load, from the get go?

Thanks!

Hey, @Peter - IK Multimedia, can I make a feature request, if I got you here? It would be the possibility of having multiple parallel FX lines in all the stages (pre amp, fx loop, post cab, etc.), without the multiple/additional amp-cab rigs? It seems like a needless load on the CPU, and makes it a little more complicated to setup. Maybe with an overall volume for each section (all the lines in that section), to ease up the gain adjustment into the next stage. Ok, two feature requests - I tend to do that: add a Coles 4038 to the mic choices. at some point - I love that microphone. I know it's an entirely different ball game, but I'm just throwing it out there for consideration - maybe at least on the new cabs, for starters. And an SM58 - I know not many people use it, but The Edge does, so... I don't know what that's worth. Some great tones to have. Maybe a The Edge artist gear pack? OK, that's three, but I'll stop here. Thanks! PS: do you know what the Vintage 20 mic emulates? I'm curious, it's a favorite of mine.

I know, but there are setting and programs that stop working. Anyway, Windows works fine. I'm thinking of doing an upgrade to W11, but for some reason have some qualms about it, for the same reason. Gotta do a full backup of my system drive before that, and I've been postponing it. Any experience with W11?

I've sent you a PM with a project link. Thanks, I know what it is, but Windows seems to be working fine. I've deleted the Waves entries to make sure I don't have anything hanging that causes conflicts, because reinstalling normally caused those problems with the browser categories. I try not to mess with Windows too much, because I highly customize everything, and redoing an install is a multi-day affair.

Sure, I'll try it later tonight, or tomorrow. It rarely works when you've got registry problems. Uninstalled it, too, and deleted its keys, too for a fresh install. Better that way, cause registry conflict can be a big headache later..

I've reinstalled the Waves bundle - pretty nightmarish, had to delete all the Waves registry keys, the really weird thing is that the reinstall made CW add all its default plugin categories to my own, in the browser, even if they were unused and empty, but deleting all the CW entries for Waves, in the registry, in the end solved it - so the VST scan toast hang went away, when opening an empty project. The same way, when I open CW by itself, wait for the scan to complete, and then open a project from the start screen, the project load toast will go away, too. But if I open a project file directly, and both toasts appear at the same time, they will both stay open, and the VST scan doesn't go through the entire list - he plugins work, they list in the browser normally, but the scan progress display freezes pretty early on.

I've checked four projects, and one works as expected - scan completed normally, both toasts go away - while on the other three they linger. If you let them sit they'll stay there till you grow old. Here's what I could note, though: on all the projects with the linger there are frozen synths, which seems to cause the project load progress toast to stop, and the scan toast seems to hang after it. It stops at the Waves shell scan, without going into the modules. So that would seem like the common occurrence, except there's a catch: when opening CW directly, with no project, the program load progress goes away, while the vst scan goes through all the modules, for a change, and completes, but stays open with the last Waves module scanned, which, for some reason, is Scheps Omni Channel, even though it's not the last alphabetically. So that kind of messes with the theory. Thanks for the advice. I'd like to keep the auto scan, though, cause I try plugins all the time, uninstall what I don't use, so it's helpful. If I open CW without a specific project, wait for the scan to finish, and then load the project, the project load toast goes away, but the vst scan remains open after the last Waves module scanned, which is SOC, as above. I think it's a good idea to keep the sandbox scan active, too. The fewer crashes the better.