OutrageProductions

Both of these items have been known and reported for several years. Nothing new here.

You're funny. You do you. I've never had a project EVER that wasn't recoverable in some manner. Trust me.

John made it sound as though this was a multiple track project where he was editing one-of-many tracks for consolidation. Of course, if there is only one track in the project, then DUH! It won't play and there will be no audio engine enabled.

After you delete the chopped track and BEFORE you drag the consolidated clip back in, have you tried to save and then play the project with the track empty? What happens then? There may be a dirty project condition that is causing it. I've seen that before, altho really rarely.

Ditto on the OUCH! I may have tried that way about 15 years ago, but for the last 10 at least, I've just put in an instance of the VSTi for each articulation, and lately (5 years) I've wrapped each one (using the Kontakt engine) in Komplete Kontrol. Ditto if it's Spitfire Opus, Chamber Strings, Albion, EW Hollywood Strings, etc. Even LABS can have an instance for each articulation if needed. They don't take any more RAM if running DFD, and I have a tendency to score a section and then freeze it to free up resources. To each their own, I guess.

Simple Editor is Windows stock; Movie Maker, or it's current replacement "Clip-Champ" (Win10/11). or Power Director Essential.

Nope. Not in my experience, and I've used nearly every sled ever made for the WinTel platform. That's why I only do video in a vid sled, and audio in a DAW. Trust me... been there many times, never been impressed in the converse. I edit the video as needed in a video sled, export as HD AVI (or Mpg4), import into a DAW, then score to picture. Mix & export audio back to video sled, then post it up to the director & music coordinator at the movie production house.

Possibly Power Director will do the job to edit the video, but for audio, it only had level & pan IIRC. I second the motion for DaVinci Resolve, or you could look into Corel/Pinnacle Studio. But none of the video sleds that I've used are competent at doing anything other that very basic audio manipulation. And this is my job, so...

You do know that, due to resistance, USB past 30 feet is useless, no matter the quality of the cable, right?

@smallstonefan; Hopefully you are also aware that this instrument REQUIRES Kontakt 7.7 at minimum to run. And if you've been anywhere near the NI/Kontakt forum lately, you'll know that Kontakt 7.x is a hot mess currently. Personally, Ima gonna wait til 8.x comes out next spring.

For some, reading is hard. Comprehending is even harder.

Battery 3 had two full sets of just cymbals with velocity layers that were really excellent, along with the best full brush kit ever, IMO. But I lost the loader SW years ago and have been searching since.

There's your problem.

Once I found that Kontakt 6.8 was only created to put in a nag to update to 7, I reverted and stopped all NI updates. And after following the cluster of UI/UX mistakes & buggy code issues, I think I'll wait a few more years for 8.x. And then to have the audacity to basically make 7.7 into the Home Shopping Network was a bridge waaaayyy to far.

Never fear though... because it's Apple, it will be replaced by a newer model next year, and will begin to slow down until it's completely rubbish.

Again: if you start with and use one of the default Keybinding files, modify it to your needs, and save it under a custom name (and don't EVER clik the <Zap All> button, this is not really a problem. Unless, of course, you find a desperate need to re-bind them to another key combination. BTW, complaining about anything that doesn't work in the existing version of the SW is a moot point, as it is slated to be deprecated in the near future anyway. May want to wait until the new paid version of Sonar is released and make notes then for the bakers to examine and determine if modification is feasible.

There are only 16 MIDI channels available per port, so it is possible that is the limit on enabled outputs as well. AFAIK Cakewalk is only considered as ONE port receiver. Others may know differently.

To be fair... for the decades that I spent on large format consoles, if you didn't press the Mute or Solo button 'in the center' it would often not work. That was especially true on Neve, SSL, API, Harrison, and any aftermarket motorized automation fader banks like Audio Kinetics. So maybe my aim is just better than yours. On my screen resolution it's more like the top 3 to 5 pixels, which is far less than the area covered by the active cursor. You could go into the THEME Editor and modify the target area of the graphic in the GUI if you want. Or just get over it. Aim for the middle of the button.😁

I suspect that if the Key Commands that you question are NOT bound to the factory defaults, that you may have, at some point in time, hit the <Zap All> button, which erases the supplied default bindings from SONAR 5 onwards {exceptions being the ones marked RSVD}. This shows that they are all still bound in any one of the standard SONAR Keybinding sets that were shipped with the program since SONAR 7 onwards. I concur with you that the functions are not available to re-bind in the verbose function list (which, in this instance, could be an issue), but you should have at least the [SONAR Default Key Assignments.kbn] and [SONAR Legacy Key Assignments.kbn] stored in your C:\Users\username\AppData\Roaming\Cakewalk\Cakewalk Core\Keyboard Binding Sets directory, from which you could restore the defaults, then modify as desired, and save under a custom name. I think that there should be a way to edit the file offline to at least mark some of the unrecoverable bindings as RSVD. I basically started with the SONAR 7 default set and have modified to fit my workflow overtime, and now make regular and timely backups of that file. I will attach the default files here in case you don't have them. SONAR Default Key Assignments.zip Those of us that are road warriors and users of CW since 1987 know that there have been many things overlooked, but I've found very few that I deemed "mission critical", and have always managed to find a suitable workaround.

If it's a "bug", it is only for you: The MSR & A buttons operate as normal, the Input Echo function is a little wonky in that it will toggle the tracks when using CTRL-Clik. (But... I've never had a reason to input monitor all tracks in a folder anyway, so...)

Yes, there is... using automation on the send control.

@John Vere; to me, it appears as though the OP is possibly attempting to operate on a mixed track, and lacks the patience or skill set to understand and use automation, as in applying different EQ, Compression, or other tools. Which, of course, also apply to individual stems as well.

Same reason that you can't open the Event View if there is no MIDI in the project. The SW is smarter than we are. 🤣

Are you starting with Simple Instrument Tracks (that contain the MIDI notes), or MIDI tracks driving individual VST instruments? I just ran 3 SIT tracks (bass, drums, piano) with MIDI (2 bars), WITHOUT setting up the receiving Audio Tracks first, selected all three clips, used <Tracks><Bounce to Tracks> which opens the Export dialog, set the source to <Tracks> and (starting at track #4) they all printed in order and correctly named in one operation. Then I left the receiving audio tracks in place (deleted the printed clips) and did the exact same <Bounce to Tracks> steering the first MIDI track to the first receiving track, and it also succeeded as expected. This has to be done for EACH "Stack" of clips separately but identically, otherwise it will print an audio track that is the entire length of the sequentially placed MIDI clips. Your issue may be from using PRE-named audio tracks and not steering them correctly inside the Export dialog. If you are using separate MIDI & VST instruments, same thing works IF you select both mated pairs (MIDI & associated instrument track), but again only in "Stacks", as it were. HOWEVER: if you are expecting the printed Audio clips to have the same names as the Source clips, you're outta luck. The resulting audio clips are just named for the source track (bounced). Selecting only the Second set of "Stacked" clips and using <Bounce to Tracks> (steering them again to the first receiving track)... results in this:

Why not just 'Freeze' them in place? It's the 'snowflake' icon on each synth in the synth rack.