Jonathan Sasor

Please try and capture a dump file for the crash and we can take a better look into what's going on. Details can be found here:

MIDI tracks can only have one output. You'd want to copy and paste the data onto another track for them to play the same parts.

I'm just catching up to this thread now. If you've seen the 2020.04 Early Access threads you could tell things have been busy in the Bakery of late getting ready for the formal drop. @Mark Withers what you need should be right here: https://www.cakewalk.com/Support/Knowledge-Base/2007013201/V-Studio-700-Control-Surface-Plug-in-version-1-2-update# If you're running a VS-700 you should likely have a single sign on account to grab that link, but otherwise let me know and I can get you a link otherwise.

As you can see, it's been a fairly large bun in the oven! ?

We primarily test with Windows 10 (which is what the the large majority of users are on), but we still 100% support Windows 8.1 We stopped officially supporting 7 because Microsoft stopped supporting Windows 7. It drains resources when you have to work around functions that are not available in older versions of Windows. As is, we still do not prevent you from installing on Win 7. We just flag that to let users know that we're not going out of our way to fix any bugs that are specific to Windows 7. I mean, you could install CbB on Vista with the same message if you really wanted to, we just give you the heads up.

It's very much ongoing! We're just working on something that requires a little extra time in the oven right now.

Depending on which SONAR install you're talking about, generally speaking, yes, running the uninstaller(s) for SONAR and the relevant plugin or sub-installers from Command Center will remove all the bundled content. If you just uninstall SONAR Platinum though, the content isn't tied directly to that uninstaller because much of that content has their own installers/uninstallers that you'd need to run. Yes you can continue to reinstall SONAR and/or it's previous content at any point via Command Center prior to installing Cakewalk by BandLab. The content is the primary reason to keep SONAR installed at this point. The main reason to install 32-bit plugins on a 64-bit system now would be more for previous project compatibility. Cakewalk by BandLab is a 64-bit application that can run most plugins through BitBridge. Some older plugins don't play well with BitBridge, and a 32-bit install of SONAR might work better in those cases. Generally though it's best to stick with everything in 64-bit. If you have both VST2 and VST3 versions of the same plugin, the only real reason to install the VST2 version would be again for previous project compatibility (although CbB can replace VST2 plugins with their VST3 equivalents when possible). The actual location of the VST2 is not that important so long as you pay attention to where that is with your plugin installers and make sure it's in the Preferences in Cakewalk. VST3 plugins have a universal global location, C:\Program Files\Common files\VST3.

Just a quick note on the subject. Since Microsoft is no longer supporting Windows 7, it doesn't make sense for us to devote resources into maintaining things specifically for that version. That said, other than the installer prompting that 7 is not an officially supported system, nothing is preventing you from installing the current updates there. It's just a flag that warns you that it's not officially supported. This update should work just as well as the 2019.12 update on Win 7. At some point, we'll start leveraging more modern functions in Windows that we haven't been able to while keeping full Win 7 support. We're not in a rush in that regard, but as we continue to develop CbB, it's always in everyone's best interests to take advantage of any optimizations so the app can do more faster.

I think there was a bit of confusion there between the SONAR X series (X1, X2, X3) and the much older SONAR XL. SONAR X2 would be about the right time frame for when the VS20 was released, otherwise the separate installer would do the job. @chuckebaby I think you actually do need to be logged in on the site for the download links, most of us just stay logged in and don't think about it anymore. ? If anyone without a Cakewalk account needs a legacy installer file off the site, send me a PM and I can provide a link.

32 is fine. This basically refers to what bit depth it renders audio to within the project, as in when you bounce to tracks/clips. Considering it's standard to record at 24-bit from the hardware, this then gives you slightly better when processing audio internally.

If you're saving a a copy of the project in the same project folder, uncheck the "copy audio with project" option and it disables those path boxes altogether.

I'll take a look at the folder boxes [EDIT: I've logged a case in the system for it], but to accomplish what you're trying to do there, there's a couple things. First off, when saving a template file, you should do put in the stock templates folder rather than opening as a saved file. When saving something as a template, there's a "go to folder" drop box that you can set to templates, and it'll take you straight there. When you save your own templates there, you can go to File | New and specify locations for folders when you create the project. Second if you disable the check box for "copy audio with project" it'll turn those boxes off at the bottom and only save the CWP, so if your project previously was using a global audio folder, it would retain that. I wouldn't really recommend using a single global audio folder though. The Save As page is designed to be able to keep your projects organized in folders that contain the .cwp and audio in the same place.

It's actually very simple. You only change a couple lines in one config file for the driver's installer, just as it shows in the thread that Mark pasted above, quite a different thing from rewriting the driver. You can actually copy/paste from that thread into the specified file, and it'll work. The worst case scenario if you goofed on the config file would be it doesn't install.

