Ahhh, I understand. It's a bit confusing to use a file to store settings, because most (all?) other plugins store their settings in the TVE database.MediaPortalIptvFilterAndUrlSourceSplitter.xml is only configuration file for TV server plugin and it has no relation to merged filter - merged filter doesn't load this file.
So to be clear: is MPIPTVSource.ini still used?
It would be the same as with any other tuner (consistent ): the user chooses the tuner which they will scan with. TV Server doesn't have to know.This makes sense, channels are mapped to cards, which can have their own specific settings. But I don't have any idea, how will works scanning of new channels, because TV server will not know, which IPTV card should be used.
Unfortunately "simple" and "complicated" aren't always objective.Keep things simple.
Make things complicated
To me it seems "simpler" (or at least more consistent) to have some/all of the plugin functionality built into TV Server configuration, rather than in a plugin. That would enable using the provider/device-supplied m3u files directly (no need for the user to modify URLs if the settings are applied automatically by TV Server). I'd also have said that all configuration should be stored in the TV Server database.
...but I'm sure some people will think another way is simpler.