OutrageProductions

Yes. Use the Track Manager (preset shortcut key = H), or available from the [Track Pane/Tracks Menu/Track Manager]. UNCHECK those types that you DON'T want to see in the track pane or Console view, but you know that. As for finding only tracks that contain audio or midi data, still use the same technique, but would require a little more work. There is no preset way to filter that I know of. If you use folders for sub-types of instruments, but don't use those instruments in the composition, that may be easier. Otherwise, just delete the empty tracks after completion and before mixing. It won't have any effect on your opening template.

That is a loop marker. Hit "L" on the querty keyboard to remove, "shift+L" to enable. Also can use the loop module in the control bar.

I use a KK S61 Mk1 all the time as a second control surface (to my Promix) set up as an MCU and everything works in the transport section except for the Loop button (don't really care). I thought about adding a Nano control, but opted to build midi editor setups where pitch & mod touch strips become CC3 and CC11, or a couple of other expression controls, and changing to the general midi is a two button press on the keyboard. If I could get it to change track focus in CbB, I'd be in Val Halla.

You are evidently not building enough time into your contract bids. I always plan for at least 4 round trips to layback audio into the directors cut on my video sled and bill accordingly. And I'm faster on that than in CbB by long shot. I have no need to export dailies for Director approval from Cakewalk, but... as @Jeremy Oakes said, YMMV.

CbB is not a video edit sled (yet!) so all you can do is to check this post reply from Mark McLeod for a workaround: I tested this method and it does work, but it's not elegant or sleek. Usually when I have my audio exported into stems, I just load them into my Video edit platform and sync.

Ok. That is definitely weird. I know someone with that keyboard as Midi input AND controller, with a MOTU audio I/O that works swimmingly. Have you trashed the ACT control and just tried it as a MIDI keyboard input device (not control surface)? If that is successful, then try to add just a Mackie Control surface for the Novation to see if that forces the issue. Again... maybe screenshot your prefs pages for us? There are several of the sales folks at Sweetwater that are tech savvy, especially with CbB. I believe a chat session with them may be in order too while we put on our thinking caps.

The Novation Launchkey is only a usb midi interface, there is no reason why it should even show up under <preferences/audio devices>, and thereby "steal" away from your Tascam audio I/O. Check in your prefs that the Tascam is your audio device, and in midi devices, the keyboard is selected. Maybe a screenshot of those two dialogs would help us to help you.

Windows 10 introduced the snipping tool: WINDOWS KEY+SHIFT+S Unfortunately, in most applications with context menus, they close before capture due to the interrupt from the low ASCII key stroke. Print Screen is a dedicated key, and therefore doesn't send an interrupt. Probably still your best option.😕

Jesse; "I should have been more specific. I would not be sending signals. I will only be needing power for the laptop, speakers, focusrite solo, and midi keyboard" I must have completely bypassed the word "extension" in your OP. My bad...

Exactly what signals are you sending? MIDI DIN is a 5 volt line and can degrade quickly in all but the best quality shielded conductors. USB loses too much level (from 3.3 volts) over about 30 feet, and your computer speakers are likely only pushing 500 milliwatts to maybe 5 watts, so 30 to 50 feet is about the limit. I've built many professional studios where the MIDI DIN lines were never more than 50 feet, and even they got sketchy with the best Canare 5 conductor wire. Good luck.

On Export, when you get to the MP3 Export Options dialog, in the "Comments" section (where the notes are transferred) just put the cursor in that box, CTRL-A (select all) and Delete. Works every time.

Not that I'm aware of. Create new folder, then duplicate the tracks that you need and drag them into it.

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.