Jump to content

Jonathan Sasor

Staff
  • Content Count

    294
  • Joined

  • Last visited

Community Reputation

228 Excellent

6 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ProChannel modules install to the global Shared Utilities for Cakewalk. The full core installers for Cakewalk (or SONAR) should always replace the stock modules which include the PC76 and PC4K compressors as well as the Tube Saturation. The actual .dll files for the modules are not obviously named though. The VST Scanner should automatically scan the folder for these behind the scenes without it listed in Preferences, although you can see the path listed if you look in the Options via the Plugin Manager.
  2. The UI is working normally on my side for everything (tried a few different installs/configurations), which would lead me to believe that something is weird locally on your system that would cause that to happen. You could maybe do a rescan/reset for plugins and see if that helps first.
  3. Aside from the GUI, it should not be possible in the current build to have both the PC76 and PC4K compressors inserted in the ProChannel at the same time. This seems like there's something with your overall installation that is not working properly. You might need to try a clean install.
  4. It should be fine on Windows 7. We haven't made any change that would adversely affect it, the only change for 2020.01 was popping the notification in the installer.
  5. The .VST3 files should already be where they need to be. The VST3 spec added a common global VST3 folder to ease the confusion that can happen with VST2 plugins that do not have a common shared folder among vendors. All .VST3 files install to C:\Program Files\Common Files\VST3. The VST 2 .dll files need to install to their separate common folder (the default for CbB being C:\program files\cakewalk\vstplugins). If your VST2 .dll files are located in the VST3 common folder, you should reinstall those and set them to a common path for VST 2 plugins (that's not inside the VST3 folder).
  6. @scook I just ran a sanity check install with EZ Drummer, and it looks like their installer has logic to determine what a system's global VST2 folder is set to. On a setup that only has CbB installed, it automatically populated C:\program files\Cakewalk\vstplugins\Toontrack as the default install path.
  7. Both issues are logged. Thanks.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...