Noel Borthwick

@TheSteven Some follow up questions. Have you confirmed that you were using the exact same audio latency as the prior release? What driver mode were you using in both .9 and .11 What dropout code is being reported when you see the dropout message. In .11 it automatically restarts playback after a dropout by default so I'm curious why you got the dropout message, unless you explicitly set RestartEngineAfterDropout to False in preferences / configuration file. If the dropout code is 9 then please try raising your MIDI buffer size (prepare using xxx millisecond buffers) in preferences MIDI | playback and recording, to a value of 100. Retest your project after that. My hunch is that this is your issue.

@kagunmarx what freezing issue? I don't see any post from you describing this.

@HeatherHaze @jesse g as you probably have discovered by now the reason for the display changes were because you had a workspace set that was globally overriding your settings. We're going to be doing some video's on workspaces to help explain this better as well. Regarding full screen mode, we're planning on disconnecting that completely from workspaces or the project settings. FS mode should be only controlled by the button in the UI. Not sure if we will get to it for the hotfix but its on the radar. This happened because on some systems the installer and app got confused into thinking it was a first time install and launched the onboarding process which suggested the "Basic" workspace as well as may have defaulted to WASAPI. As a result of this after installing the .11 release the app was set up to run the basic workspace which sets up the initial view of the app. The user could have changed it in the onboarding process but if you zipped through it without reading the text then this is likely what happened. I wanted to clarify that this was not intentional and we have fixed this for the upcoming hotfix, so very sorry for the inconvenience and confusion. After installing .11 it should have been set to exactly the way you had Cbb set up. i.e if you had no workspace to start with it should have been left the same way. To go back to your preferred settings you have two choices. Either save versions of a workspace that fits your workflow OR set the workspace to none, in which case it will no longer override settings. You can always go back and tweak a custom workspace later.

@Colin Nicholls Strange. is this a MIDI or audio project? When it goes silent, do you see meter activity on the Main outs in the console?

Its wired to Melodyne always

Yes ARA 2 is aware of selection. There was a change that was deselecting the clip so that made the blobs not visible on execution of the command. If you select something else and then reselect the clip the blobs would be visible again.

@Matthew SorrelsDoes it work for you with CTRL-M?

@Matthew Sorrels we were able to repro it when you create a region effect from the menu. The shortcut CTRL-M still apparently worked ok. We think we have identified the cause and fixed it. It will be in the hotfix that we release soon.

@Matthew Sorrels are you sure that this is new to the .11 release? No changes in that area that I know of that could have impacted that.

Definitely not for wasapi shared. It's capped at 10 msec always. Wasapi exclusive can both go higher than 10 and lower. Maybe you were using that?

Hi @Krecikdwamiljony thanks for the report. in wasapi shared mode unless you have a win10 driver that supports lower latency the latency is fixed at 10 msec. Since you are running win 7 that would be the expected result here. I think there is a ui issue with the slider being grayed out which we'll look at. Thanks!

@gmp none of this would be specific to 2019.11. No changes in that area. How did you switch between 2019.09 and 2019.11 - did you uninstall and reinstall?

@Jetrel thanks, are you running the newest Focusrite driver? They fixed bluescreen issues in that update. There is still one bluescreen that happens if you turn off or unplug the device while in use. I have reported that to them. Just to clarify bluescreens in drivers are always the responsibility of the vendor to fix. Just like an application can crash, a bluescreen is caused by a crash in the driver code. Regarding the driver switching, Cakewalk does not change the driver unless you ran the onboarding process on start. Did you get prompted to pick a driver on startup? If you had an existing CbB installation that shouldn't have happened by default. My guess is that the FL driver somehow messed up the focusrite settings because Cakewalk doesn't change the ASIO driver latency unless you go through the panel or the new latency slider is changed.

The slider will be grayed out if the driver doesn't provide a range. 32 GB is plenty. I doubt you will have any issues. As far as clicks go there shouldn't be any worse performance in .11. If anything a few people reported improved low latency performance. The code also now handles buffer sizes as low as 16 samples properly. I can play with the focusrite 6i6 even at 16 samples without any clicks in a moderate project.

