Noel Borthwick

The sound enhancements tab is shown for some devices. It should not be enabled for pro audio devices. Were you seeing this applied to your audio interface output? Also Spacial sound should be disabled if its on. Below are screenshots for the focusrite device and for my headset. You can see that Enhancements is not shown for the focusrite.

Changing the extension wont do anything. We look for the signature of the VST which is very different for VST3.

Please note that the installer now tries to install a Microsoft Webview component that is used by CbB. This installer will download what it needs from Microsoft so if it appears to be stuck its likely due to a slow internet connection or internet connectivity issues. 32 bit is just the Cbb installer thats normal. Here is a manual link to download the Webview components if its not downloading. Download and install the 64 bit fixed version and after that our install should go through.

There should not be a need to uninstall and reinstall. If its crashing please send us the minidump so we can diagnose the cause.

VST3 plugins can be shells. A single dll can store one or more plugins so it really depends on which plugin you installed.

Hi @winstonhulley Im guessing but this seems to indicate that you had a beta release. Can you try reinstalling that release or install the latest early access release that we posted and let us know if it addresses it.

As I said it's an obscure issue Yes acid is not related to red directly but inside our code we leverage the same acid structures while handling rex files. Hence the confusion because apparently that app is writing data that confused our code. Irrespective the issue has been solved.

Yes there is a new elicenser build from Steinberg that resolves this issue but as far as I know it has not been released yet. I can try and get you a link to the build if you pm me.

Its not clear if you are referring to a crash or a drop out since you say that it completes the bounce and then you get a drop out. A drop out is not a crash...

@forkol you ran into an obscure very old bug with acidized file import. Apparently your file is authored by a plugin called Edison from FL Studio (I found this in the files metadata). This plugin is writing information into the ACID chunk of the file which confuses our import code into thinking that it was a REX loop. Hence on playback it was using rex stretching and generating the clicks. I've fixed it for our next CbB release.

No snow this week here fortunately. Thanks for the update. Technology can be very frustrating when you are trying to get something done and things don't work. Don't feel bad because I have it it happen to me when I'm doing sessions too. I take a note and move on and try and figure it out later but it can be very disruptive. We try whenever we can to make the program as fault tolerant as possible but as you know there is only so much we can do. Perhaps we can try and detect this issue and at least warn the user that waveform generation is failing.

Wow this is literally the first time I have heard of this happening to anyone. Do you have an AV program? Maybe something went awry and it decided to block that folder. Cakewalk definitely doesn't change folder permissions. Do you by any chance have OneDrive syncing that folder as well?

There is no "standard" that the range should be 0 to +10 dB. Cakewalk has always had 0 to +6dB from day one. Its not easy to change the max range to +10 dB because the faders have art that is calibrated on the 0 to 6dB scale. It would be better for surfaces to allow calibrating their fader strips more flexibly rather than forcing the DAW to change based on one particular surface.

I don’t believe that the surface API allows for specifying the fader throw. We’ll look into it and see if there is something that can be done.

Thanks for reporting it. The symptoms look like heap corruption. We’ll try and reproduce it and follow up with the developer as well. @jon sasor [cakewalk]

Cakewalk requires you to log in once if you choose to activate it from within Cakewalk. It does not know that you are logged in to the bandlab website since that is independent. Similar for BandLab assistant, you must log in from the app. Its the same for all applications like spotify etc - if you run a desktop app it needs to be authenticated independently. Make sure you are running the latest version of CbB which is 2020.11.

@Michael Fogarty can you elaborate on what you did to fix the permissions? I have not encountered a windows update causing waves to not draw.

What is the repoted dropout code?

Correct, it uses pipeline parallelism to split the buffers and process them in parallel to achieve greater parallel processing even though the DSP pipeline itself has serial dependencies. I have a known limitation in the implementation that I hope to improve this year that may help improve performance when using it.

Good points. A few driver vendors create dependencies that cause unpredictable realtime behavior. Ive had this discussion even with Roland who claimed that background processing was the proper setup. Its completely counter intuitive to me since its now allowing any background process on the system to be given take priority over the DAW which means that audio processing could get less resources in theory! I’ve even discussed this with a systems engineer at Microsoft many years ago who said it was not a good idea to do this in general. Maybe @Pete Brown could verify this. Your theory that they have a (bad) dependency on some background process is possible. I’ve definitely seen drivers start to glitch when there is excessive activity on the UI thread - in theory this should NOT happen since the UI thread is running at much lower priority than the engine. Cakewalk’s UI is on the heavy side and I’ve been chipping away at reducing its footprint all of last year so it has helped but in an ideal world this should not be an issue. Regarding drivers that share this is likely because they are internally synchronizing to block processing until all clients have processed audio, similar to what WASAPI shared mode does because they have to mix all streams and potentially do SRC as well. Its not surprising that this scenario would cause some glitching. I wonder if the ASIO drivers that support multiclient access are running their mixing code in a different process. If so I could see how having background priority set could potentially change things there.

@forkol thanks we'll investigate this.

Can you clarify whether you were seeking on the timeline AFTER making changes or if you were stopping and restarting playback. As mentioned until you stop and restart playback it will not read the currently recorded automation. If its a BREVERB issue it would be up to Overloud to address it. However the version of BREVERB that Cakewalk had distributed is an older one so I'm not sure if they would update that.

I agree. It was a very good solution at the time and with some minimal decent driver support it would have been fully functional even today. Its a shame that Roland has this approach discontinuing stopping support for hardware devices prematurely.

Kurt, BREVERB has known bugs with its rendering of automation so most likely you are running into one of those. That is not an issue that can be solved from the Cakewalk side. Please retest with a different plugin and you should not see the same issue. Also something to note. In Cakewalk recorded automation is only applied when you stop playback so if you seek on the timeline to an earlier point where you had recorded automation, it will not render until you stop and restart playback. I don't think this is the issue you are encountering but I thought I would clarify it.

It's rarely useful to set track outputs directly to hardware outputs because now you lose control of the master mix. Good practice is to always output to a bus and or send to an aux bus.