winkpain

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 !)

@User 905133 "Lock to SMPTE" is another way of saying lock to absolute time. This is as opposed to the markers being tied to a musical time - Measure:Beat. When working with film or non-tempo based or fixed audio (dialogue, voiceover, or an unchanging source audio track you want to work with) it is very common to want to mark off "hit points" (in the film or audio) that stay fixed to those points in real time in the source material. Then you can work on/edit your score music, editing and developing your work, changing tempos and time signatures without affecting the placement of those locked markers. Without being "Locked to SMPTE", the markers would move around with the Bar:Beat that they are associated with as you edit your tempo based material, and they would no longer be in their desired place in the film, as this material will not move or stretch along with tempo changes. For example: If you want to work on a track that builds to a "Ta-da!!" right when the pie hits the face in a film clip, place a marker locked to SMPTE at that point, and it will stay there as you work on music leading up to that point.

Thanks so much @David Baay The playback buffer you speak of is, of course, the buffer set on my ASIO panel under Mixing Latency in Preferences/Audio/Driver Settings. I was not aware that this also was the default for the fast bounce buffer. So if I were to change that to a higher setting, as I frequently do after recording in real time (when mixing and working with synths/FX), this higher setting would also affect the Fast Bounce buffer? And otherwise, if I change the BounceBufSizeMsec entry as you mention it will default to this higher buffer no matter what I have set on my ASIO panel. Is this correct?

I know what this is!! Read:

Funky setup indeed. I do wish I had not accepted the advice to install programs and plugins on a separate drive! It felt intuitively wrong at the time, but I thought I was being advised by someone more knowledgeable on the subject... I take your point, @scook. I suppose it's likely at the root of all my weirdness, huh? Making Cakewalk behave like a schizophrenic or a split-brain patient. It is my intention, when finished the current large project - theater installation project for Times Square, NYC(!) deadline next week - to do a clean re-install of Sonar/CbB both onto the same (default C) drive in hopes of rejoining the land of the sane. HOWEVER, my main issue has nothing to do with my quirky setup. The obscure Enhanced Editing with Keyboard function tied to the NUM 0 key by default and no other way to control it seems a bit wonky. I know of no other functions, certainly nothing that radically changes the way CW behaves like this one does, not accessible with menu choices, preference settings, context menus, etc. It doesn't even show up in the Key Bindings window search function: type "Enhanced Editing", nothing shows up. Only if you know to look for it, or even what to look for, will you see that NUM 0 is reserved for its function (even though I have somehow overridden that and bound NUM 0 to something else). Like I said, it took me years to root it out. Anyway, I say all this is for the few who may wander innocently into this particular quagmire so that they can find their way out! Most apparently do not. I certainly hit the NUM 0 key inadvertently all the time given my use of the number pad. This is for the others who do too...

I am moving this post here because it was buried deep down in the feedback for a release last summer. It has nothing to do with that release and has maintained through all CW versions that I can remember and continues to plague me: After the years of suffering the confusion it causes and the in-depth weeding it out last year (by un-binding its default NUM 0 from key bindings), this "Enhanced editing with keyboard" function mysteriously started showing up again for me this week. For no apparent reason, this function is mysteriously re-engaging all of a sudden whenever I hit the NUM 3 (numberpad 3) keystroke, which I have always had bound to the Nudge Right one bar function since time immemorial. When it happens, I go to press the NUM 3 key to do a quick nudge to the right, which I may have successfully done only minutes before in the same project, and instead the keystroke will engage Enhanced Editing, and pressing it again will not disengage it, unlike pressing NUM 0 in the default keystroke assignment. Then the only way out of this workflow-stopping, mind-boggling "enhanced editing" state is to either "Zap all" key bindings and then press the re-established default NUM 0 to toggle on/off Enhanced Editing, or otherwise to close and reopen the project. However, then pressing (for me) the NUM 3 key again will only engage it again and only repeating the above will clear it. It started happening to me yesterday, I cleared it, re-imported my custom Key Bindings (with NUM 3 bound to Nudge) successfully only to then be working for a while and suddenly, with no editing of the Key bindings in the interim, NUM 3 is again engaging Enhanced Editing! Does anyone use this Enhanced Editing function?? And why, oh why does it want to persist even when I "get rid of it"? And most importantly, even if all of the above is some isolated random craziness on my machine only, why is it a function that can only be turned on with a default key binding and is not otherwise configurable or controllable from the Menu (from the Edit menu, perhaps?) or in any other way? For curious readers, if you've not had the experience of the confusion it causes, just press the (number pad) NUM 0 key (provided it is on its default binding - achieved by "zapping all" and applying if you've changed it like I finally did) and go back to editing your session - clicking, cutting, pasting, inserting, trying to edit with the mouse. A strange, slightly thicker cursor appears somewhere on one track only (which may even be out of your current view) and is the only indication that you are in this other editing mode and shows (if you happen to notice it) the new location where any of your inserts/pastes/etc. will take place no matter where you click your mouse! Now imagine having hit that NUM 0 key inadvertently, and never having ever used this, or even heard of this "Enhanced editing with keyboard" function, being completely confused as to what is going on! Bloody hell !

