scook

Thanks for the reminder. I don't use the CAL scripts myself and forgot why I did not bind them in CbB. This is the best solution. Binding these to ALT+Left/Right Arrows before I forget. Will be part of the new build next week.

Try adding the TTS-1 synth to the project

To use ASIO driver mode (the last image) requires a device with an ASIO driver. If you are running Win10 and are using the internal sound chip in the PC try WASAPI Shared or WASAPI Exclusive driver modes in the Playback and recording screen. Once the driver mode is set, the devices using that mode will appear in Devices preferences. Once the device is selected, the Driver Settings preferences will be populated and the warning in the first image should go away.

New version of Sitala is release. This one supports the VST2 opcode for instrument names so, the pad names show up in the PRV and step sequencer note names area. Something few synths support.

There is no reason to have 32bit plug-ins in the CbB scan path if there are 64bit versions installed. Maybe moving the 32bit versions out of the CbB scan path will help. It can't hurt.

There may be entries in the Windows Event log. Sometimes running screen capture software such as ScreenToGif or LICEcap will pickup fast flashing messages. Turn the capture rate up high to take more images while the capture software is running. ScreenToGif can step the the images. I will be building out a new machine soon, installing X2 through current. This should take an hour or so. It's all the third party stuff that takes time. Should you ever need to perform a clean install it is possible to avoid messing with third party stuff. Make sure not to delete the VST folders containing 3rd party plug-ins. If they are in the default VSTplugins folder used by Cakewalk move the whole folder to a new location before deleting the Cakewalk folder and put it back before running the Cakewalk installers. There is no reason to delete all the plug-ins in the VSTplugins folder.

Software "sampler" plug-ins that actually sample live data are pretty rare. As I mentioned above, synths that process audio may be placed in an audio FX rack. Some developers make FX versions of their synths, some just code the synth to accept audio input. Most of these work fine when placed in an audio FX rack. I have one synth that can sample and play back live data but it is not really designed as a sampler, the samples are short and intended to be used as oscillators . The modules are limited in what they can do with the sampled audio.

The gain knobs in CbB adjust the gain of recorded clips. See the signal flow diagram CbB has no control over audio levels coming into the DAW. This level must be set before the DAW.

Use the search function or click on your user name and click the "See Their Activity" button in the upper right.

I have no problem recording audio into the sampler modules in Cherry Audio Voltage Modular, various loopers and the like in CbB. Unfortunately, the sampler modules are very basic and loopers just are not the same. TX16Wx is a standout. According to the developer recording was tested with Reaper only and he is not interested in addressing how audio recording is implemented.

If CbB is hanging on exit, it sill could be plug-in related. While 32bit plug-ins are often the cause, some 64bit plug-in fail as well.

May be Regardless, deleting the StartPageCache folder is harmless and will fix corruption issues with the Start Screen data.

type %appdata%\Cakewalk\Cakewalk Core\ in the Window Explorer path entry field

What I am waiting for is a sampler that can sample data live. Drop the sampler in an audio FX rack and control it from a MIDI track. To me that is sampling. Clip players I have a plenty.

That is odd. I would expect the files to be missing from the menu too. That list comes directly from the registry. This means CbB is shutting down properly. The start menu data may be corrupted. Delete "%appdata%\Cakewalk\Cakewalk Core\StartPageCache" and the next time CbB starts up the start page will rebuild the folder and its content. After this, it should be in sync with the File menu.

Clicking the track number selects the track Clicking the track name gives the track focus To see the difference: Click on a track number - this selects the contents of the track Click on the track name of a similar track then CTRL+V pastes the selected data into this track at Now time.

Just tried the update. Worked OK. Looks like they reworked the loop browser. Fortunately, BA is no longer needed once CbB is installed.

I tried several plug-ins too. I have the fade settings set to the default 0. Surge VST3 v1.7.1 built 2020-08-02 stops when the transport stops The following all continuing playing when the transport stops Rapture VST2 v1.22 CA2600 VST3 v1..0.20 MTron Pro vVst2 v3.0.2.0 Loom II VST2 v2.0.0.80 Synthmaster VST2 v2.9.9 Changing the fade setting in Preferences > Audio > Playback and Recording did not change the behavior. I tried 1 and 5ms.

I believe you may be thinking of Always Stream Audio Through FX http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x22B19

One is built into CbB

Here are a couple of CAL scripts. They are set to jump at 30 tick increments, adjust as needed. Copy and paste each one into a file in the CAL folder and create shortcuts for them. ;; Name: Now Forward.CAL (do (+= Now 30) ) and ;; Name: Now Backward.CAL (do (int offset 30) (if (< Now offset) (= Now 0) (-= Now offset) ) )

When splitting clips often it is necessary to slightly fade the ends where the split occurs. This is because the clip was cut at a point where the audio wave is above or below zero. Fading eliminates the click caused by splitting at other than the zero crossing point in the wave. Here are a few places in the documentation where this is discussed: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingAudio.08.html https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingAudio.05.html And an old knowledge base article on loops https://www.cakewalk.com/Support/Knowledge-Base/2007013136/Get-Looped

I am not instructing you to do anything and my first response to any problem is rarely to re-install. The fact that a re-install has already been attempted lead me to the ask about the process used. Uninstalling CbB or any previous SONAR/Cakewalk DAW affects all of the related DAWs. Only with the third post was there any mention of software other than CbB. Maybe providing more information about the system would be a good idea. If you want specific information about error messages, images of those messages may help. Guessing without an exact recitation of the message is often not useful. WRT "hudnowtime" I could guess (Heads Up Display Now Time could be playback head and now time line images that track the current play position) but would rather defer to support@cakewalk.com or the Cakewalk staff that frequent this forum for a definitive answer.

This begs the question was the clean install process used?