msmcleod

FYI - You can also use "Apply All Articulations to Track" to convert the triads into MIDI events in the PRV.

I managed to upgrade to 20H2 using the media creation tool, and selecting the "Keep my files" option... which deletes all your program files (and all your stuff in ProgramData), but keeps your "personal" files intact. Copies of your program files / program data are in the windows.old directory, so it's easy to copy stuff over (e.g. VST's that don't have an installer) if need be. I got about 1/2 way through re-installing programs before a reboot refused to boot again. I've gone through this procedure TWICE this week (so wasted around 30 hours). The second time around I was running sfc /scannow before every reboot, just to make sure no installation had screwed anything up. The last time it failed was just after installing Antares AVOX 4. I seriously doubt that would have caused the issue, but it was rebooting fine up until that point. So now I'm back to square one having restored my 1909 image yet again. I'm gonna re-enable system restore the next time I try this, in the hope I'll be able to rollback the state if this happens again, but I'm very close to losing all confidence in these Microsoft upgrades.

Articulation events are always handled before any other MIDI events, so it shouldn't matter if they're at the same time as the note. In saying that, there may be some VSTi's that require a delay before they'll respond to the changes, so in this scenario you may have to place them slightly in front of the note.

Have you an example project that can repro this? A lot of effort was made to ensure articulations are always sent out before any other MIDI event. If this isn't happening, then we need to know about it. The only scenario I can think of that this might happen, is if you've spread your articulations/MIDI events over several tracks (e.g. MIDI events on track 1, articulations on track 2)... but for any given track, the articulations are always handled first. This is controlled by the "Transpose" checkbox within the triggered events. If transpose in unchecked, then the MIDI channel of the articulation will be left unchanged, as will its pitch and velocity trim. The articulation sections aren't sections in the same way as arranger sections, they are actually events (you can see them in the MIDI Event List). So the way to stop or allow articulations getting cut/copy/pasted is to control whether they're selected in the first place. This can be done by: - Using the selection filter (Edit->Select->By Filter) - Toggling the state of the "Select Events with Time Ruler"

When you say time code, do you mean the time code display within CbB itself ? The "Pause" key (next to scroll lock) puts CbB into low CPU usage mode by reducing the UI refresh rate. Pressing pause again will take it out of that mode.

This is likely you're issue - make sure the master fader is set to Bus 1:

At one point I moved all my projects into MS Sourcesafe, and later SubVersion to give me version control. But to be honest, the extra hassle of checking out projects / checking them back in far outweighed the benefit of the very few times I needed to go back to an earlier version of my projects. My current solution is just to use cloud storage. I have a couple of batch files which copy my CbB project directory to and from a directory that is synced to the cloud. It's important that the sync directory is different from your actual projects directory to avoid the cloud client app accessing project files at the same time as Cakewalk (although an alternative might be to just manually run the cloud client app). I run the download script when I start up (once the cloud sync has finished), and the upload script when I finish a session and wait for it to upload everything. This has a few advantages: I have a backup of my projects in the cloud The cloud storage gives me access to previous versions of files I decide when a project gets synced All my Cakewalk projects are in sync across all my PC's. I've always got access to my previous version in the sync directory. The disadvantages: The initial upload to the cloud took ages... but it was just a one off. Delta updates only take a couple of minutes at most. I've got two copies of my projects on each machine, which takes up disk space When working on another machine, I might forget to run the batch files to copy the latest to my project directory. The annual cost of cloud storage... not a biggie though for the piece of mind.

Make sure your Master bus is set to output to your audio device:

@OutrageProductions - is this happening in all projects for you? I've tried this in 2020.09 with both Kontakt and Komplete Kontrol and the instruments are fine after unfreezing. If you've got a sample project that has this issue, please zip it up and send it to @Jonathan Sasor and so we can take a look.

@micv - there's two ways to edit only a specific envelope: 1. Use the Track filter to select the envelope you want to edit: 2. Use the automation lanes: Also another thing to bear in mind: Deleting an automation lane does not delete the envelope - it only removes the lane. You can get the "hidden" lanes back by SHIFT + clicking on the show/hide automation button...

