Jonathan Sasor

As @scook mentioned, if you don't see the Event List, you're likely in a Workspace. Switch to the Advanced or "None" workspaces and you'll see the Event List available. As for the export, Cakewalk renders based on selection. Simple way to adjust the end time of the project is to simply hold Shift and click the time ruler where you want the export to end. Then go to File | Export -> Audio.

We recommend that users who had previous versions of SONAR install that and its related content first, then install Cakewalk by Bandlab. Then you'll have access to all your previous content in the latest version of the app. SONAR Platinum/Professional/Artist can still be downloaded and installed via Cakewalk Command Center.

@e2studio How consistently are you seeing this? Is it specific to this project? If so can you upload us a copy of the project file?

You can also go to the Clip Properties in the Inspector and adjust the start time for the clip which displays in Measures : Beats : Ticks.

While you were recording, you were likely using direct monitoring through your interface rather than monitoring the audio that's actually going to the track (via the input echo button on the track). As mentioned, microphones are a mono source, you just need to make sure you set the input on the track to be the proper input for the microphone. Cakewalk groups your audio drivers as stereo pairs, so choose the appropriate left or right input on the track, then it will play back as expected.

Everything should be back in order now. There were some server side issues with delivering the installers have now been resolved.

I did some checking and noticed that I was on v1.0.0 for Cassette Transport. The one you can download now is v1.0.3, and that seems to fix the problem.

I can understand your point, but at the moment this is how Input Echo is designed because the track states are always saved as part of the project, and if Input Echo were to be turned off, it would cause Aux Tracks to stop working as you mentioned. Also it's a common use case to have monitoring kept if you're working on a project and want to pick back up where you left off.

Region FX utilize Celemony's ARA format where the host (Cakewalk) can pass the audio directly to Melodyne (or other ARA plugs). This is by far the preferred method for using Melodyne with Cakewalk, and we work closely with Celemony to provide the best possible experience in Cakewalk when using Melodyne.

If you're intent on always using a singular snap setting, I'd suggest turning off Smart Grid (which dynamically sets the snap value), then save the project as a template so every new project created will persist that. Otherwise it's a matter of saving it per project, but if you start with your own template, you can just roll with it moving forward.

A little more detail would be required to give you a specific answer. If you're trying to simple record MIDI mod wheel message, then as mentioned you can just make sure your MIDI device is enabled in Options | MIDI Devices, then you would simply arm and record on the MIDI track that you wanted to add the modulation too. If you're trying to add modulation in the form of an audio effect, then you'd be adding a plugin to the FX bin and doing plugin automation if required.

Import is already fixed and will be in the final 2020.05 release.

There's an option in the Preferences to Hide Related VST2 plugins, if you want to see both the VST2 and VST3 versions, make sure that's unchecked.

This crash doesn't seem to be 2020.05 specific, but I can repro it. We'll investigate if it's an issue on our side or Wavesfactory's.

We have a number of Surface Pros in house and test on them regularly. You can find details on the multitouch support here: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Multitouch.html

As others have said, it's really up to you. You can put a compressor anywhere really. They're all different color crayons in the box, its up to you to make something with them. Some people put them on master buses, some people don't. Personally, I tend to just run a clean limiter on the master bus, but that's just what works for me. Try different ones. See what you like. To borrow a tagline, "if it sounds good, it is good".

Offline auth is coming with the next set of updates for CbB and BA: That should be totally unrelated to the issue with the audio device though. It's possible something with Windows updates created a problem, but Cakewalk is just going to check for what the available drivers on the machine are. I'm not that familiar with that particular device, but if it has multiple outputs (many class compliant devices are simply stereo) it should show those. It's possible they might need to try a different driver mode if that works any better.

That's relative to where you save. By default, the path for all of your projects is C:\Cakewalk Projects. You can simply copy this directory to an external drive (or upload to cloud storage) and then bring it right back on the new install.

There's 2 ways to monitor single going into Cakewalk (or any host). Direct monitor and (in the case of Cakewalk) Input Echo monitoring. The difference being Direct Monitoring is done directly through your interface and is your dry signal before it goes to the PC. If you're not direct monitoring, when you open a project in Cakewalk, you need to turn on the Input Echo button on a track before any audio passes through it. Input Echo is your signal after it goes through the track/audio engine. This will be affected by any plugins that are there. If you turn the Input Echo button off, and you still hear your dry guitar signal, that means you've got direct monitoring turned on on your interface, either via a control on the hardware or through a software mixer panel that's part of the driver. If you hear no audio from your guitar before you turn on input echo, then you still hear some dry guitar when you have an amp sim turned on, then it's something with how you have the signal routed in your project.

Your projects will retain all their settings as those are all kept internally within the project file, you just need to make sure you have all the same plugins installed. If you're using custom presets, you'll want to export those, and that will depend on what plugin and how you save them. When you're on the new system, you'll probably want to install SONAR Platinum and all of it's plugin content to have first, then install Cakewalk by BandLab after so you can keep using all of the extra included content there (as well as any other 3rd party plugins you're using).

This is by design with ASIO, it exclusively uses a single device driver at a time. You'd either need to connect the audio outs of the TD-50 to the Focusrite or use the Roland for both playback and recording. You just need to deselect everything from input and output drivers in the Preferences to switch between ASIO devices.

@Percy Ferry In your screenshots, you don't actually have an "Arrangement" per the feature design. The general workflow is that you have your sections in the top half of the Inspector, but then you add those to the Arrangements pane in the bottom section. This is where you can preview or export different Arrangements from the picker in the Inspector. The Sections pane at the top will list you the Sections currently in your project, and you can reorder and preview those sections from there, but it's not an "Arrangement". If you have a project file where all of the different Sections in an Arrangement export at once, you can send that to us and we'll take a look at it.

Can you provide a screenshot about the problem you're having?

It's likely that you didn't install EZ Drummer into the default location that Cakewalk scans for VST plugins (C:program files\cakewalk\vstplugins). You'll need to find the path where the .dll file for EZ Drummer did install to, then add that path to the VST Settings tab of the Preferences in Cakewalk. Check for places like C:\program files\steinberg\vst plugins or C:\program files\vstplugins or C:\program files\common files\vst2. Just be sure not to add something like "C:\" to the scan path because it'll hit a lot of things that .dll files, but not plugins and cause your scan to be slow and have problems.

Are you on the most recent update? The behavior for this has changed in 2020.04.