scook

Can make a video using one of the PC-based screen to animated gif tools too.

It does not appear to be exclusively a CbB problem.

Or use the VST2. Simply using the VST2 or rolling back to the previous VST3 does not help with fixing the problem. Reporting it to support may. Relying on VST2 is not a good long-term strategy.

After running a few updates yesterday, KORG Software Pass says I am current. Just ran through all the VST3 plug-ins and the only ones ignoring saved settings in CbB are Wavestation and M1. If anyone experiences the same problem in another DAW, please report it to KORG support.

Please report it to KORG

fixed

Yes, it looks like KORG broke their VST3 plug-ins. I was using Wavestation VST3 v2.3.0 when posting yesterday. After posting, I ran all the updates for KORG plug-ins. The latest VST3 versions of Wavestation (2.3.1) and M1 (2.3.2) are ignoring the settings stored in the DAW. Everything works as expected after reverting to Wavestation (2.3.0) and M1 (2.3.1). Running CbB 2022.06 build 28 on Win10 Pro 21H2. Reported to https://www.korg.com/us/support/

For some time now, rollback installers are provided in the product announcements to roll back to the previous version. These rollback installers may be sequentially applied to get back to older releases. The rollback installer for 2022.02 is in the 2022.06 product announcement.

Try setting the preset in the plug-in, make sure the channel, bank and preset drop downs in the MIDI/instrument track are set to None and forget about adding this info to the MIDI data. These drop downs may be found in the MIDI/instrument (MIDI tab) track inspector "C" below or the track header when the Track Control Manager drop down is set to All

Please, do not cross-post thanks

Incomplete files

You are welcome. If you ever need access to the audio and MIDI track hiding in an instrument track, bring up the track context menu for the instrument track and instead of "Make Instrument Track" there will be an option to "Split Instrument Track". While rarely necessary as most audio and MIDI controls/functions are available on instrument tracks there are a few things that require audio+MIDI track pair such as synth audio recording.

By default, ALT+F4 has no global binding in CbB. If you have unsaved changes before export, consider saving before starting an export. To interrupt an export, click the x next to the progress bar in the transport It may not respond immediately but ultimately should show the dialog in the image above just before stopping the export.

The 200th issue of CM came out in 2014. At that time, it was possible to create accounts and register products on the Cakewalk website. In 2017, Cakewalk went out of business and the customer account database was closed to new accounts. Without a Cakewalk account, there is no way to register Cakewalk products.

Assign the MIDI track output to the synth. The MIDI output drop down is always available in the track inspector and depending on the Workspace and Track Control Manager drop down may be available in the track header. In the images above, it is impossible to tell if the track inspector has been collapsed or removed from the UI and what the Workspace setting is (it is off image in the upper right of the UI) but the Track Control Manager is set to Custom. By default the Custom setting does show the track output drop down when a track header is expanded. Assuming the default Custom setting for the Track Control Manager drop down, here is a video showing how to route a MIDI track to a synth and the optional step of creating an instrument track from the audio+MIDI track pair.

In the project that does not expand selected track take lanes, is auto track zoom enabled? If so, disable it.

You are welcome. This is a common problem with 3rd party MIDI clips and affects all the Cakewalk sfz engine synths. I made the SI-Bass image posted above around 6 years ago. Of course, the issue is a lot older than that. The data that messes with the synths is often at the beginning of the track (but can be anywhere in the track) and may be viewed/removed in the Event List view. That said, the more expedient solution, as noted above, is setting up the synth to ignore the data.

Whether a plug-in is multi-timbral or not is up to the plug-in manufacturer not the DAW. Refer the plug-in documentation for its feature set.

No, track templates work at the track level. FX Chains will not work on partial clips either as they reside in FX bins and operate at the track or clip level. You will have to split the clips to process sections individually (some of this could be scripted), use plug-in automation or use Process Effect from the clip context menu after making a selection (this could benefit from scripting after making the selection).

There is not enough data in a MIDI file to completely build a project using an arbitrary collection of plug-ins. Track labels are part of the MIDI spec, plug-in references are not. There is no requirement to move or delete anything when adding plug-in and audio track information to a CbB project created from a MIDI file. An Instrument track is a presentation layer above an audio+MIDI track pair. After opening the file, add the synths using any method other than the Add Track menu such as Insert > Soft Synth from the main menu or dragging a synth into the project from the plug-in browser. These methods open the Insert Soft Synth Options dialog. Select the "First Synth Audio Output" from the Insert Soft Synth Options dialog and point the appropriate MIDI track's output to the synth. That is all that is necessary to complete the track routing for a synth. Creating an instrument track from the audio+MIDI track pair is optional. To convert an audio+MIDI track pair to an instrument track, select the tracks then choose "Make Instrument Track" from one of the track header context menus.

Usually when a Cakewalk sfz engine synth (DimPro, Rapture, Studio Instruments...) goes silent, the cause is unexpected MIDI data in the track. The easiest fix is enable "Do not intercept NRPNs" in plug-in properties

For GM MIDI files, if there are no MIDI output devices selected in preferences, while opening the file, CbB automatically adds TTS-1 to the project with the appropriate instrument assignments.

Been doing the same when I have more than a few plug-ins from a manufacturer. Reorganizing plug-in folders makes the more simplistic plug-in menus used by some hosts much easier to work with.

It does not violate the recommended VST3 plug-in paths. The spec does not require plug-ins be in the root of "C:\Program Files\Common Files\VST3" or the recently added "%LOCALAPPDATA%\Programs\Common\VST3".