Promidi

@dogufoDid you get this sorted?

The description for this forum is “Provide feedback on features, ideas and requests for future releases of Cakewalk by BandLab.” However, can feature requests for Sonar 2024/25 also be placed here? If so, should not the description be “Provide feedback on features, ideas and requests for future releases of Sonar 2024/2025”?

The SY77 is a 90s synth. It uses 5 pin din MIDI cabled. The OP needs the driver for what ever MIDI device they are using. The OP also said “lately”, which, I believe implies tat it as working, but now its not.

I believe this would explain why Eventides BlackHole Emmersive only provides two outputs when used in Sonar/CbB, even though it is a surround sound reverb. The “at present” in your statement, gives me some hope that one day this might change..... Cantabile 4.0 does indeed show all of BlackHole Emmersive’s plugn outputs.

Yes.

There must be something you have missed. Is the SY77 actually transmitting? How have you confirmed this? For the MIDI track that is set to receive the SY77 MIDI data: · Is the correct MIDI channel set. Is the MIDI track meter moving when you press keys on the sy77 · Is input echo on? What have you tried so far?

Have you tried Real Time Export? Are there any other plugins in the project or just Spire? What else have you tried?

Scratch that , I downloaded the demo..... Looks like the reverb types are very small NRPN values and you cannot MIDI learn the reverb type like you can other parameters. Also, in Cakewalk’s PRV, only two values actually change the reverb types between Plate_1 and Aura

How many reverb types are there?

Because NRPNs have such a high number of possible values (16384), any graphical method of editing NRPNs (in any DAW) will give you this issue when editing really low values. The values will, however, also show in the Event List View. In there you will be able to enter (or edit) specific entries.

Let's hope the bakers restore at least the ability to change colours. I can understand doing away with custom bitmap elements with Sonar being vector based, but custom colours should have been retained (IMHO).

It should be noted that if you open the PRV of any MIDI track that is routed to any VST plugin that has automatable parameters, those automatable parameters will also be available in that MIDI track’s PRV NRPN parameter dropdown. Curiously, the Cakewalk user guide does not mention this (not that I have found anyway)

Do any of these files have any sysex info therein?

As you know, holding CTRL while adjusting a parameter that is part of a group, temporary overrides that grouping, allowing one to adjust just that one parameter. The issue is that to create a quick group, you also hold CTRL. It appears that one cannot create a quick group using parameters that are already part of a group, because the function to temporary override that grouping prevails. What we need is a key modifier to allow the temporary quick grouping of parameters that are already part of a group.

No problem here (Malwarebytes 5 Premium) That would be a false positive. Might want to let BOZlabs and Bitdefender know.

I would go through soloing and muting tracks to help troubleshoot.....

The way I interpret it, for CbB to continue to be activatable, this new update is necessary. I would not chance it.

You cannot, because of this: (from the Updated to 29.09.0.120 release notes.) Note: All users should upgrade to this build as prior builds do not support the new back end that is used for activation. https://discuss.cakewalk.com/topic/74522-current-cbb-release-202411-updated-26-nov-2024/#comment-517554

Try these. In Preferences - File - VST Settings > enable Send All-Notes-Off Messages on Stop In Preferences - File - Initialisation File (Advanced) > set a PanicStrength=1 option in Cakewalk.ini.

Does your audio interface come with true native ASIO drivers or is it a variation of ASIO4ALL? An audio interface that comes with true native ASIO drivers is always recommended. ASIO4ALL is never recommended for a professional set up. One other thing you can try is Driver mode WASAPI/Exclusive.

Are you saying that all tracks are louder - but the e-drum kit is the only track that clips? This sounds like an over all project issue rather than just confined to the e-drum kit..... Sounds like there is a double up somewhere or maybe there is a gain staging issue....

I have to admit....... that's true. Mind you in my case, it could be that I have a script that starts the "NTKDaemonService" service before it starts Native Access, and stops the "NTKDaemonService" service after Native Access has closed.

Whenever I have updated just one Arturia product, ASC has always updated that product very quickly. Rarely had an issue.

It's not ASC. If you have any collections, it's the fact that multiple products have to be downloaded updated at a time. Any brand that has collections or bundles will take a while to update. I rarely have any issues with ASC - the only time I do is during those rare occasions when Arturia’s server is down.

If you have never saved then sorry, it's lost. I think for autosave to have worked (if enabled), you have to have saved at least once (if this is not correct, can someone please correct).