msmcleod

If you can find a solid recipe for reproducing for this, please let us know. [Edit] - it's ok, I've found one... got it fixed for the next release.

I think this is a limitation to how track templates currently work - i.e. they save the tracks in the selection, then if that track is in a folder it saves the folder too. Therefore in order to preserve the nested hierarchy, there needs to be track inside each folder - i.e. at least one track at every level. I'm sure this is something we can address in the next release.

They're stored in %APPDATA%\Cakewalk\Cakewalk Core\master.ins

I've rarely had to do this, but when I have, I've just: Inserted a new slower tempo 4 measures after the end of the project recorded what I needed to there moved the clip back to where I wanted it deleted the tempo entry at the end Either that, or just recorded it in separate project and copied/pasted it back. The tempo map itself cannot be bypassed, as literally all timing calculation within the engine depends on it.

@Jeremy Murray-Wakefield - what MIDI interface are you using? Another user was reporting stuck notes in normal playing through Cakewalk. As it turned out, it was the MIDI interface drivers. I could reproduce using this interface, but was fine using another :

Native Instruments are going through the process of releasing VST3 versions of all their plugins, which is why there have been so many updates recently. They seem to be releasing a new batch every week or two.

@dogufo - I can confirm the issue is with the MIDISport driver. How I came to this conclusion: The stuck notes also happen in SONAR Platinum, and they certainly never used to The MIDISport refuses to even appear as device within MixCraft or Reaper, and the device freezes on exit and needs unplugged/plugged back in Replacing the MIDISport with a MidiTech Midiface 8x8 solved the issue, with no stuck notes The MIDISport driver is now 8 years old, so it's not really surprising. Most manufacturers needed to update their drivers for Windows 10 2004 / Windows 10 20H1. For example, the Korg USB drivers stopped working when this update came out, and it took a month or two for them to issue a replacement. I've not had the chance to try it yet, but I suspect if I try the MIDISport in Windows 7 it'll be fine.

@dogufo - ok, I set up a similar rig as follows: Fatar MIDI Out -> MIDISport Ch 1 In SY77 MIDI Out -> MIDISport Ch 2 In SY77 MIDI In -> MIDISport Ch 2 Out SY77 L&R -> spare input channels on my audio interface In CbB, the MIDI inputs & outputs were enabled to match the three above - i.e. MIDISport In 1&2, and MIDISport 2 Out. On the SY77 I turned local off - this is important, as otherwise you'll get MIDI feedback. For the most part, everything worked as expected and I could record/playback in CbB. However, I did manage to reproduce the sticking notes. At this point, I'm not sure whether it's CbB, or it's the MIDISport drivers. There hasn't been any recent changes in CbB's MIDI behaviour, and the MIDISport drivers haven't been updated in a long time. That being said, Windows updates have been coming along regularly, and it's not uncommon for them to break stuff with MIDI - it's happened before a few times. I'll do a bit more investigation and get back to you. Thanks for reporting this.

IMO the Korg nanoKONTROL Studio is one of the best of the lower price hardware control surfaces. I use it daily in my office. The nanoKONTROL 2 is also very good. For motorized faders, Mackie MCU, Presonus FaderPort 8 or 16 and Behringer X-Touch are all good. The Icon series are good too, but you need to be careful to select a model that actually supports Cakewalk/SONAR.

Try the following: 1. Turning off Waveform outline drawing under Track View Menu, View->Display->Show Waveform Outlines 2. Either turn off "Display Clip Fade/Envelope attenuation" within Perferences->Customization->Display OR... Reduce the resolution of the envelope attenuation display by setting ClipGainWaveformAccuracy=4 within Preferences->File->Inititialization File. This controls how often the waveform envelope is "sampled" in order to reflect clip gain/pan automation in the waveform display. A value of 1 is the highest accuracy (more CPU), whereas a value of 8 is the lowest accuracy (less CPU). This doesn't affect playback, only the display.

FWIW - I almost exclusively use Crucial MX500's nowadays. They're the only SSD's that have never let me down.

Just to be clear - we're not considering any changes to the console view at present.

You have that already with Track Manager presets.

While this is possible, it does start getting very complicated. How do you properly display sub folders in a meaningful way? Also, how would it affect control surfaces?

The input looks fine, but looking at the MIDI output, you've almost certainly got a MIDI feedback loop going on here. What's more, it's echoing the program changes on all ports, although from the looks of it this could be how you've configured MIDIOX. The MIDI Port Routing window shows all ports connected to each other. You don't want any additional routing in MIDIOX - just the monitoring. It may be simpler to just take MIDIOX out of the equation. Luckily, I've got more or less the same gear as you... I've got a MIDI Sport 8x8, Fatar StudioLogic 990 and an SY77 lying around. I'll try to make time this evening to replicate your setup into a working system and let you know what the settings are.

@Alain Duchaine - As @Keni as pointed out, it seems the StudioMix control surface DLL's came as a part of a separate installer. Unfortunately, this installer won't work unless you have SONAR platinum installed. I'm not sure if there are other reasons for not bundling it with CbB other than it being a legacy device - I'll need to double check with the guys in the US. We certainly don't officially support it anymore though. I'll PM you with the details on how to manually install this.

Strange - I don't have issues with velocity on mine, although in general I find the hi-hats on most kits mixed too low, but this is a simple hi-hat volume thing not a velocity issue. You can adjust velocity curves on the nitro mesh. Maybe this will solve your issue. IIRC I couldn't find any way to change the output notes on the nitro mesh though. I actually use an Alesis DM5 along side it for extra cymbal pads, as before I bought the nitro mesh I had a DIY kit made out of a Remo practice kit and piezo transducers. On the DM5 everything is configurable, however there's no half hi-hat on that, just open/closed. It's fine for adding a few cymbals though ( note these are fed directly into CbB through another MIDI interface, and don't play the internal sounds on the nitro mesh). For the most part the nitro mesh is mapped to GM. The only exceptions are the half open hi-hat, and the hi-hat splash sound both of which can be tricky to get at first until you get comfortable with the hi-hat pedal. These are output as Note 23 ( half hi-hat ) and Note 21 (splash hi-hat).

I use the nitro mesh with AD2. I did the mapping in AD2 itself.

@Andres Medina - It never occurred to me to leave the recording checkbox unchecked! Good thinking!

@Lonnie Dawkins - we've found the cause of this and fixed it for the main release. The issue is actually at template save time. So once the main release is out, you'll need to re-save your template. The main release should be released some time later this week.

If you've not got a metronome bus, then it'll not sound. Also, the in-built metronome will play all the time through recording - not just at the count-in.

The only way to do this is to record your own click in the first measure, then start recording on measure 2. You can use SI Drum kit to provide the click, using the side stick sound.

You moved the track between track 17 and the track immediately above it, which is currently hidden due to it being in a collapsed folder. There's no way for Cakewalk to guess your intent here - did you mean below track 16, or above track 17 ? Hence the left/right gestures and the indicator.

The drag indicator indicated it was going to move it into a folder. This is because you had moved it to the right hand side. If you had moved it to the left half, it would have appeared directly above Track 17. Keep an eye on the left edge of the indicator - it shows the level at which the track will be placed.

Normally all you need to do is enable the meters in the Mackie Control Surface panel: I normally enable "Select highlights track", and set the Master Fader to bus 1 ( otherwise the master fader ends up only changing the left channel).