Jonathan Sasor

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?

If a minidump is not being generated automatically, you can create one in Windows. Details on this can be found here: https://www.cakewalk.com/Support/Knowledge-Base/2007013262/How-to-collect-a-Minidump-file-when-your-Cakewalk-program-crashes

"w" will do that behavior now

If you exit and reopen BandLab Assistant, do you still see the app in Demo Mode?

SONAR 8.5 variants predate VST3 support, so you need to make sure anything installed for it is a VST2. On a 64-bit system, the stock scan path for Cakewalk/SONAR is C:\program files (x86)\cakewalk\vstplugins on a 64-bit OS or C:\program files\cakwealk\vstplugins on a 32-bit OS. As Craig mentioned you can pick similar paths from the plugin installers, but you need to make sure Cakewalk/SONAR scans those. VST3 uses a common path in the specification, so they all go C:\Program Files\Common Files\VST3

Do you have a project where this is reproducible? We have not seen this issue on our end, but if you have a project where we can verify, then we can work on a fix.

Hi Max, Unfortunately this is a known issue with aux tracks and track templates. It's logged in our system and will be addressed as soon as resources allow. Thanks!

You can uninstall your current build and reinstall the 2019.07 release build from BandLab Assistant to grab the update (all of your settings will persist okay).

@Hapsiainen, PM me with your Serial Number for Dimension and I can pull your registration and make sure that you've got the latest version that you'll be able to download.

The files in AppData will get automatically copied from the C:\ProgramData\Cakewalk if they're moved/deleted from your existing AppData folder. You can clear AppData\Roaming\cakewalk\Cakewalk Core\Help Module and when you open CbB, they'll get updated.

If you check the files in C:\Users\your user name\AppData\Roaming\Cakewalk\Cakewalk Core\Help Module, what is the date modified for the file HelpText_EN.dat? The change for 2019.07 is not to show the ProChannel, but rather if you're on the Inspector, you'll get Help Module info for the EQ plot as shown above the FX Rack.

Yeah, we'd definitely recommend going line out from the amp rather than trying to use 2 USB devices like that. ASIO4ALL doesn't have any way for the devices to clock together.

@Jaime Ramírez @Blades, What version of Windows are you running?

You've simply increased the vertical zoom in the PRV. There's the little magnifying glass buttons in the bottom right corner, or if the PRV has focus you can use CTRL + Up/Down Arrow keys to adjust it.

I mean, there's no right answer to this kind of question. Both have their advantages or disadvantages, plus it'll be relative to which compressors or EQs you're using. As mentioned, shaping the bass before you hit the compressor is going to have a big impact on how the compressor reacts to the input, but maybe you want to tailor how the EQ sounds after the compressor too. Depends on the material and what you're going for. Most important thing is to train your ears. If you understand how your tools work, then you'll be better able to apply them as you see fit. Experiment, listen, learn how things play together, then adjust as needed!

As @scook was saying, it sounds like your audio device is not configured correctly. If you're using the stock integrated audio card that came with your computer, go to the Driver Settings tab of the Preferences, and see if your Driver Mode is set to WASAPI or not. Integrated audio cards will work best with either WASAPI or MME driver mode. If you're using a separate audio interface for playback, you'll want this set to ASIO instead to use the device's specific drivers.

It sounds like something is blocking the .dll files from being able to register in Windows. This wouldn't be specific to 2019.07 as the installer hasn't changed. Typically its a pending Windows update or possibly an antivirus interfering with the install. I'd double-check if you can force any additional Windows updates for sure, and if you keep having trouble, you can e-mail support for additional troubleshooting steps.

That's very dependent on everything else that is in your chain, particular on your master bus. If you're using a brick wall limiter to boost the level to -.3, that limiter is going to impact the sound more as you boost the signal going into it.

Hi Mariano, This issue is not new to the 2019.07 update, but is logged on our end. Thanks!