Alastair Cardwell

Thanks, If I can find some free time I'll experiment a bit for curiosity if nothing else.

Thanks for the explanation @msmcleod The VSTi in this case is Spitfire Audio BBCSO, the articulations are latched and just require a note for a short duration to switch from one to the other. This is an example of one I have the configured: - Kind = Note, Channel = Follow, Note/CC = E-1, Vel/CC = 100, Transpose = unchecked, Play At = Duration, Chase Mode = Full. In the documentation it states: - Full =All instances of this event from the beginning of the track will be sent up until the playback start time. From this explanation and the articulations being configured to send notes I would expect that when starting play back it would send a note for every articulation on the articulation map up to the play start point so should end up on the correct one. Am I incorrect in my interpretation of this?

Thanks for the reply's and sorry for the delay getting back to the thread. It is not a major problem as you can just start play from a bit earlier, just seems like it is not working as it should per the setting selected and is mildly annoying!

Hello all I am having a minor issue with the chase mode in articulation maps. While it is easy to work around I am not sure it is something I am doing wrong or a problem with Cakewalk so wondering if anyone else has come across this? I have the chase mode for the articulations set to full. If I start playback from this position it behaves as expected and the articulation changes to Rolls. If I start playback from this position the articulation changes to Rolls whereas I was expecting it to change to Hits as this previous articulation in the map.

I have been experiencing either the audio engine crash or a full crash to desktop with some projects when using Spitfire Audio - BBCSO. I have now found the cause so am posting in case anyone else is also having an issue. I previously posted about this in the this in the 202.11 feedback thread as it started happening after the update and I incorrectly thought it was something to do with the update. I have automation for expression and dynamics and have found that the crash was being caused by automation points being on top of each other or directly in line vertically as in the image below. In the former case you could not tell that there were two points until you dragged one and found there was another directly under it. I assume this happed while dragging clips around, once the points are separated there are no longer any crashes.

I would be happy to pay a lump sum for the new version but have no interest in a subscription only model. The problem with subscriptions is that there comes a point where you just can't afford any more subscriptions! Or circumstances can change and you have to cut back on subscriptions. If it is the pay or loose access to your work model then you have a problem.

I have had a couple of issues with crashing in recent versions, there are a few posts further back in this thread about one of the crashes. Another one I experienced that was repeatable was crashing when stopping playback when using VST instruments. I managed to cure this one by increasing the buffer size under Audio - Playback and Recording. I can't say for certain that this was specifically related to the latest version of Cakewalk as other things may have changed on my PC. It might be worth a try to see if it makes a difference for you.

Fully understand Noel's point about the plugin crashing but, as sometimes it is ok and other times it crashes there must be some interaction that is triggering it. I would like to find what that is and try to avoid it as I don't expect there is likely to be a quick fix from the developer. I have updated again to 2022.11 Update 1 and done some more testing. What I have found so far is that increasing the buffer size has reduced the crashing the point were it now only crashes at the end of playback. The sound will still stop during playback with the meters for the master bus and another bus that I have set up for reverb going to max which I assume is the cause of the crack from the speakers. The track meters continue to show normal playback levels. If I stop playback the meters for both of these busses remain at max while none of the track meters are showing any levels. Lowering the fader has no affect on the meters until they are all the way down. Moving the faders up any amount sends the meters back to max. If I bypass then turn back on the effects rack on these buses the sound starts to work again. I have tried deleting the bus with the reverb and removing all effects form the master bus but this makes to difference. Even with no effects bypassing and turning back on the effects rack restores the sound to working. I have also re-crated one of the projects from scratch with the same routing/effects and copied and pasted the clips from the original project to the new one. I have tested this one a several times over the last few days and it has been working flawlessly. Unfortunately this is a laborious workaround and as I have not found the actual cause I am not confident that the new project won't start to exhibit the same behaviour eventually.

Admittedly I didn't pay any attention to the time on the minidump, I just took the latest one that was there which must have been from after I rolled back. It is strange as after I rolled back to 2011.09 I didn't notice any crash and I played through the project several times without any problems. I also worked with it at least once since posting without any issues. I just opened it up to test again and it crashed first play through! Looks like there must be something else going on on my system that is a least somewhat intermittent. I have feeling this could be a tricky one to nail down. Thank you for taking a look.

Thanks for the feedback. The same project using BBCSO is working fine after rolling back to 2022.09 and also worked without issues in previous versions so it does appear to be related to something in the update. Is there anything else I can test or information that I can provide to help narrow it down?

Any suggestions or feedback on this issue? I notice the crash dump hasn't been downloaded. Is it incorrect? Do I need to send it somewhere else instead?

After installing 2022.11 I am having an issue with audio dropping out and Cakewalk crashing. Sometimes there will be a crackle from the speakers and audio stops even through playback is continuing. I will get a crackle from the speakers when clicking play and clicking stop. Clicking run/stop audio engine also produces a crackle. Sometimes there is a crackle during playback and Cakewalk crashes. I have done some troubleshooting and it appears to be related to the Focusrite Scarlet Solo interface. I tested with a different interface (Yamaha MODX synth) and did not experience the problem. I also tried all combinations of MMCSS settings, but it did not make any difference. Also updated the driver for the Scarlet but that also didn't make any difference. I have rolled back to 2022.09 and all is well again. I have attached a crash dump from 2022.11 Update 1. Cakewalk.exe.17432.dmp.zip

I am having this same issue with 2022.02 but it is not limited to scrolling with the mouse. With a long list clicking on the up or down arrow or clicking on the scroll bar above or below the thumb results in a jump to the beginning or end. Not a show stopper but annoying. Initially I thought a lot of instruments had gone missing until I realised what was happening!

@John T Thanks that was it. I was working on creating a template so that track was empty and the events option was greyed out. I had added automation lanes to control parameters of the VST and it didn't occur to me that the automation lanes themselves are part of events an not just the automation on the lanes. The workaround is to have a clip on the track so that events check box can be selected when duplicating the track. @Will_Kaydo Thanks for taking the time to look at this and create the video.

When I duplicate a track where I have added automation lanes the automation lanes do not get copied. Also if I have changed the property settings for automation like for example Write Mode = Overwrite these properties also do not get copied to the duplicated track and revert to defaults. When duplicating the track I have selected properties in the Duplicate Track dialog. I have looked but can't find any settings relating to this. Does anyone know if there is a setting I am missing that will allow the automation lanes and properties to be duplicated along with the track?