Thanks for this response, @dcumpian ! These points match well with my findings and intuitions. I have indeed had issues with Fast Bounce and some VSTi's, notably Kontakt loaded with intensive sample libraries. I wonder, when you mention those VST's that don't "support" Fast Bounce, is this an aspect that is made explicit ever, or is it simply a fact to be discovered by rote and usage? And I'm still a bit curious about the MMCSS setting and the current CbB architecture either on Win7 or if upgrading to Win10. I do remember reading somewhere about the wisdom of turning this to off for some reason, but can't now remember why or where I read it...

@Noel Borthwick The issue outlined in the above interchange between us last summer has reared its ugly head again! Perhaps it's a bit of a niche issue, but if it comes up, wow! After the years of suffering the confusion it causes and the in-depth weeding it out last year (by un-binding it from key bindings), this "Enhanced editing with keyboard" function mysteriously started showing up again for me this week. For no apparent reason, this function started engaging whenever I hit the NUM 3 (numberpad 3) keystroke, which I have always had bound to the Nudge Right one bar function since time immemorial and thus is a very useful and oft-used keystroke for me. Now pressing the NUM 3 key will engage Enhanced Editing, and pressing it again will not disengage it, unlike pressing NUM 0 in the default keystroke assignment. Then the only way out of this enhanced editing state is to either "Zap all" key bindings and then press the re-established default NUM 0 to toggle on/off Enhanced Editing, or otherwise to close and reopen the project. Does anyone use this Enhanced Editing function?? And why, oh why does it want to persist even when I route it out? And most importantly, why is it a function that can only be turned on with a default key binding and is not otherwise configurable or controllable from the Menu (from the Edit menu, perhaps?) or in any other way? For curious readers, if you've not had the experience of the confusion it causes, just press the (number pad) NUM 0 key (provided it is on its default binding - achieved by "zapping all" and applying, if you've changed it like I finally did) and go back to editing your session - clicking, cutting, pasting, inserting. A strange, slightly thicker cursor appears somewhere on one track only (which may even be out of your current view) and is the only indication that you are in this other editing mode and shows (if you happen to notice it) the new location where any of your inserts/pastes/etc. will take place no matter where you click your mouse! Now imagine having hit that NUM 0 key inadvertently, and never having ever used this, or even heard of this "Enhanced editing with keyboard" function, being completely confused as to what is going on! Bloody hell ! Sorry, I'll stop.

Curious about the ghost cursor thing. I'm still getting it even with the latest release. Although I have not seen the other issue I outlined above, thank the Bakers (I assume). Just reporting in...

These questions apply to a relatively modern PC setup with a quad-core 3.5gHz processor and at least 16g of RAM and a 64bit architecture. And my particular system is still on Windows 7... I have read the corresponding info in the ref. manual (~ page 869 in the downloadable pdf ) on Fast Bounce. I have always simply assumed it appropriate to have FB chosen for bouncing/freezing operations, given a mix or track's status of not using any external processors or side chains. Is this the correct attitude to have? Are there other factors that may come into play even on a very simple mix or synth bounce/freeze operation that would make one want to prefer to not opt for a fast bounce? Should final mixdowns always default to not using fast bounce to be "safe" ?? (I've only done this on large VST/synth/automation heavy projects) AND, while we're at it (in case someone is feeling geeky-sharesy), what are the appropriate choices and pros and cons for: choosing/not choosing 64bit "double precision" engine in Preferences/Audio/Driver Settings and or bouncing/exporting settings choosing/not choosing MMCSS in Preferences/Audio/Playback and Recording setting the correct Thread Scheduling setting (per the latest release) setting Multiprocessing engine and load balancing choosing the various dithering options does the setting of any of the above affect the preferences for any of the others? My approach has always been to choose the best or highest versions of any of these, in other words a choice for rather than against in binary choices and the "best" version of any multiple choice. Unless noticing a detriment, is this the correct way to approach it? These questions are for any info over and above the provided reference info, which is not always thorough enough for those of us who are mere musicians before we are computer techs! 😉