Noel Borthwick

It's not. Most encoders write audio directly without first being written to wav. Only the external encoder does that

I'm thinking of adding a parallel export to wav for other encoders

I can repro it with your file! I'll investigate it thanks.

Yes you can create two tasks and they will render the wav and mp3. Its not rendered at the same time however it will do two bounces.

@rocstudio I'm not seeing any cases where audio disappears when you do a bounce to clip with buffer size set to 350. If you can reproduce this can you share a zip of your project folder so we can look at it?

Yes the that buffer size is global so is used by bounce to clip as well. That part is not new to this release. Perhaps we should ignore that setting for bounce to clips since it has no UI.

Fast bounce is not related to the buffer size option directly. All it means is that Cakewalk exports as fast as it can and is not gated by realtime playback. The custom buffer size itself only applies when Realtime playback is unchecked in the 2021.09. The only change in 09 is that fast bounce is now renamed to "Render in real-time". So to do the equivalent of a fast bounce make sure render in real-time is unchecked.

Are the dropouts actually impacting your work or is the message and audio stopping bothering you? If so you can turn off the dropout detection here:

For activation please read this FAQ on Activation, especially the section on in-app activation.

Some discussion of optimizations in win11 https://www.tomshardware.com/news/microsoft-details-how-it-made-windows-11-faster-than-windows-10

Oh God no, the cookie is only used to remember the users identity so that it doesn't have to prompt you to log in everytime we want to access something from Bandlab. The mystery of the overloud plugins activation is most likely because we install the original overloud TH3 installer which may be resetting the activation to what it used with SONAR. So this is probably why you see the custom code getting clobbered. Why it worked this time is when you updated you got our "thin installer" which only installed the program and anything that changed. This is another reason to update frequently since the updater will only get the differences rather than the full program installer No legal issues with Gibson, but your original FX chains referenced a lot of SONAR exclusive plugins which we don't ship with BL. So it did not make sense to include those chains out of the box since they would reference missing plugins for most users.

Correct. Also every time the activation is refreshed you get a new lease. You can also do it manually via refresh activation for the obsessive compulsives

Being "logged into BandLab" from Cakewalk simply means we save a cookie that allow you to reach user specific BandLab services such as the BandLab library view to download from BandLab, and of course activation itself. Cakewalk doesn't actually send any data to BandLab based on being logged in, so there is really zero need to log out unless multiple people use the system and you don't want them looking at your songs Regarding updating frequently if you don't use the program often that's really your call. Activation will still work automatically (if necessary) the next time you launch the program even if it's after a long time. I've never heard of overloud plugins losing activation as a result of updating Cakewalk. There is no correlation. Maybe you are confusing it with command center.

If you have logged into your BandLab account from within Cakewalk (and stay logged in), you should never need to manually reactivate even if you go past 6 months. As long as the PC is online it will automatically restore its activation whenever needed. Additionally if you ever install a new CbB update within a 6 month window it automatically restores activation. People complaining about this have been using an old version of CbB that didn't have these improvements. This was done back in April. Current CbB users will never see this message. The bottom line is issues like this is why we want people to keep up to date. Otherwise they complain about things that have been fixed ages ago.

Do you see the audio data in BandLab's mix editor when you edit the project there?

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,