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

scook

Kamikaze
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.

I will be glad to remove my post if it will make you feel better.

Where I have I commented on your post. That quote doesn't.
 
Weird

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. 
 

Kamikaze

scook

Kamikaze
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.

I will be glad to remove my post if it will make you feel better.

Where I have I commented on your post. That quote doesn't.
 
Weird

Just trying to stop the negativity. I do not want to

Kamikaze
...chip in on thread which was meant to be Forum Noise. Forum Noise or no noise.

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.
 

scook

Kamikaze

scook

Kamikaze
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.

I will be glad to remove my post if it will make you feel better.

Where I have I commented on your post. That quote doesn't.
 
Weird

Just trying to stop the negativity. I do not want to

Kamikaze
...chip in on thread which was meant to be Forum Noise. Forum Noise or no noise.

Another weird quote chucked in at the end. That other thread 'Theme Editor Anonymous' wasn't negative.
 
Weird again Scook
 

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.

Yeah that was

scook

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.

Yeah that was response to your garbage response from the other
 
Agreed, pointless in pointing out some truths around here. Nothing gonna change
 

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.

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