msmcleod

Have you determined that Cakewalk is actually receiving MIDI data on that port, and you've got the correct port routed to ACT? There should be two ports that the MPK is transmitting on, one is for the keyboard / pichbend / modwheel, the other is for the DAW functions. You need to use the DAW MIDI port with ACT.

Maybe you're running a 32 bit version of Reason? AFAIK for Rewire to work, both apps need to be the same bitwise.

Paste always pastes to the active track, which is indicated by the name being highlighted. There can only be one active track. The track number being highlighted indicates that the track is selected, and many tracks can be selected.

If you want really smooth curves or lines, it's far easier to use an automation lane. If you really need it back in the PRV, select the automation envelope, right click on it and select "Convert to MIDI Events". Note that the current global snap setting decides the resolution of the conversion.

First of all, have you tried setting the MPK to preset 12, along with Cakewalk's ACT MIDI Controller set to the "MPK49 Preset 30" preset? If this doesn't work, from a quick look through the user manual, it does look like you'll need to map every function. I would start with using preset 12 on the MPK, since this claims to have Cakewalk/SONAR compatible CC's. On the Cakewalk side you can use the "ACT MIDI Controller" control surface, and use the ACT MIDI Controller dialog to learn each of the CC's. This is a pretty good tutorial showing you how to do this: Make sure you remember to save your preset within this dialog after mapping all the functions.

Try Edit->Select->By Filter: You can use this to only select Kick Drum notes over certain velocities by setting the note min/max to just the kick drum, and the min velocity to what you need. Once it's in your selection, you're free to delete, or Process->Scale Velocity, or whatever.

@Max Arwood - here's a project with 80 bars of the tempo switching between 114 and 114.01 every 8th note: https://msmcleod.co.uk/cakewalk/Tempo114_005.cwp You should be able to copy/paste the tempos from this project into yours. I created the tempos by inserting a bar's worth of tempo changes, then copy/pasted them into the tempo track: If you still get flanging with this, you could try changing the tempo change intervals to 1/16th or 1/32nd note.

You could try Cakewalk's "Velocity" MFX plugin. This allows you to offset and scale velocities. Just drag it into your MIDI track's effect bin. F1 brings up the help. If you're using an instrument track, the track view will show an audio effects bin, so click on the MIDI tab in the inspector and use the FX Bin in the inspector.

You can use either - it all depends on what your needs are. Automation lanes are great for recording automation and drawing accurate/smooth transitions, and editing the curves. Drawing CC events in the PRV is useful if you want fine control over each individual event. The PRV also has the transform tool which can be useful in some circumstances. It's also possible to swap between the two: - To convert PRV CC's to an automation envelope, left click on the controller within the PRV controller pane to select it, then right click and select "Convert MIDI to Envelopes" - To convert MIDI Automation to PRV CC's, right click on the envelope and select "Convert to MIDI Events". You can also select a time region to only convert a part of the envelope. The current project snap resolution is used to to determine the time resolution of the converted events. Just be aware that because CC Events are stored as discrete events, and Automation Envelopes are stored as curves, you may lose accuracy in conversion.

FWIW I too started getting BSOD on boot up with the Focusrite drivers (almost certainly down to a Windows update). I upgraded to the latest beta driver, and everything is fine now.

What does it sound like at 114 or 114.01 ? You could try swapping between 114 and 114.01 a few times within the project. The difference is so small, I doubt if you'd notice any difference.

From what I can gather, I think the MIDI Control Center is used to configure the device - i.e. set the various modes. You should be able to use the MCC to configure the device, then the device should remember those settings from then on. But as it doesn't specifically list Cakewalk or SONAR as one of it's listed compatible DAW's, you'll probably find it limited in support for Cakewalk. In saying that, it does say it supports generic Mackie Control and HUI. You may be able to get it to work using either of those modes by setting it up using Cakewalk's Mackie Control Surface, and making sure the "Disable Handshake" setting is checked. As the button layout for the Mackie Control mode is DAW specific, you may find that while it connects, the buttons don't do what they say on the keyboard. So you may want to try HUI mode instead. If you've selected HUI mode, make sure you've checked HUI as the protocol within the Mackie Control Surface dialog. Alternatively, you might want to contact @azslow3 and see if he or any of his users has an Arturia Keylab II profile for AZController.

