No, because I do not share your opinion about the issue.

scook
No, because I do not share your opinion about the issue.

That's the problem, you think it is an opinion.
This is a basic function that should be intact. It's like saving a mix template that resets
certain parameters and you claiming that it is not an error but part of the design. No way.

A template is not a plug-in, a project is not a plug-in. Wouldn't the vendor be in a better position than either one of us to decide if it really were by design or a bug? If you feel that strongly about it, rather than arguing the point, write up the bug report.

I understand completely. You want to cut cookies and paste them on every track regardless of gain coming in or out. Instead of starting at a reasonable default value like 0 you want to start at some other arbitrary value that you set....for no good reason. And, you refuse to hear or listen to anyone without beating them about the head that they don't understand your vast mixing knowledge. And then you whine and complain about it being a bug so that you can waste someone's time that could be better spent working on actual bugs. Cakewalk has given us the benefit of the doubt that we wouldn't want to make the mistake of saving the gain value in an fx chain, apparently, they weren't accounting for you.

Bottom line...this is not a bug. I think you've now admitted that. It's a design change YOU want. Good luck with that.

T4
I understand completely. You want to cut cookies and paste them on every track regardless of gain coming in or out.

 
Nope. Not what i said.
 

Instead of starting at a reasonable default value like 0 you want to start at some other arbitrary value that you set....for no good reason. And, you refuse to hear or listen to anyone without beating them about the head that they don't understand your vast mixing knowledge.

 
Nope. Wrong again moron. You have no clue as to what I am talking about. 
 

And then you whine and complain about it being a bug so that you can waste someone's time that could be better spent working on actual bugs. Cakewalk has given us the benefit of the doubt that we wouldn't want to make the mistake of saving the gain value in an fx chain, apparently, they weren't accounting for you.

Nope. It is a bug. It's really simple actually
Any where there is an intention to save something as a preset, it should save wholly until THE USER changes it.

T4
Bottom line...this is not a bug. I think you've now admitted that. It's a design change YOU want. Good luck with that.

Nope. It is fundamental issue, it should be addressed.
You have no idea about certain workflows that rely on this.
Don't worry bro

Transcending Music

scookNo, because I do not share your opinion about the issue.

That's the problem, you think it is an opinion.This is a basic function that should be intact. It's like saving a mix template that resetscertain parameters and you claiming that it is not an error but part of the design. No way.

BTW, mix templates don't save gain settings.

Do you know what a bug is? If the developer didn't intend for that usability then the absence of it is not a bug.

scook
A template is not a plug-in, a project is not a plug-in. Wouldn't the vendor be in a better position than either one of us to decide if it really were by design or a bug? If you feel that strongly about it, rather than arguing the point, write up the bug report.

No a template is a not plugin. No a project is not a plugin. Cool we cleared that up!
 
But what do they have in common from the user side? They are required to save any and all
settings without resetting anything until I change it. That is called recall-ability and reliability.
 
A vendor is not an end-all-be-all to design. I understand this peculiar opinion is upheld
around here quite a bit, but it is not right. Vendors make mistakes