msmcleod

The easiest way to do this is: 1. From the main menu: Project -> Insert Time/Measures 2. Ensure "At Time" is 1:01:000, "Insert" is set to 2, and Measures is checked - make sure all the other checkboxes under "Slide" are also checked. 3. Click OK.

The order the driver presents them. If you're using ASIO with ASIO drivers that support multiple interfaces, the order of installation is unlikely to be a factor. The ASIO driver presents the ports in a particular order, and that's the order CbB uses.

As far as I know, the audio ports are always listed in driver order. This is by design. So the short answer is, no, you can't do this as it stands. The only thing I can suggest is to use friendly names, and perhaps prefix those ports with an asterisk or some other character that might make it stand out more in the list.

I don't really get this one... surely once you've committed an arrangement, all of your existing sections are all in the wrong place? Or rather than preserve, do you mean "arrange" the sections in the other arranger tracks too?

The new Sonar will fully support the scale size you set in Windows - so if you set scale to 125% or 150%, the fonts within Cakewalk will adjust accordingly.

You can already do this using FX chains: To create them:

My PC has been sluggish all day... then it became apparent why... the latest windows 2023/12 update had been doing it's thing in the background, and when I finished up for the day was telling me to restart to complete the update. I can't count how many times this has caught me out. Before troubleshooting all your audio settings / cakewalk config etc... check Windows update - it could be the cause of the slowdown and memory usage. Some day I'll remember my own advice myself!

This is exactly what happens. You can set your global audio folder in Preferences under File->Audio Data.

There is no clever interaction between Kontakt (or any other multi-timbral VSTi) and Cakewalk. No special notifications are sent to Cakewalk when you delete a library from Kontakt, so Cakewalk has no way of knowing you've pulled the rug from under it. Re-running the batch-script in Kontakt after deleting a library after all the tracks have been created in Cakewalk is a bad idea. All the MIDI / audio port mapping is going to change. If you do need to delete a library in Kontakt (unless it's the last one) - don't run the batch script - be prepared to manually set the MIDI / Audio channel outputs in both Cakewalk and Kontakt. Note - it's fine to delete a library, then add a new one to the end and continue to use "Append Instrument Track" as long as the MIDI Channel / Audio Port continues to ascend. Just make sure you don't change the MIDI channels / Audio ports for any existing libraries. If deleting libraries is a common part of your workflow, consider using simple instrument tracks and having separate instances of Kontakt for each track. For Kontakt at least, the difference in CPU/Memory usage is minimal.

You can't use the same MIDI port for both Mackie Control and normal MIDI input. The Mackie Control takes sole ownership of the MIDI port. Devices that support Mackie Control will expose extra ports specifically for that purpose.

FYI - some electronic pianos support more than one pedal value. My old Yamaha PF80 used to send four different values of "on" depending on how far the pedal was pushed down. How synths / VSTi pianos react to that is up to how they are programmed - i.e. some will see anything other than zero as on, for others it'll be 64 and above, and others will support a range of values adjusting the sustain accordingly.

Not yet it hasn't. The download links for Cakewalk by BandLab on www.cakewalk.com are still active.

Even after renaming CW130Auto.dll in C:\Program Files\Cakewalk\Shared Utilities ?

Just tried it - the Korg Triton VSTi is indeed mono-timbral. Makes sense, as both the VSTi versions of the M1 & Wavestation are mono-timbral too.

I'll need to check out the Triton's implementation, but certainly on the Korg X series, combinations could be multi-timbral - you'd simply set the MIDI channel of the different patches within the combi to different channels. I use this technique on my X5D (live use)/ X5DR (studio), simply because there's 100 combi's that are easily saved and only one Multi... and the multi is a pain to set up. [EDIT] - looks like Korg removed the ability to set different Combi part receive channels in the N series. Pity... it was very useful for live use.

Right click on the curve and change it to a jump.

FYI - that particular video was a very early beta (from around the beginning of Sep). We're still unsure as to how it got out. It's really not representative of how Sonar is looking now - and work is still ongoing.

