Theme - Colour Guide

..

Exellent , thks

Global > Alternative Color #1 is the text foreground color for 32bit plug-ins in the browser
I set it to match the color of the 32bit icons in the "Plug-in Tree" image in Browser > Plug-in Browser positions 12, 13, 16 and 17 and the appropriate Browser > Plug-in Browser > Plugin Types icons.

Here's my contribution...
 

Yeah well reason is rubbish. Being that the support team ore over whelmed, here would be the place where the initial feedback would occur, instead of just dropping it for us to beta and run, it's obvious stuff would come up, especially in the first month.
 
I saw the video, so I know the guy your referring to. I only said graphics team as to make it clear I'm aware it's not the same team that do the other work.
 
What's the point of writing stuff in bullet points like I did, if no one reads it, and then they chip in on thread which was meant to be Forum Noise. Forum Noise or no noise.
 
So many posters have asked where you can edit the performance meter colour, which you can't.
 
Click on Help in Sonar, and there's an option to take you to the forum. We lighten there load, but logging stuff that gets ignored doesn't lighten ours. Completely disillusioned with Feature request and Problem reporting, and so many people say they not had responses to things they've emailed. It's more than the Support lines that not working here.
 
Thread title edited

Anderton
 
What we need is a centralized place where any oddities are consolidated in individual, bullet point-type sentences so they can't get lost in "forum noise." Then the Theme developer could just set aside a few days (or weeks or whatever) and go down the list.
 

Here's an idea, why don't we have a subforum for the cakewalk product, so we can have a centralised location for logging alll these issues, along with threads like this, resources. Themes etc, so it doesn't get lost in Forum noise, such as people complaining about Tech help (which may need it's own subforum at this rate).
 
Oh wait, the consensus of the unelected team whose consensus doesn't matter as they don't have the power, is no. And they recommend supporting the thread in the feature request section that produces one User's feature request implementation per 24 months. So we'll wait until 2019 to see if that get the go ahead then

Kamikaze
What's the point of writing stuff in bullet points like I did, if no one reads it.

 
This is exactly why there needs to be a centralized place. I recall you mentioning specific things but I wouldn't know where to find them, so I doubt other people would either. The devs have been spending more time on the forums lately to supplement support, but they still don't spend all that much time here.  
 
I did see in one thread where someone (Noel?) mentioned passing along comments to the Theme Editor guy. But he does a lot more than just the Theme editor, so probably has other priorities. For example I assume Cakewalk would prioritize finishing up the load balancing and the Phase 2 for comping and take management compared to making the performance meter color editable. There have already been some changes to the Theme Editor (hence the new download in 2016.08) but they didn't relate to additional customization.
 
Meanwhile, complaining about limitations dilutes from what I thought was a great premise for this thread. I'd rather contribute more about what can be done, as I did with the Step Sequencer (and as scook did), rather than mix in comments about what should be done. That way this thread could be a useful and compact guide about which elements relate to which colors. 
 

Yeah it shouldn't be Noel job I'm not suggesting that, but if it's not the Creator of Theme Editor to have some responsibility for dealing with the initial release of the product (beyond making a video), then it should be someone's. Just writing a guide for it would make you realise there are various contradiction, omissions and seemingly non functioning elements.
 

Kamikaze
 
Oh wait, the consensus of the unelected team whose consensus doesn't matter as they don't have the power, is no. And they recommend supporting the thread in the feature request section that produces one User's feature request implementation per 24 months. So we'll wait until 2019 to see if that get the go ahead then

Maybe it is garbage like this which I find overly negative.
Forget it. There is no point in this discussion. Keep on complaining if it makes you feel better.

Kamikaze
 
Here's an idea, why don't we have a subforum for the cakewalk product, so we can have a centralised location for logging alll these issues, along with threads like this, resources. Themes etc, so it doesn't get lost in Forum noise.

 
That's what the Feedback Portal is supposed to address. It's like a version of the forum that focuses on specific issues. For an example of this sort of approach see Stackoverflow.com or how Ableton.com handles support. It's a model that more and more sites are using as a way to surface and rate issues.
 
