scook

Try this

• Record 1 Bar of the metronome
• Select the clip, open the Loop Construction View and in the LCV
  • Click the Loop button
  • Set the Slice drop down to "No Slice"
• Roll out the clip and try different tempos

Instead of rolling out the clip, the Matrix View may be used to play the clip.

It is pretty hard to compare binary files like MIDI files by simple inspection.

Text files are much easier to read and compare.

Here is a website containing  a couple of utilities to convert MIDI files to csv text files and back to MIDI.

Here is the direct download link to the Windows binaries buried in the middle of the page.

I believe that does not indicate who's cost

Use a drum map or create a step sequencer template. A step sequencer template is an empty step sequencer pattern step up as desired.

After adding the synth, set the output of the MIDI track to the drum map to configure the step sequencer. When using an instrument track, the drum map assignment is made in the MIDI tab of the track's inspector.

Without a drum map loading a step sequencer template performs the same task but must be loaded for each instance of the sequencer.

IOW, a drum map is a per track setting, a step sequencer template is a per-sequencer setting.

Yeah, my image above used TTS-1.

Usually I just reply to "type in the number" but for some reason this time decided to look at the drop down before replying.

This is often caused by a combination of two settings.

1. Always Echo Current MIDI Track is enabled (the default). As a result, inputs set to None are automatically switched to "All Tracks > Omni" when the track is given focus. Instead of not listen for any MIDI data, the tracks are receiving all MIDI data coming from anywhere. Turning this option off in preferences and setting inputs to specific MIDI sources (such as a controller) are the solution. This has been the subject of a recent thread

2. One or more plug-ins have "Enable MIDI Ouput" turned on. Some plug-ins have the ability to generate or echo MIDI data out of the plug-in. When a plug-in has this feature, it is enabled by default. Turn this off if the feature is not needed. This may be done one of two ways

• Some methods of adding plug-ins show the Insert Soft Synth Options Dialog. "Enable MIDI Output" is near the bottom of the dialog.
• To change the setting of a plug-in already in a project use the VST2/3 drop down above the plug-in UI as shown in this image

As a result of these two settings, tracks may be listening for MIDI data coming from anywhere and one or more plug-ins are sending data (along with any data coming from the controller).

It is pretty hard to have more then one copy of VstScan.exe install.

So this means both X3 and CbB are most likely using the same scanner.

Make sure to run the scanner from preferences NOT the plug-in manager.

Check Windows Task Manager to see if VstScan.exe is running. If it is kill it.

Then run a VST Reset from preferences with "Scan in Sandbox" and "Generate Scan Log" enabled.

The second option creates a log in %appdata%\Cakewalk\VstScan.log

If the scan fails to run to completion the log may show where the process stalls.

Not a bug

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=SYSX.01.html#1177298

When a documented feature is missing it is likely because the current Workspace does not have it. Either change to one that has the feature, create your own or set the Workspace menu to None.

15 minutes ago, StudioNSFW said:

How about a CbB supported, signed driver for Win10?

Can't be done without Roland.

Even then, it would be unusual for a company to spend resources to develop free software and support another companies discontinued product.

As a company adds products to their subscription, it seems reasonable the price may go up.

AFAIK, @jon sasor [cakewalk] uses a VS-700 system as his principle interface on a Win10 machine.

Double check the routing

If possible, use controller specific input settings instead of "All Tracks"

Check the VST2/3 drop down above the plug-in UI and turn off "Enable MIDI Output." Some plug-ins generate or pass though MIDI data.  This is enabled by default.

VST3 plug-ins should always be installed in the paths recommended by the VST spec

• C:\Program Files\Common Files\VST3
• C:\Program Files (x86)\Common Files\VST3

VST2 plug-ins cannot go in those folders.

Aside from that it does not matter where VST2 plug-ins are located as long as they are in the scan path.

There was a problem with the first CbB VST scanner enforcing the VST2 exclusion but the current scanner does not have a problem scanning VST2 plug-ins in folders starting with VST3 except for the two paths mentioned above.

