g_randybrown
I just set up a template for all strings (violin, viola, cello and bass).
The colors are all shades of blue (light blue being violin down to dark blue being bass).
Working on a string arrangement and bringing the velocity of say a violin up to a certain point makes the color exactly the same as say the viola (not the intensity of it's color but the color itself changes) to where they are the same color.
Are we talking about the same thing?
 

Yes, we are. It is for this exact reason that I use the following color coding for my string quartet arrangements:
1st violin = Gold
2nd violin = Green
Viola = Blue
Cello = Violet
Bass = Brown
 
I would never use the same color for these - how the heck do you distinguish them? OK, I understand your complaint about the Velocity/color tinting, but you are doing things the hard way.
 
As others have said, you can disable the color/velocity relationship, but to me it is much more useful to have different hues per instrument and leverage the velocity color fade.

brundlefly
Set PRVColorizeVelocity=0 under Preferences > Files > Initialization File (goes in in the [WinCake] section of Cakewalk.ini).

Wow thank you brundlefly!
Unfortunately I need a little elaboration though...in that path I'm seeing an option box and a value box.
Would I type in "PRVColorizeVelocity" into the option box and 0 in the value box? 
I hate to sound like an idiot here but I really don't want to screw things up even more.
Thanks again,
Randy

Yes, there is an example in the help screen.

stickman393

g_randybrown
I just set up a template for all strings (violin, viola, cello and bass).
The colors are all shades of blue (light blue being violin down to dark blue being bass).
Working on a string arrangement and bringing the velocity of say a violin up to a certain point makes the color exactly the same as say the viola (not the intensity of it's color but the color itself changes) to where they are the same color.
Are we talking about the same thing?
 

Yes, we are. It is for this exact reason that I use the following color coding for my string quartet arrangements:
1st violin = Gold
2nd violin = Green
Viola = Blue
Cello = Violet
Bass = Brown
 
I would never use the same color for these - how the heck do you distinguish them? OK, I understand your complaint about the Velocity/color tinting, but you are doing things the hard way.
 
As others have said, you can disable the color/velocity relationship, but to me it is much more useful to have different hues per instrument and leverage the velocity color fade.

Well my "clever" idea was to have them all different hues of the same color (lighter being high frequencies and darker being lower) so that I could easily see what was strings in a crowded PRV.
Before this I was setting the colors randomly and so my issue wasn't too noticeable but I may just copy your color scheme and commit it to memory.

Thanks Steve, if I didn't like it after setting it to zero can someone tell me how I would change it back? 

To revert the behavior set the value to 1 or delete the option completely

Thanks everyone!

I've just tried PRVColorizeVelocity=0 but the note colors look a little too light overall for me so I think I'm going to keep using the default setting.

While I agree they are much lighter, I'll take that trade-off (thanks again brundlefly) and will live with it.
Even like this though I still feel there is too much variance in color when selecting and deselecting an instrument (ie black to light grey or brownish red to some shade of pink).
What I'd like to see is the colors not change at all but have maybe an outline around the perimeter of the note(s) to see what's selected...okay, okay I know...I'm off to do a FR
Thanks again everyone,
Randy

brundlefly
Set PRVColorizeVelocity=0 under Preferences > Files > Initialization File (goes in in the [WinCake] section of Cakewalk.ini).

That's great.  Colour consistency in PRV is something that I've been missing since Sonar 6.