Anyone need chroma=false in Decomb?

[neuron2]

I am preparing the next release of Decomb and want to remove the chroma (=false) option for postprocessing. It seems to me that chroma should always be deinterlaced and the option was just there for historic reasons. Removing it would simplify the code and make maintenance easier. There is little performance difference between chroma=false and chroma=true. And the default has always been chroma=true so most people don't even know about it.

Before I go ahead, is there anyone that demands the retention of the chroma=false option for postprocessing? Speak now or forever hold your peace. And please justify your demand. Thank you.

[N_F]

@neuron2

According to the last (I think) decomb documentation default is chroma=false (for both fielddeinterlace and telecide). Which is correct?

[IanB]

@neuron2: By all means remove the code. But please leave the option in the syntax table, so library/generated scripts won't prang.

Maybe you could chuck a script exception if it is declared and false.

Thus ..., Chroma=true, ... is a useless but harmless option.

While ..., Chroma=false, ... throws a "no longer supported" script exception.

IanB

[neuron2]

@N_F

It's always been defaulted to true. The documentation was in error.

@IanB

Specification of any undefined option will throw an exception. Is that good enough? Thank you for your feedback.

[IanB]

@neuron2Specification of any undefined option will throw an exception. Is that good enough?Not quite, the idea was such that existing scripts that explicitly declare the default behaviour would continue to work unimpeded. It's all about providing as much legacy support as possible. Obviously it's a step forward to make the code faster by deleting some slow, unused feature, but it's a pain editing all the library scripts and generator programs that explicitly declare default behaviour. It cost nothing (almost) to leave the verb in the syntax table as a legacy with an exception throw if the value is non-default (false) and a do nothing if the value coinsides with the default (true).

The way the syntax in Avisynth and it's filters subtly changes over time is the single most annoying thing about Avisynth, it must drive the Gknot people crazy.

IanB

[neuron2]

Gotcha. Thank you.