It looks like you've tried to re-install CbB 2022.11 over the top of CbB 2023.09. It's unlikely that having the 2023.09 version of CW130Auto.dll running with CbB 2022.11 will cause any issues, however you will get this warning. If you want to stick with CbB 2022.11 (bearing in mind, it'll no longer re-activate when it expires), the easiest thing to do is to rename CW130Auto.dll in C:\Program Files\Cakewalk\Shared Utilities to CW130Auto.dll.old and re-install CbB 2022.11. The best thing to do however is update to CbB 2023.09.

The 18i8 allows for two headphone mixes (one being identical to the stereo mix), and the other which is separately configurable. What I suggest: 1. In Cakewalk, set the output of the metronome bus to a separate audio output (e.g. DAW 3/4) 2. In the Scarlett MixControl application, set the headphone routing to DAW 3->Headphone Left / DAW 4->Headphone Right. One of the headphone outputs should now only contain the click, and the other headphone output everything else. This tutorial may help:

In Preferences->MIDI->Playback And Recording, there's a "Always Echo Current MIDI Track". This causes MIDI input echo to be enabled on the active (focussed) track - you'll see an "A" on the echo button to tell you it's enabled because it's the active track. It this is unchecked, you'll have to manually enable input echo. There's nothing stopping you manually enabling MIDI echo for all of the tracks yourself of course, but this will cause all of those tracks to respond to MIDI input. Also be careful that no other tracks are transmitting MIDI data, as this will also cause it to play on those tracks (this can happen when MIDI output is enabled on another VSTi). Enabling MIDI echo on a track will cause them to react to those MIDI messages too. Although you can change the input filter on each track only to respond to a particular device/channel, most users find this inconvenient, as it requires you to change the MIDI channel on your controller keyboard to match the track you want to echo. The default setting is to have the MIDI filter set to "None", with "Always Echo Current MIDI Track" checked. MIDI echo will be enabled and the filter set to "Omni" when the track is the active track.

If you use the Append Instrument Track function, you don't need to force the MIDI channel - it's done for you. In fact, altering the forced MIDI channel will confuse the Per-Output Track functionality, and will likely not allow you add new tracks using that method. To use Per-Output Instrument tracks, you need to configure your VSTi so that the MIDI channels are ascending from 1 to 16, and they match (in the same order), the audio outputs for those channels. In other words, the sound listening on MIDI Channel 1 goes to Stereo Output 1; the sound listening on MIDI Channel 2 goes to Stereo Output 2 etc. The batch functions in Kontakt do that for you. Other VSTi's will require you to map them yourself. Once you understand the concept more thoroughly, you can create more advanced setups - e.g. layering sounds by ensuring the MIDI channel / audio output of more than one library are the same... but if you're just starting out, stick to the basics.

FWIW - I have used the following control surfaces with Cakewalk (and of course the new Sonar), without issue: Mackie Control Universal / XT / C4 Presonus Faderport 16 Yamaha 01X Behringer BCF2000 Korg nanoKONTROL Studio Korg nanoKONTROL 2 The Presonus Faderport 8 is essentially an 8 fader version of the Faderport 16, and works fine with Cakewalk/Sonar. A fair number of users use the Behringer X-Touch (the big one), which is basically a full clone of the Mackie MCU. For surfaces that claim to support the Mackie Protocol, but don't specifically support SONAR/Cakewalk, you can usually get it working by checking "Disable handshake" in Cakewalk's Mackie Control surface dialog. You may also want to check one of the compatibility modes such as Cubase or Universal. The control surfaces that seem to cause the most issues are the single fader type, so unless you know it works with Cakewalk, I'd avoid them.

Everything is converted to either 32 bit float or 64 bit float internally for mixing, so as long as the 16 bit files sound good to start with, you'll not have any quality issues. The only thing you lose with 16 bit is dynamic range - but even with 16 bit, the dynamic range is huge.

The only consideration is that Sonar 8.5 doesn't support VST3, only VST2. So if RipX is VST3 only, then it's not going to work with Sonar 8.5.

sorry I meant ports... I'll edit my original post.