msmcleod

@Jun Kwan , @Milton Sica - did you manage to resolve your VST scanning issues? If not, please PM me so I can try to help resolve the issue.

Normally with gain staging you use track gain (and this is certainly what Mike is using in his video). Track gain is not the same as clip gain. Clip gain is applied first, then it goes into the track gain.

I've been through that pain... took me around 4 days if I remember correctly. The last time I did it, I made a clone image of the disk partition, which has saved me no end of problems. I've had a few hardware failures that have caused the OS to die on me, and being able to restore saved me loads of time. I strongly recommend backing up your disk once you've got everything installed.

There's a huge difference between installing Visual Studio and installing the Visual Studio redistributable libraries. It's the redistributable libraries you need. Installing an earlier version of the redistributables (e.g. VS2015 , when the current OS has VS2017 ) does not overwrite the current VS2017 redists. It just adds them so both versions are then available. You may find however that by installing Sonar, it installs the required libraries in any case. If you're trying to call regsvr32 on a 32 bit plugin though, that isn't going to work at all in a 64 bit OS.

This is the key statement. Anything your create yourself using Cakewalk by BandLab is yours.

In the next release, the staff view will respect the global snap setting for note positioning. The note duration settings will remain unchanged. In other words, you'll be able to independently set the note duration and the snap positioning.

Just to let you know, we've got a fix and it'll be available in the next release.

It's shown in the installer. This is what it is currently:

@Alastair Cardwell - a couple of questions: 1. Is your MIDI mode set to UWP or MME (I've found MME to be far more reliable with some devices, especially older ones) ? 2. Have you tried disabling "Zero Controllers When Play Stops" ? Maybe Cakewalk is flooding your control surface on startup with reset messages, causing it to hang up.

Just to clarify the possible issues with freezing Region FX like Melodyne.... When a track is frozen, Melodyne's state is saved to a subdirectory within your project's directory. For the most part this is fine, but should you update/upgrade Melodyne at some point, there's no guarantee that it will reload the state successfully when you unfreeze. If I want to keep my original audio track, what I do is: Freeze the track with Melodyne on it CTRL + SHIFT + drag the audio to a new audio track Unfreeze the track with Melodyne on it Remove the region fx Archive the original track Doing this ensures there's no Melodyne instance data saved with my project, and I'm free to create a new region fx with whatever version of Melodyne I may have in the future. Normal VST effects and VSTi synths don't have this problem as the way they store their parameters is very different.

Thanks @scook - I can repro, and have got a fix. It'll be in the next version. In the meantime, there's a workaround: 1. Before deleting the effects, remove all the automation lanes for the effect you're deleting (note just remove the lanes - don't delete the envelopes). 2. Delete the effect. 3. While holding down SHIFT, left click to open, close then re-open the lanes again - the automation lanes should re-appear.

@Gaston Arevalo / @scook .... Hmm - just tried it myself. Although the automation lanes are reset (in a similar way to split instrument track/make instrument track), the envelopes are still there. If you shift + left click on the automation lanes do they come back?

I've used these to strap my sticks on.... I was pretty impressed with them:

I definitely see it being less responsive, but it's still responding ok for me. You might want to consider hitting the scroll-lock button to stop the clip view from scrolling (you'll not get anything useful out of it when zoomed max in any case). You'll find the lack of responsiveness completely disappears.

lol - none in particular, just general handling

1. When you set your return inputs on the external insert, they're "used up" by the external effect chain, so you can't use them as an input on another track. You could create a send to an aux track though, which would achieve the same result. 2. To measure latency, you need to have a signal going through and then click the Delay Measurement box (where it says *0ms, 0 samples). It's best to have your external effect on bypass to ensure accurate measurement. More info here: https://www.cakewalk.com/Documentation?help=Mixing.32.html&language=3&product=SONAR X2

No, I think it's been like this for a while. We've been looking at some control surface issues which has put more focus on it.

@Adam Grossman - thanks for highlighting this - we'll look into it.

@jono grant - can you post a screen shot ?

We're currently looking into these issues. From what I've noticed so far there's a few issues: Cakewalk isn't always getting connection/disconnection notifications from Windows. Interestingly though, if Windows Device Manager is running at the time, the notifications are received instantly. Not all users are seeing this issue though. If you re-connect a MIDI devices while Cakewalk is running (and Cakewalk does actually get notified about it). Cakewalk doesn't enable it- it leaves it unchecked. Related to (2) - if you go into preferences and change anything. in any page, the MIDI preferences are overwritten meaning that your unchecked devices are saved as unchecked. Until we sort the issues out, there are a few things you can do in the meantime: Always use the same USB ports for MIDI devices, and always plug in your devices before you start Cakewalk If possible, make sure they're plugged in before starting your PC so they're always assigned same device ID by Windows. If you have a stable MIDI setup you want to keep, consider making TTSSEQ.INI read-only. This will prevent Cakewalk from overwriting it. Make sure USB sleep is disabled in your power options.

My laptop gives me the choice of using its NVIDIA graphics card, or the onboard Intel graphics adapter. Due to problems with some plugins, I've set Cakewalk to only use the Intel graphics adapter. In theory the NVIDIA should give better performance, but I've found the Intel to be far slicker within Cakewalk. Also given that most plugins will only use the 2D features of OpenGL, I doubt if using a separate graphics card gives you any real benefit.

The difference here is that each Matrix cell contains a single audio or MIDI clip, then records the results of playing all your cells to an audio track. An arranger section however, is a vertical strip of multiple tracks. I guess the only way this could work, would be to bounce down the arranger section as single audio clip first, then it could be used as any other audio clip in the matrix. You can kind of do this already, by creating a separate arrangement for each section (i.e. arrangement 1 only contains section 1, arrangement 2 only contains section 2 etc), then exporting all the arrangements.... then you can drag them into a matrix cell. I take your point though - it would be good to make this more integrated.

@spiffo - the link still works fine for me, but you shouldn't need to use my version any more. The standard Cakewalk MackieControl dll now contains all of the enhancements in the MMcL version, so I'd advise just going with Cakewalk's one.

I couldn't see any issues either. I did notice that both AmpleSound guitars weren't there tho, which were listed in your original screenshot:

Wow - this works a treat if you dock the plugin in the multi-dock.