msmcleod

Yes, it is the wave shell that is causing the re-scan every time. I suspect the toasts not closing are a result of the project loading a synth that is also being scanned at the same time. There are few ways around this ( in order of preference ): Switch to manual scan - unless you're constantly installing new VST's, there's really no reason to have scan on start-up or automatic background scan enabled; or Wait until the scan is finished before loading the project; or Turn off scan in sandbox ( I wouldn't really recommend this one though ).

This will do it - changing USB ports can cause Windows to treat it as a new device. To avoid this, I normally always plug the devices in the same ports and ensure I power up my PC with them all plugged in. The ensures that not only do they keep their device name, but their ordering remains the same ( less important for MIDI Out in CbB, but is important for MIDI in).

This isn't a bug - it happens when "Split MIDI Notes" is enabled. When enabled, any notes or active CC's are retriggered at the split point. The primary purpose of this is to support arranger operations, so that the status of any CC's at that split point are honoured regardless of where a section is moved. Turn off "Split MIDI Notes" and you won't see this behaviour.

The HUI protocol has been deprecated for a long time. If a genuine Mackie HUI comes up on the second hand market at a reasonable price, I may get one and improve the HUI support... but until then, we don't plan on doing any other improvements.

Things to try: 1. Turn off the splash screen in Melodyne 2. Make sure you've got a default algorithm set You may want to run it as standalone first to do this.

Have you enabled "Select Events with Sections" ?

There's threads on the Microsoft forum regarding high latency with Wdf01000.sys: https://answers.microsoft.com/en-us/windows/forum/all/wdf01000sys-latency-windows-10/41a8fbac-3c87-4b45-965d-9d6607f91ad9 ... and a bunch more on pretty much all of the DAW forums. While none of the suggestions completely cured it, the main thing seems to be: 1. Make sure your power scheme is set to high performance - i.e. both min/max CPU should be 100% 2. Turn off USB & HDD power saving/idling Also depending on how the internal hardware is set up, you may want to disable network and any other audio devices in case they're sharing resources with the USB port your main audio interface is plugged into. The best thing to do is google wdf01000.sys latency and read all of the posts - hopefully one of the suggestions might fix your issue.

The comp/looping enhancements in EA 2022.06 only affect audio recording at the moment. We did look at MIDI recording, but there were complications there so we've postponed that for a later release. The main issue is the automatic cropping of MIDI clips, and creation of new clips when gaps exist in the performance. This then causes extra splits at those points when recording stops. This behaviour is baked in at a pretty low level, so it's tricky to overcome. It is on our list of things to sort out though.

FWIW I've never managed to get any Antares VST3's working properly in Cakewalk. Using the VST2 instead is my workaround.

Either ASIOLink or WASAPI Exclusive will allow you to use all devices. However, unless you have their wordclock's sync'd you may find they record/playback out of sync.

You could try this:

Your could try deleting ctrlsurface.dat from %APPDATA%\Cakewalk\Cakewalk Core\ while Cakewalk isn't running, and restart Cakewalk.

Either: - Save your workspace as a custom workspace; or - Set your workspace to "none"

Just a heads up... the option to open parent track folder when changing track focus currently defaults to on. We've changed this to default to off for the main release, but this will only affect those who haven't installed 2022.06 EA. If you don't want this option on, just turn it off under the Track View options menu. It's a global rather than project setting, so it will remain off once you change it.

This is an old bug, but it was a simple fix. I noticed it was also ignoring track envelopes / articulations if they were in the selection - this has also been fixed. The fix will be available in the main release.

It was highlighted in the release notes in the post at the beginning of this thread: Option to open parent track folder when changing track focus The Track view Options menu contains a new Expand Track Folder on Track Focus option, which automatically opens the focused track’s parent folder if it’s currently closed. This behavior may be desirable when using control surfaces or changing track focus via the Console view. To disable this, just uncheck this option within the Track View Options menu. It's there for people who use the primarily console view, or control surfaces along with the console view.

You probably need to ensure "Select Highlights Track" is checked within the Mackie Control Surface dialog:

This is the equivalent of pressing Function Key F3 on the Mackie Control, which you can map to what you need within the Mackie Control Surface dialog. FWIW - setting it to "Keypress: SHIFT + F3 " will make it open the metronome settings dialog - setting it to "Keypress: F3" will allow it to toggle the record metronome.

I don't know why this didn't occur to me before, but if you lock the Left & Right faders together within the console view, then keeping the Mackie Control set to controlling Master 1 will adjust both faders:

Just to be clear, if "Extend Takes to Punch Out Time" is off when recording in comp mode and you've recorded more than one loop iteration, it will now ALWAYS extend the clip to the end of the loop. The Extend Takes to Punch Out Time option is of use when you want to add to a single take to an existing set of comp takes, and don't want the split behaviour. To put it another way: Extend Takes to Punch Out Time off + Comp Mode with > 1 loop iteration: last take is extended to end of loop Extend Takes to Punch Out Time on + Comp Mode with > 1 loop iteration: last take is extended to end of loop OR punch out time... which ever is earliest Extend Takes to Punch Out Time off + Comp Mode with < 1 loop iteration: take is left as is, with clips being split at record end time Extend Takes to Punch Out Time on + Comp Mode with < 1 loop iteration: take is extended to punch out time Extend Takes to Punch Out Time off + SoS or Overwrite Mode, with or without looping, regardless of # takes: take is left as is, with clips being split at record end time Extend Takes to Punch Out Time on + SoS or Overwrite Mode, with or without looping, regardless of # takes: last take is extended to punch out time

If you click on "Insert Audio FX..." another menu will appear listing all your FX. FYI - the "..." at the end is used an indication that you need to select it before proceeding.

Track Templates are probably the easiest way to go, but if you just want a particular combination of effects to add to an existing track, you can save it as an FX Chain preset. To do this: 1. Right click on the FX Chain and choose "Save FX Rack as FX Chain Preset". This will then become available at the bottom of the Plugin Browser under the "FX Chain" section. 2. To reuse it, just drag this preset from the Plugin Browser into the FX bin of your track. You can right click->"Extract FX Chain Plugins" on the FX chain after dragging to unpack them all again if you wish.

It looks like the engine gets re-initialized after pausing. I've found a workaround that might work for you: 1. Remove the MCI command 2. Set a loop point of one beat length in the silence before the main music starts and enable looping 3. Start playback. You should now be able to play your piano part while it's busy looping over silence When you're ready to continue playback, just press the "L" key to turn off looping and the song will continue without interruption. I tried this with an organ patch just to ensure it wasn't being interrupted and it worked for me.

@chris.r - is this still happening for you in the 2022.06 EA release? If it is, PM me a copy of your project ASAP.

The interruption is likely caused by the transport pre-roll. I think the trick is to add a pause event just before your music starts, starting playback before your start playing your rubato intro, and continuing when you want the rest to start playing. This is how I would do this: 1. Move the whole of your song within Cakewalk by a whole measure. 2. Insert an MCI Pause command just before the new start time of your song, so it's still within in the silent measure but before everything else starts. Depending on your ASIO buffer size, you may need to leave a small gap before the start time (e.g. an 8th or 16th note or so). When you play: 1. Start playback first - it will play a blank measure then pause at the MCI pause command. The key thing here is, that pre-roll has already been performed. 2. Play your rebato intro 3. Press play again as normal to continue playback