msmcleod

If you hold down CTRL + SHIFT while dragging the clips on to the track, they'll be put on the same track one after another.

I wasn't giving guidance, I was answering a specific question. I'd have thought that after buying a piece of equipment you'd at least read the user guide that came with it. And if you'd bothered to read the Cakewalk user guide, you'd have found the answer I posted as well.

I can confirm that. It uses heaps of CPU in every DAW I've tried it in. Scheps OmniChannel is pretty light in comparison, as is the Waves SSL Channel / SSL G Channel.

@Pitarch - this is most likely something specific to your project. We'd need to try to reproduce the issue using your project file. Can you zip up the folder your project is in, and send it to @Jonathan Sasor along with details of exactly what you're copying / pasting?

I've not come across this function, but they way I'd envisage it would work would be: 1. Take a list of all the notes that are still on at the time CC64 is switched to > 0 2. Now add all the notes are are on before the time CC64 is switched back to 0 3. Extend the duration of all of the notes above so that it matches the time that CC64 is switched back to 0, but only if their duration ended before that time. 4. Remove the CC64's. Obviously it'll need to cope with multiple CC64's throughout the track. I can't see this being a huge advantage for cutting down MIDI data as CC64 messages are only 2 bytes long. Assuming you're only ever transmitting on a single MIDI channel I guess it could interrupt the state of running status, requiring a re-transmission of the first byte of a Note On event immediately after the CC64, but even then that's just an extra byte. If you're transmitting on more than one MIDI channel for that port, it'll likely not affect running status at all. Also, it'll likely make your notes look like a complete mess in the PRV.

They should already have received that info from Mackie when they got the SDK from them. The button layout is as follows ( taken from https://www.loudtechnologies.eu/shop/data/articles/images/zoom/m_3375.jpg?version=Z24we9Yi - Loud Technologies is the Mackie subsidiary that wrote the control surface firmware )

On the nanoKONTROL 2, you can use the Cycle button as a shift button: Hold down Cycle then press Track " > " to switch to buses Hold down Cycle then press Track " < " to switch back to tracks FYI - all of the shortcuts are as follows:

When Mackie first brought out the MCU, they asked all the major DAW companies at the time to provide button mappings. Cakewalk provided Mackie with mappings for SONAR, and Mackie shipped overlays for all the DAW's with the MCU. The basic transport controls, faders and v-pots are standard across all the DAWs, but all of the other buttons vary between DAWs. When other control surface manufacturers provided emulation for Mackie, they had different modes for each DAW in order to match each DAW's button layout. So unless they specifically mention they support Cakewalk/SONAR, they won't have the correct button mappings. Furthermore, it's not just a matter of re-mapping within Cakewalk - the control surfaces themselves assume a particular state when a button is pressed ( this is due to these surfaces having far fewer buttons / controls than the original MCU ). I'm unsure why some manufacturers have decided not to include Cakewalk/SONAR mappings, but they've obviously made a conscious decision not to include them. I suggest contacting StudioLogic and ask why they don't have Cakewalk/SONAR mappings, and if they could add them.

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.

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

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.