Promidi

To date, I have yet to pay RRP for any plugin..... (well maybe the $US29.00 spitfire originals - but they are more bang for buck anyway)

Yes, that's what I have always done to select notes or notes that don't fit around the selection rectangle...

Is it possible to add a feature that can allow note (or nodes of an automation lane) selection using an irregular shape. A way it could be implemented is, with the smart tool enabled, holding a modifier key (say SHIFT) while right mouse button drawing anywhere around the notes (or nodes of an automation lane) you wish to select. Much like a vector graphic drawing program allows.

I tried another audio export and the issue with the quantised pitch bends with a buffer > 0 appears to be resolved in build 111

What synth are you playing with the MIDI track? Just to make sure nothing was introduced with the Cakewalk early release (I am on early release 2021.9 Build 99) I did another test. This time with TruePianos with some notes intentionally off by a bit. I opened the quantise and set the Quantise duration to 16th and set it to affect the start times. When I hit “Audition”, the selected notes temporarily shifted to their quantised start times and played the result (as expected) So, as we speak, and with a fresh test, I am not having the issues you are describing. Does this hang happen on any synth (or even a straight MIDI track that is routed to external gear)?

Is this the 64 BIT version?......

No a little more info....?

Needs some cow bell...

I created a simple tempo map to test and I did not find the issues that you described. Is it possible to, rather than deleting the node, hold down SHIFT while dragging the node from 17 to 18? Holding SHIFT restricts the movement to the initial mouse movement. Also, I was able to edit the M:B:T values of any of the nodes that were not on the measure. Basically, the workflow for editing a tempo map is identical to editing automation.

I was actually liking the Effect bin menus having the dark background in build 95. I was kind of hoping this dark background could be used for the adding synth selection as well... (Same with the marker selection drop down in the marker console module) Any chance these can be exposed in the Theme Editor?

I concur about reinstalling CbB.

If you really want to do it in the same track, you could find a synth that responds to polyphonic aftertouch - and then map polyphonic aftertouch to pitch. Such synths are rare. Cakewalk’s Z3ta+ 2 is an example of such a synth. However, multiple instances to multiple tracks might still be easier - especially as, at this time, Cakewalk does not allow easy editing of polyphonic aftertouch events in the PRV.

You’re right that pitch bends will bend all notes on a given instrument track. If you want to bend just one note in a chord, you might want to run multiple instances of the instrument. That way you can bend notes independently of each other. I use this technique when programming pedal steels using MIDI and pitch bends.

Which exact version of Cakewalk?

Being a production machine I run regular backups. The default location on your hard drive for your VST3 plugins is “C:\Program Files\Common Files\VST3” Most backup programs allow you to select which folders you would like to include. To prevent data loss of your VST3 plugin files, it would be good to include this folder. Actually, I do a weekly backup that is pretty much the entire C:\ drive. If you have one, your IT specialist should really be on top of all of this.

I have fired off an email to AAS support regarding this. I tried another of their VST3 synths (VS-3) and I got the same issue with that one as well. Here is hoping AAS can take a look at this for us.

I rechecked the version of String-Studio VS-3 I was using when this issue occurred. It was actually the VST3 vsti of that plugin.

Excellent update. However, I have noticed something with the export results using different export buffer settings that I am not sure if it’s expected. If I have a VSTi (in my case, AAS String Studio VS-3) that has sequential pitch bend events applied to achieve a glide from one note to another, the higher I set the export buffer setting to, the more stepping in the pitch bends I can hear. I am using pitch bends i9n the PRV controller lane. I have net tested it using automation as I use CCs in the PRV for my workflow. To achieve an exported file with a smooth pitch bend generated glide, I need to set the buffer to 1. To make sure it was not a String Studio VS-3 issue, I tried the same thing in a Rapture Pro patch that had just one sawtooth - same ting happened there as well. I get stepped pitch bend. Is this expected behaviour if I set the export value is set to higher values?

Different.

I think he is after a mid point marker for the PAN CC10 controller. The centre value for pan is a value of 63, not zero. If you open up the PRV and select CC10 in the controller lane, there is no horizontal line denoting the value of 63 - which is the centre value for CC10. To see what I mean, open up the PRV and select “Wheel” in the controller lane. That MIDI event lane does indeed have a horizontal line showing where the pitch bend value of zero is. This makes it a bit easier to insert Wheel = 0 events (You see a small dot where the event is if the value is zero). It would be handy if CC10s showed a horizontal line denoting a value of 63 - which is the centre value for CC10. What I have done is created a Studioware panel (using a very early version of Cakewalk) with CAL scripts attached that inserts default values for the most used controllers - of course, for CC10, it inserts a value of 63.

Sometime when I would like Cakewalk to implement something, I like to try and find work-a-rounds while I wait (which, sometimes, could be a while). I have written a few CAL scripts that help with my work flow. I have written one that shifts the selected controller event’s values so that the average of them is CC = 63. Of course, if applied to CC10 events, this CAL script makes the lowest value the same to the left as the right is to the right. If the script is run on a single selected CC10 value, it changes that value to 63 (which, of course is centred. Then I have another script then draws a line of CC values between the first and the last selected CC events, replacing what is in between with that line. I know CAL scripts have been officially depreciated in CbB, but they still come in handy to speed things up a little.

I do have the PRV track manager open all the time, and I do edit multiple tracks in the PRV at times. While I very much welcomed the improvements in the PRV workflow with CbB, sometimes it would be nice just to have a quick way (by means of a keypress) to access a track selector (like you can in the Staff and event list view) No biggie, but no harm in asking....

The version distributed with Sonar Platinum and Professional was Melodyne Essentials 2. This was eventually freely upgradeable to Melodyne Essentials 5.1.1.003 However, the version that is provided with Cakewalk by Bandlab is the 30 day trial of Melodyne Editor. I am not sure what functionality you are left with within Melodyne once this trial is over. I have Melodyne Assistant 5.1.1.003 so I can’t really check. What ever version comes with Cakewalk by Bandlab, can be upgraded to the latest version (Albeit, still the trial)

Can we please have a “Pick Track” in PRV in the same way that it's available in the Staff and event list view. Yes, I know we can use the track manager to the right in the PRV window, but sometimes it would be handle to just quickly use the “Pick Track” from the menu (or even a keybinding)

As a test, I dragged an audio clip to an existing MIDI track. The Melodyne menu appeared. I chose the “Melodic” algorithm. The converted MIDI events appeared in the MIDI track (and played the same notes that the audio contained) I also tried the “Percussive” algorithm. That also created the MIDI events (albeit on the same note). So , on my system (configured as per my signature) that worked as expected. I have Melodyne assistant 5.1.1.003 and the source audio clip I used was a monophonic.