scook

33 minutes ago, Mark Liu said:

MIDI > Devices > Outputs

Defines hardware outputs only. This includes the MS GS Wavetable Synth because it resides outside the DAW in the PC hardware.

When the DAW does not have any MIDI devices defined in preferences, opening MIDI files will be automatically setup to play with TTS-1. This and the better performance of TTS-1 over the MS GS Wavetable Synth is why I recommend deselecting it from output devices.

TTS-1 and SI Electric Piano are software plug-ins that run inside the DAW. They will never show up as MIDI hardware devices. You have already found one of several methods to add these plug-ins to a project - Insert > Soft Synth another is the add track menu. (see the "To create Instrument track" section about midway down the page).

Plug-ins may be added as needed to a project and once the project is saved, the plug-ins will be there when the project is re-opened.

It is possible to create a project template containing the synths already setup if you wish. For now, it may be a good idea to add them as needed to get familiar with the process.

To have snap always land exactly on the measure set intensity to extreme.

1 minute ago, David Baay said:

I think he meant to label that last link 'PDC button'

fixed

1 hour ago, Mark Liu said:

just playing around with the basic piano

Which one: TTS-1, SI Electric Piano or the MS GS Wavetable Synth? If the latter, try one of the plug-ins? The MS GS Wavetable Synth is not a low latency device. In fact, it may be a good idea to disable it in preferences.

1 hour ago, Mark Liu said:

I've tried what I think is all possible combinations of settings, using WASAPI or ASIO4ALL, at different settings for all the common tweaks, stuff like 44.1 or 48k, 16 or 24bit, things I don't actually understand but seem to make a difference with other people. No noticeable change, for the better or worse... What really confuses me is that others have proven that they can get essentially zero latency on far older computers with practically the same set up.

Of all the "common tweaks" the only one that makes a difference to latency is the driver buffer setting. Sample rate can affect latency but there is practically no difference between 44 and 48 (doubling sample rate halves latency at the same buffer setting). Bit depth does not matter. Switching driver modes may make a difference because different drivers may work better with smaller buffers.

Having a purpose build audio interface with a manufacturer supplied ASIO driver performs better than the sound chip in the PC. The driver makes the difference. That said, PC chip may be enough for simple projects.

The other source of latency is plug-in delay compensation. If bypassing all plug-ins makes a difference, then one or more plug-ins in the project are contributing to the latency problem. To bypass all plug-ins toggle the FX button in the Mix module. While reading about the FX button review the PDC button function as well.

In the PRV Notes menu enable "Show Durations in Drum Grid"

There should be no problem. Updating CbB from any version older than the most recent prior production release causes BA to download and run the full CbB installer.

The initial error message suggests changing the Driver Mode. This is located in preferences

When using the internal sound chip try one of the WASAPI modes if running Win10, WDM for other OSes and last choice is MME

2 hours ago, Craig Anderton said:

@Jim - thanks for the mention!

@Dave - if questions remain after reading the articles, I'll be monitoring this thread so I can answer...assuming scook doesn't get to it first

It's all yours Craig

Why should I have all the fun

CbB always records the signal at a track's input. Any time one wants to record a signal affected by plug-ins, the track containing the plug-ins needs to be routed to an aux track or another track using a patch point. The wet signal may be record in this track.

Try this,,,

1. Add Sonitus Gate in the FX rack on the mic track

2. Click the Audio button on the Sonitus UI changing it to Duck

3. Enable input echo on the mic track

4. Route the mic track output to a new aux track

5. Record enable the aux track

6. Create a send on the music track to the Sonitus:fx Gate (Side Input)

7. Enable input echo on the music track

Now any time signal hits the music track, the aux track will be muted.

Anytime this method of recording a wet signal is used, it is a good idea to record the dry track too, just in case.

May need to experiment with the hold and release times to make sure the gate does not open with quite parts of the music.

The few 32bit plug-ins I have are all from SONAR Product/Platinum.

