scook

@Noel Borthwick just mentioned the padding in m4a loops

The help in each plug-in describes how to use the Sonitus preset manager.

While the help is very detailed, it fails to mention the ini files used by the preset manager may not have the permissions setup to accept user changes.

Unless the user has permission, updates to the ini files silently fail.

The default location for the preset ini files is C:\Program Files\Cakewalk\Shared Plugins.

There is one preset ini file for each plug-in, The files have the pattern FX{plug-in name]DX.ini. For example, the Sonitus Surround plug-in preset ini file is FXSurround.ini.

One may change the ini files, one at time, by editing User permissions using the Security tab on each files Properties page (right-click each file then click on Properties at the bottom of the context menu) and allowing Modify and Write

or

Navigate to the "Shared Plugins" folder open a command window as administrator and type  the following on the command line

cacls *.ini /e /g Users:c

to change all the ini files at once.

For several releases now, announcements like the one below have a link to an installer providing rollback to the previous release 

32 minutes ago, Jack Hawk said:

On 5/15/2021 at 9:41 PM, Toddskins said:

I'm still using Win 7 and the latest update of CbB is working fine still.  But when the day comes that an update causes havoc for me, is there a way to revert back to the prior version built into CbB software?   I think that was spoken about a year ago on this site, but don't remember.

And then 2nd, when updating can no longer be done by Win 7 users, is that going to cause a problem in some manner with regard to the activation thing?  (Will we be able to maintain using CbB on the latest good Win 7 version that works for us, forever?)

Before updating, go to C:\Program Files\Cakewalk, and copy Cakewalk Core to a location of your choosing. Rename to Cakewalk Core Rev# (ie Cakewalk Core 2021.04). Then run the update. If need be, copy the renamed file back to C:\Program Files\Cakewalk, and you'll be running your old version. I do this for each update, and it's saved my @$$ more than once.

Better to rely on the rollback installers available in the release announcements.

Copying "C:\Program Files\Cakewalk\Cakewalk Core", running a CbB update then copying the old program back into "C:\Program Files\Cakewalk\Cakewalk Core" is not a good idea.

While this was fairly safe a few years ago from CbB 2019.09 onward using this method is dangerous.

In fact, CbB 2021.04 contains logic to detect this and issue a component mismatch warning message.

The warning results from having the program out of sync the the automation library cw130auto.dll in "Shared Utilities". This dll must be the same version as the program file. When they are different it may result in automation failure and program crashes.

Don't own it but here is info from their FAQ https://www.vilabsaudio.com/faq

Quote

Can I use my library on more than one computer at the same time?

Yes your license includes three activations, so you can authorize your library on three devices at once if needed, computers and/or iLok USB keys. For example, you can use the library both on your main system and laptop plus keep an activation as a backup. Activations are easy to manage using the iLok License Manager app.

There should not be much difference in the sound of any DAW. 

While there may not be many plug-ins included with Cakewalk, the program can access a nearly limitless supply of 3rd party plug-ins and samples both free and paid. Here are a couple of threads on this forum about free FX and synth plug-ins.

Projects in Cakewalk are limited only by the hardware running the program.

BandLab Assistant provides access to a lot of the BandLab loop content. This may be used in Cakewalk.

Given the ongoing improvements in integration between BandLab and Cakewalk,  a good argument may be made to learn both DAWs.

If you are using 2021.04 make sure to run Update 1

Read the info regarding Error Detection in the link

Until the official update, adding the Tungsten Key/Meter view images for insert, delete and properties should work for Lead too.

Run two copies of the theme editor, load Tungsten in one (this may be easiest by running the editor from preferences)  and the theme to modify in the other, then copy/paste the images between Tungsten and the dark theme needing the update.

This

was instrumental in finding and reporting the bug.

thanks @Colin Nicholls for the doc

@jsg may want to grab a copy of the pdf

5 hours ago, Fleer said:

I’m quite amazed that MDrummer is included in MSoundFactory. Good show, Melda!

MSoundFactory is the synth version of MXXX, Melda's all in one multi-effect.

2021.04 Update 1 (build 175) was released with new images for Key/Meter view insert, delete and properties replacing the old tempo view images.

These need to be updated in custom themes.

For dark themes based on Tungsten, I copied the new images from Tungsten.

Bump for changes to Tuncury and Tuncury Light Green required by CbB 2021.01 Update 1 (build 175)

The clip inspector is empty when no clip is selected

Pretty sure it's a bug in 2021.04.

Looks like the tempo view images used by other views were removed.

Hopefully it will be addressed before the final release.

The patterns play continuously when the button on the right side of the pattern transport in the plug-in UI is enabled.

By default, the patterns are setup up to play continuously. To disable looping click the button at bottom right of the pattern transport (the infinity symbol).

Patterns are loaded with the drum kit in programs supplied with the plug-in. By definition that is what an SD3 program is, a collection of MIDI loops and a drum kit.

Patterns may be unloaded by clicking on the MIDI button and selecting "Unload All Patterns" from the menu or by right-clicking on the pattern buttons A through H and using their context menus.

Alternately, instead of loading a program, click the Drum button below the MIDI button and load a kit.

All of this is covered in the SD3 help. To bring up the help, click on the plug-in UI to bring it into focus, then click the F1 key.

Which plug-in?

Maybe the audio driver buffer is too small.

The driver mode is set in CbB preferences.

The audio driver buffer size for most driver modes is set on a different CbB preference page using the slider under Mixing latency.

WASAPI shared is not adjustable. It is set by the OS.

I bought the Modelling Collection in 2017 to get Object Delay. I had everything else in the Collection at the time.

Have not purchased anything from AAS since.

In my case, the $69 complete your collection included Multiphonics CV-1, upgrades to Chromaphone 3, String Studio VS-3 and Ultra Analog UA-3.

By

10 minutes ago, Shawn Armstrong said:

Just did an update this morning so I'm on the latest - any ideas?

do you mean

if not update to 2021.04 build 170 or use the 2021.01 roll back installer

To save more typing see this similar thread

Make sure to uninstall ASIO4All and any other generic ASIO "drivers" while using the factory supplied ASIO driver.

Generic "drivers" have been known to conflict real ASIO drivers.

1 hour ago, Junichi Aoki said:

I am using Release 2021.04.

This is the current production release.

The current production release has a dedicated feedback thread. In this case the thread is

This is where posts about  the current release should go.

That said, 2021.04 build 144 has a known timing issue. There have been several interim releases to address this and a couple of other issues with 2021.04.

The most recent release is build 155 available here

A final build of 2021.04  should be release soon.

All I can suggest is review the videos.

The project image is a little odd.

Track 2 is unnecessary.

While one can have multiple MIDI tracks pointing to a synth and some like to have different kit pieces on separate MIDI tracks, starting out this may just be confusing.

Track 3 is an instrument track, meaning it is a combination of a MIDI and audio tracks. In this case, using SI-Drums.

And just to make sure, do NOT play or click the drum image in the plug-in UI and expect it to record on the instrument track.