msmcleod

Select what you want to copy, set the now time.... press CTRL + D .

Try pressing F11 - it toggles whether the title bar is shown or not.

I guess it's because I'm still tied to my old 8-Track workflow, but I quite often go for destructive editing as for me tidying up as I go along makes life easier for me - i.e. a lower track count is easier to manage. If I really need to keep the originals, I'll just archive the original tracks and hide them... but I rarely go back to them. I do use instrument sub-buses though... in fact, in more complicated projects I may have several. For example, I might have a single lead vocal track, but have it send to 2 or 3 different buses that in turn are sent to a main vocal bus (e.g. a Vocal Verse Bus and Vocal Chorus Bus... both of them go to the Vocals bus ). I'll use automation to control the bus send to the sub-buses at the appropriate parts of the song. For the most part though, I can get away with going direct to a single lead vocal bus. All I'm really doing here is using the sub-buses as different effects racks. But having my vocal in the one track for me makes things easier to see visually. The other reason why I do this is because I tend to use the track Pro Channel/FX bin for sound design, and put any mixing EQ / FX in the buses. Back in the old days, I'd have recorded the track with some compression & EQ (and obviously any analog magic) already on there. So using the track PC/FX is getting my track to sound how I would have recorded it if I hadn't gone DI into my audio interface. This keeps it separate from the mixing phase, where I'll go to the buses to add any EQ or FX needed to get my "in the mix" sound. At final mix-down I pretty much stick to riding the "main" bus faders, which I try to limit to around 8 so I can record my automation rides with my MCU.

Wouldn't it be almost as easy to just switch to the draw tool ? Pressing F9 will select the draw tool... from then on you can use F5 to toggle between the smart tool and the draw tool. Alternatively, you could use "T" to bring up the pop-up HUD tool menu.

Icon says, "Mackie control built-in for Cubase, Nuendo, Samplitude, Logic Pro and Abelton Live". As it does not mention SONAR or Cakewalk, there's a good chance none of the buttons will work properly. The transport controls, faders, vpots, Mute/Solo/Record/Select, and the display should work though. The reason for this, is that Mackie reached out to all the major DAW companies at the time they brought out the MCU and asked them how they wanted their buttons mapped. They then shipped the Mackie with lexan overlays for each DAW. So the button layout for, say, Cubase is completely different from the button layout for SONAR/Cakewalk. As a result, whichever DAW mode you choose when using Mackie mode will result in most of the buttons doing the wrong thing. Ones I know definitely do work are: Mackie MCU / MCU Pro Presonus FaderPort 8/16 Behringer BCF2000 (discontinued) Korg nanoKONTROL 2 / Korg nanoKONTROL Studio I believe the Behringer X-Touch can work, but may need a custom overlay to show the correct button mappings. There may be others, but as I said, check that they definitely support SONAR or Cakewalk. In saying that, you may be able to get it working using AZController - @azslow3 may be able to help here.

IIRC Lyrics in SONAR/Cakewalk are primarily used for those wanting to create Karaoke tracks. Personally, for lyrics I either use either the Notes tab or MNotepad by MeldaProduction. MNotepad has the advantage of having its scrollbar automatable... so if it's docked to the multidock, and you've automated the scrollbar position, it'll jump to show the correct lyrics as you move the now time.

Apologies if this is already here... I did a quick scan through and couldn't find it. This is a surprisingly good sounding free ( donationware - but optional ) drum VSTi: https://www.powerdrumkit.com/ There's only one kit of drum sounds, but the sounds that are there are VERY useable, and there's some other sounds not shown in the UI (e.g. cymbals / levels of hi-hat openness) - just work your way up the keyboard to find them. It's got a built in mixer with control over volume/pan/compression, and can route to up to 8 separate outs. It also comes with a bunch of MIDI grooves too.

After months of about 10-15 attempts (to be honest, I've lost count) of trying to update my main Studio PC to Windows 2004, I finally managed to get it upgraded to Windows 20H2. For months I've been getting a consistent BSOD on the second boot with a KERNEL SECURITY CHECK FAILURE, followed by a failed recovery and then it reverting back to 1909. The weird thing, is that I've got a Win 10 install (which I use for development) on another boot partition on the same machine that upgraded with no problems a few months ago. The two partitions are pretty similar: apart from the dev tools, both have more or less the same software on there. Anyhow, I downloaded NirSoft's DriverView, ran it on both installs, and did a comparison between the two. Turns out the culprit was KORGUM64.SYS - Korg's USB MIDI driver (which is used by the nano series). Given that I use this on both boot partitions, it would seem this driver isn't actually needed in normal use - just the Korg editors need it. Just uninstalling this didn't work, but manually renaming it to KORGUM64.sys.bak and rebooting did. The other suspect driver was NIWinCDEmu.sys which is used by NativeAccess, or at least it was at one point (it's not present on my dev boot, even though NativeAccess is). I renamed this to NIWinCDEmu.sys.bak, although the Windows upgrade promptly put it back after the upgrade. So the moral of the story: If you can't upgrade to Windows 2004... check your drivers!

Neither of these two observations is any different to SONAR Platinum from what I can see. 1. Inputs - if you want to specify a more granular input setting, use the presets. 2. If "Always Echo Current MIDI Track" is enabled in preferences, it always swaps to Omni on the active MIDI track if the input is set to None. Both of these from what I can see are behaving as they were designed.... in fact I've just checked in SONAR X2, and it's absolutely no different.

Personally, I don't use it a lot... but here's the scenario I do use it in. Say I've got an un-quantised MIDI recording, or an audio recording that is in no way snapped to anything. For arguments sake, lets say the start of the clip is 1:04:527. If I want to move it by 1 bar, I'll set snap to be Whole and set it to snap by. Moving it to the next bar gives a start time of 2:04:527. If I'd used snap to, the start time would be 3:01:000.

As to why... I really can't add much more to what @Creative Sauce says about it. The whole first half of his video is on why you might need them. Obviously if the VST's you use don't support any sort of key-switching, then you probably don't have a need for them. Both videos cover how to create your own maps.

@Creative Sauce's and @Xel Ohh video's pretty much cover 90% of it. Is there anything specific you're unsure about? https://youtu.be/8miZoWXxz3Q https://youtu.be/owkYPMuhcQo

@Herve Maratrey - what you might want to try, is forcing Cakewalk to use your integrated graphics rather than your NVIDIA and see if this improves things. I've had to do this with my laptop, due to incompatibilities with some plugins. You should be able to do this from your NVIDIA control panel:

Can you PM me a copy of your project ? - I can't reproduce any crash or hang.

It shouldn't be... the only condition for keyswitches being in the same clip is when the articulation generates more than one event (e.g. CC n 127 at start, CC n 0 at end) . In this case, both events need to be in the same clip. It any case, it shouldn't crash or hang. We'll look into it.