I set up that very same VS-700 in the office in Singapore when I was out there in 2018. Trying to get the drivers from Roland is not quite as cut and dry of a thing as one would like, plus you're dealing with only so many units for what's a 10 year old piece of gear at this point. So while they still run, I wouldn't hold my breath for there being any updates.

The short answer is it generally works fine. Unlike the VS-100, Roland never got around to making a Windows 10 installer for the VS-700 driver. The v2.2 driver itself will work on Windows 10, it just requires you to manually edit a configuration file in the installer to allow installation on Win 10 (which then requires booting into windows with driver signatures disabled for the install). There's a whole big thread on the old forum with the details on how to do it. In practice, it's a pretty simple thing to do. I personally run a VS-700 every day. All the major functions work just fine in Cakewalk by BandLab. I'm not sure that I'd want to throw large sums of money to get one at this point, but if they're offering a deal for it, it's a pretty good piece of hardware. Bear in mind its hard to say how long the Windows will keep the status quo with how the drivers work, but at least for the past few years it's been fine in my personal experience.

Having a bootcamp installation of Windows is the only way to have Cakewalk run on a Mac. You're booting the mac hardware into Windows rather than MacOS, and that will work.

You can do this in Track View's Options menu, Meter Options. This is then saved with a project/template. The template will appear in the start screen so long as you save it as a .cwt file in the correct location with the other project templates. There's a "go to folder" drop down that will take you right to the template folder when saving a template.

Assuming you get the drivers installed, it should work okay. I run a VS-700 with the tweak to the driver installer. So long as the correct ports are set for the right surface in the Control Surfaces tab of the Preferences, it should work, assuming you're not having issues with the MIDI information getting sent to Cakewalk in general.

We're aware of this issue and it's logged with development. Like Dave said, we recommend not making changes to your MIDI device configuration while you have a project open in the meantime.

That's exactly it, so feel free to request whatever you might find useful. We can't do everything for everybody, but if someone has a a good idea, we're definitely open to hear it.

Just bear in mind that if you install Platinum, you'll want to then reinstall Cakewalk by BandLab on top again as there's shared components that will get overwritten by Platinum.

If you're using the Smart Tool, you can CTRL Click to adjust the gain envelope for that clip. The ProChannel has always had the option to save/load presets. You can use CTRL + Shift to do this in the PRV now.

While I can't speak to everyone's experiences, I can say that the Bakers collectively are very passionate about CbB and we do everything within our power to make it the best possible app it can be. Every app has bugs, that's part of the game with software. If we can identify a problem, we'll fix it (as time/resources allow). Workflow stoppages get our attention first. Our team is not the biggest one on earth though. We wear a lot of hats and juggle a lot of responsibilities. It becomes slightly more complicated with third party vendors. We try our best to reach out and work with other companies to ensure that plugins work as well as they can. Some companies are more receptive to working with us than others. What's difficult to tell is that sometimes a plugin might have a bug that is only exposed using a given host. Not every host handles plugins exactly the same- there's some wiggle room in how the VST spec from Steinberg is implemented in each case. If a plugin itself is failing in Cakewalk, there might not be much we can do, we can't debug other people's code. That said, if there's something we're doing incorrectly, we will absolutely make every effort to fix that on our end. Sometimes we'll find a problem with how a plugin is operating and reach out to the developer, and not get much in the way of a response. In those cases we can't do much, but we're always open to working other companies. That said, we try to replicate problems as best we can. A lot of times there's system environmental variables that we can't account for. This is part of why we push updates and hotfixes. When we can identify and reproduce a scenario that's reported, we try to get a fix out as rapidly as we can. The CbB dev team spends a good deal of time working with users to this end. We want the app to work as smoothly as possible for everyone. Sometimes people hit roadblocks, we do our best to avoid that from happening in the first place, but when that happens, we're more than willing to work with end users towards a resolution. Sometimes there's a system configuration issue that needs to be tweaked. Other times some hardware behaves unexpectedly. Obviously it can be frustrating when you run into a problem, but as with third party vendors, if users are willing to work with us, we'll do everything within our power to get them back on their feet as rapidly as possible. All we ask is for a positive attitude and we'll return in kind and do our best. We're not perfect, no one is. But we're always striving to make improvements wherever possible, and will continue to work with our users both through support and via this forum.

They're Heritage guitars, a H-150 and H-535.

If you go to Task Manager when you're seeing that dialog, you can generate a dump file that you can send us that will provide a bit more information. This link has better info on that: If both the VST2 and 3 are installed, its not unusual to see both unless you specifically have the option to hide related VST2 plugins in the Preferences. Is the "replace if possible" option there also enabled?