Noel Borthwick

3 hours ago, scook said:

A sidechain input sums just like a bus or aux track input.

Unless the bus or aux track output is going to be used for something other than the sidechain maybe forget about the bus/aux track and point the sends directly to the sidechain input.

Indeed a side chain is internally a bus and will sum all sends to that side chain.

Soloed buses are not coupled with tracks so if your solo a bus you will also need to manually solo other other tracks that aren't dependent.

2 hours ago, David Baay said:

I still get a stereo signal when selecting only L or R input from a Patch Point:

"Mono inputs from Patch Points and Aux Tracks

Prior to this release, if a track or bus had an input assigned to a mono input (L/R) from an AUX track or Patch Point, the input would always and include both left and right channels from the patch point when playing back. Patch point inputs now correctly include just the channel specified as a track input."

 

@David Baay please check your PM’s. we sent you some info and questions.

2022.09 has been released. Thanks for your help testing it!

Thanks for the heads up, we’ll sign them.

46 minutes ago, SCHENCKEL Frédéric said:

Hello,

First thanks a lot for your job!!

Just one remark, would it be possible to sign all the included Dlls (like the .exe), so we get a smooth installation without windows (or AV) complaining about any safety problem ?

Thanks  a lot.

Regards

Which dlls in particular are you having warnings with?

Thanks everyone for checking out the latest EA. We plan to release this officially tomorrow. We just updated the build to 28.09.0.027 which includes a couple of important fixes. If you see this, we'd appreciate it if you tried it out before we release tomorrow.

 

Quote

Updated to 28.09.0.027

This build contains the following additional improvements:

Integrated zplane élastique Pro audio stretching and pitch shifting has been updated to version 3.4.0 with bug fixes and performance enhancements

Some ProChannel modules cause the UI to get unresponsive on stopping transport when using high track counts

Don't send 'all notes off' on stop - just silence any active managed notes

Tracks sourced from aux track L/R/S always behave as S during playback

Note: Existing projects that utilize aux track or patch point mono inputs will sound different because previously these would render as stereo only.

On 9/26/2022 at 6:41 PM, Michael Richard said:

Thanks Bakers....

I get no one should complain about the pace of continued advancements of a free World Class piece of software such as Cakewalk.

So I will also only leave a kind observation stating that the pace of innovations appears to have slowed down of late. For example, this release took 3 months to bake and only offers 10 bug fixes. This seems to be a first.

Hoping that there is no negative subtext to be read behind this; such as Bandlab reducing ressources on the Bakers' Team...

No not at all. More like our (small) team has been working on some other equally important things.  CbB is a pretty mature application and it's not always necessary to add new features but rather refine what we have.

If the internet is gone permanently, I think you will have far worse problems than not being able to use your DAW
You can authorize cakewalk via the offline auth mechanism but yes that requires at least a remote internet connection somewhere.
Pretty much most software today is tied to some sort of activation mechanism, its just how the industry has evolved.

1 hour ago, Craig Anderton said:

Specific DAWs (including Cakewalk) have specialized features that other DAWs don't have. Unless you need a feature that can be found only in one DAW, Cakewalk will do pretty much anything you want it to do, and do it well.

Of course, the biggest advantage is the money you would normally spend on a DAW, you can spend on plug-ins to supplement what comes with the program. 

 

 

For me any product its actually more than the sum of its features, but its workflow. If a product has a million features but the workflow doesn't suit me, I don't use it.
Time is too short to waste on things that aren't intuitive to you.

On 10/2/2022 at 3:40 AM, SVSX said:

Not that i'm questioning your experience, but on my PC  Cakewalk is running pretty stable/smooth. Can't imagine how its running even better. But my brother is using Reaper for his Apple PC and its a good software.

 

Thanks for using Cakewalk software. It has grown by leaps and bounds over the last 4 years and is more stable and performant than it has ever been.
In general, if any DAW meets your workflow and needs there is no need to keep endlessly looking elsewhere because you will waste more time learning new tools. And believe me when I say this - every product has flaws and bugs despite what you might hear from anyone else  
We're also working on something exciting that will be announced relatively soon so at minimum hold out until then 😛

Thanks to some tests from @David Baay I have isolated the issue that causes the UI to be unresponsive after stopping when there are hundreds of tracks with certain prochannel modules. It is fixed it for the upcoming release.
The issue is easily reproducible if you have 200 tracks containing the console emulator. The reason for the delay on stop is because the console emulator ends up blocking the user interface under certain conditions. 
I have worked around the plugin issue in our code.

Edit: This fix is included in the 2022.09 official release.

On 9/15/2022 at 4:24 AM, Antre said:

When play pressed there is a delay before audio starts playing and this delay is longer if the project is bigger.

For me it was always like this, on several computers during decades using Cakewalk, and it was always extremely annoying.

