audio/videodecoder: Reconsider max-errors default value
The following discussion from !720 (merged) should be addressed:
-
@ndufresne started a discussion: (+1 comment)
Overtime, this internal feature has cause a lot more harm then good. At least in live pipeline, giving up rather then skipping is always the wrong choice, so it's nice that it can be configured through properties too, but shall we reconsider the default value ?