Promidi

What is the locale of your windows?

I loaded that exact same patch here fine. No crashes. Analog V Pro Stand alone and as a VST3 in CbB. Also moved the recorded MIDI to an SIT of Prophet VS - played as well. This is one system configured as per my signature.

Your driver for your audio interface. To “apply the script”, create a file with a bat extension with any text editor (notepad.exe will do) Put the following in there and save. wmic process where name="Cakewalk.exe" call terminate Remember the location, maybe even create a shortcut to it Pressing winkey + R and putting the above therein and hitting OK will also terminate Cakewalk

Glad you found the solution. I am wondering if it's actually recommended practice that once you have completed working with Melodyne as a region effect, that one does indeed apply the changes. Personally, when I have completed fixing up a track with Melodyne, I would usually do the bounce to apply the changes. Looking at my CPU (in my sig), you'll probably work out why.

Also, if using a Workspace, then edit that Workspace setting so that it does not save screen layouts.

Grove Quantise can do this Select and copy the notes containing the source velocities to the clipboard. Select the destination notes you want to apply the velocities to Go Menu > Grove Quantise . Set Velocity Strength to 100%. (Maybe set Time and Duration to 0%). Click Audition to test the settings (The settings will be temporarily applied) If happy with the results, click OK

Selected the track that won’t select. Open that track’s properties with the inspector. Deselect “Arranger Exclude“, in the inspected track properties. See: http://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.6.html

Which specific Spitfire instrument are you referring to? Also by “touch sensitivity”, I am assuming you are referring to velocity?

For the PRV and Staff view, I have set key bindings to set the durations (I use the top row of numbers to set various durations) In the Staff view, I have set the L key to enable lyrics entry. So in answer to your question “Is there a way to use the computer keyboard to select note durations?” is, yes you can.

The only reason I can think of for not using Articulation Maps is if you wish to have multiple articulations playing at that same time. Personally, I prefer using Articulation Maps - just remember to set the Chase modes to “Full” (They are set to “CCs by default” )

Open the project that displays the download error in safe mode (hold shift while opening) to see of you can narrow down the plugin causing this. Start by eliminating ones that you know it could not be. If, after removing the found plugin and Cakewalk is still not re-opening, this looks like a driver issue. This is when I would do a driver check (manufacturer's websites, not Windows update. Note: I have a script that closes the cakewalk.exe process. This script contains the following command. wmic process where name="Cakewalk.exe" call terminate Yes, I could use taskkill but I have found this not to do it sometime.

I think I had the middle issue with Massive X in CbB - hopefully that does not happen again.

Is the “BL” BandLab – Music Making Studio the mobile app or Cakewalk by Bandlab the Windows DAW?

Works fine here.

I see your point.....

I would definitely miss more than “a couple of bug fixes and maybe about 2 new features” if I was ever forced to go back to X3. I believe Satan actually uses Sonar X3 as one of his cruel and unusual punishments in Hell....... next to Pro Tools and Windows Millennium.

I am not sure if this is what you are after. You can edit out the expression events (CC11). I also added the initial pitch bend and shifted the MIDI to start on measure two. Some notes I have added intermediary notes - of course these can be edited as if not required. You should be able to just import this MIDI into your project Note: I do not have Dimension Pro, but this should work in SI Strings using the preset “Default Prog” Attempt 1 pitch bend.mid

In the 30 years of editing MIDI data with the various iterations of Cakewalk, the pitch zero event is invoked exactly where I place it. In that time, I have had zero issues with any pitch bends in any synth. If a note has a release built in, the pitch bend will act on the release component as well at the time stamp of the pitch bend event. It's always worked that way for me.

Ah I see. I took a look at your CWP file and I think I can see what you are meaning. What you have to realise is that sometimes a note off event does not immediately chop off the note’s actual sound. There is a release component of that sound that will continue to sound after the note off event (Even if a short duration). If you enter a WHEEL > 0 event before the note on, the note will be shifted in pitch (as required) If you change the pitch bend value right at the note end time and start a new note, you will still hear the release component of the previous note playing, but at the new pitch bend value. This would happen with any synth where the release times is not set to zero. The way I get around that is either temporarily change the release time to zero (Usually CC72), or make sure that the same actual note is used from one note to the next and sure there are no pitch bends on any note ends (or starts for that matter). If you need a note to be bent, pitch bend before the note start. Note: I use heaps of pitch bends in each of my projects.

Are you using actual WHEEL Events or CC events. There is really no such thing as “cc wheel events” I just tried using WHEEL events in SI strings and if the last Wheel even is not zero, the pitch of all subsequent notes are shifted. So the pitch bend does not end earlier than it should. Unless I am completely misunderstanding your question. Note: I always use 960 ppq

Ah THAT double arrow. Now I see what you mean...... I was looking at the workspace name itself. That double arrow makes Cakewalk as Full screen as it can be - even losing the Windows title bar. On my system, it does just that. Even when Full screen is activated, the workspace name itself is still visible. So what you describe happening on your system is not by design. What graphic card do you have, and have you gone to the manufacturer's website (as opposed to relying on Windows updates) to see if there is a later driver? Also, are you running a fully patched Windows 10 PC? (“fully patched” means with all possible updates installed).

I use workspaces all the time. No issues here. I am not sure what you mean by “double headed arrow to remove the Cakewalk strip at the top of the screen”

Are you running Windows 10? If so, is your Windows 10 fully patched? Have you tried a Reset then Rescan? Does updating to Cakewalk by Bandlab 2023.09 Build 62 solve the issue?

One other thought. Are all MIDI events on a given MIDI track set to the same MIDI Channel. Are all MIDI tracks set to a specific MIDI channel rather than “none”? Personally I make sure all MIDI events on a given MIDI track set to the same MIDI Channel. I also set all MIDI tracks set to a specific MIDI channel. I have also configured my Cakewalk so that when I bounce MIDI tracks, all MIDI channels that are in the resultant MIDI clips get re=channelled to the MIDI channel of the track containing those clips. One other uncomfortable possibility is that you simply have a corrupt project.

Do you run any CAL scripts and then, immediately after, do a delete of events? (Using the “delete” button on your PC keyboard) I know, from actual, experience that that can cause unpredictable results in CbB (including adding CC events in other parts of the project). In some circumstances immediate deletes after CAL scripts can crash CbB. In all of my projects, I use heaps of controllers and I have never had MIDI events just appear. The only MIDI events in my projects are ones I have manually entered with the mouse and CAL scripts. Of course I am extremely careful not to run a CAL then immediately delete. Has turning off those MIDI outs in the VSTs and the MOTO M make a difference?