Noel Borthwick

@Vyacheslav Thanks for the video. So let me verify whether I understand what you are doing: You open a plugin window from within the VEPro window When that plugin window has the focus you press space bar and the spacebar does not start the transport in CbB Is this correct? In your video you have not enabled the "give all keystrokes to plugin" button in the main VEP plugin window. Does it make a difference if that button is enabled? Also to clarify - the video you posted is with it working properly correct? BTW we had a case for this already logged. Unfortunately it did not get investigated in this release. I will escalate it and we'll address it since it appears to be a regression.

I’m having trouble understanding the exact problem since there seem to be conflicting reports. Are you trying to start playback from within the VEP window and is this the plugin version or the standalone version runnng on a different PC? i.e when it says “start and stop your playback from within Vienna Ensemble PRO” are you referring to an instance running within Cakewalk or external to Cakewalk. It may be helpful if you post a video so we can see what you are doing. We normally intercept the spacebar and it should start the transport. PS: binary thinking like it works in x/y/z but not cakewalk is not useful for diagnosing problems so lets focus on trying to find out what is happening. The problem could be in Cakewalk or could be in the plugin until we find out what the issue actually is.

You are conflating different issues. The BandLab assistant issue is not the same as the one where error 12175 is reported from within Cakewalk. That is a Win 7 specific problem. The BL assistant issue is different. As mentioned we're planning on deprecating that tool and provided a link to an alternate installer for new users.

Please report this to the PC vendor you got your computer from. Until they fix these buggy drivers from Realtek users will continue to have problems.

Yes in WASAPI shared we disallow multiple interfaces because recording from multiple devices would be very complex to synchronize. In WASAPI shared mode the device returns variable size buffers so handling them and synchronizing them across multiple devices would be difficult to do. Its more deterministic and fixed size in WASAPI exclusive so we allow it there. WASAPI shared mode is quite complex because you are really reading and writing data that has is processed by the Windows audio engine additionally, unlike exclusive mode where the app is directly communicating with the driver (similar to ASIO). This is how audio output from Cakewalk output can be mixed with other application streams in Windows (via the Windows audio engine)

It depends on the manufacturer. Some allow running two interfaces of the same kind and aggregate the I/Os via the ASIO driver. Presonus allows it with some of their devices. MOTU, RME, LYNX all do.

Until Microsoft drops support and it stops working yes Similar to Win 7.

No that looks like a bug in the program you are working with not properly understanding the Wavformat extensible format. I don't think this has anything to do with our export. Choosing Wav(microsoft) is simply choosing the libsndfile wave file writer rather than Cakewalk's built in one. There is probably some difference in the format that is confusing your encoder. I would log an issue with their support to find out why it fails.

post some screenshots of how you have set up the track inputs and your audio preferences settings. Also what driver mode are you using and what audio interface.

This is a win 7 issue. See this thread. Note that win7 isn't supported

Well I think a better adjective is workflow rather than old school Those programs are built for different primary use cases rather than production. Cakewalk has deep midi editing tools and now articulation support that those programs don't have. And our console view is one of the better implementations depending on your perspectives of course. Look and feel aesthetics vary a lot and we will continue to update our UI. Cakewalk is a program that has roots 30 years ago so there are bound to be some elements that are legacy but that isn't always a bad thing for reasons that you state. PS: try going to Europe and telling people that their architecture is old school lol.

Curious what aspect feels old school to you and what you are comparing it to.

Realtek ASIO has bugs that are known to cause symptoms like what you saw. I would uninstall that driver.

Thanks for your feedback. In friendly names mode you can now also name the left, right and stereo components independently for completely control over the names.

Its an old bug. The same thing happens in SONAR. We'll look into improving it.

Bus waveform preview is completely different from the clip waveforms so it doesn't show clip outlines there. Its not a bug but we can consider doing it for consistency in the future.

@Brian Lawler I verified that it is related to a fix I made in 06. There were cases where some windows messages were being skipped by certain UI controls that could cause unexpected UI behavior in some plugins. The spin control used for changing tempos was one of them that had the bug. >>Also- the data does not send on mouse up for me- I have to click somewhere outside the tempo window (Win Pro 21H1) That part is expected, only when you press enter or click away from the control is the new value committed. It's normal behavior for a spin control.

Which version were you using before you updated? The slider always send data at the end (on mouse up) but there was a a bug fix for something else in the UI that may have caused an unwanted plugin interaction.

This may seem unrelated but what audio interface are you using and what is the driver mode set to?

Honestly, that is subjective depending on whether you prefer seeing stereo or mono first. I like the bold text but currently it isn’t easy to do. When we switch to the new menuing system in the future we can consider it.

We have discovered that there is a serious bug in the latest Microsoft VCRedist installer. The Cakewalk installer includes this to install various files that are required by the application. The latest iteration of this file has a bug where if you run it for the first time it works. However if you run it a second time it removes several files from the system32 folder that are used by our application and many others. The most typical symptom would be that our installer fails to register CW130Auto.dll (error code 3) and after that the application will fail to launch. Fortunately we have not shipped a version of CbB that uses this VCRedist yet. However if you install the latest redistributables manually from the Microsoft website you will most likely run into this issue so please be aware of it. Here is a thread where several people have reported the issue. Please upvote the post if you have a Microsoft account so that they escalate the issue. If you have the problem you can typically fix it by running the vcredist manually a second time.

Oh wow, is that something you installed recently? Most likely it installed something that gets enumerated on startup of CbB and crashes. So many things that can screw up a machine!

Please follow this thread. If its crashing on startup most likely your VC redists are somehow out of date.

I’ve made a few tweaks to the port naming logic for the next update. When friendly names are used it will no longer show the generated prefixes and leave it upto the user to name them appropriately. The I/O channels are now only shown in the menu and not in the actual port name field to make the name even more compact. (it will be shown in the tooltip) The channel display in menus now separates the channel from the port name text from the driver more clearly by using columns You can choose to display the I/O channel information as a prefix or suffix to the port names showin in the menu. Hopefully these changes should make it even more useful. Regarding arbitrary ordering of ports, while its technically possible it would be quite complicated since we already have abstraction for ports because you can already choose to disable channels that are not in use. Adding reordering on top of that would make my head explode

@Steve_Karl were you running the latest Cakewalk release for 2021-06? BandLab assistant will likely be deprecated soon so you will ultimately need to be able to login through Cakewalk. How were you attempting to log in - did you use the Google auth or Facecebook sign in option or just the BandLab sign in credentials? If it worked in BandLab assistant as long as you are using the same kind of sign in the same credentials should work. If this is not working send me a PM and we can try and work through why its failing for you.