winkpain

Thanks for the suggestion, but I think you miss my point. I know fair well how to select multiple transients. My question is: after selecting multiple specific transients (with the Audio Transients edit tool, ctrl-clicking or drag selecting, etc.) how then do I edit , and specifically, how to apply Quantize to only those selected transients?? As far as I can tell even still, when choosing quantize, Cakewalk ignores chosen transients and simply quantizes all transients in a clip. So, simply put: How do I quantize only selected multiple transients in a clip??

Yes. This I know quite well. Thank you, 'though. That is, as I mention, a very time consuming process with the issue that I outline above.

Is there something I'm missing? I am not a frequent AudioSnap user in CbB to say the least, but I am very familiar with the profound ease of adjusting chosen audio in, for example, Ableton (sorry for the reference to someone else ? ) I think it is this very issue that has kept me away from it, but I am trying again.... So, here in Cakewalk I have an audio performance that is mostly good. In a few places there are some transients that could be tightened up, nowhere near all of them but enough that makes editing them individually very time consuming. If I quantize the entire clip to a single resolution (the only option), the notes/beats that I don't want affected become edited, of course, and many of them undesirably. I want to quantize just select transients to the selected resolution. I turn on edit transients (with edit tool, AudioSnap enable, or such) in an audio clip, select only specific transients by their markers by ctrl/shift-click or drag selecting, and then when I choose to quantize, ALL the transients on the clip are affected as opposed to just the transients that are selected, just as if I had simply quantized the entire clip to begin with. Is there a setting somewhere that allows me to edit only the selection? And if so, the default setting is off?? That is certainly counter-intuitive. No doubt I am just missing some very obvious thing right before me eyes....

When I am editing in Audio Transient mode (with Smart Tool) on a track's transient markers, I can select markers and move them manually one-by-one, but when I have selected only certain markers either by ctrl-clicking or drag-selecting, thus making only my chosen markers turn yellow, and then choosing Quantize, instead of only my selected transients being affected, all the transients on the track are quantized. I want to quantize only my selection. What am I doing wrong?

...I also just found your "VST Inventory Tool" which helps see things more clearly, as well!

Excellent! Done. Thank you!

Yes, my Sonar is X3 Producer. And, sorry I'm still a little confused: by "restore the excluded plug-ins", do you mean restore them to their excluded state? And, since there are two versions that Cakewalk sees - for me one in the default "Shared" folder, the other in my custom "E:\Vstplugins64" folder - which ones should I use (have enabled), and which ones should I have excluded?

Thanks for this! Yes, it would seem to be these very excluded plugins that are the issue here with that referenced window/message. I had, indeed, enabled them as led to by a friendly post by Creative Sauce on YouTube, not an official CbB post, I know, but he does have good and seemingly knowledgeable presentations. So, you are saying that I should re-exclude them as they were done by default? And then, on the per-project fixes you mention above, how do I go about "replacing the plug-ins with the appropriate version"? They are, after all, the default plugins that came with the install. Where would I find other more appropriate versions? Again, my re-installation process was a "clean" one. So all traces of previous installations had been wiped from Registry and all, as directed. So where would the "confusion" now stem from?

Well, that is possible. But I have CbB pointed to my custom VST(2) folder as well as the separate default VST3 folder, and all my other VST2 plugins were seen. However, now the project in question is, in fact, loading those VSTs. I guess it just took a few scans to see them...? I don't understand that, but I'm not complaining. I didn't realize the migration issue with iZoptope. By that, I see that you mean that CbB's ability to choose the better of multiple versions of a plugin as chosen in Preferences/File/VST Settings will not function with iZotope plugins. NOW, the remaining issue with this project (and others) is that, upon opening I get the attached message about those few included CbB plugins which, in my case, were installed automatically by CbB into both the /.../Cakewalk/Shared AND my custom VST folder as indicated when choosing from the pull-down menu in the window. The items in the two locations have different CLSIDs and the window seems to indicate it doesn't know which to use. It also seems to not matter which one I choose, however, and simply clicking "OK" allows me to continue as usual. This is an issue I have noted elsewhere here, but it was one that I thought my clean re-installations would remedy. Should I just remove the duplicate dlls? Why does Cakewalk install them in both places if it on confuses itself? Along the same lines, should I just remove the "duplicate" VST2 versions of the iZotope plugins in the above original issue in order to force VST3 usage in their case?

Works as expected with clips AND works as expected with notes in the inline PRV, but just not in the main PRV. Closing the project and re-opening will allow Duplicate with Ripple on notes in the PRV for one go at it, then again it stops functioning. 2020-03-14-21-11-12.mp4 2020-03-14-21-28-13.mp4

I have completed a squeaky clean re-install of CbB and now have certain iZotope plugins that show up as "Missing" when loading projects using them. I did not touch these VST3 installations throughout the re-install process. They are in the default VST3 folder right were they have always been and were earlier today when the same projects opened (before re-install of CbB) without them showing as "missing". I have tried re-installing these plugins to their defaults, but they still show as "missing" when loading projects already using them. I can load new instances of these exact, untouched VSTs and use them fresh without problem. However, in the case of many projects, they were in use on every track with specific, long worked on settings that are now supposedly saved by "stand ins" mentioned in the attached window, but the saved states do not apply to the new instances. What gives?! Why does CbB no longer see these plugins as being installed when loading a project using them despite being able to load new instances. Why does it not apply the "stand in" states to the working versions?? How do I now recover the hours and hours of work established over weeks of careful editing??