There is no standard location for VST2 plug-ins. There are a couple of conventions used to set VST2 install paths. A registry entry is used by a few installers HKEY_LOCAL_MACHINE\SOFTWARE\VST but most either write their own entry to use as a default for updates or code it into the installer.

If a plug-in comes with an installer, the safest way to move it is to uninstall and re-install to the new location.

That said, most VST2 plug-ins can be moved using Windows but some may fail due to config file or registry entries made based on the install path.

Moving folders using directory junctions may be used consolidate the files into one physical location without having to re-install or worry about the potential impact to config files or the registry.

By default Cakewalk Command Center stored all of the files it downloaded in C:\ProgramData\Cakewalk\Command Center\Downloads

The path is set in the CCC settings.

All the files in the Downloads folder are installers used by CCC. They are the same as the installers in your old Cakewalk account. None of the files are used directly by the DAW.

The best thing to do is backup the files then clear the folder.

Restore the installers as need (for example when installing on a new machine). It will save the time needed to download the installers again.

Run a scan from preferences with "Generate Scan Log" enabled.

This will create a list of the dlls already scanned at the top of the VstScan.log found in %appdata%\Cakewalk\Logs

I did not realize you were trying to assign more than one track to SI-Strings (should have looked at the image more closely) or trying to change synths assignments after CbB opened a file using TTS-1.

Track setup happens when opening a MIDI file

Adding synths does not affect the track channel setting.

SI-String does not care about MIDI channel assignments. It is really designed to work with one instrument/MIDI track but you can send  it data from more than one track.

After opening a MIDI file, I have never swapped out TTS-1 for a single instance of another synth. None of the synths bundled with CbB are up to that task. If this is the goal look for a multitimbral synth like Kontakt, Expand!2 or TX16Wx.

Usually what I would do is add a synth like SI-Strings along with an audio track and route a MIDI track to it. Then add another synth with an audio track and route a MIDI track to that synth and repeat until all the MIDI tracks are reassigned.

A DAW simply captures the data at the track input. The level must be set using the audio interface.

The gain knob and volume slider affect clips not the input.

If one synth plays and another does not the routing is OK.

If a synths plays some but not all of the notes it is either a note range or MIDI buffer problem. The key+ slider can help with range issues. "Q" in the image below

SI-Strings also has a transpose setting just above the transport buttons.

MIDI playback buffer used to be an issue. Not sure if it is anymore but there is no harm in making larger.

Which of the two methods did you try from my previous post to fix the data?

If any of the notes are in range, SI-Strings has a fairly large range, and no notes play where TTS-1 does the problem has all the indications of a data issue.

Assuming the notes are in the synth's playable range. it is very likely data related.

There is a problem with some 3rd party MIDI files and Cakewalk sfz engine synths like the Studio Instrument series.

Once the synth encounters unexpected data, the sfz engine shuts down and will not make any sound until the project is restarted.

There are two ways to deal with this:

1. Clean up the data. Open the Event List View and remove the data before the first note (CCs are OK too). Usually this is enough but there could be more instructions later in the data so scan the entire track.
2. Tell the synth to ignore the data. Open the plug-in UI and enable "Do not intercept NRNPs."

Where's the lava lamp?

Old or new project nothing happens to the project with the arranger until you start working the project with the arranger tools

IOW opening old or new projects in 2020.04 is no different than opening in a prior release.

Select the tracks

Open the audio export dialog either from the Export Module Advanced... option or from File > Export > Audio

Set the Source Category to Tracks, enter a file name and click Export.

Boz Digital has a couple of packages on sale now that have PC modules

• Plus 10db bundle https://www.bozdigitallabs.com/product/10db-bundle/ $49
• Hoser XT https://www.bozdigitallabs.com/product/the-hoser-xt/ $39

10db includes compressor and EQ PC modules

Hoser XT includes an EQ PC Module

Softube TSAR-1R reverb is on sale $45 - the PC Module is included (iLok  protected no dongle required)

CC102 is listed in the MIDI Event drop down.

There is no text next to it because  CC102 is not assigned in the MIDI standard.

It is also possible to type 102 directly in the Value field.