2015/11/16 23:46:51
icontakt
jkoseattle
The product is so bloated with features whose usability is only marginally examined. 

 
Agreed. Lots of good requests for usability improvement have been posted in the FR&I forums, but almost all have been unimplemented.
 
 
jkoseattle
Try opening two tracks in PRV that are two of those very close default red shades and look at notes with different velocities and I dare you to tell them apart, defeating even the workaround of coloring tracks differently! And then, one of the default colors is yellow, which, using the default PRV background of white and gray, makes that color basically unusable. 



Agreed again. I disabled the velocity coloring feature by registering PRVColorizeVelocity=0 in Preferences > File > Initialization File.
I also posted a feature request:
http://forum.cakewalk.com/Add-a-custom-color-area-in-the-new-X32015-color-palette-m3202079.aspx#3202079
 
 
Kev999
icontakt
Changing the clip foreground color (via Clip Properties Inspector) doesn't change the note color in PRV. This is a bug.

 
I do agree that it would be preferable for PRV to follow clip colour rather than track colour. But it's probably not a bug.

 
I think you're right, Kev. I thought the PRV note color was linked with the track header color via the clip foreground color (which is more desirable IMO), but the two must be linked with each other directly.
 
2015/11/17 12:11:42
jkoseattle
icontakt
 
Agreed again. I disabled the velocity coloring feature by registering PRVColorizeVelocity=0 in Preferences > File > Initialization File.

 
For a minute there I thought that would be a good idea. But then the buggy nature of the velocity bars and the aforementioned yellow-on-white type issues would mean that sometimes I wouldn't be able to tell the velocity of a note at all!
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account