msmcleod

As of the 2021.06 release: "Instrument" will only refer to instrument tracks (i.e. linked audio & midi tracks such as Simple Instrument or Per-Output Instrument tracks ); "MIDI" will refer to any MIDI track hardware or software; "Audio" will refer to any audio track.

FWIW, running Windows 21H1 here without issues. @cclarry - definitely sounds like a compatibility issue with your graphics driver. I'm running with my on-board graphics card, but Intel released an updated graphics driver shortly before the Windows 2004 release (which was surprising given it's for an old 3rd gen i7). But I guess the updates were needed to support the newer Windows versions.

20H2 was a tricky one on my DAW machine too - the KORG USB driver and an old Native Instruments virtual CD Image driver were stopping it from upgrading, but once I removed them it was fine. I'm now on 21H1 on all my Win 10 machines with no issues.

The original server for this PDF has gone unfortunately.... luckily I've still got it on my server: https://msmcleod.co.uk/cakewalk/Cakewalk%20Application%20Language%20Programming%20Guide.pdf

You could bind a key just for the Event View, e.g.:

Bluetooth MIDI is supported in the UWP MIDI driver mode. Several devices use it (e.g. Korg microKEY series, Korg nanoKONTROL Studio). Latency definitely isn't an issue, as the MIDI baud rate is extremely slow compared to Bluetooth's baud rate. The main reasons I don't use it myself, are: 1. I've got older MIDI hardware that only work in MME mode. 2. I don't like having to constantly replace batteries for remote devices (especially when they don't move on my desk in any case).

As long as they don't completely change the driver model making half my hardware obsolete... that would be VERY annoying.

We're actually working on something like this at the moment. It won't be in the 2021.06 release, but hopefully the one after that.

Also check that a recent Windows update hasn't set your power plan back to "Balanced" or "Battery Saver" - make sure you're running at "High Performance"

We've made some improvements to this for the next release.

It's probably going wrong because there's no events on track 2 within the selection (i.e. the selection is in a blank space between two clips). A lot of the older commands rely on event selection before considering other things like envelopes. To be honest, you're better off turning on Ripple Edit All (or Ripple Edit Selection) and pressing the Del key.

Yes it's explained here for zooming: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Arranging.22.html#1838690 I can't find anything specific in the docs for scrolling - normally the mouse wheel alters the control it's currently hovering over, but if it's over a clip or a blank space in the clips view: Mouse Wheel = vertical scroll bar. CTRL + Mouse Wheel = horizontal scroll bar.

All the standard keyboard shortcuts are listed here: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=KeyboardShortcuts.html#1306571 The closest thing to scrolling horizontally is CTRL + Page Up / CTRL + Page Down, but this also moves the Now time.

In the track view, CTRL + LEFT/RIGHT will zoom horizontally, CTRL + UP/DOWN will zoom vertically. All the zoom controls are detailed in this chapter: https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Arranging.22.html (scroll about half way down the page)

@Ronny.G - We've fixed the issue with templates that you reported in your first post. This will be available in the next release. Your latest issue sounds like it could be different, but it could also be related to the original bug... did you load any track templates in this project? The original bug means that the MIDI ports are in a strange state after importing the template. This might explain why you cant change the ports after importing. For the moment, I'd advise against loading/saving synth templates with routing until the next release. Routing from hardware MIDI ports should be fine, but if the template contains MIDI routing from synths within the template, that's where the issue arises, and it pretty much messes up all the ports. Like I said though, it's been fixed for the next release.

Whilst this is true, it basically boils down to this: 1. Take a note of the measure the clip ended on before you change tempo 2. After changing tempo, you want to stretch it so it ends it on exactly the same measure as it did before. This is why I recommend slip editing to end exactly on a measure boundary before doing the stretch. As a general rule, the bigger the change in length, the worse the quality is going to be. There are different stretch algorithms that do a better/worse job depending on the type of material you're stretching. Also there's an offline / online method - where online is what you'll hear doing what is showed in my video, and offline is what is used when using bounce to clip(s) and exporting. By default, the online algorithms are quick but average in quality. It's designed to make editing quick. The default offline algorithms are slower, but much better quality. There's nothing to stop you changing them to be the same however (i.e. make both online/offline the slower, high quality versions). You can change the methods in preferences:

For non-groove clips, this is what I'd do:

My thoughts exactly. I rarely need to display them, but when I do, I need to be able to scroll them. Especially on my RME, which has 17 of them.

I normally use the Event View, and insert it right at the top of the list.

If all your audio clips are groove clips, all you need to do is make sure your Now time is at 1:01:000, and change the tempo in the transport module. The groove clips should automatically change to the new tempo.

1. No - just non Cakewalk 32 bit plugins. 2. If it's a 32 bit Cakewalk plugin, use BitBridge otherwise use JBridge for other 32 bit plugins. The only other plugins that benefit from JBridge are the UJAM virtual guitarist plugins ( yes, I know they're 64 bit, but they work much better in Cakewalk via JBridge ).

@Mike1212 - There's an extra function that was added that won't be in the help: Holding M1 and pressing the Plugin button will switch to the Synth Rack, allowing you to control synth parameters. The synth rack is a "Mix Strip" in the same way tracks, buses and mains are. Navigation works in the same way to plugins on a track or bus, but it navigates through the synths within the synth rack. The best way to envisage it is to see the synth rack as a special track, with a collection of synths as opposed to a track with a collection of effects.

This is likely to be due to limitations of layer functionality in MIDI tracks. If you put each clip is in it's own lane (so they're not overlapping), does it behave correctly?

The overlay just ensures the buttons on the X-Touch match what Cakewalk expects. As far as I can tell, the X-Touch has all of the Mackie Control buttons. The X-Touch Compact, X-Touch mini and X-Touch One have less buttons, and may not directly map to what Cakewalk expects. Documentation for the buttons can be found by pressing F1 when the Mackie Control panel is up ( Utilities->Mackie Control 1 ), or alternatively you can open the help file directly - "C:\Program Files\Cakewalk\Shared Surfaces\MackieControl.chm"