Jonathan Sasor

4 minutes ago, JM2 said:

EA2 Version: 2020.04 (Build 164,64bit)
Lang Japanese: no 3 menus 
Create Secion from Selection|Markers|Sections
I can't do this 3 functions.

2020.04 is not fully localized yet, which is why it's missing in Japanese. These options will be there in the final public release. 

3 hours ago, Mark Withers said:

The latter is true.  It doesn't show up in the control surface setup list . It does show up in the  midi though.

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.

3 hours ago, JM2 said:

Event view key Ctrl+Alt+Space

2020.01 event list. Ctrl+Alt+Space to play one next note. 

EA1 Ctrl+Alt+Space doesn't work. 

then 2020.01 Rollback installer. now 2020.01 and it works.
I will test EA2 at other PC for easy to check 2020.01 and EAn.

why you changed s-key and no notice? or just a bug?
there is no info at EA1 EA2.

in EA1 
perf /shortcut key /area evetlist view / not same as 2020.01

my edit work speed get very slow.
if keys confrict, (key for Arranger, 
please keep all function with other keys.

any combo key in windows system I can setup.

Here is my set up with external macro system.
// key C-P        = Enter NumPlusSign    Enter C-A-Space Up Down        # Enter + Enter 音だし Up Down
// key C-O        = Enter NumHyphenMinus Enter C-A-Space Up Down        # Enter - Enter 音だし Up Down

Ctrol-P to play + note and sound play
Ctrol-O to play - note and sound play

and Ctrol-Sapce to Ctrl+Alt+Space with external keymacro
// # 1180914 21:38:18    Cakewalk Ctrl+Alt+Space CW Event Listで 音をならす これを Ctrl+Spaceに
//#    左が押す元のキー
//# key C-Space = C-A- Space         # Ctrl+Space -> Ctrl+Alt+Space
//#    1180914 21:46:14    逆も一応いれる。
//p# key C-A-Space = C-Space         # Ctrl+Alt+Space -> Ctrl+Space
 

2020.04 builds have Ctrl + Alt + Space bound to Preview Play Arrangement From Now Time as a Global Binding. This is overriding your existing binding which is view-specific to the Event List. If you unbind the global one the Preferences, it should return to the 2020.01 behavior. 

7 minutes ago, GreenLight said:

When working on tight deadline, I'd recommend staying away from EA's to begin with.

In fact, I'd say that most studio people don't upgrade at all during deadlines... I lagged 3-4 Cakewalk releases behind during an intense period, where stability was priority #1.

It's worth checking out (or at least reading the release notes) as we go through updates. We're certainly striving to increase stability with updates.

Maybe if you've got a deadline "on Monday" you might want to hold off, but if you've got a couple months to go, it could be worth it to check out an EA. Maybe we fixed something that's been bugging you, or optimized performance on something. I actually used the early iterations of the Arranger to help write a song on a record I put out last month. 

The rollback is simply there just in case. 

1 hour ago, Jan said:

Ah, I see, so assuming there'd be a 2020.03, 2020.05 - 2020.05 would let me rollback to 2020.03, then from 2020.03 I'd be able to rollback to 2020.01, correct?

If you kept the previous releases' rollbacks, then this would theoretically work. There might be some minor differences related to content (presets and the like) by successively rolling back than if you had never installed the later updates, but the actual Cakewalk app will work per that given update after rolling back. The primary goal of having a rollback installer is that if we release an Early Access or other update that if you run into a blocking issue, there's a simple way to go back until we've been able to address the issue. In general we recommend sticking with the current version though. 👍

2 hours ago, Fabio said:

Bugs I found so far in the inspector view as attached.

This looks like you're using a custom theme. User themes will need to be updated to work with 2020.04.

1 minute ago, Keni said:

Okay... No one else seeing this? This is starting to drive me crazy!

Was this intentional? It does appear that in PRV, ctrl-scroll-wheel is now scrolling in the opposite direction. Yes I posted it above but it seems no one else picking up on it? Is it me? Have my muscle memory tools reversed???

The CTRL + wheel scroll direction got reversed as a side effect of another change. It's logged and on the list to fix before the final 2020.04 release

UPDATE: If you're not seeing the presets, the link for the EA installer has been updated on the original post. You can run the rollback installer, then grab the updated Early Access installer. 

14 hours ago, scook said:

 

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

15 hours ago, Kurre said:

The reason i'm negative to win 10 is multitude.

Expand your thinking.

With CakewalkbyBandlab, which i like. is this movement towards an extremely small niche for a daw.

A daw that is to be not solely windows only, but windows with the version 10 only.

PS. To give back something positive i propose to the developers:

Fork the software.

Release todays version of CbB as free software. Remove the update and authentication from it and give it a slightly other name. Copy Reapers way with a notification in the center when started. But have it to be manually exited so people can take their own time to read it carefully.

The notification should state that it is released as is and are never going to be updated or supported. If they want updates and support they have to use CbB instead.

In that way you can continue to develop CbB as usual and still have win 7 and 8.1 users contribute to the community.

PPS. Music hardware seems to be of good quality. Folks take them out from their storage and fire them up without a problem 30 years later. People like that nowadays, reuse things and not throwing them away. But you need the old software to still be around to be able to use lot of the old hardware.

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.

23 minutes ago, GreenLight said:

Considering the recent relative silence from Bandlab, I just wanna double-check that development of my favorite DAW is still ongoing? (If it was a paid product I wouldn't worry as much, but the future of a free product just seems a little less certain, that's all.)

Stay safe and keep on truckin' everyone! 🚚😎

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

3 hours ago, winkpain said:

1. the uninstaller will remove all the bundled content (synths and such) that came with Sonar (that is also in a custom location)?
2. these will be re-installed with the re-installation of Sonar if I wish?
3. and wanting to continue to have access to this bundled content is really the only reason to re-install Sonar in the first place, or are there other reasons?

My plugins: These are all in a custom location on a non C drive. Can I leave them installed there? Is there a reason why this should be an issue as long as I point Sonar and CbB to these custom folders ?

And a general question about VSTs installations, if I need to re-install those as well:  Is there any reason at this point, on a 64bit system running 64bit CbB(and other programs), to install  both 32bit and 64bit versions (if two are offered)  of the same plugin, or both VST2 and VST3 versions??

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.

1 minute ago, abacab said:

Just curious, but where are those 3 PC modules in question stored on the computer, and which installer puts them there? I think I need to re-install them.

I just noticed I am completely missing them, and have had Sonar Platinum installed since before I installed Cakewalk by BandLab. Just checked Sonar, and they are missing from there as well. Command Center indicates that everything for Sonar is already installed.

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. 

4 minutes ago, winkpain said:

Interesting. To be clear, though, the GUI issue is there with all three mentioned modules when installed individually as well.

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.

18 hours ago, winkpain said:

More GUI weirdness

Similar to my above mentioned Saturation module issue, I've now found these two ProChannel console compressor modules to display oddly:

 

What gives??

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.

13 hours ago, Freyja Grimaude-Valens said:

Has anyone tried running this on Windows 7? What's the verdict on that?

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.

1 minute ago, Terry Kelley said:

So can we add a path to .VST3 files in another folder?

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

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

2 hours ago, Zirrex said:

Tracks (channels) are not added to the folder.  

49 minutes ago, craigr68 said:

"The following files were either unreadable by CWAF, or written by a newer version of SONAR than CWAF expects."

Both issues are logged. Thanks.

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. 

2 hours ago, Neil McGrail said:

Just to close the loop on this thread;

Installing Sonar XL did not solve the problem  (I was unable to install Sonar 3 in Win 10).

Running the installer v1.0.0.4 worked like a charm for both the VS-20 Control Surface AND the embedded COSM effects within the V-Studio hardware!  

Many thanks  for the help  @chuckebaby !!! 

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. 

52 minutes ago, Rod L. Short said:

In File >Audio Data what should the Render Bit Depth setting be set at? Mine is at 32 bit. Should it be at 64 bit?

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. 

1 hour ago, marled said:

Since the introduction of the automatic subfolder logic it happens to me from time to time that I end up with a folder constellation that I have not intended! 😡

Although I get more and more used to this 'special' logic with an automatic project folder with the same name as the project. IMO this is not really a good idea, because in any other program out there it is different and second, it makes it impossible to save a project with a changed name in the same or another folder (in such a case you have to save and then copy manually, crazy)! Just to make it clear I do not mind the automatic audio folder name, I don't care about that!

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. 

16 hours ago, Scott Reams said:

I'm finding that when I use Save As (might also be the case with Save), Cakewalk is always saving my project in a Folder with the same name as the project file (under the current folder), and saving it's audio in a subfolder under that. No matter what I type in "Project Path" or "Audio Path" at the bottom of the dialog, it is ignored. I never used to have this issue... although I don't know how long ago it started.

Here's a capture of the problem in action. Pretty easy to replicate:
 

 

 

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. 

16 hours ago, Alan said:

The rewriting of the drivers in windows 10 goes beyond my comfort zone and skill level.

 

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.