Promidi

Now I am not saying there is not an issue at you end, but on my system (configured as per my signature) I am not getting any crashes with any of the updated AAS synths. They just work - within Cakewalk by Bandlab, a slim host and standalone. Using CbB, I recorded MIDI into a track with a SIT of String Studio VS-3 v3.2.0. I played it back, saved, exited and reloaded, played again, then exited. I then reloaded, replaced that same track's instrument with Chromaphone 3 v3.1.0 (using a dual layer patch). played, saved, exited and reloaded, played again, then exited. I did not experience any crashes. Nor have I ever so far There has got to be something particular about your system that is causing this on your end Hopefully AAS will get back to you. I have actually recently reported a bug with Ultra-Analog-Va3 3.2.0 and they have acknowledged it, and will “ have a fix for that very soon”. FWIW, you might want to send Cakewalk support a crash dump, to confirm it is the plugin actually causing the crash. Maybe CbB is interacting with the updated plugin in a way that the new plugin does not like but was tolerated with the previous version.

Depending on the specs of your PC - that might be enough. you may simply need just the USB Audio interface. My PC is using the configuration as per my signature and I can still get some decent results with no dropouts.

I have received a reply from AAS regarding the change logs. They are as follows: Of particular note for all: Dropped support for 32-bit DAWs. Dropped support for Windows 7 (This did not surprised me) Note: not supported may not necessarily mean that it does not work - it just means if you contact AAS support, and you say you’re running Windows 7, their first answer will be to update to Windows 10. Chromaphone 3 v3.1.0 March 30, 2021 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. • The Scala file name wasn't always properly shown in the settings panel. • The master tuning frequency could fail to load properly in some DAWs. • When a project was loaded in a DAW, the current preset was always shown as "Edited" even if it was not. • When resizing the window, vertical alignment of text could be wrong. Lounge Lizard EP-4 v4.4.0 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for 32-bit DAWs. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. Objeq Delay v1.3.0 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for 32-bit DAWs. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. String Studio VS-3 v3.2.0 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. • The Scala file name wasn't always properly shown in the settings panel. Strum GS-2 v2.4.0 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for 32-bit DAWs. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. Ultra Analog VA-3 v3.2.0 Added in this update • Apple Silicon (M1) compatibility. • Dropped support for Windows 7. • Dropped support for macOS 10.7, 10.8, 10.9 and 10.10. • Improved behaviour of Windows installer. Fixed in this update • Fixed possible crash in Logic Pro when removing plug-in from track. • The Scala file name wasn't always properly shown in the settings panel. • The master tuning frequency could fail to load properly in some DAWs.

Looks fine here. Have you tried another browser?

One thing I noticed is, from these latest versions going forward, that they no longer support 32bit systems. See: https://www.applied-acoustics.com/support/deprecation-of-32-bit-applications-and-plug-ins/

Open Bandlab Assistant > Apps tab, down arrow to to the right of “Open”> install addons.

I have written to AAS and asked for a change log for all of these updates.

All Applied acoustics instruments and effects have been updated. The current respective versions are now as follows: Chromaphone 3.............................................v3.1.0 Lounge Lizard EP-4........................................v4.4.0 Lounge Lizard Session 4................................v4.4.0 Objeq Delay....................................................v1.3.0 String Studio VS-3..........................................v3.2.0 Strum GS-2.....................................................v2.4.0 Strum Session 2............................................v2.4.0 Swatches (AAS Player, all sound packs).......v1.5.0 Ultra Analog Session 2.................................. v2.3.0 Ultra Analog VA-3............................................v3.2.0 Download links are all here: https://www.applied-acoustics.com/support/ If you own many of these, it might be easier to download and install the combined installer from your AAS products page (select Custom “All” installers) https://www.applied-acoustics.com/portal/products/ you will be asked for your AAS login credentials.

I immediately thought of MeldaProduction as well...

Only MIDI notes. The only use for CC data to as a shift function (if configured as such).

Articulation maps can do this.

Normally Google is your friend. Also, what you could do is grab the MIDI Reference for the P-125 and create your own. (They are simple text files with an INS extension) https://au.yamaha.com/en/products/musical_instruments/pianos/p_series/p-125/downloads.html Here are some instructions to do this https://www.tweakheadz.com/how_to_build_a_cakewalk_ins_file.htm

What I would is write two CAL scripts that move the Now Time 1 at a frame (1 CAL script for forward , another for backward) Then assign a keybinding to those CAL scripts.

Is each instrument set to a specific MIDI channel, rather than onmi?

Select all the notes you want to change. Head over to the Event Inspector Module. Change the MIDI channel there. Done

Are there any other events in the Windows system or Application event logs that might shed some light.... Do you have any other software running in the background - like antivirus software. Anything else in the start up. Systernals Autoruns will show you what start up programs are disabled. You might want want to send a crash dump to Cakewalk support at https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633 https://discuss.cakewalk.com/index.php?/topic/3865-better-problem-reporting-how-to-capture-a-crash-dump/

Are you using the latest version of CbB (Which is 2021.1 Build 98)? In the Export dialogue box, under Bounce settings, what is your “Source Category” set to? What happens if you disable “Fast Bounce”? What happens if you disable “64 bit engine”?

Because I want to use the CC Controllers in the PRV. (I use the Transform a lot, for eg)

Title says it all...

Title says it all......

Define "the program" Sounds like this is an issue with something other than Cakewalk by Bandlab. Many people on here are not having these issues with Cakewalk by Bandlab. You really need to be providing much more information rather than simply assuming that the issue must be with Cakewalk.

Looks like a plugin that the old project is using that looks to be causing the issue. You might want to hold shift while opening the project to try and narrow it down. If you have many plugins and looks like this will take time, you might want to start with any 32bit plugins (if present). Then start removing the older ones.

Have you rebooted. Otherwise, can you give us more information?

When you did this, did you follow steps similar to those outlined in the following article? https://www.windowscentral.com/how-move-default-user-folders-new-drive-windows-10

I just tried it from my PC and it's fine. There must be some issues with your PC itself that is causing this. Have you moved your Windows document folder by any chance?