David Baay

I can't repro either if those issues on either my desktop DAW with PCIe MOTU interface or my laptop with a USB Roland interface. But I have noticed that the Win10 spinner (hourglass in Win11) persists for a long time when the Start Screen is opened though it doesn't seem to interfere with launching anything.

FWIW, there is a workaround to use the left and right sides of the External Insert to process two mono signal independently though you'll still have to give up two I/O channels to the one EI instance: 1. Set the Outputs of two mono source tracks to a new Aux track named generically 'EI Host' and pan them hard left and right. 2. Add the External Insert to the FX Bin on 'EI Host' and assign I/O pairs to it as usual. 3. Output the 'EI Host' track to a new Patch Point. 4. Create two 'EI Return (L)' and 'EI Return (R)' tracks and set their Inputs to the left and right sides of the new Patch Point (renaming it "EI Return" in the process for clarity). 5. Leave the Interleave of the two Return tracks set to stereo. You can now route the two I/O channels through indpendent mono FX. The 'Return' tracks will echo and record the processed signals independently and muting/soloing/panning will work as usual. The one anomaly you might notice is that the Confidence Recording preview will show the two return signals merged to a mono waveform while recording, but when you stop recording, you'll see the correct mono waveform in each track. Also, I found the input assignments of the Return tracks changed to Stereo when I saved this setup as a Track Template which is unfortunate. @msmcleod Did say he would look into addressing this limitation at some point, but that it wasn't trivial.

The Project Preview file is created by default on the first Export of the project from the new Sonar (see the checkbox at the lower left of the Mix and Render section). After that, you can choose to enable/disable the option to replace the preview file or not on subsequent exports. The rendering of the preview file should follow the Source Category and other settings in the Export dialog so that it matches the level of the 'external' export file. I suppose it's possible that routing of the playback from the Start Screen could alter the playback level, but I haven't noticed a difference in any of my projects; the Preview always plays at exactly the same level as the live project. You can find the preview files in the Audio folder of the project; they have long UIDs for names. If you save alternate versions of projects to the same project folder (as I often do) there will be a preview file for each and it won't be easy to tell which file is associated with which .CWP except maybe by its date or by changing the file extension and seeing which project loses its preview capability in the Start Screen.

@Kevin Walsh what are you specifically referring to when you say UI lags behind? Also can you share some info about your displays and windows settings for display resolution and scaling? Yeah, this is not the norm. Sonar is currently no different from CbB in which the Now Cursor animation has always been a bit jittery with 'ghosting' at higher zoom levels, but not "lagging".

Where possible, I always recommend clicking the virtual keyboard in the synth UI to generate audio output. This also verifies the synth output is correctly assigned to input of the Instrument/Synth track.

Track 4 is an Instrument track (combined MIDI and Audio) for SI- Electirc Piano. All you need to do is Shift+Drag (shift to constrain the time when dragging vertically) the MIDI to the Instrument track, and get rid of the separate MIDI tracks. If you click the button at the lower left of the instrument track to Show Lanes, you can add a lane and keep the two MIDI clips separate in that one Instrument track. It should actually work the way it is but, technically, the synth associated with an instrument track is intended to receive MIDI only from that Instrument track.

I found the cause in my case: having a Disconnected synth associated with an Instrument track above the one from which I was saving a template. I haven't tested all the possible permutations of where the Disconnected synth is in the Synth Rack, but I suspect that having any disconnected synth above the one for which you're saving a template will cause a problem. In my case, the synth was manually Disconnected, but I'm guessing that freezing an Instrument/Synth track would have the same effect because it disconnects the synth. Reported to the Bakers.

Are you seeing this in CbB or the New Sonar? I just did a quick test and found CbB working as expected, but Sonar assigned the input of the audio side of the Simple Instrument to the audio interface input instead of the synth's ouput when saving the template. I know it happened on save because Sonar's template is broken in both Sonar and CbB, and CbBs template is working in both. But when I tried it in a fresh project, it worked in Sonar. I thought possibly it had something to do with the Instrument track having MIDI in it when the template was saved, but that didn't check out. I'm still looking into it, but the bottom line is that your template is probably being saved with the wrong input assignment on the audio side. You can split the instrument track to see and correct that. EDIT: I found at least one older report of this issue. Looks like I will need to send a reproducible case to the Bakers. Based on what I;m seeing it seems to be project-specific somehow - possibly to do with what other virtual MIDI ports that are in the project and/or hardware ports coming and going. The USB connection to my audio inerface has been mechanically flaky lately which might be a factor. Users have reported other cases of port assignments getting crossed-up when hardware ports change.

The screenshot is showing a few events at 640 ticksso CbB is at the default 960PPQ. If you open a MIDI file recorded at a lower PPQ, CbB will adopt that. Or did you maybe mean rpn/nrpn messages?

In that case you should get the same good result exporting only the Master bus. What source did you use originally in the export dialog?

Not that I'm aware of. Try bouncing the Master bus to a track and see if the one channel's phase is visibly reversed from the re-imported export that you fixed.

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.