scook

That is a way. Consider saving incrementally. As mentioned in the OP Possibly the machine was used for some other purpose and something changed to cause the failure. Maybe some other software was installed or updated (including the OS). I have no idea how the machine is used or maintained. Of course, we are not sure if the problem is plug-in related but it appears to be a good candidate ATM.

In CbB to send the same MIDI data to multiple targets either Clone the instrument/MIDI tracks and use linked clips or Use one MIDI track and a virtual MIDI cable (LoopBe1 is the best free choice for this) to drive multiple instrument/MIDI tracks.

Large projects with lots of plug-ins are certainly more challenging that small projects. Again if projects load in safe-mode with no plug-ins and fail to load with some or all plug-ins, the problem is likely with the plug-ins. Determining which ones can be time consuming. If there is a common plug-in or set of plug-ins used in a collection of failing projects, those would be the first to suspect.

If a project loads without plug-ins in safe-mode, it becomes a process of elimination to determine which plug-in(s) if any are the problem. It could be any one or a combination of plug-ins. Even if the project appears to get past a plug-in when loaded in safe-mode, it does not exclude that plug-in from being a problem. Still there are a finite number of combinations and it appears that loading without plug-ins gets past the error message so this may be a good way to work the issue.

You are welcome. Glad it worked for you. At some point consider playing around with buses. They can be very useful for a variety of tasks.

Start with no to all plug-ins If that works then it is likely one or more plug-ins causing the problem. If not, it is likely something else.

It appears that CbB does not see any ASIO driver. Usually ASIO drivers are supplied by the hardware manufacturer and must be installed before using the audio interface. When using a device without an ASIO driver such as the internal sound chip in the PC (n.b. the RealTek ASIO driver is buggy and should be avoided) a differenT driver mode must be selected. This is set on in Audio > Playback and Recording preferences shown in the image above. For Win10, the WASAPI modes are best choice. For other OSes try WDM then MME.

Craig Anderton did a review of an older Anthology release which included the H3000 Factory and H910.

When Melodyne Region FX sections are rendered references to the Melodyne plug-in are removed from the project. AFAIK, any plug-ins in frozen/archived tracks are not accessed with a project is loaded. Uninstalling a plug-in is functionally the same as running in safe mode, skipping offending plug-ins then deleting them. Of course, safe-mode is per-project solution where uninstall may be less work if there are many projects involved. Either should allow the project to open if the problem is related to the plug-in.

The H3000 Factory does not include all the algorithms from the hardware unit. Eventide broke out the algorithms into several of their plug-ins including the H910, H949, Octavox and Quadravox (and probably the H3000 delay, IDK my H3000 did not have multi-band delay but it was an older unit). The H3000 Factory is OK but of the plug-ins currently on sale I use the H910 most often.

There were reports of un-rendered Melodyne 2 parts crashing SONAR when Melodyne 4 was released. This could be the problem. If it is, the original clips should still be in the project but the Melodyne affects clips may be unavailable.

It is a hot fix for 2020.01 see the announcement post for details

OK Based on what has been reported - There is a problem in a project. It occurs at or before loading Melodyne. There are "many" plug-ins that load before Melodyne. Does this mean the project created prior to upgrading to Melodyne?

No, they are two different programs. BandLab runs in Chrome and Edge. It stores its projects on the BandLab servers. Cakewalk by BandLab is a Windows program that stores its projects on your PC.

This is only an option if the plug-in is used in the FX Rack. Region FX clips require the VST3 plug-in. While the project stops when loading an instance of Melodyne, it may be a symptom and not the cause. It will take more experimentation with safe-mode to rule out a previously loaded plug-in as the cause of the problem.

given opening an existing project in safe-mode may be instructive (once the OS is finished updating).

There are a variety of note fields in CbB. For now, if you wish to see the same notes in the Inspector, Track and Console view use a notes plug-ins. I posted links to a couple in another notes request thread

It depends on the plug-in. If it lacks an automated on/off there are several other ways to get the effect. Here are two - To add a echo on a single word or phrase, split clip(s) from the rest of the track and add the delay as a clip FX. Every clip has an FX Rack just like the track. Another way to achieve the same result is using a send to a bus with the delay on the bus. Automate the send to the bus and if necessary automate the bus volume to kill the delay.

If the project is all MIDI, all you really need is the project file itself. There is nothing to bundle (a bundle is a single file containing the project and associated audio). You could copy the folder containing the project and the empty audio folder onto the flash drive if you wanted to take the entire project. If there is other stuff in the project you could bounce the MIDI clips in the track and drag it to the desktop and render the MIDI file to audio at your friends house. Or save the project as a MIDI file.

The owner believes the software should be available at no cost. Cakewalk is a small part of BandLab.

Some plug-ins do not have on/off exposed for automation. VST3 plug-ins should have a host bypass in their automation parameters which can serve as on/off. There is extensive help for automation here. One way to automate a plug-in is click the W button above the plug-in UI and with the transport running use the mouse to manipulate the controls of the plug-in.

This may help

Cakewalk released 64bit versions of their plug-ins starting with SONAR 5. There were two Pantheon reverbs bundled with SONAR. The first was a surround version. It was 32bit DX only. The stereo version released later was 32 and 64bit DX. There are some DX plug-ins that never were ported to 64bit, for example the DSP-FX series. If you want V-Vocal run X2 Producer or older installer first, use the advanced install options and select minimal installation like this Then perform complete installs Platinum and CbB. Use the XLN installer for Addictive Drums and use the Melodyne from your Celemony account. Follow up with advanced installs of any other versions to get legacy plug-ins and content.

Definitely need separate paths for VST2 and VST3. The VST3 recommends a plug-in path and CbB will not scan VST2 plug-ins in the VST3 path. The few 32bit plug-ins I have are installed in the same path as my 64bit VST2 plug-ins, the default CbB path - C:\Program Files\Cakewalk\Vstplugins They were put there by Cakewalk installers some time ago. It was their practice when installing 64bit SONAR first. Can't recall the last time I used a 32bit plug-in. CbB still bundles BitBridge. That said, 32bit plug-ins are best avoided. Unmaintained software does not get better with age.