Bug: Unable to record non-manual home values into palettes

Are you asking for this with a selective record?
This is a major change as unown data is set to be ignored.

I just put the channel @0 or Out and it will then record you don't need to Make Manual the whole channel.

Yes, this is what I'm asking. I don't know why this would be a major change. I also don't know why anyone would want it to be the current way. If you don't want channels in a selective record to be included in the palette, then you won't select them.

As it stands, it's misleading and can lead to palettes not being recorded when you think they are recorded.

 

Good point with "Out".

Yes, this is what I'm asking. I don't know why this would be a major change. I also don't know why anyone would want it to be the current way. If you don't want channels in a selective record to be included in the palette, then you won't select them.

As it stands, it's misleading and can lead to palettes not being recorded when you think they are recorded.

 

Good point with "Out".

I was double checking you wanted it with a selective record, it was a major change otherwise.

I've just got used to using out in live. Although most of the time I have these merged in from a master showfile or I add the data in blind or use out before hand.

I'm sure the team would class this as a feature change.

My experience has taught me that many things are geared for the least knowledgeable users.
You earn your paycheque by knowing how to circumvent ETC's protections.

I suspect this is only a thing so noob users don't record values they didn't outright specify.

Wuz314159 said:

My experience has taught me that many things are geared for the least knowledgeable users.
You earn your paycheque by knowing how to circumvent ETC's protections.

I suspect this is only a thing so noob users don't record values they didn't outright specify.

 

That's possible but noob users would assume, as I did, that the channels would be recorded into the palettes as-is.

Regardless of why it is that way, that doesn't mean it's the best way.

I wholeheartedly agree.
but I've encountered lots of things like this and was lambasted for saying they didn't make sense.
I accept that it's standard operation to make things less easy.

the rule for record has always been "record every parameter for each channel (that qualifies within command line filtering) that has at least one parameter not at its home state anymore".

i vote to keep it like this.

but why is the home position not considered recordable data?
If you're specifying the channel and parameters, you should be able to record that regardless of what the home value is set at.