Thanks @ASM , much appreciated
That’s a really nice colour palette - I think I’ll like it better than the customized one I have used for years. Cheers
Just a FYI for other Cubase users: I was not able to open the Nuendo 14 *npr with Cubase 15.0.6 (freeze). After opening it in Cubase 14 and saving it as a C14 *cpr I was able to load it in Cubase 15, too.
UPDATE: There seems to be more to it than just a simple incompatability issue between Nuendo 14 and C15. Saving the new colour palette as default in Cubase 15 will also set the samplerate of this project to a new default (it shouldn’t, obviously). Afterwards, I can’t change the project samplerate in a new C15 project (which correctly displays the new colour palette) - Cubase will freeze.
Steps
open the N14 npr above in C14 and save it as a cpr
open the new C14 cpr in Cubase 15 and save the color palette as new default (Project → Project Colors Setup → Options “Save color set as default”)
open a new C15 project and the colour palette will be displayed as expected
at the same time your default project sample rate will be set to 44,1 kHz (in case this wasn’t your default sample rate)
try to set the samplerate from 44,1 to 48kHz and the project freezes
Does anyone else have this problem? Maybe it’s just my system, I don’t want to call it a bug, yet.
@twelvetwelve Do you have the colour palette as a cpr (maybe even at 48kHz) by any chance?
I made that initially with Nuendo 7 so maybe that’s why? It was re-saved on Nuendo 12. I don’t use Cubase sorry.
You should just be able to open it, save thr project colors as the default palette, then open your existing sessions as they are and load the new/default palette into them.
I opened the project normally with “File > Open…” and had no problems doing so. The sample rate is 44100, the colors are there, and no crashes occured (C15.0.6/W10).
The only thing that was a little strange was what happened when I made this color palette the Default. A new project created with Create Empty displayed the palette like this:
There’s also the other option of editing the XML directly and just swapping out the necessary parts. From memory (it’s been a while!) that’s also what I did when making them as it was faster to generate all the XML needed and then do a bulk replace.
That happens because there is nothing selected (you can see the palette window also says “No Selection”). The palette will go to greyscale until something is selected. Completely normal behaviour.
Is this the same one that Chris Selim gives away for free on his youtube channel?
It looks to be very similar if not the same.
Going back about 15 years ago, Seyoum aka Iro made a great pack that was very configurable and came in sets. Free, then later asked for donations.
I think the issue is that with developer updates, the colors slightly change which make ones like Seyonum worthless, unless it’s been updated to a newer version.
Frankly, for myself, the one Chris Selim distributes, works great. I think this one has been used as a base to configure others for different themes…such as turning them all to pastel shades.
I have work with a palette that had 300+ colors, and for me that is simply too many. The one posted here seems about the right size for me.
Okay, that didn’t work here. Maybe, because my default samplerate is 48k?
Yes, I can get to this point. My problem is the sample rate which cannot be changed from 44,1 to 48k. And it also seems strange that the sample rate from the Color Palette project was transferred as well the moment I save the color set as my default. This is not how it is supposed to work.
Yes, I was thinking about that, too. They reside somewhere in the preference folder, I think that’s another option.
Have you tried to set the sample rate to 48 kHz? That’s the weirdest part of all.
