chuckebaby

I believe he already tried  Duckbar
http://forum.cakewalk.com/FindPost/3456716
 

Hey chuckebaby, I'm having a weird problem with that link (that page doesn't allow me to scroll), so I can only see what comes up on the page's initial view.  But I was able to see something that zoffmeister wrote, and the rest of this post replies to that:
 
Zoffmeister wrote: "I tried Duckbar several years ago for this very reason but track strip colour wasn't something it could influence."
 
Having seen that comment, I want to point out to zoffmeister that Duckbar indeed does not influence track colors - there is no need for it to!  You already automatically have track colors in Mercury.  What Duckbar does do is allows changing the graphics for buttons, different backgrounds/images, etc. as in Theme Editor.   I thought this is exactly what zoffmeister was looking for - his previous post in this thread included ""I still can't see why making any modification to the Mercury Theme in Theme Editor removes Strip colour. I should still be able to restyle buttons without losing this". Using Duckbar allows just that: modification of the Mercury theme without losing strip colors.
 
When you do it in Duckbar using the Mercury theme, it does not remove strip colors ... if you're still using the initial factory Mercury (with track colors!), not touched by the Theme Editor.  It occurred to me that perhaps when the OP was trying Duckbar the Mercury had had already previously been saved using Theme Editor.  If you do that, you will have already lost the track color ability before even opening Duckbar - make sure you start with a fresh factory Mercury untouched by Theme Editor.  And don't ever use Theme Editor on a Duckbar modified Mercury, as it will remove track colors from that point on.
 
In summary, Duckbar does not affect track colors (you will still have them)!  Leave the track colors to Mercury (a fresh unmodified stock Mercury), change the Mercury graphics (buttons, backgrounds, etc) using Duckbar.  Do not ever alter the Mercury theme using Theme Editor, or you will lose track colors.  Simple ... and it works!
 
Pete
 
 

Wait...there's a theme editor? Cool.
 
But does it do animated icons? I want that little picture of a guitar to be strumming, so I can distinguish rhythm guitars from lead guitars. No? Better fix that bug!
 
Apologies to the OP, I don't mean to trivialize your frustration. But you need to understand the difference between a feature request and a bug report. If a feature doesn't exist, it doesn't exist. Unless the developers explicitly promised you that feature, it's not a bug.

Pete, I hear ya man.
I used it before the theme editor was given to us. I loved it.
As for this thread, ya it stinks we cant modify track colors in other themes but its not the end of the world in my opinion. Surely not a bug or a show stopper for me anyway.
When I want full track colors I use the Mercury theme.

I just loaded mercury-theme because I have forgotten how colored strips look like.
My personal opinion it looks very UNprofessional.
That is why I revise my opinion of yesterday. I remembered it differently.
  
If I were asked, it would be enough to color the little stripes left of the track - and of the bottom of the channel in console. Just like now as in Tungsten. But WITHOUT coloring the clips foreground. Therefor I use only colored icons.
 
 
 
 

Hello again. The other thread from last year that I created was more to do with wanting darker coloured strips, like those you see in most top pro's ProTools sessions. ProTools has really got this sorted and has for years. Cakewalk don't allow you to specify the exact colour and saturation of the strip colours because in Mercury there are dark text elements over the strips. This is why they won't let you darken the strip colours in Mercury. They could do just that in Tungsten if they wanted. However that is a separate gripe to the one I have here. 
 
People don't seem to understand the nature of a bug. I'll say it again. If in Theme Editor I want to change my track solo button to pink, for example, why on earth does that remove strip colours? It is totally unrelated. This IS definitely a bug with Theme Editor. Clearly saving a theme in Theme Editor creates a totally different format of file to the stock Mercury Theme. Why else would it remove the required code for strip colours?

zoffmeister
People don't seem to understand the nature of a bug. 

Now I understand. If people keep saying over and over again that it's a bug, it must be a bug.
 

Brando

zoffmeister
People don't seem to understand the nature of a bug. 

Now I understand. If people keep saying over and over again that it's a bug, it must be a bug.
 

+1
 
Im sorry but I just cant agree with the OP that this is a bug.
Annoying ? Yes. 
A bug ? No.
 

zoffmeister
The other thread from last year

You mean the other 2 threads you created.
http://forum.cakewalk.com/THEME-EDITOR-Oh-FFS-m3455128.aspx
http://forum.cakewalk.com/Please-bring-back-coloured-strips-in-Tungsten-m3429609.aspx
this is the 3rd one.
 
I admire your passion and I am 100% behind you. but I cant agree it is a bug.
I wont comment anymore out of respect for your inquires, My apology's if I seem forthright.
Im just voicing my opinion similar to you.
 

If it's no a bug then it is deliberate. Clearly you are not editing the Mercury Theme. You are creating a new theme that has some elements that look like Mercury. 

zoffmeister
If it's no a bug then it is deliberate. Clearly you are not editing the Mercury Theme. You are creating a new theme that has some elements that look like Mercury. 

Actually you're not creating a new theme. You're adding overlays to the Mercury theme. That's why if you remove customizations, you'll find Mercury underneath. It's clear from what Lance Riley said above that it is a deliberate design decision based on existing graphical limitations (not graphical errors that could be construed as "bugs"):
 
"The changes to accommodate it are not trivial and require redesign of how the console view looks due to how we display text. We were able to create a pseudo tint in Mercury because the Strip background is light and we can blend a little color without making the text in the strip unreadable. This same approach did not work for Tungsten and so that feature is not available through the Tungsten theme or Theme editor currently."
 
"Bug" is not defined as "the program doesn't have a feature I want." It's defined as "an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect result, or to behave in unintended ways."
 
The bottom line is you are making a feature request, not reporting a bug. There's nothing wrong with that but it helps to be clear about the language.