Along Cakewalk I use few others DAWs and I tried probably every existing DAW - NONE OF THEM IS BEHAVING LIKE THIS.

?

@Antre I realize that it's frustrating when you have a problem that apparently doesn't occur elsewhere, but the truth of the matter with troubleshooting is ALL DAW's are vastly different and that a symptom that appears in one and not another doesn't necessarily shed much light on why this happens. 
As others have indicated there are a ton of moving parts that can lead to something like this.

The proper way to troubleshoot is through a process of elimination:

- Start by deleting tracks - you may be surprised to find that the problem occurs with one of the tracks. If so go further to look at the content.
- Bypass or remove all plugins from the project. Does the transport still take time to start?
- When you press play there are many things that happen as a part of the preroll process. One is opening and prereading to cache audio data for all the tracks. If you have many tracks (many hundreds) and there is a disk fragmentation or slow read issue this process can take a couple of seconds. Try playing with the settings in  Audio | Sync and Caching. Setting a very large playback buffer can cause preroll to take longer.

- Check if you have one or more plugins with huge delay buffers. If there is a large delay buffer, again preroll before playback starts will take longer because the engine cannot start playback until all plugins process initial audio.

- Check if always open all device is enabled. If you have many I/Os enabled in preferences and the audio driver is slow it can take long to open the devices.
 

- Check if Allow arm changes during playback and record is enabled. If its on depending on the number of inputs and the driver this can slow the preroll process down 

The above settings are the most typical reasons for lag starting playback.

On 8/30/2022 at 7:28 PM, Mark Morgon-Shaw said:

Been away from the forum a few days and my thread has gone crazy  😃

So I think after reading all the back and forth that my preferred  way to deal with it would be :-

1. Update the tooltip as there seems to be a consensus this would be helpful so it's clearer whether the user is engaging or bypassing the FX

2. Leave the way it functions but try to label it more clearly as the " FX Bypass " button rather than it just saying " FX "

I think this would lead to less confusion without changing the way it operates. I suppose I could always put some masking tape on mine and write on it with a Sharpie.  

Next update will include masking tape 😉

Thanks for your support, guys. It is great that we are able to offer Cakewalk free to our users.
As long as we are able to do so, enjoy it....

We can consider reducing the minimum loop size below 8th notes. A single tick resolution is too low. 
A DAW needs to do a lot more setup for looping than an audio editor or sampler so looping tiny region on the timeline is not as simple as it might look. Please move threads like this out of the release thread because its more suited to the feature request section.

Um you can do as much surgical editing as you need. Looping is not intended to be an editing tool.
Use normal snap and zoom with the sample ruler to do surgical edits. Please move this to a different thread since its not related to this release.

There is nothing to fix because it isnt a bug. It is intentional that the loop length cannot be made smaller because there are problems rendering tiny loops. In any case there is no musical value in setting loops that small.

22 hours ago, DaveMichel said:

That did it. Thanks a bunch @scook!

I also got the onboarding dialog, which I didn't want, so I ended the Cakewalk task, set OnboardingShown to 2 and fired up Cakewalk successfully with my old working settings.

Greatly appreciate the help.

@Noel Borthwick - I think this constitutes a bug. We shouldn't be able to paint ourselves in a corner by a simple preferences change to WDM/KS driver choice.

Version: 2022.06 (Build 034, 64 bit)

Hi Dave,

With all due respect, I don't think it's a Cakewalk bug if your audio driver hangs the app  
However, your point is taken - within limits there are things that can be done to mitigate bad audio driver behavior. I'm not sure if it would help in your case however. 
In WDM mode we're at the mercy of how Windows drivers interact with the app if the driver deadlocks there isn't much the app can do. However perhaps we can remember an improper shutdown and reset the driver mode on next launch. Also did you already try launching in safe mode?

@Skoo How are you installing the instruments?

15 hours ago, Sven said:

I can't seem to find the thread anymore but someone said the solution was a Win 7 registry fix and this was a known Win 7 issue.  Can someone point me to that thread if that's the problem?

See this thread for the connection error issue.

As Scook said the web installer does similar checks to the in-app install process. All CbB versions from more than 6 months ago update seamlessly from within the app itself without needing to run the web installer manually.

Yes at some point we'll update to mix recall. Lots of stuff on our plate currently...

Cakewalk was the first DAW to add this in 2016. Cubase added it somewhat later but its not quite as powerful as our implementation.

Please stop using BandLab Assistant. For several months it's no longer been the mechanism to update Cakewalk.
Use this link to get the standalone installer.

Once you have a recent version there is no need for an installer since updates can be done inside the app itself by using Help | check for updates.

there are always some bug fixes. we updated the compiler so needed to push the latest redist as well. Shouldn't be any compat issues.
I also did it because I originally thought it would address the error 20 issue. That turned out to be something completely environmental and not related to our code.
But I've worked around it with the help of a couple of forum users.