David Baay

Good point. The one time I had realy chronic and mysterious crashing turned out to be due to bad RAM, verified by Memtest. And other apps were not affected; only SONAR was using RAM extensively enough to hit the bad blocks. But it seems the OP has disappeared...?

The region muting is due to the 'Mute Previous Takes' option being enabled for Punch recording. As Mark pointed out, it can be un-muted by sweeping in the top half of the clip with the Mute tool.

This doesn't make complete sense. The Quantum should be ouputting directly to and external amplifier or powered monitors; your onboard sound should not be involved. This is also oddly stated. It should the Output of the Master bus that's assigned to the Quantum's main outs, not a Send. That said, a Send would work. Are the meters on the master bus showing activity?

Understood. I often do that, and sometime regret it when someone later posts that I overlooked something. ;^)

FWIW, I don't see that here with a wireless Logitech mouse using its proprietary dongle. Maybe depends what you're hovering over in the TV...? Othewise could totally be hardware/firmware/driver-specifiic.

That all works for me, but because it's a "Selection Group", you have to select the group to have the edits apply to the group. This is actually handy because it allows you to still make individual edits to unselected clips in the group or to deselect a subset of the group without having to jump through hoops.

a.k.a. "new code". In an application as complex asa DAW, even the best coders will occasionally produce problematic code that fails to anticipate some use case or set of conditions that leads to bad/unexpected behavior and even the best beta-testing process can miss things. The point is simply that all code changes are potential sources of regression and instability. Obviously there's no avoiding this if the software is to be enhanced, and some changes are riskier than others. In this particular case, I would say the risk is relatively low except that adding new tracks is one of the most fundamental and frequently-used functions in a DAW so any breakage would have a big impact. In any case, I never expressed any particular objection to it; I simply suggested that track templates largely address the need. IIRC, the old forum did have a voting system for feature requests. Here, the 'Like' option should suffice. But the level of participation in the forum these days is so low, I'm not sure how useful any voting system would be.

Seriously? Where do you suppose bugs/instability come from if not from adding new code/features?

Shouldn't you be posting this on Microsoft's forum since a Windows Update precipitated this? That's a lot of vitriol for someone who has apparenly only found it necessary to come to the forum with a problem once in years of using CW. In any case, it seems you missed this post about CW's fix for Microsoft's blunder:

I knew I should have asked for a screenshot that wasn't zoomed in so far to see the full context, but given that the clip gain was having a visual (as well as audible) effect on part of the clip, shouldn't his screenshot show a color change in the clip where the Region FX starts?

Clip Groups. These can be created after the fact or while recording (see record options): https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.34.html

Duh, of course.

You should be able to import .m4a files into Sonar the way you would any other audio: drag and drop to an existing track or to an empty area of the clips pane, or File > Import > Audio to a focused audio track. Sonar will convert it to a wav file. I just tried it with a random file pulled of the Interwebz, and it worked as expected.

CW's default octave numbering starts at 0, making middle C (Note Number 60) C5. There's no standard in the MIDI spec and different software/hardware manufacturers use different standards. Numbering from -2 so that middle C is C3 is common. You can either just keep it in mind or change CW's 'Base Octave for Pitches' in Preferences > Display to match the VST. This won't change the note number that's sent, just the displayed octave number. The MIDI might still need to be re-mapped or transposed.

Sigh...

For default audio tracks, you only need one template. This would be no different than having a default for Insert Audio Track. Only Instrument tracks would need individual track templates, and they already do. Just add the EQ to each Instrument track template when you create it, and you're done. And a track template includes the Prochannel configuration. Yes, a modicum of extra mousing is involved in navigating to 'Insert from Track Template', but in the grand scheme of how long it takes to conceive, record, edit and mix a project. it's insignificant in my view, and maybe not worth the development time to implement a new feature that's largely redundant. Let me just add that there comes a point where it's truly more sensible to simply accomodate the way a program is designed and make the best use of what's available rather than insisting on having everything optimized to your personal workflow. Progress is in the eye of the beholder. This is a forum, meaning all are welcome to share opinions on any post. I leave it to the developers to weigh the responses on their own scales which may be calibrated differently than yours or mine.

Slate probably just has different note mapping. You can add a Drum Map, but for quickie testing you can just drag the cymbal hits up and down in the PRV until you find the right sound.

If you have a project that 'Commits' correctly in CbB and not in Sonar, you should share it with the Bakers.

Yeah, I had a look at it and the logic seemed inefficient; seeing a typo in the header had me worried from the get-go, but it worked so I let it go. ;^) One of the challenges of writing a CAL script is designing it to handle unexpected input in a way that gives a desirable result, including not hanging! It can take a lot of extra thought and effort to anticipate and handle all possible inputs gracefully. In this case, it should have at least been expected that the input might already be variable, and ask the exact question that Promidi asked. You can open a CAL file in any text editor like Notepad, and the header section will often clarify how the prompted variables are used and/or other details about how the script works. A really good one will include comments to explain what it's doing at key points. I do this for myself so I can understand what the hell I was thinking at the time if I have to revisit something later.

Sounds like a job for Track Templates.

Are these systems using English language? There have sometimes been odd issues like this specific to certain system locales.

Sorry, I have no really good ideas why this might be happening other than that. But if it's failing in just a few specific places, you might try splitting those clips at a convenient point and seeing if the separate clip envelopes will behave.

I just did a quick test randomizing notes that were all at 100 to be between 90 and 110, and it seemed to do exactly that. Any chance your CAL file was modified at some point to override what you enter and hard-code 50? Last Modified date on mine is 12/30/2011.

This is optional, and disabled by default I thought: Preferences > File > Advanced > Allow Only One Open Project at a Time EDIT: Ctrl+Shift+T is Insert MIDI Track and has been for long time so far as I can tell though I never used it. Ctrl+Shift+B is Maximize/Restore Tabed View which is pretty much the same as Shift+D to maximize the multidock. I'm not aware that there were ever default bindings for Bounce to Clip(s) or Transpose.

Just be sure to switch it off agin when not needed. Forgetting it's on can lead to some head-scratching moments when you're just trying to make on little change on one track.