msmcleod

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!

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.

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

@Jeremy Murray-Wakefield - The time line scale is always displayed in musical time. Even though you can display tempo entries as SMTPE time, the tempo entries are actually always stored in musical time. The tempo itself, directly affects SMPTE time - in fact SMPTE times and sample times are actually calculated from the tempo map. As MIDI notes are musical time based, MIDI clips will change size with the timeline as the tempo changes. So a 4 measure MIDI clip remains a 4 measure MIDI clip regardless of tempo. As audio clips are absolute time based, they will change size as the effective time in absolute time changes for each measure. So, as an example if you record an clip that is 4 seconds long. At 120 bpm, this will be shown as a exactly 2 measures long in the timeline. At 60bpm, it will be shown as exactly 1 measure long.

Most probably a VST that hasn't been authorised. Quite a few VST's emit periodic white noise once their trial period has ended.

@Craig Thiem - can you PM me one of your projects that has this issue? Also, can you confirm which version of Cakewalk you're using, and whether it's a bounce or export you're doing.

This is certainly not new to 2021.12. I can get it in SONAR X2, SONAR X3, SONAR Platinum and CbB: 1. Open the PRV 2. Make the main window floating 3. Undock the PRV 4. Lock the PRV View 5. Set PRV to "Disable Floating" 6. Make the PRV full size. Here it is in X2:

No, it's the locked view indicator - see : http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=WindowManagement.05.html Locked views are particularly useful for things like the PRV, as it means you can have multiple PRV's open with each one locked to a particular track.

This is because the images are stored on a non-secure server, whereas the rest of the site is being served up from a secure server. Either: 1. Change the start of the website address to http:// instead of https:// or 2. Set your browser to allow mixed content for cakewalk.com

You can assign a keyboard shortcut to CAL scripts within Preferences -> Keyboard Shortcuts

Export presets don't save the file location because they are global presets of the export settings - in other words they store the source type and format settings, but not any project specific information like specific tracks/buses and location. The Export Tasks however, do store all of this information. So the way to do it is to create an export task in each of your album's projects set to your album location.

1. Select the Clip 2. Process -> Apply Effect -> Reverse

This is my go to method for moving stuff along, especially with larger or more complex projects. Comparitively speaking, from a code point of view, the implementation is very simple and therfore much quicker than moving sections or using ripple edit.

What's your dim solo level set to? The lowest level is -18db, which might be too quiet to hear depending on the project. You can change the level in Preferences- > Audio -> Driver Settings -> Dim Solo Gain:

Yes to both questions. 2021.12 Build 91 and above will try to divide the 5 button image into 8, and end up showing a garbage image.

That I'm not sure about, as its a change to an existing image - no new image resources have been added.

Aha - forgot about that one - cheers @scook !

The only advantage I can see with VCA faders vs CbB grouping is that with VCA faders, you can adjust the other tracks independently from the VCA fader. In CbB to do this, you need to first remove the fader from the group, make the adjustment, then add it back. E.g.: Yes, this can be a pain, but I normally get around this by grouping the automation R/W buttons too. This way I don't forget!

My old location recording rig was running on an old laptop with a 1280 x 1024 screen. I used a combination of @Colin Nicholls suggestion and screensets, e.g: ScreenSet 1: No browser, No track inspector, track view fully maximised ScreenSet 2: No browser, Half width track inspector, console fully maximized with narrow strips ScreenSet 3: No browser, Half width track inspector, track view fully maximized For screensets 1 & 3, I used custom control manager settings to minimise widgets available.

Just a heads up... any custom themes will need the Archive button updated to work with CbB 2021.12 EA (build 91 / 93). It's now a tri-state button similar to the mute button (i.e. 8 images), in order for folders to indicate that some of the tracks are archived. Old Button: New Button: