msmcleod

@Jeffrey - I've tried to mirror your options, and can't reproduce your issue. We've not heard reports from any other users regarding this either, so I suspect it's something local to your system. First of all, make sure you're using the latest build ( 170 ) : https://discuss.cakewalk.com/index.php?/topic/29141-cakewalk-202104-update-1-release-candidate-updated-to-build-170/ If you're still seeing the issue, could you PM me a copy of your Cakewalk.ini ( from the %APPDATA%\Cakewalk\Cakewalk Core folder), and also a registry export of: Computer\HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core Hopefully I can reproduce if I can match all your settings, then narrow it down to what is causing this. If you're unsure of how to do the registry export:

Have you got a MIDI feedback loop? It may be that the MT-power drum kit doesn't cope with that. I've got both the Nitro kit and the M-power VSTi - I'll give it a try this weekend and see how I get on.

Unless you've got a Komplete Kontrol hardware controller, I personally find very little use for Komplete Kontrol at all. IMO you're much better off just inserting Kontakt 6 directly as either a Simple Instrument Track, Per-Output Instrument Track (my personal preference), or a Split Instrument Track. The settings wrench @treesha is referring to is here (it's actually a gear icon, which may be the source of the confusion): You may also see it here: Disabling "Zero Controllers When Play Stops" is important however when using certain Kontakt libraries, as they've broken the MIDI rules and assigned the mod wheel to things like cut-off filter.

@Junichi Aoki - the latest 2021.04 Update 1 EA build (170) should solve all of your issues: While this isn't officially the final Update 1 build, unless we hear of any major issues over this weekend, it'll probably end up being released as the official release early next week.

It's strange that the Music Industry seems to be the only industry that has this bias against Windows. I've worked in a LOT of industries over the years - health, defence, hospitality, travel, retail, recruitment, law enforcement & security... I could go on... but in the vast majority of cases, it's Windows that is taken seriously, and the Mac is seen as being largely irrelevant and at most an afterthought. I've not worked in finance, but have plenty of friends who do, and it's the same there. The general consensus for most industries is Linux for servers, Windows for desktop, although Windows has a significant footprint in the server market too. Even a lot of parts of the media / design industries (e.g. video production, web design, architecture ), where the Mac has dominance, they at least put Windows and Mac on an even keel.

I don't see any issues with this. It sounds like a sensible approach to me for anything that isn't recorded to a click. Although this is true, It might be wise to set all the audio clips to absolute first... just in case there are custom settings under the groove clip setting for one of the clips. FYI - the way I'd go about changing everything to absolute: 1. Press "H" to bring up the track manager, and hide everything apart from audio tracks. 2. Select all your audio tracks 3. Go to the Clip Properties in the inspector, and set Time Base to "Absolute" 4. Press "H" again and unhide all the tracks I'd hidden in step 1.

@Colin Nicholls - I was hoping that putting a final check that the ctrl key is down just before it adds the note to the selection would solve this.... but the code is already doing this. So I don't know what to suggest. I can't repro this. Maybe a sticky CTRL key?

Groove3 has a SONAR Platinum course. It's very good, and covers at least 90% of Cakewalk. SWA Complete SONAR X2 is also pretty good, albeit a bit older: There's also a follow up which includes the Pro Channel:

Out of interest, does this setting make any difference? I suspect it might have to be unchecked when using VEP.

This series by @Creative Sauce is probably exactly what you're looking for. IIRC he uses Cakewalk for the whole process:

I used to use TouchDAW quite a bit... and in fact I used the HUI mode on it to develop the HUI beta support in the CbB's Mackie Control control surface DLL. It's pretty amazing to be honest - full MCU and HUI emulation for £4 and a cheap £40 android tablet. The only reason I don't use it now as I prefer real tactile faders. But its perfectly useable.

^^^ This is the best method IMO. Use Bounce to clip(s) on the groove clip to make it a regular clip, then slip edit back an 1/8th note. Once it's a regular clip, you can use duplicate clips ( CTRL + D ) to make extra copies of the clip.

@Alvaro Diez - this was indeed a bug in the tempo track. It was adding a tempo node at the uncropped end of the project, rather than at the cropped end. The official 2021.04 Update 1 release (soon to be released) will fix that. Tempo nodes will no longer be added at the end of the project.

Also make sure you have the required video codecs installed in Windows. Cakewalk uses the video features built into Windows, so if Windows doesn't have the codecs installed to play a particular video then neither will Cakewalk.

@Richard Penrose - did you do a VST scan after installing the SI Instruments? All the SI Installer does is install the VSTi's. Cakewalk won't pick them up until its done a VST scan.

The web based BandLab DAW doesn't support video, however if you're running Windows 64 bit ( version 7 or above), you can use Cakewalk by BandLab to download your BandLab project and add a video (Cakewalk supports a video track). This thread highlights the new BandLab integration for Cakewalk: It's worth mentioning however, that: 1. Cakewalk is a DAW, not a video production suite. The intention of the video track is to score music to video - not to produce videos. 2. You need to ensure that the correct video codecs are installed in Windows.

The settings are sored in flash memory in the nanoKONTROL 2, and no, they don't need any button dance when starting up. Once you've configured it, it should just work from then on. @Dav Mar - up until recently, the Korg USB MIDI driver was not compatible with Window 10 2004 / 20H2, which meant the editor wouldn't work properly (you'd make edits, but they wouldn't be saved to the device). I believe they've now got updated drivers on the Korg website. Personally, I've removed the drivers from my Windows 10 boot and just use the nanoKONTROL 2 as a class compliant MIDI device. This works fine, but you can't use the editor. I've got a Windows 7 boot that has the old drivers & editor on it if I ever need it though.

It could be something like a virus checker trying to access the WAV file while Cakewalk is trying to finalise the file after recording has stopped. Have you checked that all of your Cakewalk project & audio folders are excluded from virus checkers, OneDrive and any other cloud-sync apps?

The Mackie Control support was developed by Cakewalk in association with Mackie, at around the time the original MCU came out (I think it was around 2004/2005). With the exception of the faders and transport controls, most of the MCU's buttons were "up for grabs" and Mackie worked with the major DAW developers at the time (Cakewalk included) to come up with overlays that better reflected the functionality provided by each DAW. The result was that each button had a different function on each daw, and common functions such as looping were controlled by different buttons between DAWs on the MCU. Since then, the majority of control surface manufacturers have decided to provide emulations of the Mackie Control, rather then opt for their own protocol - however most of them lack the all buttons provided on the original MCU. Up until the demise of Cakewalk Inc., most of these control surfaces provided a SONAR mode which sent the correct button combinations to achieve the desired function in SONAR and Cakewalk. Some control surfaces such as the PreSonus FaderPort series, and the Korg nanoKONTROL series still provide a Cakewalk/SONAR mode, so users should have no issues using those surfaces using that mode. The Behringer X-Touch (the largest one), seems to fully emulate an MCU - it has all the buttons, and you can buy Cakewalk/SONAR overlays for it. This should also work fine with Cakewalk. But unless a control surface specifically says it supports Cakewalk, do not assume that it will work. This is especially true for the single fader controllers, where one button press on the controller actually sends out a combination of button presses to the DAW. Unless they're sending the button presses Cakewalk expects, it's not going to work.

That decision was made before I joined the team. I don't know the reasons behind it.

Yeah, I do this too - especially when switching between laptop & desktops. I tend to use loopMidi as you can rename the ports so they even look the same.

From what I remember, the Window and Strength parameters give you similar functionality: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.39.html

FWIW - in this scenario I use one of the two workflows: 1. Use SHIFT + double click to maximise the waveform, then either SHIFT+double click again or CTRL + ALT + Z to minimise. 2. Open a new screenset and use SHIFT + double click on the other screenset. I can then switch between screensets quickly using keys 1 through 9.

You need to turn the groove clip back into a normal clip. Select the clip and right click "bounce to clip(s)"

Yes, this is exactly what the issue is. You need to use 64 bit DLL's.