Noel Borthwick

What audio device are you running currently? Post a screenshot of the drivers page if you don't know. If its onboard audio your best bet is to use WASAPI shared or WASAPI exclusive mode which are designed specifically to work well with onboard audio devices in Cakewalk.

What ASIO driver are you using. Do NOT use the RealTek asio driver as it is buggy.

interesting developments from Asus https://www.pcgamer.com/asus-is-issuing-bios-updates-to-support-windows-11-on-unsupported-intel-cpus/

Yes I know what the Fader is. We have the original Console One unit (and Cakewalk does work with it) but the fader is a more recent update.

Regarding the "secrets" of the console emulator and what it does internally, I have no clue lol. We purchased the technology many years ago for the prochannel. Only the original dev would know the technical details of circuit emulation are typically a closely guarded secret. I personally think there is some degree of snake oil in all this analog emulation stuff but I'm no expert on analog consoles

In theory this should work with Cakewalk. We support the original Console One but do not have the Fader version which is newer. If there is an issue we can look into it but the user should contact Softube support first.

Yes its primitive to discriminate on a product based on what users pay for it.

Have you contacted Softube support about this? We don't have a Console One fader to test here.

Yes a matrix cell has a full copy of the underlying data stream. While the base data type is similar, clips in tracks are more complex than data in matrix cel’s, hence its not trivial to share data directly across tracks. Editing operations are different etc.

you are running an old version and many such issues have been fixed since then. Update to the latest using this installer Also Win 7 is not supported as stated in the install message. It is not tested anymore by us and you use it at your own risk,

@Gavin Davies thanks for your interest. There is no way to contribute to actual development other than being a developer because Cakewalk isn't open source. Matrix cells store a copy of data and there is no linkage with tracks so it cannot be edited in realtime unlike the step sequencer which has native cel data. The cel data can be copied out of a cel into the TV via drag and drop and edited there and copied back but there is no direct way to do that in real time today. We have update to the matrix in our backlog but it won't be in the immediate future. Recording and direct editing were considered in the original spec for the Matrix but did not make it in.

@JamPro Which version of Cakewalk are you running and what version of Windows?

In 30 years of Cakewalk I have never seen this issue Glad you figured it out. I can assure you that it has nothing to do with any recent update. If you find out that markers are being created without user intervention please let us know.

Which version of Cakewalk are you running. We have not seen any issues with the VST3 version of Kontakt. In fact we worked with NI on ensuring compatibility for the 2021.06 release.

A new early access release is available with several new features. Please check it out and comment in the thread. This is a massive update so any testing and early feedback would be appreciated.

Can you share a copy of the project that has the issue? Include the audio data.

Some perspective from my viewpoint. Best by definition is going to be subjective, because even though Cakewalk is an incredibly deep and powerful DAW with its 30+ year lineage, there are other simpler DAW’s that may be more appropriate to some workflows because of their genre bias or other reasons. Live is a great example - if your primary interest is beatmaking you would be hard pressed to find something better for that workflow. If you leave behind very personal preferences or workflows, to the original question I would say that IMO Cakewalk has by far the deepest feature set of any free DAW out there. Its mature and has decades of experience baked into it which few other DAW’s including many paid ones have. Of course we have our share of quirks and bugs (that arguably others have too) but it has been our highest priority to solve the more serious issues since the last 3 years. To the last point I want to say that since day one our approach has never been “this is a free DAW now, so lets do the minimum to support it”. To the contrary, we have used this generous opportunity to obsessively make this as good as we can for our users. The effort that has gone in the last 3 years has been more than ever in the history of Cakewalk, to focus on improving stability as well as building truly usable and useful features. None of us have a free lunch mindset here - we do this because we care for the product and users and want to excel. As far as users cutting us slack because its free, while some more casual users might, we have thousands of professionals who make a living with this software, where the fact that its free makes no difference - the need to efficiently get their work done. We often work one on one with many users to ensure that our tools are robust and meet their needs as far as possible. The next release has a huge new feature directly based on feedback from many users working in exacting production environments with deadlines. All this to say that its as much of a pro product as anything out there and its being constantly improved with fixes and new features even more than some paid choices. Don’t let the free price tag fool you.

This is completely normal behavior. What you see when drawing is just a preview of the mouse drawing nodes. The actual recorded automation removes redundancy nodes but the net effect will be the same with fewer redundant nodes because they are converted to curves. There is no reason to have extra nodes and they would use excess CPU.

That's great. Yeah I got a message from them last week and was going to post and mention that it had been fixed by them. Its nice when companies are proactive to work together and resolve problems. It benefits everyone. This is what they told me: "We just released a round of updates for almost all plugins. Those include the fixes for the problems with parameters not being recalled correctly in large Cakewalk projects, as well as the crashes when reopening projects that used our VST3 effect plugins. The only plugins not updated yet are Filterscape, MFM2, TyrellN6 and Uhbik. Those will receive updates later this year, or early next year. All others are now save to use within Cakewalk, after installing the current version."

Can you share the project file in question for us to look into?

Have you read this thread? The point of this new installer is to replace BA.

To be fair unless they tested it in Cakewalk with other synths in a project they wouldn’t have seen a problem. Technically though its not normal for instruments to change output counts its not disallowed in VST, but because of the way we handled port routing in Cakewalk (since the 2000’s really) this affected the port numbering. I’ve changed the code to adapt to changes in outputs now so this shouldn’t happen in the future. Of course older versions of Cakewalk software will still have the issue.

Hi @Creative Sauce it should be live soon. The delay is primarily in updating the website to link to this instead of BA where some stuff needs to be worked out. We also wanted to get more feedback and testing on the tool before releasing it. Thanks for the update regarding the help. Yes that article needs to change as well, because as you point out activation is automatically handled from within Cakewalk itself by virtue of signing in.

Mix recall is fully confiigurable and you can save snapshots of the faders and recall them at will. If all you need is A/Bing two different mix settings this is the ideal feature to use and switching scenes should be very fast if you do not choose to recall the FX settings.

@jsg we’ll investigate this thanks.