I know you believe Cakewalk doesn't listen, but I think you're confusing not listening with not acting on everything they hear. I can tell you right now that they can't. Nor will they talk about everything they're working on. For example right now they are exploring a specific option on how to integrate better notation into SONAR. Whether it will pan out or not, I don't know; but they're not going to say anything until they know whether it's doable or not. So it may appear they're not listening to the notation "vocal minority" (which includes me) because there's no apparent tangible progress, but they are...or they wouldn't be seeking a solution.
 
Furthermore regardless of what they hear, some changes simply will never be made because CW can't do everything they'd like to do, let alone everything the universe of Cakewalk users would like them to do. So the priority is on functionality that affects the greatest number of users. For example, plug-in load balancing is a high priority because probably everyone uses at least some plug-ins. I would be willing to bet a much lower percentage of people cares about the performance meter color, or even have any interest at all in a Theme Editor...they have Tungsten, they're happy.
 
Meanwhile, we have a Theme Editor and a lot can be done with it. I still hope this thread will concentrate on the latter, despite your taking the thread into a different direction in post #6. If you want to complain about Cakewalk, I recommend starting a different thread or contributing to one of the existing ones.
 
I still think it would be a good idea to delete all posts that don't relate to the raison d'etre of this thread so it can provide something genuinely useful to the community. However if that's not your priority, I'd be happy to start another thread devoted exclusively to tips that will help people get the most out of the Theme Editor.

Kamikaze
List the feature request that have implemented in the past 3 years. 

 
I already took the time to do so in another complaint thread of yours, and I know you read what I posted because you basically replied (to paraphrase) that you'd been there, done that and weren't going to respond. Look it up yourself.
 
There's a certain irony that you're complaining Cakewalk doesn't introduce feature requests in a thread about a feature request that Cakewalk implemented. 
 
And by the way, Noel responded to one of your complaints in another thread with "What specifically are you unable to edit? We have plans to enhance editable content as we progress." Call me crazy, but I think most people would interpret that as CW listening, and responding they have plans to enhance editable content as they progress.

In mentioning those items, I thought the community requesting a feature qualified as a feature request from the community. Everything I mentioned was in fact requested by the community. If in your mind only requests presented in the Features & Ideas forum qualify, given that the forum started less than two years ago it seems unfair to want a list of features from the last three years that could be attributed to it. Furthermore, many of the updates happening now were started in response to user requests from X3 and even before, when there was no Features & Ideas forum and only requests in the SONAR forum itself. It can also take months, or even years, for something to transition from "cool idea" to QCed lines of solid code with an installer.
 
Personally, I'm glad so many of the community's requests have been implemented, regardless of when or how they communicated those requests to Cakewalk. I think they've added major functionality to the program.
 
Also, there is no problem with pointing out failings. Many bugs have been fixed because people, including myself, did point out failings. In fact this forum is filled with posts that point out failings, in my opinion to a fault when the same complaint gets repeated over and over again by the same people, as if there's some belief that if you say something enough times, code will somehow materialize. Yet I don't see those posts being deleted, nor those users banned.
 
However, I strongly believe that threads are most useful and receive the greatest participation when they stick to a topic. I didn't expect that a thread called "Theme - Color Guide" would become a platform to complain about Cakewalk after only six posts, particularly from the person who set the thread topic, and particularly because prior to that at least scook and I were conforming to the original premise in order to encourage others to do the same.
 
I still think one thread with all the screen shots and tips would be the best way to go, and I wish you would re-consider doing that. My objective is helping people get the most out of SONAR, but we obviously have different ideas of how to do that and that's okay. We probably make different music, too. 

Hey Scott. This your picture was very helpful, but some reason now it's disappeared. Can you please send it again?

Kamikaze
http://forum.cakewalk.com/FindPost/3472160
http://forum.cakewalk.com/FindPost/3472267
 
 

Thank you very much :)