Promidi

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.

Like any controller number, CC numbers can be anything you would like them to be. Most synths have a MIDI learn function where you can map any controller nunber to any parameter. This is totally up to the synth. Not all synths allow this. (perversely, Native Instrument's Massive X does not) However, there is a Roland General MIDI (and Yamaha XG) standard where certain controller numbers are assigned specific functions. For instance, CC7 is usually volume, CC10 is usually Pan, CC 72 is usually release time, CC73 is usually attack time, CC123 > 127 usually stops any notes if they are still sounding (for what ever reason)..... and so on. However, synths are under no obligation to follow these standards. It just so happens that Rapture Pro does. The way to test is to insert a Simple Instrument Track (SIT). Then in the Piano Roll View (PRV), insert some long notes (about a whole note). Then insert a CC123 > 127 followed by a CC123 > 0 somewhere under those notes. If your synth goes silent when the CC123 > 127 is encountered, then that synth does indeed respond to the CC123 > 127 MIDI event.

With the scenario you have described, the synth would need to respond to CC123 (which is all notes off) If your sampler allows for a very long release time or responds to CC64, then the note will still sound after playback has stopped. In that case, the panic should still work.... if the note off events does not do it, then the CC123 should. Not all synths respond to CC123 > all note off. I just tried this with Rapture Pro with a long sample. I used a sustain event, before the note, to cause a hung note after I stopped playback (expected). Even then, the MIDI panic stopped the note. When I restarted the audio engine, then note did not resume. I also confirmed that Rapture Pro responds correctly to CC123. It does. So, really, it's down to the individual synth as to how it responds to MIDI Panic..

Don't know what to tell you..... MIDI panic works here every time. (has for ages) Maybe contact support support@cakewalk.com

Objectively, does this synth really do that much more than any other synth with two saw, sine, triangle, square ware oscillators, LP, BP filters and volume and filter ASDR cannot do? Something like AAS Ultra Analog VA-3, or Pigments, or many other Arturia synths, like Prophet 5 V, OP-XA v, etc (all of which I have) Even at $AU103 (after conversion), it would take a bit of convincing to get me to pull the trigger on this one.....

Sounds like you are pressing the engine stop button..... If you are pressing the MIDI panic button and the notes are not stopping, that's down to the VST. Setting panic to 1 should work. It works by sending a note off for every note. This works every time here. So if the VST is not responding to PanicStrength=1 something is really wrong with the plugin itself. Just to note. Make sure you: ­· Have exited Cakewalk while editing the Cakewalk.ini file? · Are editing the Cakewalk.ini in the %APPDATA%\Cakewalk\Cakewalk Core folder (this is for Cakewalk by Bandlab) . Are adding the “PanicStrength=1” under the [WinCake] section.

Probably not going to happen.....

Sorry and am not quite sure what you mean by “is it possible too launch it from an external Midi Controller”. Please describe, in detail, what you are wanting to achieve?

Yes. I can send Bank/Patch change MIDI events from a Edirol PCR-800 to Cakewalk. If I arm a MIDI track and hit record, Cakewalk records any Bank/Patch events sent from the PCR-800 into the MIDI track. You do have to make sure that “Patch Changes” is selected in Preferences - MIDI - Playback and Recording.

See: https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.089.html

Even though depreciated ages ago....even CAL scripts can be programmed to perform algorithmic music generation. I have written a few myself recently that utilises the Random command to generate usable musical and rhythmical phrases.

Did you leave the Nvidia drivers removed or did you (clean) re-install them afterwards?

Are you using Cakewalk by Bandlab 24.07 Build 108 - If the version is too old, Activation will fail. I am assuming you are activating using Cakewalk by Bandlab's Help menu and the browser window that follows Maybe try doing this after a fresh reboot.

Yes, it activates and deactivates the entire prochannel for that track. See: https://legacy.cakewalk.com/Documentation?product=SONAR&language=3&help=ProChannel.03.html

Do you have a standalone softsynth that you can test that your keyboard is working correctly. What else have you tried? I am assuming you have checked that you do not have a Control Surface using those MIDI ports.

That would be down to the INS file. With the SW1000XG, there are about 1536 patches to choose from ... many using the bank parameter to get to them. With my SW1000XG file, I do not have to worry about the banks.... the INS file contains them all. All I have to do is select the right patch name from the drop down and the right bank/patch number gets inserted. I nver have to worry about actual bank or even patch numbers. I have done it that way for about 25 years using various iterations of Cakewalk.

I also have ran the Arturia updates via ASC and I have no issues with any of Arturia's GUIs (including CZ V 4.3.1.5024). My PC specs are in my signature. Strictly as a test and only very temporarily, what happens if you disable your NVDIA drivers and then run a problem synth (like CZ V) Have you tried uninstalling and then reinstalling your NVIDIA drivers, this time a doing clean install? Are you in a position to temporarily replace your RTX 3080, just to rule out a possible hardware issue with your RTX 3080. Yes, I know all other programs that require the NVIDIA GPU are working fine. However, Arturia might be using a section of the card that other programs may not be - and that section may be faulty. A real long short, but just to rule out that possibility. Other than that, I am quite out of ideas....

Only Sonar 2024 lets you use use articulation maps to specify offset delay (in ticks or in milliseconds). In CbB, the only way to set an offset delay is in the MIDI or Simple Instrument Track's inspector - and that is only in ticks.