Promidi

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).

Check your TTSseq.ini file for a SendLocalOff=1 entry in the in the [Options] section. If there is one in there or if there is no SendLocalOff entry, change (or add) it to SendLocalOff=0 You might also need to ad a SendLocalOn=1 in the same section This file is in the "%APPDATA%\Cakewalk\Cakewalk Core" folder Make sure CbB is closed and copy the file before editing. Another thing to look to check is that there might be some sysex data that is being sent when you open the file. Check the Sysex view to see if any are present and if they are set to Auto send.

I would say if not familiar with end markers, then you would not have entered one. Also, I had another think. If it was an End Marker, you would not end with wave file data at zero after the drop out. The duration of the resultant wave file would be up to the time stamp of the end marker. You say that here isn't any plugin or track that kicks in right at this mark. However, are there any plugins at all in the project? What happens if you export with Track FX and Bus FX disabled?

Now that you are using a Focusrite 2i2, have you set your driver mode to ASIO. This is in Preferences - Audio - Playback and Recording Note: I do not do Zoom.

Yes, that would do it. I was going to point out that you can set these track parameters parameters with a CAL script. The above would definitely set the key and time to zero of all MIDI tracks less than 256 to zero. You would have to remember not to accidentally save the CWP file and exit with the zero offset intact - you would lose any offsets previously set. Maybe do an undo after running this script (and saving the MIDI) before resuming with your project. If you were to use a CAL script to set the time offset to a non zero value, the value would only be in ticks. If you want milliseconds, you would still have to set the unit of time for each track one by one. Still a good and useful work around though. I am so glad that Sonar still allows the loading and execution of CAL scripts (and Studioware Panels for that matter)

I am wondering if this helps http://www.raisedbar.co.uk/InsDef.htm

Sounds like a good feature request. (same with Key+) You might want to consider posting this here: https://discuss.cakewalk.com/forum/8-feedback-loop/

I know this has been mentioned, but can you confirm and double check that there is no "End Marker" present in the project. CbB would ignore this if present.

What you might want to do is set each MIDI track tthat is routed to the modx+8 it's own MIDI channel. When you insert a MIDI track in Cakewalk, its MIDI channel is set to “none” by default. This means that the MIDI channel sent is determined by the events themselves. When you set a MIDI track 's MIDI channel, all MIDI events contained in the MIDI track will be sent on that channel instead of the MIDI channel of each event. I also send MIDI data to an external 16 part multi-timbral playback device. For my MIDI only projects, I have had 16 MIDI tracks routed to an external 16 part multi-timbral playback device (a Yamaha SW1000XG), all set to specific MIDI channels (1 to 16 respectively).