Normal
As said, your proposal is interesting.Therefore, there are already many settings in MP1 and, this complicate code because, some options could interfere with others.A newer option could be interesting but, only, if it doesn't break the existing MP process.I don't think adding a newer option only because "let's users choose" is a good way if, this option breaks the compatibility.What happen (for example in DB) if users check this and uncheck it after ?When checked, what with all MP functions and all plugins (integrated or third) ?For me, you can propose a newer setting to let users choose only, if it change what you are supposed to improve but, without others side effects.You have a setting example with multi tuner grab EPG, not integrated yet (choose if single tuner grab or, parallel tuners) without none effect with the rest of process.And yes, this is a pain and, we have to break our a*s each time to make it possible.
As said, your proposal is interesting.
Therefore, there are already many settings in MP1 and, this complicate code because, some options could interfere with others.
A newer option could be interesting but, only, if it doesn't break the existing MP process.
I don't think adding a newer option only because "let's users choose" is a good way if, this option breaks the compatibility.
What happen (for example in DB) if users check this and uncheck it after ?
When checked, what with all MP functions and all plugins (integrated or third) ?
For me, you can propose a newer setting to let users choose only, if it change what you are supposed to improve but, without others side effects.
You have a setting example with multi tuner grab EPG, not integrated yet (choose if single tuner grab or, parallel tuners) without none effect with the rest of process.
And yes, this is a pain and, we have to break our a*s each time to make it possible.