msmcleod

It's probably more to do with your audio interface / audio interface driver. When the PC wakes up from sleep, the status of everything (including the audio interface driver) is restored. However if the actual status of your audio interface mismatches what the driver thinks it is, you'll get these sorts of issues - at worst you could get a crash. You could try turning the engine off then back on again within Cakewalk to see if this solves things: The only other alternative is to save your project and close Cakewalk before putting your PC to sleep.

Try this:

It's still there from what I can see, and the Event's View hasn't been touched for a few releases now. Maybe you've just not scrolled down far enough?

I tried the upgrade using both older projects and also a test project I made just before I upgraded. I didn't get any issues, but then I can't remember if I'd actually upgraded to the early June or not. It's possible (if not likely), that I was on the previous version before upgrading.

One gotcha with SI Bass that gets me every time, is the fact that it's transposed down an octave, while still only playing the range of a bass guitar. In other words playing A2 in SI Bass will play the open A string on the bass (whereas on GM / GS you'd play A1 to get the same note). If you play a A1 in SI Bass, there will be give silence because there's no lower octave A on a standard tuned bass guitar. The answer is (for this issue anyhow) is to transpose the MIDI track up an octave.

fair enough - although personally I just freeze the track, or if I need to keep it copy the frozen audio to another audio track

Yeah, the split instrument track is basically the audio & MIDI tracks separated. I almost never use split instrument tracks nowadays, as I hate the fact I've got twice as many tracks, and also it makes it less clear what is a real audio track and what is actually just a source for instrument audio. Nowadays you should be able to just about everything you could with split instrument instrument tracks with Per Output Instrument tracks. I think we've sorted out all the loose ends such as the Replace Synth scenarios, automation etc. If anyone can think of anything you can't do, please let me know...

Unless I'm recording quick sketches, I pretty much always track through analog pre's. Occasionally I use a hardware compressor (mainly on bass guitar), but most of the time I'll compress ITB. The only analog hardware compressors I've got are in my TFPro P3's (same as JoeMeek MQ3), which are optical, and the TFPro HooterSound B1, which is a VCA compressor. Both units are very coloured, so I'll only use them if it suits the sound. The P3's compressor is pretty good for spoken word though. My Alice 828 has a nice sounding limiter on it which works well. It's been handy for overheads in the past, as long as it doesn't have to work too hard... but I rarely take it out of the studio nowadays (and my studio is way too small for real drums).

@Klaus / @azslow3 - This has been fixed and will be available in the main 2021.06 release when it's out of EA. There was also an issue with the Bus Send Enable labels not being shown... this has also been fixed.

I suspect the actual size of the SSD is larger than is available to the OS. Most SSD manufacturers recommend you leave 10% or so of the SSD unformatted so it can re-allocate blocks from there if any blocks from the main partitions fail. So even if blocks do start failing after 7 or 8 months, there's probably enough spare good blocks to keep it going until around the time Apple decides your Mac is too old to run their latest OSX offering.

Switch to the MIDI tab - you can insert MIDI effects there:

@Terry Kelley - in a lot of cases, you can just use the "Append Instrument Track" command. This will create a new instrument track (i.e. combined Audio & MIDI tracks), assigning the audio track to the next available audio port, and the next available MIDI channel. Before doing this, I'd recommend you set the MIDI output channel of the existing track to Ch 1 (by default it's "None" for simple instrument tracks, meaning it can receive on all MIDI channels). You can do this in the inspector, by switching to the MIDI tab: Changing it to Channel 1 will ensure the next MIDI channel assigned is Ch 2, and the audio port will be the second one. If you don't do the channel change the sequencing of Audio / MIDI channel pairs could get confusing. I've pretty much stopped using Simple Instrument Tracks now, instead leaving my synth options as follows: The only difference between this and a Simple Instrument Track, is that the MIDI input output will be set to Ch 1 instead of None. Apart from that, its identical to inserting a Simple instrument Track. But it does mean that I can use "Append Instrument Track" to add new tracks to the existing synth instance without worrying about my MIDI channels getting confused. EDIT - I meant to add... although this will add the new instrument track, and assign the MIDI/Audio parts accordingly within Cakewalk, you're still going to have to configure the MIDI to Audio output routing within the plugin itself - i.e. you need to use the plugin's own UI to tell it to output MIDI Ch1 to Audio Output 1 & MIDI Ch 2 to Audio Output 2 etc. Unfortunately the method of doing this is completely different for every plugin.

I guess this depends... if you're happy having the aux tracks hidden in either the track view or console view, you could hide them in one of those views and set your control surface to take their tracks from the one where the aux tracks are hidden.

If set up properly, articulations do chase. They're set to chase before any other MIDI events. Make sure the chase mode is set appropriately within the articulation map editor. For simple key-switches, the "Note" chase mode should suffice. For more complex articulations, use the "Full" chase mode, which replays all articulations up to an including the start of the playback position.

I rarely need to send MIDI to multiple synths, but when I do I either: 1. Copy the MIDI as linked clips to the other synth tracks; or 2. Have a single MIDI track with its output set to a loopback device (e.g. http://www.tobias-erichsen.de/software/loopmidi.html ), then have the input for the synths fed from the input for that device.

You should be able to import it from C:\Cakewalk Content\Cakewalk Core\Instruments\Korg.ins ... but yeah, you'll probably have to add the expansions yourself.

If the bottom mic as 90 degrees, it's not going to be completely out of phase, so you'll need to use your ears to tell whether inverting the phase works for you or not. Alternatively, zoom in on the waveforms of the top/bottom snare, and see how the peaks and troughs of the waveform align between the two tracks. If they're mirror images of each other (i.e. when one has a peak, the other has a trough), then the phase needs to be flipped (usually on the bottom mic - you don't want the top mic to be out of phase with any bleed from the overheads). If they waveforms aren't mirror images of each other (i.e. if one has a peak, the other one also has a peak), then don't flip the phase. You can try various mic positions until you get the right sound, or alternatively just use the one mic pointing towards the snare shell.

It's not a bug. As @Starship Krupa says, if you've got "Display Muted Clips in Parent Track" and "Display Ghosted Data" unchecked, muted clips will be hidden.

Apparently you can bypass the TPM 2.0 requirement by replacing Windows 11's appraiserres.dll with the one from Windows 10.... see: https://winaero.com/how-to-install-windows-11-without-tpm-2-0/ ... and scroll down to the "Modify the ISO image without using UltraISO" section I'm not sure if this will be enough though... apparently if you're using an Intel chip you also need a 8th gen or greater.

Looks like my DAW PC is in the same boat... better start saving up for a new DAW PC!

A workaround was put in a few releases ago. If you've imported the Triton .ins files into Cakewalk, clicking on the patch browser will allow you to choose them:

If your instrument tracks are simple instrument tracks, you'll need to split them to get access to the underlying audio track. You can then set the audio track's input to the synth's audio output.

This is the one I tend to use too.

This sounds like a driver issue. I'd recommend re-installing the A & H drivers. If you're connecting through Firewire, you may want to re-install your Firewire drivers too.