The only way I know is more of a deterrent.
Open the Project Colours setup dialogue, find the colour you want, copy it to the clipboard. Close the dialogue.
Open the track colour picker, select a colour and paste. Close the dialogue.
Rinse and repeat, as they say.
The copy and paste functions are not visible, they’re on a context menu - right-click the “current” or “new” colours, or just use the keyboard.
Works for me, I’ve tried it.
But I don’t recommend it!
This is just a guess but they might be using different color systems - HSV vs HSL, both of which interpret color and light somewhat differently, and the inconsistency might’ve been a result of being coded at different times by different people.
To test this theory it might be worth converting that HSV value that you have to HSL for the other picker using a tool like this Convert HSV to HSL | Color Designer - at least to narrow down the issue.
Thanks. Clever idea! I tried it but the colors still did not match. Turns out this was added (or broken) in 15. Here is an AI summary:
In Cubase 15 Pro, the color picker has undergone significant changes, most notably removing the “color wheel” style selector that was present in version 14. Users now face limitations where HSV values are the only manually editable fields, with RGB values displayed as read-only, which can lead to discrepancies between entered and stored values.
Key aspects of the Cubase 15 color management include:
Color Space Shift: The interface has largely moved to an HCL (LCh) color space, which some users find less intuitive than previous RGB or HSV methods.
Dark Mode Limitations: The color picker does not allow pure black (RGB 0,0,0) or the darkest shades for custom schemes, restricting users to grayish tones for deep backgrounds.
Inconsistent Implementation: There are noted inconsistencies between the Project Colors Setup dialog and the User Interface Preferences, where color picking behaves differently and lacks a common paradigm.
Workarounds: Users can still define custom project colors via Project > Project Colors Setup or global UI colors via Edit > Preferences, and may need to restart Cubase for changes to fully apply.
Third-Party Solutions: To bypass these limitations, many users import extended color palettes from community-created files (such as the Cubase Extended Colour Palette.cpr) or use external tools like Cubendo for easier customization.
PS. I do not think the “work arounds” solve the issue of being unable to use the same palette colors with the Preferences>User Interface>Track Type Default Colors.