sjoens

Don't remember if Sonar default themes are separate files like .sth files or hidden internally. but I suspect the new color theme files will be similar to .clr files that are exported/imported thru Preferences or Menus to mildly alter them.

If it's ARA, it's RegionFX. The fact they show up in Plugin Manager and Insert FX lists as well can be confusing.

Sorry, not sure how that would work with onboard Realtek sound as it only provides microphone inputs. However, try these: 1. Change Windows default format to 16 bit, 44,100 Hz or to the same as Sonar 2. Make sure Signal Enhancements is deselected (yours is selected) 3. Double check Audio enhancements and Spatial sound are deselected or turned OFF after each Windows update

Which list do you see it in? ARAs are normally in the RegionFX menu and a clip's right-click menu. https://docs.aurallysound.com/blog/ara_plugin_setup_daws

According to the one Lukasz posted, they are simple text files containing ARGB hex code and True and False show options. The old .clr color set files were also text editable using a unique color code not easily decipherable.

True, but wouldn't take much to clean it up. It had multiple categorizes to help narrow down elements, tho many were incomplete. My dream is to right-click the header of any view for a 'view exclusive' color edit window.

Nice! Mine seems more compact tho, and, where's the global Set As Default button??

Question: Unless the Theme Editor will eventually affect more than just colors, why not simply update the color changer already in Preferences? If the two reside in tandem, will they affect the same elements, or will one override the other?

And a screenshot of your Export window settings. To insure sound consistency, you can record the entire mix real time to a stereo track from the hardware output. The resulting audio can be dragged to desktop (wait for the process bar in the Transport module to complete).

Curious why so many have been reporting for weeks the red toast and it not activating.

Each view should have it's own customization w/o affecting other views. It became an issue with X series because it was never meant to be user customized. I was hoping it would be fixed with the all new UI venture.

Sounds like someone's still trying to find himself... Mine says @userxxxxxxxx, not my login name.

Still like to know how some users are getting 5 octaves when most only get 3.

Not sure if that applies to CbB but I'm currently testing it on my Win11 system and it's working correctly there. I will miss Win10 but it's just too buggy anymore and sanity is too valuable of a commodity to mess with going forward.

Bouncing clips would sometimes remove clip names but I've never seen tracks lose their names so not sure what would cause that.

My guess is most users use one or the other, not both, so they never noticed.

If you keep the default name, Replace synth will change it. If you type in a new name, Replace synth seems to keep the one you typed forcing you to change it again.

Unfortunately the reference guide uses screenshots from CbB with raster graphics, so not a good reference for this.

Just checked it on a Windows 11 system and it works as expected, so it must be a Windows 10 issue specific to my laptop. Just one more glitch telling me it's time to retire this one.

Most bizarre issue with new 34" Samsung ViewFinity S5 monitor (3440x1440) when it's zoom is 125% or higher. Issue: Oversized buttons and text. Affects: most Cakewalk plugins. Issue persists when UI is opened after screen zoom is set to 125% or higher. No issue if screen zoom is 100% before UI is opened even if zoom is changed afterward. No issues with 29" LG Ultrawide (2560x1080) monitor. Only happens with plugin inside Cakewalk. Standalone displays correctly.

If you have Boost 11 it shows graphically what's happening to the sound.

Not all mouse sensitivities are created equal, so the slightest movement in the wrong direction can be applied before you even think you moved the mouse.

Interpret this as you may, but if Cakewalk has proven anything over the years it's how different it operates on different systems by different users. The magnetisphere may be messing with you as well.

Holding Shift should lock the clip horizontally when dragging up or down to another track. Make sure you're not moving the mouse even the slightest bit right or left when dragging as it can be touchy. Other wise it could be a bad key so check both left & right Shift keys. Then try a different keyboard.

Today the window opened normally when I posted in another thread. Then I watched it switch to this broken one before I started typing. So something's misbehaving. Maybe this glowing symbol on the lid has something to do with it... ¯\_(ツ)_/¯ Probably explains everything.