Fix #200 resolve interaction between DB optimizer and reshaper

I have a question regarding JVET_M0428_ENC_DB_OPT: by default EncDbOpt is set=0 in CTC test cfg, but why current VTM will enter process that is implemented for encoder deblocking optimization? Should this part be entered only when EncDbOpt is set to 1?

@tlu I believe this merge request changes the behaviour such that when DB optimization is disabled, xCalDebCost is not called anymore.

When EncDbOpt is set=0, only distortion is calculated in the function, so we can regard this as lossless change. In the merge request, I changed the code such that xCalDebCost is not called anymore when EncDbOpt is 0.

Thank you, that sounds like reasonable.

changed title from Fix to ticket #200 to Fix #200 resolve interaction between DB optimizer and reshaper

merged

mentioned in commit 59a6556a