Promidi

Ideally you should not have any of these issues when saving projects. In last 30 years of using Cakewalk, I have just saved projects to a folder with no read errors, no read only stuff. It just works. Something funky must be going on with your PC. Even though, even this should not be necessary, what happens if you run Cakewalk as administrator? Failing that, maybe drop a note to Cakewalk support (though not really being a Cakewalk issue per-see, they may say so) https://help.cakewalk.com/hc/en-us/requests/new Another way out there option: Because you are running Japanese Windows, maybe your Cakewalk by Bandlab also needs to be set to Japanese? Preferences - Customisation - Display > Language

Do you have another drive other than the C:\ drive you can save your projects to?

Do you have any Antivirus software (including Windows defender). Are all of your folders used by Cakewalk excluded from all scans (including that c:\tomorrow folder)

Yeah I would definitely lose those exclamation marks.

What language and locale is your Windows set to?

No I don't think so either. You might want to contact support. Make sure you mention that another Sonar user has also confirmed this issue. https://help.cakewalk.com/hc/en-us/requests/new

Track zoom level is one of those settings stored in a Screenset. Have you, by any chance, locked your screenset. If you lock the screenset you are using, and then change the Track zoom level, the Track zoom level will not return to what you set it to when the project is reloaded. Note: Every project uses at least one Screenset.

Maybe try this https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d

That sounds like a corrupted Windows issue, not a cakewalk issue. It could even be a hardware issue. How long has this been happening? Are there any events in the Windows Event Logs that might point to a clue. Maybe try a system restore to the time before this started happing. You might also want to check your system drive for any corruption - again, there may be entries in the Windows System Event logs that may indicate this. One other thing to check is that Windows updates have all installed to completion and you have rebooted. I am assuming you have performed a full backup of your project data. Other may have more suggestions.

Update or Reinstall your Vdist Runtimes (Scroll down to X64) Note: The latest version is 14.42.34430. You appear to have 14.32.31332 https://learn.microsoft.com/en-au/cpp/windows/latest-supported-vc-redist?view=msvc-170

Generative CAL Scripts.

Arturia moves in mysterious ways..

I definitely have not got ASIO4All or any of its variants installed. I am putting this issue on my PC down to an issue with the latest Focusrite drivers. As mentioned, on my pc, the 2020 Focusrite beta drivers does not exhibit this issue - and I have no issues with these drivers on my old rig.

I still can't see your MIDI channel of your MIDI track (underneath the MIDI FX bin). Note: That “in/out” that is set to Omni that I can see is the MIDI channel from your MIDI controller that the track responds to when playing live or recording. If your MIDI track’s MIDI channel is set to “None“, that the MIDI channels of the events themselves determine the MIDI channel sent to the Triton plugin. The Triton plugin might expect the MIDI data to be sent on a specific MIDI channel (probably channel 1). You have some MIDI events set to MIDI Channel 2. This may be be why they are not sounding. Wrong MIDI channel. Other plugins may not require MIDI data to be sent on a specific MIDI channel, because may be set to respond to any MIDI channel (a setting in the plugin itself). That's why the MIDI data is sounding on these other plugins. The solution here might be to set MIDI channel of your Triton Simple Instrument Track (SIT) to 1. This will override any MIDI channels that your MIDI events are set to in the MIDI track. As mentioned, I alway set SITs and MIDI tracks to specific MIDI channels. This give me control of the MIDI data that those MIDI tracks are sending on. Also, in Preferences - File - Initialisation File (Advanced), I add the option RechannelMIDI=1. That way, when I bounce clips in that track, The MIDI channels of all the events in that MIDI track get changed to the MIDI channel that the MIDI track (or SIT) itself is set to. This becomes important when you want to edit Controller lane events.

What channel is the MIDI track set to (if any)? Can you show us the contents of that MIDI clip using the Event List View. To me this looks like a MIDI channel issue. Personally, I set my MIDI tracks or SITs to a specific MIDI track rather than “none”.

With Focusrite devices (or at least the 2nd gen 2i2 and the 3rd gen 8i6), if I start Cakewalk or Sonar while playing audio though my browser (Firefox), I get a half a second interruption in the audio. However, this seems to only happen with their later drivers. This is why I am still on the 2020 Focusrite beta drivers (see sig). This particular version does not experience this interruption. Also, with the latest Focusrite drivers, if I have a standalone synth open that uses ASIO mode, and I start Cakewalk or Sonar, Cakewalk or Sonar does not see the Focusrite 8i6 audio interface at all. If I want to run Cakewalk or Sonar and a standalone synth, I have to start Cakewalk or Sonar first, then start the standalone synth. Again, this does not occur with the 2020 Focusrite beta drivers. I never really reported this to Cakewalk as I just put this down to the Focusrite drivers and live with it (staying on the 2020 Focusrite beta drivers that is)

Which audio interface are you using?

See:

What exactly do you want the MIDI controller to do in the middle of a song. What outcome do you want to achieve. If you say, “launch this track from an external midi controller”, I still don't understand exactly what you mean by “launch this track”.

What about issuing a CC7 > 0. Mind you, the plugin will technically still be playing the sample, just at a volume of zero (this is assuming Looptrack responds to CC7 events)

Insert cc123.mp4

...And I am sure there are many more things coming to Sonar 2024/2025 to be thankful for.

When the login and synchronisation issue first occurred, I opened a support ticket with Arturia. After a few days, I got a reply from Arturia (prior to the release of the updated ASC), and I was advised to do the license deactivate and reactivate cycle. After doing this, I thought the problem resolved itself. However after a while the issue returned. I did some of my own investigation. I found that, when I started an Arturia Standalone synth with Task Manager open, I noticed that two instances of the ArturiaSoftwareCenterAgent.exe process started, then one stopped leaving one remaining. Then an event appeared in the Windows Application logs with a C000005 error (Which is basically a Windows, something bad happened, not sure what). I thought, this must be an issue with the then version of Arturia's ASC which they will resolve soon. Now, after updating to ASC 2.8.1.2731, I too still got the login and synchronisation when starting any Arturia synth. I thought, bugger, they didn't fix it. But then I thought, I wonder what happens if I repeat the license deactivate and reactivate cycle with this new version of ASC. This appears to have solved the issue. No login and synchronisation issue when atarting an Arturia synth. Only one ArturiaSoftwareCenterAgent.exe starts and then closes. No remaining process. Arturia synth fully usable (not in Demo Mode). So what must happen now, when you start an Arturia synth, is that one instance of ArturiaSoftwareCenterAgent.exe starts, confirms licence status, and then closes. On my PC this happens quickly. So, yeah, try the deactivate/reactivate cycle.

Arturia released an update of Arturia Sound Centre. (now at 2.8.1.2731) Since updating to this version, deactivating and reactivating all my licences, I no longer have the log on screen temporarily appearing when I open an Arturia softsynth.

No, it is not possible to “launch this track” (whatever that entails) Once the Bank/Program change event is in your MIDI track, your external sound module will change the part to that Bank/Program at the time of the Bank/Program change event. I use multiple Bank/Program changes all the time in my MIDI projects. These change the Bank/Programs that are on an external SW1000XG card while the project is playing.