I am also finding that when duplicating notes in the PRV with the Duplicate command and Ripple on that it will not engage the ripple functions. Leaving the Ripple edit button untouched and apparently "On", I can then switch to the Track View, select a clip (which may be the exact selection that were the notes in PRV), initiate a Duplicate command, and the Ripple functions DO work. Back to the PRV, select notes, Duplicate, and again no Ripple. Then a few moments later, without toggling the button, Ripple will begin to function again when copying notes. Odd behavior all around when trying Duplicate on notes, and this is confirmed on a glistening, clean install of CbB

Thanks

The most recent question was in regard to a second machine that already has the latest, unproblematic, CbB on it. If I were to want all the same resources on both, I may want to install Sonar on that as well. So, is a clean re-install of CbB also necessary there ?

Thank you, @Jonathan Sasor My version of Sonar was/is X3 Producer. Is there any necessity for installing one before the other? For instance, if I already have a fresh CbB installed, can the older Sonar still be installed afterwards?

I am finding that Ripple Edit is disengaging mysteriously even while it's indicator (in the upper right of the Track view) shows it to be on. Simply toggling it off then on again will re-engage it. With consistency it will be mysteriously "off" 'tho showing to be "on" right when opening a project saved with it "On". And otherwise randomly, after being in regular use of the Ripple Edit functions with it in the on state, and having done some other types of edits, changing views, etc., and then executing an edit that should cause the Ripple functions, it no longer functions. Although still showing to be on, I need to toggle it off then on again to get it to work.

I'm moving this post here. My apologies for the double post, but perhaps I put it in the wrong location before. I would certainly imagine someone knows a thing or two about the issue... I am about to do a clean install in hopes of rooting out some issues that I have that are likely caused by my having Sonar and CbB installed on two separate internal drives. I will, per instructions found here, re-install them both onto the default C drive where they "prefer" to be. I will hopefully get all my presets, key bindings, etc. backed up first. I still want to verify a few things: the uninstaller will remove all the bundled content (synths and such) that came with Sonar (that is also in a custom location)? these will be re-installed with the re-installation of Sonar if I wish? and wanting to continue to have access to this bundled content is really the only reason to re-install Sonar in the first place, or are there other reasons? My plugins: These are all in a custom location on a non C drive. Can I leave them installed there? Is there a reason why this should be an issue as long as I point Sonar and CbB to these custom folders ? And a general question about VSTs installations, if I need to re-install those as well: Is there any reason at this point, on a 64bit system running 64bit CbB(and other programs), to install both 32bit and 64bit versions (if two are offered) of the same plugin, or both VST2 and VST3 versions??

I hear you, @LarsF Using the Waves suite exclusively will surely do you no wrong! I do a lot of competition/notation as well but have found nothing better than Sibelius for that (and now maybe Dorico), which I re-wire into Cakewalk if needing to work with digital audio as well. It's not the same as having a robust notation editor built in (which sadly, Cakewalk's does very much not have) and being able to edit with both MIDI and notation approaches, but it can work if needed.

There's no forgetfulness on freezing here. It's a regular part of my workflow. But so is having the PC eq, comp, and console modules sometimes on even already frozen tracks. Anyway, I see that the original post was an issue of the number of tracks involved, not necessarily the all-inclusiveness of it. And, of course, the fact that you didn't even intend for them to be on - which is the strange part. So, speaking of the ProChannel modules then, is there any reason other than preference/taste to prefer them or not compared to VSTs added to the FX bin? I have tended to think of them as more "efficient", perhaps just in a workflow and/or signal flow manner, but when stopping to actually think about it now, I realize that this may be not really true...

What does this mean?? Surely we should be able to use ProChannel on all tracks, shouldn't we? Or is this an issue only in the case of this many tracks as mentioned in the OP? If so, then, how many tracks is too many?

How/where is this done?

...any advice on these points?

There are several improvements in the Markers world that we could see: Layered markers, color-coded, multiple auto-insert, chord-based, locked to clip boundaries... But at least we can lock them to real time, or musical time. Anyway, your current project sounds like it is precisely where you would want to lock your markers to SMPTE, especially if you are going to be adding musical tempo based material to it. Just go to the tempo setting and change it to something other than what it currently is and watch how the the markers end up at different absolute (SMPTE) time locations. (mind you, It looks like they don't move because the visual scope changes to maintain the same amount of measures in the screen, but your audio file will appear to stretch out or in, and the markers will not correspond.)

I am about to do a clean install in hopes of rooting out some issues that I have that are likely caused by my having Sonar and CbB installed on two separate internal drives. I will, per instructions found here, re-install them both onto the default C drive where they "prefer" to be. I will hopefully get all my presets, key bindings, etc. backed up first. I still want to verify a few things: the uninstaller will remove all bundled content that came with Sonar (that is also in a custom location)? these will be re-installed with the re-installation of Sonar? and wanting to continue to have access to this bundled content is really the only reason to re-install Sonar in the first place, yes? My plugins: These are all in a custom location on a non C drive. Can I leave them installed there? Is there a reason why this should be an issue as long as I point CbB to these custom folders ? And a general question about VSTs installations: Is there any reason at this point, on a 64bit system running 64bit CbB(and other programs), to install both 32bit and 64bit versions (if two are offered) of the same plugin, or both VST2 and VST3 versions??

...Thanks again @David Baay I got my further answer by reading the dang reference page. Imagine that! On the BounceBufSizeMsec setting in AUD.INI it says like you said: But thanks for leading me to it. Always read the reference material ! (It's just so informative -and fun- to chat with you all !)