David Baay

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.

... or under one.

Undiagnosed chronic crashing is not wholly unusual; given the symptoms and other factors having been eliminated, I would tend to suspect audio driver misbehavior. But unsuccessful saves with no indication of a problem is pretty much unheard of which points to some sort of O/S or hardware/firmware level issue. Is there anything atypical about your storage setup like disk arrays or network storage? Have you recently changed/updated your ASIO interface and/or have another one you can try to see if stability improves?

'Delete Hole' has largely been superceded by Ripple Edit All. See the control at the top right of the Track View.

Try enabling 'Set Now Time with Full Restart' in Track View Options. This shouldn't always be necessary to keep things in sync when changing loop points, but it can be in certain situations with certain plugins, etc. The downside is it will tend to make transport seeking audibly 'glitchy'. You might also check whether the behavior is affected by the size of your 'Prepare Using..." buffer for MIDI.

Verify the Master bus output is assigned to the correct ports. It may be going to 'None' or to some other driver or to the wrong pair if the onboard sound driver offers more than one.

Good thought, but as the OP pointed out, the view is showing 'Note' events in the Kind column, and even showing them all selected, but not showing the data for them. I does look to be some sort of system-level display issue, but I can't think what it might be other than scaling or some issue with specific display driver being used.

I coudn't reproduce this. A few questions: Is it audible or just a waveform drawing error? Have you seen more than one instance of this? Is it a single clip in a single-lane track? Was the range of the lowered gain segment modified after setting the level?

I can repro that.

Make sure you have Stop at Project End enabled - last item in Track View Options.

Aim Assist looks just like the Now Cursor here, and I'm not aware of any setting that would change it other than toggling the time indicator on and off with Alt+X. What theme and display resolution? If this just started, maybe try a restart/reboot, or even just tab away from CbB and back.

The result of loopback recording depends on record latency compensation; if your Manual Offset is dialed in to correct for the difference between the actual/measured latency and the driver-reported latency (almost never accurate) , the timing will be sample-accurate. Recording internally to an Aux track via patch point has no latency and requires no record compensation. It should be sample-accurate regardless of count-in.