This is a pretty good video for getting you started:

For piano, I find a buffer size of 64 at 44.1K is the maximum I can tolerate with my Focusrite Scarlett (4.6 msec latency, 9.3msec roundtrip). Any higher, and I notice the latency. Increasing the sampling rate to 96K will more than half these figures, giving a input/output latency of 2.2 msec (4.4 msec roundtrip)... but this also increases the CPU usage. For a CPU intensive project, that might mean temporarily bypassing FX or freezing tracks to avoid drop-outs. A more extreme version of this would be to mix down the whole project to a stereo track, and temporarily archive all the other tracks. In some ways this can be more convenient as there's very little "thought" about it when switching - i.e. you select all, unselect the mixdown track, and archive everything else. Another alternative is to use an external MIDI sound module. I used to use my old Yamaha MU10 for this purpose, however depending on the part I was recording, the differences in response (e.g. velocity / feel) may or may not work as well when the part is played on a different piano sound. Which method I choose depends largely on where I am in the project. In the early stages, I'll use FX bypassing or freezing. The mixdown/archive approach is more useful for last minute overdubs. In all honesty though, I rarely need to any of this as I tend to treat tracking / mixing / mastering as separate tasks - i.e. I avoid trying to mix as I go along, and only use effects that contribute to the sound during the tracking stage.

You'll probably get more consistent results recording automation in Latch mode: This will stop the jumps from being created when recording automation. Notice the "W" button has an "L" in the corner rather than "T". An explanation of the automation modes can be found here: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.04.html ...but in essence, if you're creating automation for the first time on a track use Latch or Overwrite mode. Touch mode is more for tweaking existing automation, but to be honest, you'll probably find it easier sticking with Latch mode even for altering existing envelopes. The only gotcha is remembering to move your fader to the correct position when you stop your edits, and of course stopping the transport so it doesn't overwrite the remaining automation. @Will_Kaydo / @Simon Wilkinson - I did manage to repro your delete issue twice, but had difficulty reproducing again. What I did notice was that once the Jumps were all changed to Linear, the issue went away. So it looks like there's a corner case where it sometimes gets confused with jumps between nodes. We'll look into it. In the meantime, you can always delete the remaining nodes in a second pass. For the meantime though, give Latch mode a try and see if this works better for you.

If you're using per output or simple instrument tracks, make sure you're on the MIDI tab:

FYI Amazon UK are doing 2TB Crucial MX500's for £159.66 for the next 10 hours...

As @Noel Borthwick says, arranger tracks should be able to do this for you. You can do the two tier thing already by having two arranger tracks, or you can use one arranger track in combination with markers if this works better for you. You can also convert markers to / from arranger sections by using the time-ruler selection and the time ruler context menu.

IIRC you need to set your MIDI driver mode to UWP to use Bluetooth MIDI in CbB. This certainly works with my Korg nanoKONTROL Studio in Bluetooth mode, but it doesn't play well with my other MIDI interfaces (midisport 8x8 / midiface 8x8), so I use the wired connection with MME.

I'm still using my 18i20 - I love the pre's on that thing. However I'm likely to upgrade to an RME Digiface USB in the near future, allowing me to use my existing hardware / interface pre's via ADAT, while take advantage of the RME's excellent low latency drivers. The Digiface USB has 4 x ADAT inputs giving a maximum of 32 inputs / 34 outputs @ 44.1K / 48K. Anyone looking for a cheap way of getting an RME should take a look at the Digiface USB. An RME Digiface USB + Behringer ADA8200 will set you back around £500, with the option of adding or upgrading the ADA8200 to something better (e.g. Focusrite Octapre / Clarett Pre 8 / Audient ASP880) at a later date... or just adding a bunch of ADA8200 if you're happy with their pre's. If you've already got an interface with an ADAT out already, then you're half way there already.

