Promidi

Dark mode for the Augmented series..........???? Nope! They still burn your retinas out. Oh and they still have not fixed the issue the SQ80 has with using sustain of any patch with Unison enabled. Lifting sustain silences notes that are held down. I reported this over 12 months ago - and they even reproduced it at they end and acknowledged the issue.

Open Project. Set CbB windows how you like them. Lock screenset. Save project.

As I said, I have never experienced this. Maybe contact support@cakewalk.com

Insert CC72 values.

Depends on how programmable these buttons are on your MIDI controller in term of what MIDI events you can program them to send. Configured as a standard MIDI controller and not a control surface or an ACT controller, I can do this with the Edirol PCR-800 This is how I do it here.

Still use a Yamaha SW1000XG here.....

Just hope you have a nice big SSD drive. Stormdrum 2 12.5 gigabytes Stormdrum 3 87 Gigabytes Hollywood Fantasy Percussion 10 Gigabytes 109.5 Gigabytes all up.....

You probably should update to 2024.08 Build 108. Can you post a video recording of the issue. Here is how this works with CbB. Change Note Duration.mp4

On the Gong SIT, make sure the plugins MIDI out is deselected. On the Bodhran SIT, make sure its input is set to a specific MIDI controller and specific MIDI channel.

Never had this issue with recent versions of Cakewalk. Which exact version of Cakewalk are you using?

"pause just the event view display" - slightly different to what the OP was asking. The OP said "It would be ...... handy if that could also apply to the Event List." Are you wanting the scroll lock to effect the ELV only while everything else scrolls? And no.... I did not have to change any setting. Scroll Lock affected all screens - even ELV.

I just tried it here. Scroll Lock does indeed stop the view from scrolling in the Event list view.

Are all of your MIDI tracks inputs set to specific MIDI channels and MIDI devices other than “all”. Are all MIDI outs of any vsti plugin deselected?

Velocities are set per note as part of the MIDI note on event data packet. If you are using the PC keyboard, then the note velocities would be a constant value because your PC keyboard cannot generate velocity information in the same was a MIDI controller can. Velocity is actually how hard (or fast) each key is pressed as you play. What you are probably meaning is track volume. The track volume is probably set to a high value to start with. then as playback gets further into the track, the part lowers in volume. You probably have CC7 or CC11 MIDI events after some of the Note On events have been encountered. Use the Piano Roll View or Event list view to check for these CC7 or CC11 MIDI events after some of the Notes Note: I recommend you eventually plan on getting a MIDI controller that can transmit velocity information.

Need more information. After you have imported your MIDI data, where have you routed your MIDI tracks to? Which VSTs are you using> Does the MIDI data contain any NRPN or RPN events. Some VSTs stop producing sound when they encounter NRPN or RPN events. As mentioned use the Event Viewer to check for non note or non CC events. MIDI channels might also matter. I always make sure any MIDI tracks or SITs (Simple Instrument Tracks), I have in a project, have their respective MIDI channel set to a specific MIDI channel rather than “none”

I have had AD2 since it was released with Splat and have never had your issue here Are you using the latest version of the AD2 installer (which is 4.12)? I guess you would be because when you run an outdated XLN installer, it auto-updates itself (well it does on mine). I also used this opportunity to update AD2. I am going to assume that you have configured the correct paths for the VST3 and DLL file in the XLN installer.

Beats me..... Maybe your default startup project template is corrupted. Have you tried New Project, but choose “No tracks or Buses”. The create an audio track and then right-click its FX. You might want to flick an email to support@Cakewalk.com. Be prepared for them to tell you to do a clean reinstall of Cakewalk. See: https://help.cakewalk.com/hc/en-us/articles/360034066393-Clean-Install-Cakewalk-by-BandLab

On my system: HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\Inventory Obviously, export this key to a reg file before doing anything..... And remember, this might not even work for you.

Looks like something is corrupt with your VST scan tree in the registry. I once had some plugin weirdness. (in my case, the scan button in preferences and the plugin layout manager was greyed out) Even going to Preferences - File - VST Settings and doing a RESET did not fix it. I ended up going to the registry and deleting the entire VST inventory. Then I did the RESET then scan to fix it. (I believe that rebuilds the VST inventory from scratch. That fixed it. First this I would try in you case is to go to Preferences - File - VST Settings and do a RESET then scan.

From track view, press H to bring up the Track Manager (or track menu > Tracks > , Track Manager) and make sure your buses are visible. Also make sure your Bus pane is visible. Press SHIFT+B to Show/hide Bus pane.

What make and model sound card do you have?

Where have you routed your MIDI track do? This either needs to be an external MIDI device, or a VSTi plugin. Otherwise you are just sending data to nowhere. It's a bit like trying to send print data without a printer.

CTRL+D only duplicates to the right. There is no keyboard short to CTRL+D to duplicate to the left by default The way I personally would do this is create a CAL script to copy to the left, then keybind a key shortcut to that CAL script. Be careful with CAL scripts though. Deleting events straight after using some commands can crash Cakewalk.

Are Bass.dll, Bassmidi.dll and BassMidiVsti.dll all copied to the same (VST) Folder? Is that folder listed in preferences - File - VST settings > VST scan paths? If yes,to above, did you try a RESET then SCAN? Did you turn on VST scan logging to see if that reveals anything?

No. Could it be that you have loop points set very close together?