msmcleod

You could use a CAL script I guess: (do (do (int startTrack 0) (int endTrack 0) (getInt startTrack "Start Track: " 1 255) (getInt endTrack "End Track: " 1 255) (int currentTrack startTrack) (int chan 0) (while (<= currentTrack endTrack) (do ( TrackChannel chan currentTrack ) ( ++ chan ) ( if ( > chan 15 ) (do ( = chan 0 ) ) ) ( ++ currentTrack ) ) ) ) ) The above will prompt you for a start track and end track, then will set the track MIDI channels starting at channel 1. If there are more than 16 channels, it'll go back to channel 1 again. Attached is the CAL file. Save it to C:\Cakewalk Content\Cakewalk Core\CAL Scripts You can then run it by selecting Process->Run CAL from the main menu. You could also assign a keyboard shortcut to run it if required. ReChannel.CAL

Unfortunately not. Cakewalk uses Note On velocity 0 for note off's, rather than actual note-off messages, so you lose the note off velocity.

That's a 2nd gen i7 - you need at least a 7th gen i7 to run Windows 11, and also a hardware TPM module on your motherboard. I've got a 3rd gen i7 (3770 @ 3.4Ghz), which has been running Windows 10 for years now. Windows 10's end of life isn't until October 2025, so there's a good few years left.

I've had timing trouble with pure MIDI projects in the past. The issue I had is that normally timing is tied to the audio clock, but as there were no audio tracks in my project, the timing was drifting. There's two solutions: 1. Just add a blank audio track. 2. Set the timing in Project->Clock->Source to "Internal" However, depending on how your hi-resolution timer is set up both in your BIOS & in Windows itself, option 2 might not be accurate enough. I find keeping the clock source as "Audio" and inserting a blank audio track the most reliable. Also make sure that your Playback Timing Master is set to the correct audio device.

Probably the most common use case is when using CTRL+D. As this places the duplicate clip immediately after the current one, this is invariably in the wrong place unless the clip ends on a measure boundary. Personally, I'd like the default behaviour to never shrink MIDI clips to the the events extent - I'd rather it left the clip alone, or at least make it an option. Unfortunately the code that automatically shrinks MIDI clips to the the events extent is buried deep within the code. My first attempt at the "Automatically extend final take when loop recording in Comping mode" change for the 2022-06 release tried to circumvent this behaviour, but ended up causing a raft of bugs as side-effects. So I had to take a different approach: rather than preventing it from shrinking, it just re-adjusts the clip end times before it does it's any of the splits. For the use case I've described, this feels a bit like a workaround rather than a solution... however if you've never manually adjusted the clip in the first place, maybe this is the command to do it to avoid having to do it manually.

On the main menu, go to Window->Tile In Columns. This will put the projects side by side. You should then be able to drag/drop the effects between the projects.

@CTL 21 - One thing you should be aware of... You can only use one ASIO driver at a time per application ( this is a Steinberg restriction on Windows), and quite often this also means that only one application can use this ASIO driver, closing it off for all other applications when in use. So this means: 1. You can't have one ASIO device for input, and a different ASIO device for output 2. If VoiceMeeter is using ASIO for a device, Cakewalk can't use it. If you need to use more than one device, you can either use WASAPI shared or WDM in Cakewalk. There are small complications, such as lack of word-clock sync, so the timing may need to be tweaked after recording, but it will work. My main advice would be to anyone using Windows is, don't use USB microphones for anything other than voice-over recordings or Zoom meetings. You are far better off using the XLR equivalent. In addition to the above reason: 1. The XLR equivalent can plug straight into any decent audio interface, everything will work using the same ASIO device. 2. An XLR mic will work with anything - stand-alone pre-amps, studio & PA mixers, audio interfaces etc. 3. In years to come when the USB drivers no longer work on some future version of Windows, an XLR mic will continue to work regardless. 4. With a USB mic, you're stuck with the mic pre-amp built into the mic, which in most cases will be far inferior to any decent audio interface.

There is a registry setting you can use to get those back... I did that, as I rely on a bunch of shell extensions for TortoiseSVN / TortoiseGit. https://pureinfotech.com/bring-back-classic-context-menu-windows-11/#:~:text=Enable classic right-click context menu on Windows 11&text=Right-click the CLSID key,and select the Key option.

CC #123 is All Notes Off - I guess you could use that. The value field for CC#123 is ignored, so you can set it to anything. This may not affect sustained notes when CC#64 is in play though, so you might also want to add a CC#64, 0 immediately before that.

You can convert your MIDI CC data (and also Pitch Wheel data) in the PRV to MIDI automation lanes, and back again if need be:

