Because PLE can only select based on Colour Names, and not actual colours, it has never been able to select default tracks based on their default colours.
There could be a number of development paths to fix this, which would be easiest I’m not sure.
1.) In preferences, when selecting default track colours - allow users to pick colours from the project pallete thus, giving default colours a name in the background. One potential contention here, is preferences are global, whereas project colours are project based until saved as default - if that matters I’m not sure… Because PLE is also global.
2.) Allow PLE to select colours based on colour code rather than only name… Either by letting the user enter the colour code into PLE, or PLE auto-detects colour code and it’s up to users to enter/match their default track colours to ones that are also in their pallet. One contention here, is that users might some time later down the road, alter their default colours which would require them to also alter their pallete colours.
Just so that I can understand better. Why do you want to select tracks based on their default color which is set by type, instead of directly selecting tracks of this type defaulted to this color?
Just so that I see if I understand, using a simplified example:
You have 1 track (audio) which has the default color for this type (audio). Then, you maybe have another audio track with a different color. What you’re saying is that you want to select just the audio track with its color set to default and ignore the other audio track which has a different color?