They are all installed in the default plug-in path C:\Program Files\Cakewalk\Vstplugins.

They scan OK. Yesterday, I have reason to load Cakewalk Sound Center.

I just installed and tested DSK xXx, a 32bit synth into C:\Program Files\Cakewalk\Vstplugins\DSK xXx

Could try installing one of the plug-ins on a different drive.

42 minutes ago, Nigel Mackay said:

All of them. Not a single one loads. Mostly they are DSK. They are in a custom folder.

It is hard to help without better info.

Is the "custom folder" compressed?

Deselect "Copy all audio with project"  in the "Save As" dialog. There is no requirement for "Save As" to always copy clips when creating a new project and the new project may even reside in the same folder as the original.

In the track view Apply Trimming crops clips to the size used in the project.

May want to experiment with both of these on a copy of the project to see how the work.

Either export a mix or the individual tracks starting at 0.

If there is an autosave copy or versions either copy them somewhere else (so they don't get overwritten) or rename the bad project file. Then try opening the bad project in safe mode by holding down the SHIFT key while opening it.

Any particular 32bit plug-ins being reported as "NOT a VST plug-in"

Where are these plug-ins installed?

What version of C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe is installed?

how do these compare...?

Plug-in automation is available on a per-plug-in instance basis. A single instance of a plug-in with multiple outputs has one set of automation lanes available to it. They may be placed on any track.

Until MIDI automation is added to instrument tracks, it is necessary to (temporarily) split instrument tracks to access MIDI automation on the MIDI track created.

May want to follow the link the image to the help center and open a ticket with them.

Here is the thread to report problems with 2020.04

Put the project on One Drive, Google Drive, Drop Box or a host of your choice and post in the thread with a steps to reproduce and a link to the project.

There are several ways to enter MIDI data mentioned in the second thread

28 minutes ago, zaquria said:

It is older Projects which use different (Sometimes all over the place) Screensets settings. I have to load up a Template to load Screenset settings, and doing this for 100's of previous Projects is time consuming and not practical.

Sounds like a good autohotkey project

Here is how I add Wheel to the Controller Pane in the PRV

For now Instrument tracks do not provide access to MIDI automation so there is no point in using instrument tracks if you know you want to draw MIDI automation in the track view.

When Cakewalk sfz synths go silent is it often due to try to play unsupported data. This may be cleaned up in the Event List view or by enabling "Do not intercept NRPNs" in Plug-in Properties from the plug-in header. When running 32bit plug-ins in CbB using BitBridge the track header is in a separate window. To gain access to the window hold the ALT key when adding the synth to a project or opening its UI. The header usually opens behind the plug-in.

16 minutes ago, zaquria said:

No, I want a Global Screenset which I can use across all Projects regardless of the Work Space or Project. Every-time I load up a Project, I have to either change the Screenset Manually or load up a Project with my preferred Screenset to Import it into the current Project.

This is a feature request (and given Noel's reply will likely not materialize). For now, screensets are a per-project setting. To have your screenset available in new projects create a template from an existing project that already has the screensets in it. Going forward, use the new template(s) for new projects and the new projects will inherit the screenset from the template(s).

16 minutes ago, Dave G said:

This is also indicated by the numeric meter there which seems to just go from 0 upwards. (I just searched YouTube for literally an hour not finding an instruction for this.)

Notice in the animation, MIDI automation for wheel events shows a 0 in the middle for the automation lane. MIDI automation works just like any other automation in the Track view. MIDI automation is only available on MIDI tracks so, if using an instrument track, it must (temporarily) be split into its constituent audio and MIDI tracks to gain access to the MIDI envelop dialog.

16 minutes ago, Dave G said:

Also, what you suggested about inserting wheel events via "CC data in the Piano Roll View". Piano Roll View, there's a Controller Pane beneath that, where I normally draw wheel events. How would a CC event create that, and where?

It does not create CC for Wheel. It is the area where the Wheel data along with CC data are displayed in the PRV. I could have written that a little better.