Check the release notes regarding MMCSS settings. For optimal performance, it's important that BOTH your driver and Cakewalk are running in MMCSS mode. It should be down to your ASIO driver to set MMCSS mode, but some don't. Cakewalk can set it on the driver's behalf you have the option checked in preferences, however be aware that some drivers may crash if they've already set it to MMCSS mode and Cakewalk then tries to set it again. If neither the driver or Cakewalk are running in MMCSS, you'll experience less than optimal performance; if only one is set to MMCSS, then this could explain your crashes.

Yeah, this is a major issue for me. I use 5/4 and 7/8 all the time, and just can't use BIAB in these scenarios. Apparently you can use RealBand for this, but I've not taken the time to learn that yet!

Where it is makes it consistent with the current Delete effect position. It prompts you in any case, so you'll know if you select it by accident.

FYI - Kontakt 7 appears as "Kontakt 7.vst3" within my VST3 directory.

The fact that it does it when playback is stopped / clicking around the screen leads me to think it's more likely to be a hardware/electrical interference / audio ground issue. I get this when using my onboard audio interface (I've always used the onboard graphics on an intel board). I solved it by using an audio isolating transformer between the audio output and my monitors: However, I've never heard of this issue using an external audio interface (I'm assuming your interface is an external and not a PCI based one?) ... so maybe it's something else. BTW - the isolation transformers do a great job, but I find they only last 3 - 5 years or so... not a huge issue as they're only around $10, but something to bear in mind.

Articulations are pretty low level, so if you send an aftertouch on message it doesn't automatically send an aftertouch off message unless you tell it to. You need two events in your articulation - one that sends the "on" message at the start, and another that sends the "off" message at the end.

A friend of mine had a V-STUDIO 700, which had the T-Bar for controlling X-Ray. It was pretty cool, but always made me wish I had a Raleigh Chopper again...

Just remember that Melodyne 5 doesn't work on Windows 7 - so I guess if you've got a >= 10th Gen Intel machine running Windows 7, you're completely out of options for Melodyne unless you upgrade both Windows and Melodyne.

Take a look at the preset functionality in Track Manager (default shortcut is the "H" key) - you should be able to get similar functionality from that. Basically, it allows you to create a set of presets, on a per project basis, that show/hide whatever sets of tracks or buses you want.

I've only done a quick test, but I think it might be a bug in the plugin. I did eventually get it working though... I had to actually send something to the side chain, then play the project. As soon as a signal was detected on the side chain, suddenly the button started working, and I could switch it on and off.

Normally you'd use an ethernet audio interface such as MADI or Dante. There are other solutions though - ASIOLink allows you to send audio over ethernet from one computer to another. I think some of the VBCable suite might do it too. You can also use shielded CAT6 cable as XLR cables as a cheaper alternative. Using a common ground, you can carry 4 balanced signals. Of course, that isn't using ethernet - just the cable.

You can do this with a combination of groups and assignable controls:

I've now got a D110, but for a long time, I used the CM-32L which is basically an MT32 with a much lower noise floor and without the display. It also had double the waveforms, and a bunch of sound-fx samples in the drum track. I later replaced it with a CM-64 which is the CM-32L and the CM-32P (a U110 with no display) combined. Having written editors for both, I'm sure you know that although the MT-32 / D110 share a very similar architecture, the PCM waveforms are different - so patches transferred between them will sound different. The CM-32L / CM-64 are great low noise alternatives to the MT-32, but you'll obviously need an editor to change anything. I believe the D5 is also basically an MT-32 with a lower noise floor.

The main issue with running as Administrator, is that you lose the ability to drag/drop between applications or Windows explorer (unless of course that application is also running as administrator). It can be very convenient to select / drag drop clips to a folder in Windows Explorer rather than having to go through the export dialog. Other issues are largely plugin-dependent - e.g. some plugins use the user's documents folder to store plugin or preset information. Depending on how you are running as administrator (i.e. the administrator user vs just elevated administrator privileges), these may not be found by the plugin. The final reason is security. Plugins, by design, run in the same process space as the host DAW, so they have complete access to ALL of the DAW's memory (and other plugin's memory too). Giving the host application admin privileges also gives those plugins the same admin privileges. If a plugin was infected with a virus, or even written with malicious code it would bypass any protection UAC gives you. The only reason I've ever needed to run as Administrator is with older DirectX or 32 bit plugins, and that was only ever needed for the very first time I ran them.

I've got an MT-32 and I used to have a Sound Canvas. The MT32 is an 2nd generation LA synth, where very short attack samples are combined with an early version of virtual analog synthesis. The Sound Canvas is completely sample based. Although there are sounds in the Sound Canvas that have obviously been sampled from the D50 (a 1st generation LA synth), the MT32 and Sound Canvas sound very different.