David Baay

Which drum kit, and are you monitoring the kit's brain through CbB or directly, or using a VSTi? Either way, I would record the audio from MIDI playback, sync the first audio transient with the first MIDI event, and see if there's a significantly variable timing discrepancy between later MIDI events and their corresponding transients. There should be virtually none with a VSTi and if you're monitoring the kit's brain, jitter in the MIDI interface and the brain's response would usually be on the order of only 2-3 ticks (1.0-1.5ms at 125bpm) which shouldn't be noticeable. EDIT: Seems I wasn't reading carefully and missed that playback is through a VSTi and maybe you're just recording MIDI from a keyboard rather than electronic drum kit as I originally thought. My suggestion still applies in any case: check the audio transients of a realtime synth recording against the MIDI to verify what you're hearing is real. Then maybe try a freeze/fast bounce to see if it's different.

Anything other than CC7 Volume, CC10 Pan, CC91 Reverb and CC94 Chorus will remain in the track because there's no dedicated track control for it. Also, only the initial value will be moved to the track control; if there are additional events that change tha value later in the track, those controllers will remain visible in the Event List and PRV Controller Pane. That initial value is sent every time playback is started unless it's overriden by starting playback later in the track with Event Chase enabled in Preferences > Project > MIDI (which it is by default).

I think you exaggerate both the number of issues reported and the amount of resistance there is to acknowledging these issues. And it's indesputable that a significant majority of issues reported on the forum turn out to be due to misuse, misunderstanding or faults in 3rd-party software/hardware. so there's goood reason to question when someone cries BUG! without providing reproducible steps (acknowledging that the symptoms of some bugs are not easily reproduced). Another exaggeration; he said "hundreds".

I’m sure everyone here has only the desire and intent to help the Bakers make Sonar as good as it can be.

Controllers for which CbB has dedicated track controls are read into those controls and removed from the clip, but only when you open a .mid file as a new project. If you import into an existing project that won’t happen. And in any case, they will be written back to the file on save as MIDI.

What synth, and what exactly does "lose the guitar vst" mean? Are you seeing the patch or FX parameters change or something else? Also, if you watch the Event List is the channel or velocity of notes or anything else changing when you bounce?

Thanks for the confirmation, Glenn; I suspected as much.

I'd be interested to hear the Bakers' explanation for the flattened graphics. I presume it was a combination of "flat is the new black" and that flat is easier to design and re-theme in vector world and more efficiently rendered in a real-time application with many different and frequently-switched views where re-draw performance is paramount and users may not be running state-of-the-art graphics hardware. If converting a bitmapped UI to vectors were easy, and had no performance impact, I expect the Bakers woud have done it long ago with minimal changes to the existing look and feel. But I freely admit to having zero knowledge in this area.

Okay, John, I've seen you post this several times and also say it that way in your videos so... friendly correction it's "PRV". ?

Not seeing that here; check mark appeared immediately on the first track and persisted when enabling another track and switching back. Tried several times with different tracks.

Good one! I thought I recalled there being a way to do this, but wasn't finding it.

Yes, I see that now, though many times it looks like he's missing the hotspot. Looks like Modulation controllers but shouldn't matter. I've not used the transform tool that much but played around for quite a while and couldn't replicate the problem. I know in that past there have occasionally been issues that affect only some localizations - possibly this is one of those. Otherwise maybe a mouse driver/display scaling issue.

I knew you'd come around so I let it go without comment. ;^) I have issues with contrast/legibility of some things, but that is not one of them. That said, I wouldn't mind having the red dot on the arming buttons back.

If you drag the sides of the box between the transform nodes, you will change the selection range. Make sure you're seeing the different cursor that appears over the nodes before dragging. And if you do inadvertently change the selection, you can just drag between the nodes again to reset the range rather than disabling the transform tool and re-selecting.

It was always possible to drag those panes open in CbB but there were no lines between the Video, Arranger and Tempo tracks to indicate where the panes were divided, and no tool tips to show which was which. The pane dividers were made narrower because they were starting to take up a lot of real estate.

Hard to know without seeing the entire track view. If the muting is across multiple tracks, I would guess some other track is soloed. If the grayed clips are in lanes of the same track I would guess you clicked one of them in lower half where the Comp tool is active, which would mute everything else in that region. In that case, selecting all the grayed clips and hitting K should unmute them.

Just shift+drag the selected notes to another lane, and click the clip with the notes left behind. You can then leave them separate or bounce back together.

Okay, yes, I'm aware of that specific issue with Quick Grouping I/O assignments via the Inspector. I thought you meant something more general in the Track View itself. Yes, I see that on both my unscaled desktop displays and scaled laptop.

Newer components of Shared Utilities have always been fully backward-compatible with earlier releases. And going the other way, older CW installers will not overwrite a newer file so there shouldn't ever be an issue.

Much sharper overall for me on both my 1920x1200 desktop monitors at 100% and my 3072x1920 laptop scaled to 160%. Easiest way to see it is to have them both full-screen and Alt+Tab back and forth. I'd like to see some fonts enlarged in Sonar to better match CbB (e.g. Transport and Mix module numbers and labels), but they are definitely less fuzzy.

Check the lock options in the context menu for the Control Bar if either Lock and Justify or Lock and Center are selected, the scroll controls will go away. Lock Order or no locking will give you the controls. In general I would suggest that anyone experiencing behavior different then CbB first check for preferences/options that have defaulted to a different state in Sonar. These need more detail.

You just need to switch to the large transport. I only use the small one and do all navigation with shortcuts.

Ten years from now a chip in his head will energize the operating system and upload the latest user manual to his BRAM (Bio RAM) automatically.

Are you running an extremely small ASIO buffer? All versions of SONAR up to the final release of Platinum had a limitation that they would not display a histogram in the Perf Meter at ASIO buffers less than 32 samples. This was addressed in CbB at some point. Also, the metering algorithm was less sensitive in SONAR and would show a lower load than CbB. If the project is light enough and your buffer big enough, you might not see any activity in SONAR for a project that shows some low level activity in CbB.

PM me a link to the MIDI file (or partially-reconfigured project) and let me know what you want/don't want on each track. I'll fix it for you. Dave