Noel Borthwick

I'm curious what aspects of a chord track are attractive to you in your workflow. i.e how do you use it. Feel free to make a thread in the feature requests forum.

We'll investigate and fix it. Don't worry about the message there is nothing catastrophic. Its just an overly paranoid translation of a standard Microsoft error code that just means an operation failed

That's not our message. Check if one of your plugins is displaying that message.

Which version did you roll back to that doesnt show the problem?

I dont think you are describing the same issue in this thread. Please post in the main 2020.11 feedback thread with a description of the problem and if you are getting dropouts list the dropout code. Exporting cannot create dropouts.

@Mark Morgon-Shawcan you try rolling back to the last release just to verify for sure whether this is really a new symptom?

Which version of CbB are you running. Have you updated to the latest 2020.11 build that was released?

@Mark Morgon-Shaw are you sure that its new to this update - did you try a rollback? If its a new issue can you share the project file that has the issue?

No the driver isn't filling with zeros. If its got DSP then its passing on the floating point sample data through the ASIO input. Here is an example of a device that supports floating point ASIO. We added support for this several years back. If cakewalks record bit depth is set to 24 when the driver exposed 32 then we would be discarding the extra 8 bits permanently. Similar to if you set the record bit depth to 16 when the driver supports 24.

If your libraries have any cubase maps you can import them.

Using workspaces and a custom theme would probably be the closest way to do this. At one point in 2016 we were actually heading towards making one universal app that could be skinned to all our SKU's and have dynamic feature sets. This was one of the primary goals for lenses at the time.

You can update directly to this release. If you had a release earlier than 09 you will have to do the update using bandlab assistant. Future updates can updated directly from within the application.

As of 2020.10 you will be presented with in-app updates whenever an update is available. Updates are downloaded to a Cakewalk subfolder in your local Downloads folder. So you can transfer the installer easily from an online machine to an offline one.

If you check the release notes in the latest release its no longer necessary to activate using Assistant. Cakewalk will self activate as long as it has an internet connection and you log in to your bandlab account from within Cakewalk.

As long as you have an internet connection *somewhere* at an internet cafe or something you can activate cakewalk. All you need is to install BandLab assistant there and download the activation request as explained in the documentation. Its dead simple to do and is similar to what we had earlier with SONAR.

No thats the old SONAR help. I had posted a bad link originally, I updated it to the correct link.

It's not a ”flaw” in the system, it's by design. You can authorize an offline machine by following the offline activation workflow. Cakewalk won't get randomly unauthorized beyond the normal 6 month period unless the system has been updated in some way to break the authorization. In the activation message there is an error code that should indicate what the source of the problem is.

Just saw this. There original diagnosis of the problem was by me. This issue had nothing to do with your network interface but it's a faulty asio driver that crashes when loaded. As long as you uninstall it remove the dll it should work fine. Looks like you figured out how to do that.

One exception. There are some drivers with onboard mixing or dsp that expose inputs that are floating point. It makes sense for such drivers to offer 32 or 64 bit inputs because the signal chain is floating point.

@Winstonhulley88 that's great news. In most cases problems with compatibility can be rapidly resolved if you contact the right right party with a solid recipe. Thanks for following through and reporting back.

@Morten Saether can fix that That's sounds right.

It uses the latest LAME encoder internally.

In CbB you can use clean audio disk which works very fast and flags unused audio files within the project folder (unlike SONAR).

The default PicCache size is 500 MB not 20. Are you sure that a 3 hour project took 115MB for one wave file of that duration? My estimate was a too optimistic but a stereo 3 hour wave file at 24 bit 48Khz is about 3.1GB A pic cache file is approx 1.57% of the file size so that would make it about 51MB in size. So a 10 day recording of one file would yield a wave file of size 248GB and a pic cache size of under 4GB. PS I think the overview file can grow greater than 4Gb (it will turn into a Wave64 file under the hood) but we should verify that. As per new CbB versions we allow the pic cache to grow for that session beyond the max size but on next launch it will try deleting files to free space.

Are you using the latest build of CbB? I can't speak for Platinum