Hi @Jean I understand that any change takes time getting used to. The problem is that RTZ in any other application means what it says Return To ZERO. The behavior of jumping to a loop start is very unexpected for most new users to the program. We plan to have a new control bar module with better jump points in the future which should allow for easily navigating around various hotspots in the project. In the interim if you prefer using the mouse you can create a new button in the control bar and assign it to the "Rewind to Landmarks" which is equivalent to the W key.

Shouldn't be related to this version. However can you send us the minidump file for the crash please? See this article for more details.

@Skyline_UK There should be no decrease in performance at a lower buffer size. If you change back to 128 do you still get clicking? If this worked in the 09 release I'm interested in troubleshooting this further with you. Also please indicate whether you changed the latency from the ASIO panel or from the latency slider in preferences. The RME devices do not handle the new dynamic ASIO changes. I assume that the latency slider is grayed out for you? Also please enable StopEngineOnASIOPanelOpen for RME devices. I have an RME UFX and changing device settings from the ASIO panel doesn't apply changes properly unless this option is enabled. The driver requires ASIO to be completely stopped before a change is made from the panel. See below from the feature notes. New ini setting StopEngineOnASIOPanelOpen A few ASIO devices require that the host should not use the device while making changes to device settings. Some devices may display an error or gray out the controls in the ASIO panel while others may silently ignore changes. In prior versions of Cakewalk the only solution was to exit the app for such devices. In 2019.11 you can set the variable StopEngineOnPanelOpen in Preferences > Audio - Configuration File (second property in the list). Setting it to True will automatically stop and release the ASIO interface allowing you to change settings in Cakewalk. After making this change please try changing the ASIO latency from the panel back to 128 and see if it works well now. @Jetrel can you let me know whether you had changed the ASIO latency via the new latency slider in preferences or whether the buffer size was changed to 248 without you changing anything on first run? Why did you change to the FL Studio ASIO driver / WASAPI?

Did you explicitly run the getting started option or was this the first time you installed cakewalk? Getting started runs for first time installs.

Which version of Cakewalk are you running? Is it this month's release or earlier. Have you tried raising your audio latency?

Hi is this a MIDI project or are you seeing this on audio tracks as well? Are you running the latest release from this month? Im not sure what you mean by fading out. Are you getting dropouts, missed notes or is it that you hear a gradual fade.

Activation and updates have always been a requirement. Its also mentioned again in this months release notes. If you had been regularly updating you would have got an update that changed the application to warn you well before it required re-activation.The software doesn't "lock up". It will give advance notice when reactivation is required. It can be activated without updating the Cakewalk application itself, by using BandLab assistant's reactivate feature. It's recommended to update as well since there are often important changes and bug fixes. The process is even more streamlined as of this version. The only requirement for this free software is that it is updated periodically. Its a small price to pay for a completely free professional DAW. One of the reasons why we require periodic updates is that we continue to improve the application and cannot support multiple versions of the application in the field. Only the most current version is supported. Independent of Cakewalk itself, the BandLab assistant app also needs to be periodically updated. Its a web based application and its normal for those to require updates whenever the web back end is changed otherwise it would stop working. We live in a connected world today and completely offline use is less prevalent with most modern applications. Despite some of the pessimistic views on this, there are many ways in which this benefits customers. Users get responsive updates and we as a company get important feedback about how the application is being used, allowing us to improve the application for all.

@Carlos Gonzalez thats good. Is ASIO mode also working for you? Which audio device are you using.

There is a hotfix that was posted yesterday for an issue with WASAPI. Please keep comments about the 2019.11 release in the main feedback thread here.

@Carlos Gonzalez can you be more specific? What doesnt work with the asio driver? Without knowing more about what driver you have etc we have no way to assist you. Are you getting an error message? Post some screenshots of your ASIO setup.

@Ondrej HurbanicIt could potentially be Windows 7 specific. Can you check what the MIDI playback buffer size is set to in "preferences | MIDI | Playback and recording | Prepare using ..." Try raising that to 50 or 100 and see if it helps. Is it just the time display that is unsteady or is playback also affected?