Noel Borthwick

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!

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.

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.

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.

@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?

@Tim White I don't think your problem had anything to do with the update. The fact that increasing your latency fixed it means that you had set the latency too low at some point or some other app changed the driver latency. When you opened Cakewalk it picked up the change since ASIO latency settings are global. The distortion is because buffers are being skipped. There is a DropoutMsec value in settings that controls this. It's quite high by default so the app doesn't drop it but you can hear noise. If the latency is too low. I plan to add a notification when this happens for better troubleshooting.

Are you running the hotfix above? It is build 25.11.0.59

You can't select two inputs or outputs from DIFFERENT devices in WASAPI shared mode. Its a limitation of how shared mode works. If you want to use different devices simultaneously use WASAPI exclusive mode which has the ability to pick independent devices simultaneously. Of course this will only work if the two different devices support the common sample rate.

Please post feedback on 2019.11 in the main feedback thread to make it easier for us to monitor. Also regarding the crash when disconnecting ASIO devices please try the hotfix that was posted.

Please post feedback in the main 2019.11 feedback thread rather than making new threads.

2019.11 Hotfix Early Access 1 (HFEA1) installer now available! Thank you to everyone who has provided feedback on the official 2019.11 release! This hotfix addresses some key issues based on field reports and user feedback. We're releasing this early to unblock any users who rely on onboard audio devices using WASAPI mode. The public hotfix will be released soon but we're waiting for more feedback before final release. Please report any issues in the 2019.11 feedback thread. Note: The HFEA1 installer will only update the official 2019.11 release. Download Hotfix EA1 What's New Glitchy audio playback with WASAPI on some devices - particularly with onboard audio since updating to 2019.11. Crash if an ASIO device was disconnected while in use by the application

It would be very unexpected for double clicking to turn a clip into a melodyne clip automatically. There is a specific command CTRL-M to do that. Double clicking only opens the related UI. If it is not a melodyne clip it opens the clip properties by default but it can also be configured to open the loop construction view.

As mentioned before we don't test anymore on Windows 7 or support it actively. Having a separate install for Win 7 isn't something we plan on doing so I highly recommend that you plan for an upgrade.

It has always been possible to disable the quotes without turning off toasts altogether. "To turn off affirmations, leave the text file empty."

Some of the most common and complex problems that arise when using a DAW (digital audio workstation) are issues relating to plug-in compatibility. At Cakewalk we take plug-in compatibility problems seriously and all reported issues are investigated. It is however impossible for us to test thousands of plug-ins in Cakewalk. While we follow best practices for VST compatibility, handling plug-in's can be complex since many vendor's do not test their plug-ins in all hosts, and there can be subtle or not so subtle (crash) behavior changes across plug-ins running in different host's. Before drawing conclusions on the cause of a plug-in related fault, its important to properly collect information that can assist with diagnostics. If you encounter an issue with a plug-in here are some tips to diagnose it. Identify the kind of problem. There are a few kinds of issues: Compatibility issues. While this can be wide its important to try and isolate whether the problem appears within the plugin or the host. e.g do you notice the problem in the plug-in UI, does it occur with only certain presets, does the issue occur when loading the project or when exporting audio, etc. Crashes. This is self explanatory but its critical to observe whether the crash report indicates that the crash in within the host program or within the plug-in DLL. The crash dialog will typically list the module that the crash occurs in in the title. If a crash occurs please save the Minidump for the crash since it is the only way for developers to diagnose the issue. Hangs. In a few rare cases a plug-in can cause the host to hang. If a hang occurs you can still capture a dump file while the app is hangling, though it may be a lot larger. Project specific problems. These are cases that result in unexpected behavior only with certain project files. Diagnostics and action If the plug-in crash is listed as happening within the plug-in DLL the first course of action is to contact the vendor of the plug-in. The reason for this is in many cases the the issue is caused by the plug-in running into an unexpected operation from the DAW that can only be fixed by the plug-in vendor. Every DAW is different and unless the plug-in has been specifically tested with a DAW there is a potential for unexpected bugs being discovered. If the crash occurs in the host program (Cakewalk.exe is shown in the crash title) then one possibility is that the host ran into an unexpected condition. This should be reported to Cakewalk. It's important to note that not all crashes in the host are caused by the host. Plug-ins share the same memory space as the host program and as a result of buffer overwrites can corrupt memory, leading to random crashes or app shut-downs. In all problem cases the best way to report it is to provide the following details to all vendors concerned. Write a detailed description of the problem Include a zip file containing the project in which the problem occurs Include all minidump's if the plug-in causes a crash. Please read this for more information on how to capture a minidump In some cases Cakewalk will assist and work with the plug-in vendor to get a resolution to a problem. If you send a problem report to a third party vendor you may also refer them to contact us through our support channel at support@cakewalk.com should they have technical questions or require internal follow up with us.