OutrageProductions

Try this: Alternatively (depending on what may be easier for you to use) turn off both Metronome in Playback AND Record in the Transport module of the Control Bar, then save Workspace. Make sure that you set the count-in to zero bars. Both work for me, but I prefer the latter method... easier for me to figure out what's wrong when I DO NEED the click.

I find this update interesting in that; I've never had the issue with a KK S61 and multiple midi templates being available on the keyboard (without also having Controller Editor running, which was their posted workaround). I've had four different Templates loaded & running for 4 years now, didn't even know this was a thing. 🙂

I used AutoSave once upon a time and found too many copies, poorly differentiated, of .cwp files in my project directory, so I switched to versioning 2 or 3 copies (as high as 5 if it's a deep project) and just get into the habit of CTRL-S about every 10 minutes. I've had to use recovery a few times a year to salvage a session. It is curious as to what is causing a disconnect between the CbB counter and the internal clock in the OS.

CW/Sonar has never been a video edit sled, therefore exporting a 'Section' of video with attached audio is a joke. Use a proper video editor to sync.

If your video reference track was imported with SMPTE H|M|S|F burn-in or encoded AND your timeline is clocked in SMPTE (in addition to MBT or some other composing time base), then just save each sound selection as a Broadcast Wave file and it will be timestamped so that the music editor can lock it to picture at the exact location that you intend. Export Tracks or Busses [not Entire Mix] in order to make stems for spotting on the film mixing stage. I do stems and snippets and cues all the time and the Vancouver & LA stages never have any issue locking back to the dailies or mix sled. Good luck.

<Staff View><View> menu, <Show/Hide Fret Pane>

If not already, try launching CbB as Administrator before saving to the NAS.

I have been using the ProjectMix since 2004 on all consequent versions of Sonar through CbB without any problems. Make sure that your FW card/port is driven by a Texas Instruments chipset. I am using the old Windows Vista driver 5.10.0.5061 (seems to be the most stable on my rig) and have only one caveat: occasionally CbB will lock up/freeze/crash (for reasons that are too numerous to detail here, I've tracked all of them!) and stay hung in the RAM as shown in Task Manager, and won't quit. I have determined that it is a hang in the driver, but there are a couple of solutions that consistently work for me; 1. Use RamMap to flush the Standby set and the Working sets. or 2. Power cycle the ProjectMix (which is on 24/7 in my studio) and the app hang disappears. or 3. Go get a cupper and wait for exactly 7 minutes for it to flush by itself. or 4. Warm reboot the computer. Just warning you that there will be the occasional, albeit rare, hang, and trust me... there is nothing else that can be done with the driver, unless someone wants to waste the time writing a new one. In which case, it would be cool if they would re-implement the MIDI Control Surface API for it too. (LIke THAT will ever happen!)

Make sure that the track driving the VSTi that you want to freeze is the one that is selected and in focus in both Track View and Piano Roll View (if open) first. (That has tripped me up more than I care to remember!)

That's the way the world works. He who yells the loudest gets the most attention. Even when they're wrong. 😁

I have, over the years, tried desperately to bind a custom keystroke to <process><find/replace> and no matter what combo I assign to it (even if after binding it shows as a keyboard shortcut on the dropdown menu) it never has worked. So I just got used to mousing to it... repeatedly. 🤪

I normally run 4 monitors from a pair of nVidia dedicated PCIe cards, but had to use the on board z390a chipset video for some troubleshooting and found that it would max out on my HD monitors at only 720 lines, hence was a bit fuzzy. Nothing like having dedicated GPU 's...

I work on film over 90 minutes and have never had any issues with tempo changes by jump OR gradual ramping. I set my markers to SMPTE and also have MBT on the timeline for tempo, lock the markers and everything goes swimmingly. As previous poster stated: make sure that you're INSERTING tempo change, not modifying existing. Cheers.

Make sure that that many measures or length of time is not locked into your Workspace that is being used for your startup default project template.

Ditto here. I use Alternate Note Names for a lot of NI VSTi's and this abnormality is irritating.

I occasionally run across this issue too. When ZoomAll (horizontal [Shift-F]) and there is extra space at the end of the last note that doesn't belong there, my first thought is to <Select All> tracks in track view, Ctrl-Clik on the <Expand Automation Lanes> button on any track and see if there is a an automation envelope (or many) that extend beyond the end of the song and either delete or edit the last node back to the proper end of the track. Takes some seek and destroy, but solves my problem. Generally the session won't do that again after saving. I inadvertently will move/edit a section waaayy later after the song and then put it back into the arrangement, and at that point I find that there is usually a Volume (CC7) or Expression (CC11) envelope stuck out into the next county... Check that first.

Does anyone know if there is an easy way to create/edit the list of note names in an instrument definition OFF-LINE? (as in a text editor, etc outside of the CbB application) If so, what is the specific format and syntax? [Edit] Never mind... found the {.note names } section in an existing *.ins file, will work from there.

Don't feel bad. I write about 5 to 10 film cues every week. After I get about one minute of it done, I know if I'm on to something. Needless to say, I manage to keep only about 20% of my initial work to continue on. The rest goes in the trash. 😒

From the "something strange happens with nearly every update"... a cue that I was working on that was perfect on Tuesday, opened after the update to 2022.02 had ALL of the VSTi instruments (that weren't frozen) come in detuned by 25 cents. (Having perfect pitch is sometimes a PITA). Close the project and the application and reboot... everything came back pitched correctly. That was a weird one. The bakers did another bang-up job on the export, Dim solo, and folder issues! Kudos!

Usually, there are fader channels for your hardware outputs on the far right side of the console view with VU meter indication if audio is leaving CbB heading to your Audio I/O. If it is showing signal over there but you still don't hear anything, then check the hardware.

If you learn things easier via video tutorial, Mike at Creative Sauce has a slew of well done videos covering CbB. Subscribe to his channel, you'll like it. https://www.youtube.com/watch?v=_2izQxY_x3Q

Those are the automation data tracks. Right click and delete the envelope and your fader will operate normally. Or 'unselect' the (R) in the track (automation read) and that works too.

I have a similar issue that is totally related to my mouse pointer placement in coordination with my Kensington Expert Trackball. If I don't hover and click on the first 2-3 letters of the FX name it won't open, also occurs in PRV when inserting articulation names. Have definitely pinned it down to the way my Trackball works w/CbB. Sometimes have to click thrice to activate. Other mice, no problem.

@Noel Borthwick BINGO! Prior to the 2021.09 update I had notifications set ON. They evidently toggled OFF with the update. No big deal, now that I have it re-checked it. I have had various updates over the last year make some other minor changes to the preferences that took some thought to figure out. That's why I wish there was a way to export a backup of JUST the preferences and global settings for the entire DAW, but... in the words of my friend Steven Tyler... "Dream On"

@Noel Borthwick I was referring to a single export. I haven't experimented with any task list exports yet, I haven't had to export any multiple stems yet since the update.