FWIW I still use SoundFonts regularly. I sampled all the patches I use from my old hardware synths, and I chose SF2 as my preferred format for 2 reasons: 1. My soundfont player (SampleLord) is way more CPU friendly than Kontakt / Dimensions / Rapture Pro... PLUS I can use SampleLord on my V-Machine. 2. SF2 files are easier to manage, as they're one file vs 10's or 100's (in the case of sfz). At the end of the day, SoundFont is just a file format - it's no worse or better than any other format. Sure, there are advantages to some formats over others (e.g. release samples), but for me that's not an issue. If I export my samples as .nki, they sound exactly the same in Kontakt as they do as a sf2 in SampleLord.

As there's only 12 voices on the P-200, it should take less than 5 minutes to create a new ins definition from within Cakewalk itself: YamahaP200.ins

I'm not sure uninstalling ASIO drivers is necessary, or even desirable unless you're having issues... but in saying that, you should definitely uninstall ASIO4ALL, and any other "generic" ASIO drivers such as Steinberg's or Reaper's. ASIOLink normally requires your existing ASIO driver to be there in order for it to use ASIO for your primary interface. All other interfaces are then connected via WDM. I noticed zero difference in latency between my Focusrite ASIO driver and ASIOLink... but that was only because ASIOLink was essentially passing calls directly through to the Focusrite ASIO driver. If I had uninstalled my Focusrite ASIO drivers and let ASIOLink only use WDM, the latency would have been much worse.

There's a number of things that could cause drop-out, although since you're recording MIDI and not audio, the fact that your 7200rpm disk is 85% full shouldn't really have too much of a bearing... however: If this is your system drive, and you've not got at least 16GB memory, disk activity could be high due to memory being swapped out. If you've got audio tracks streaming from your disk (or samples for your VSTi's), then this could slow things down... especially if your audio tracks are on the same drive as your OS. Do you have CPU hungry VST's on any audio tracks, or any CPU hungry VSTi's that could be causing dropouts? I'm assuming you're using ASIO on your Focusrite? If not, make sure you are. You can try increasing your ASIO buffer size to reduce CPU load. Another option would be to freeze any tracks that are causing drop-outs due to high CPU usage (although you then might have [2] to worry about). Your CPU is more than capable of coping with most projects (it's pretty much on par with mine). So personally I'd recommend: Consider investing in an SSD for your system drive. You could then re-purpose your 7200rpm HDD for audio. Having your audio on a separate drive from your system drive can make a huge difference. If you can afford to get an additional SSD for audio/samples do so. For me, swapping to an SSD was like night & day - Omnisphere could take 45 seconds to load a patch from an HDD, whereas the same patch on an SSD is 2 seconds. Look at your memory usage in Task Manager and in particular the swap file usage. If there's a large amount of swap file activity, or your memory is over 75% usage, consider getting more RAM. Before you make any purchase though, try to ascertain what is causing the drop out. Look at the drop out code, and refer to this chart: https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.24.html . This should give you some indication as to what the underlying cause is.

I'm pretty sure CAL doesn't support Shape events... Shape events came along long after CAL was deprecated. CAL was primarily designed to manipulate MIDI data.

Every audio clip already has Gain & Pan automation. If you make it into a groove clip, you can change its pitch.

I'm using the Alesis Nitro Mesh kit. Here's how I've set mine up: - Alesis Nitro Mesh MIDI IN device enabled in CbB, but not the MIDI output device ( MIDI driver mode is MME ) - Insert Addictive Drums 2 as a simple instrument track - in AD2's map screen, I've created my own drum map to match the Nitro's notes. That's pretty much it. Seeing as the MIDI device is actually showing for you, I would look at the following: - First check your MIDI driver mode within CbB Preferences (MIDI -> Playback & Recording). If it's set to UWP, try setting it to MME. You need to have no projects loaded to change this. - Next, verify which MIDI notes are being sent. You could be really unlucky and find that the drum VST you're using has a completely different note mapping to the Nitro Mesh. Try inserting a piano VST or something that covers the full range of notes. If you're getting notes being played by hitting your pads, then look at the note mapping within your drum VSTi. If there's no way of mapping notes within the VSTi, then read up on creating drum maps. @Creative Sauce has a great tutorial here: https://www.youtube.com/watch?v=sIquUl-7NfE