Noel Borthwick

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?

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

@Matt Dunn sent you a PM for some troubleshooting.

Are you running the hotfix above? It is build 25.11.0.59

@HIBI I'm sorry I quoted the wrong post. I meant this report of yours. The other issue is related to BandLab assistant and it has been reported to the team that manages that product.

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.

Yes this is expected because the factory supplied workspaces (including Basic) all have the control bar configured a specific way. Please read up on Workspaces to learn what settings are stored in a workspace preset. When you select a workspace it applies the settings stored with that particular workspace preset to the application. The control bar settings are global application settings and are NOT stored as part of the project. If you wish to customize the control bar and retain your settings there are a few things you can do: Do not use a workspace (to do this set the workspace picker on the top right of the screen to "none"). When no workspace is used the app will have only one look as defined by your control bar. Create your own customized workspace (best option). To do this: pick one of the factory workspaces that best suit you Adjust the control bar to your liking open the Manage Workspaces dialog from the workspaces menu. Make sure that "control bar layout" is checked in the Load from workspace box. Click the + button in the dialog next to the workspace name to create a new workspace Name the workspace (eg. "Matt's Workspace") Click the save button next to the workspace name and then click OK This will create and assign a new workspace with the customized control bar settings for future use Now the next time you open or use the app it will always retain your preferred control bar settings.

@Matt Dunn what control bar bug? I don't see any post from you describing this.

@Matt Dunn what audio device are you using? If you were using WASAPI earlier this hotfix should address your problem.

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.

Its unlikely that anything in 2019.11 would adversely affect ASIO performance. In fact some users reported improvements in the early access program. Were you able to revert to a backup to verify this?

@HIBI can you check if this works in the hotfix?

We've posted a hotfix for those who had glitchy playback with WASAPI. Please download the hotfix installer and let us know if this addresses the problem. This will update the 2019.11 to build 59. @Funk @deepseasquid @Matt Dunn @Meg Aedu and others who reported this please try out this update and report back.

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

Hi folks, We've identified an issue that can affect users who are using WASAPI for audio at 44.1K leading to crackle. We'll post an updated installer soon in the early access sub forum. A hotfix will likely go out next week since we're closed for thanksgiving.

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.

If they show up in your VST2 menu then there is definitely a VST2 plugin in your path. You can check the registry key to see what dll its pointing to. For example: HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory\c:/program files/Cakewalk/vstplugins/SI-Bass Guitar/SI-Bass Guitar.dll The FullPath value in this case shows "c:\program files\Cakewalk\vstplugins\SI-Bass Guitar\SI-Bass Guitar.dll" You can also look at the path by viewing the plugin properties from the effects window after inserting the plugin (from the VST2 dropdown).

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.

That's a one time setting so you will have to manually set it to 50 if you had the early access.

@User 905133 thanks a lot for your detailed feedback. We are aware of some of the issues you point out and will try and improve it over time.

We don't have time based deadlines for updates. In fact we delayed some of the prior updates due to test concerns and implemented the early access program for this reason so that we can get more end user feedback. We had over 100 users try our early access last time around and it led to a much more solid release than would could have hoped for with just internal testing. The two month release is a sweet spot for putting out a release of moderate size. Any longer than that it gets progressively harder to test since the scope gets much larger.

We don't release unless it has been tested as much as we could internally as well as in beta test. Smaller releases are much preferable to monolithic large releases that are much more likely to cause problems and harder to troubleshoot. We switched to this model many years ago and many other companies follow the same. I would dispute your argument about users not caring about our releases. We have got direct feedback from many users who are very happy that we are addressing long standing stability issues in every release.