Promidi

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.

Throw it open to the forums as a new thread.... something else might be going on unrelated to the update.

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?

Sometimes when a certain project using certain plugins is closed, the Cakewalk process remains. Then when I attempt to relaunch Cakewalk, it won’t. When that happens, I use a script I have written that forcibly ends the Cakewalk process. This active line in the script that does this is the following. wmic process where name="Cakewalk.exe" call terminate Yes, I could use the taskkill command, but I have found that sometimes that does not actually kill the Cakewalk process.

Do any plugins (synth or effect) have MIDI out enabled?

Updates are also about new features - many of which have been added to CbB since the Splat days. Very few of these publicly released CbB updates have ever given me issues. And on the rare occasion that there were small issues, they were always quickly resolved by the Bakers.

This is why I prefer controllers in PRV controller lanes. Much more control. I even have written CAL scripts that convert linear changes to curves and some that adjust the contours of those curves.

I would have thought that, because Falcon is not multi-threaded, you would be suing Falcon more (That is if any lawyer would accept the case)

The version numbers (among other things) of any of AAS plugins are found by clicking on those two double down arrows near the top centre of the AAS plugin GUI.

What is your source? If audio, then just use a tremolo effect. Meldaproduction’s Mtremolo comes to mind. If a MIDI instrument - depends on the instrument - it may have this feature built in. Or you could map a CC to the right parameters.

Yeah, that works. It’s still a bug though. No where in the CbB help file does it say about having to have the png file in the Project Templates folder for it to show up in the Start screen. There is no such requirement for CbB Project files - the PNG file shows up even if the PNG file is not present. The image data is embedded in the project file itself as it is in the Project template file. I guess this will be fixed in the pad version when it’s released.

I think the driver that comes with the Behringer UMC22 is actually a version of ASIO4ALL. (Some please correct me if I am wrong on this) Personally, I would ditch the Behringer UMC22 and get an audio interface that comes with proper ASIO drivers (EG a Focusrite Scarlett series).

I tried it here as well. Could not get it to work with a template. Projects work fine, just not project templates. I even tried loading the BBCSO PNG file from the template zip file - nada! Must be a bug. (can't even try a previous version of CbB) FWIW you could log a ticket with CW support. Mind you, I don't hold much hope, as this version of CbB might not get any more fixes.