David Baay

I notice the transport module in your video is showing the record bit depth is 32...? A quick Google confirms the RME is 24-bit. Any particular reason you have it set to 32? Whatever the reason, I would suggest changing it to 24 to eliminate that as a possible cause.

By any chance do you have a large .zip file stored on your desktop or in any path that that Sonar might be touching? If so, try moving it to another folder or another drive entirely. More generally, check disk activity in Windows Resource Monitor and see if any large file is being read.

If you had any paid version that included them you should still have them or can re-install...?

See the 'Hide Muted Clips' option I mentioned in your original thread.

I have previously requested that muting lanes would hide notes in the PRV the same as muting clips (when 'Hide Muted Clips' is enabled in the PRV View menu). But muting clips is pretty quick and easy.

Comping with multiple lanes really needs to be done in the Track View and, as recently discussed, is not well-suited to working with MIDI. Because MIDI is fully editable in ways that that audio is not (though Melodyne gets you pretty close), it's generally easier to make the necessary edits to one decent take (or maybe a compilation of several sequential takes) than to try to piece together a performance from many parallel takes.

Move to Folder is two clicks and doesn't include specifying whether to move or copy since the latter is not possible. To move/copy clips you'd either need a third click or two diffent menu options for Move to Track and Copy to Track. Then at some point you're probably going to want to be able to choose wether to move/copy clips in multiple tracks to one track or to multiple tracks with the same relationship. This option and more are already covered by the Paste Special dialog. I suppose the value of saving a click or two and not having to touch the keyboard with a no-frills context menu option might depend on how often you use it. My workflow would not benefit meaningfully.

I can't reproduce a crash adding Spire VST3 as an Instrument track to a project that already has a Spire VST2 Instrument track. But your description of adding Spire with only the MIDI source would not create a Synth audio track to host the output of Spire VST3 in the rack. If you do that manually and then make the two tracks into an Instrument track after the fact, do you get a crash at any point?

Not sure how you reached that conclusion. Admittedly I don't normally do a lot of synth automation but I have a number of projects that do, and they are working fine and have been for years. As a sanity check, I also just added some filter and LFO automation to the Spire VST3 test that I created for my reponse to the OP in this thread and it's working fine as well. The Serum demo only installs the VST2 so I can't test that one. I see that CW Support is looking into your issue with Serum. Somehow I doubt the reponse will be "Sorry, we haven't been fully supporting VST3 for the last 10 years but we'll get right on it." I kind of liked the results of my test so I'm attaching it for your listening pleasure. Spire VST3 Parameter Automation Demo.mp3

Yes. You want to do the honors? Just tell them it worked in X3 and was already broken in Platinum 17.10.

That doesn't really keep you from hitting a note early and having it end up truncated at the end of the previous loop pass, though.

A quote from my "MIDI Comping Challenge" post back in 2013 on the old forum (from a super-secret members-only subforum [wink, wink, nod, nod]): "Ultimately, though, I think the answer is that you just can't (and don't need to) comp MIDI in the same way that you comp audio, and that the classic methods of editing MIDI - fixing bad pitches, velocities, start times and durations directly and selectively copy-pasting where needed - are likely to work better in most cases. But since the tool exists, and I'm a MIDI guy, I thought I should give it a go. Maybe over time it can become smart enough to work as seamlessly and intuitively as audio comping."

I do everything in sound-on-sound mode with manual lane-muting as needed. I also seldom use loop recording as it can also be unsuitable for MIDI recording because if you hit a note a hair early at the end of one take instead of the beginning of the next, it gets truncated. Another place where a little AI is needed.

I've answered this question in the past, but maybe not for you. The assumption when comp recording is that a new take is intended to replace some or all of the previous takes in that that were presumably inferior in that section, so it automatically makes splits in all the other clips and mutes them. If you subequently decide that one of the earlier takes is in fact superior in that section, one click promotes that other clip. If only one part of it is better than some previous clip, you can always swipe with the Comp tool to break up the section further and promote the appropriate clips for each. The automatic splits are just intended to facilitate the work of replacing not-so-good material with better material. A long time ago, not too long after comping and comp-recording was implemented, I posted a "Take the MIDI Comping Challenge" demo project that had a set of raw takes with no comping and a comped set in another track showing the goal. That goal was achievable only by an excrutiatingly complicated series of comping moves, but was easy to obtain by manually editing MIDI the old-fashioned way. One of the Devs chimed in confirming my conclusion that the Comping workflow was not intended for MIDI and was generally not suited to it in many cases. As for swiping (or Ctrl-clicking selected clips) with the Comp tool to heal the splits, my recollection was that this would work for MIDI if you had Non-Destructive MIDI Editing enabled so that the clips are abutting. If NDME wasn't enabled, the empty space between notes would be cropped away so the clip boundaries were no longer abutting and couldn't be healed. That said, I just checked this and it already wasn't workng in Platinum 17.10 so either it never worked and my memory is faulty, or it got broken way back. I wouldn't have noticed because I never try to Comp MIDI. 😜 EDIT: MIDI comp split healing worked in X3. IIRC, that's when comping was implemented.

Cool. Glad to help. FWIW Sonar now has a function to Backup/Restore Settings that basically includes all of Preferences.