Without a control surface, the only way I know to do this is to use the up / down cursor keys to move up and down the tracks. Alternatively, if you open the Synth Rack view and click on one of the synths so it's focussed, you can use the up/down cursor keys there - this might be more useful if you're synth tracks have audio tracks intermingled with them.

As long as the drivers are compatible, and they actually support Cakewalk/SONAR you should be ok. For example, I've got a Samson Graphite 49 which has a SONAR mode - this works fine with Cakewalk in Windows 10 both as a keyboard and a controller via Mackie Control. Pity the keyboard itself is not great - the velocity is so inconsistent, I find it impossible to use for anything other than organ. One thing you should bear in mind with these types of keyboards: The keyboard should present itself as two MIDI devices; one for the keys, pitch bend & modwheel; and another for any knobs, sliders and transport controls. You'll need to consult the user guide of the keyboard in question to see how exactly the second MIDI device needs to be set up. Sometimes they have Mackie emulation, in which case you can set it up as a Mackie Control surface. Others just send out CC information, in which case set it up as an ACT control surface, or just use MIDI learn on the fly. If they only present themselves as a single MIDI device, then you're limited to using MIDI learn. Setting it up as a control surface will render it useless as a standard MIDI keyboard, as the control surface will steal the MIDI port.

Other things to check: 1. Have you got any articulations that have a D key switch? If so, check the MIDI channel of the articulation is correct. 2. Have you got another synth with their MIDI output enabled that could be routing to that synth? 3. Within Preferences->Project->Metronome, have you got it set to use a MIDI note?

You can also customise which functions the smart tool operates on: I occasionally disable Comp on the smart tool if I'm working in lanes a lot and don't want the speed comping kicking in when I'm trying to select.

IIRC doing a VST rescan won't do anything with DX plugins. DX plugins are registered as COM objects in the registry, and they're registered by the installer at install time. There's two ways to get them registered again: 1. Uninstall CbB and re-install it (this shouldn't affect your registry settings); OR 2. Manually locate the VST plugins and re-register them yourself. For (2), you'll need to fire up a command prompt as administrator and use regsvr32 for each DX plugin, e.g.: regsvr32 "C:\Program Files\Cakewalk\Shared Plugins\SonitusFXEqualizer.dll" It's important that you give the full path to the plugin dll. I find the easiest way to run a command prompt as admin is to create a new shortcut on the desktop to cmd.exe, then right click on the shortcut and select "Run as Administrator" [EDIT] - you can also remove unwanted DX plugins by using the -u parameter, e.g. the following will remove the sonitus equalizer: regsvr32 -u "C:\Program Files\Cakewalk\Shared Plugins\SonitusFXEqualizer.dll"

You can use automation lanes for MIDI CC: You can then either just leave them as automation curves, or convert them to discrete CC events for use in the PRV:

Select your sections, then right click on the selection bar and pick "Create Markers from Sections"

Maybe it can't find your default browser - what is your default browser set to? Go to settings from the Windows start menu: Try changing the default browser:

“I think Selling England By The Pound is an enduring masterpiece of drumming. Beautiful drumming, lovely sound, and the arrangements, I think they really nailed the best of what that band as an entity could have done with that album” – Neil Peart on Phil Collins

Whilst it may work, consider that you're not only running a virtual machine (which is having to emulate various bits of hardware), that virtual machine is also having to emulate an Intel CPU... so performance is likely to be far inferior to a native M1 DAW or even an intel Mac DAW running via Rosetta 2. Don't get me wrong, I think the M1 is a great machine, but I wouldn't set your performance expectations too high with this level of virtualization / emulation going on.

At some point probably, however on 2nd thoughts I'm not sure if this would work in any case with automation envelopes... he might have to convert them to MIDI CC's first.

You can use an articulation map to clamp or scale the values ( using a MIDI transform articulation )

Yes, this can make a huge difference to sample load time, and general performance. On my system Omnisphere went from 45 seconds with a HDD to < 2 seconds on a SSD when loading some presets.