OutrageProductions

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. 🤪