winkpain

@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! ?

Is there a hidden way to insert multiple markers at predetermined locations? For example: by selecting all the many clips on a track and calling for markers to be placed at all the clips' start locations? Or better yet at both the start and end boundaries! This would be a function like "auto regions" in other programs. But at least at the start boundaries... At the moment it seems markers can only being added one at time, making the case in the above example a very time consuming operation.

This is precisely what I thought of doing, re-installing X3 to defaults and re-installing CbB, but I find that I no longer have the X3 installation files! Over the years since my original install, and about 4 since this latest machine and the last install there, as well as cross country moves between studios with backup drives in both, I seem to have lost track of the old Sonar files! Never should have followed that "separate drive" advice! It felt somehow wrong...

I have asked this elsewhere coming off of an issue with VST scanning, but I am thinking it may be the cause of several little glitchy things for me: How reliant on the Sonar install (content, folder locations, etc.) is CbB? What is needed from the Sonar install if Sonar itself is no longer used? Or should we get rid of it if no longer needed. My installation of Sonar was onto a separate, internal SSD drive (drive E:) which was meant to be a dedicated drive for programs. This was advice that I followed at a certain time and installed a few things there. I later thought better of it and started letting programs install where they "wanted" to on the C drive. CbB was installed on the default C drive. I have odd issues with VSTs being flagged as not installed or not installed properly (these are also installed on a separate drive and have always been) despite actually being scanned (custom location is set to be scanned) and actually working. And I sometimes have issues when using the old Cakewalk instruments (TTS, Dimension, Rapture, PSYN II, etc.) and sometimes not. I believe if I want to continue to use these older instruments (Rapture, Dimension, etc.) I would not want to uninstall Sonar. Correct? So, un-install Sonar? or... Is there a way I could move (or copy) pertinent elements from that Sonar (X3 Producer) install to appropriate places on the C drive in order to function better with CbB while no longer needing to use Sonar? Or is all this, as I assume it might be, inviting disaster?? Should I revert (move) all VSTs to the Cakewalk default folder on the C drive??

Ah yes! My previous Sonar installation is in fact on a separate internal SSD drive. When originally setting up this machine I had followed, perhaps mistakenly, some advice about a separate drive for programs and I did that with a few. CbB is on the default C drive. How reliant on the Sonar install is CbB? I know if I want to continue to use those older instruments (Rapture, Dimension, etc.) I would want to keep it, yes? Is there a way I could move pertinent elements from that Sonar (X3 Producer) install to better places on the C drive? Or is that, as I assume it is, inviting disaster and a Registry nightmere??

Hmmm, my Reference Guide only has 1712 pages, with Staff View described starting on page 1078...

...perhaps we all (who love working in Staff View) chime in over here ....?

Staff View, Staff View, Staff View!!!!! New and better functioning, all around!

Yes, the Staff View DESPERATELY needs an overhaul! It is such an important part of workflow for some of us! I don't mind the PRV for many things, But I am a composer and accustomed to writing "dot and line" for harmonies, multiple parts, whatever. It's just how it is done with some of us when writing music. Of course I mostly use Sibelius for serious work in this regard, but still Cakewalk was one the the first (if not the first) to offer music notation with MIDI in a DAW, it would be nice to maintain the legacy!

This works for me. But it is awkward. But Select - Shift dragging to move or Ctrl dragging to copy works for multiple notes with Select tool. You must press Shift or Ctrl before clicking. It is, however, a bit of a mystery where the notes are being moved to exactly. I just get randomly flickers rectangles that seem to want to indicate where the notes will be placed, but they disappear in the blink of an eye!

Thanks. I chimed in over at that post about my experience with those....

I enabled these excluded plug-ins and find that every time I start CW now, I get this message for each of them: I simply click "OK" and the messages go away, CW starts up, and I can use the plug-ins without a problem, save the project, but then when re-opening CW after an exit, the messages appear again. The same process every time. I sometimes have this issue with some other VSTs as well. I don't understand how/why CW sees incorrect CLSIDs for plugins I have not touched, not to mentioned not changed, in years, especially these ones that have been "excluded" all this time until yesterday! Weird?

What are the actual effects that are being used beneath the hood of all the Style Dial modules? Is this mentioned somewhere? Nowhere here, for example: https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=NewFeatures.044.html ta!

I like all these suggestions! We don't wanna overload the bakers, but damn good ideas!

Customizable SmartGrid resolutions! Currently SmartGrid dynamically determines resolution depending on zoom level. I'd like to be able to edit/customize at which point SmartGrid dynamically changes its resolution AND/OR to be able to set a minimum grid resolution if going all the way down to 1 sample (for example) is not really necessary but being zoomed far in is. We can do this with manual snap to grid settings, of course. It would just make SmartGrid a little smarter!

Yes! Colored markers and/or marker "Layers" for different definable types of markers.

And with an unsupported format the video will play fine if no Trim settings are altered? This is the case with me. Only if I add Trim will I have playback issues.