[ashlar]

And why is that. Did aracnoz explain?

The only reference I found was here: http://forum.kodi.tv/showthread.php?tid=...pid2138199

It appears being hardcoded in FilterCoreFactory.cpp. Lines between 105 and 114 hardcode Kodi to use LAV Source internal, bypassing the filters rules. I don't know how easy it would be to not have this and having it adhere to the rules set up in the regular way.

It's a shame to have hard coded filters in DSPlayer, as the whole point should be flexibility above all else.

I'm so sorry not to have noticed this when aracnoz was still around

I also think that we should change the mediasconfig.xml and filtersconfig.xml files to be identical to the internal versions. I'm referring to the files in C:\Program Files (x86)\Kodi\system\players\dsplayer. Those files refer to stuff that might not be installed and apparently they create conflicts when trying to playing streams through DSPlayer.

See for example, in mediasconfig.xml, this entry:

<rule protocols="http">
<source filter="urlfilesource" />
<splitter filter="avsplitter" />
<video filter="cyberlinkvideodec" />
<audio filter="ffdaudiodec" />
</rule>

I say change them to be identical as this, empyrically, solved it for me. Maybe there's a better way to go. But I don't know how to operate on source, hence this solution allowed me to bypass the problem. I end up having mediasconfig.xml, filtersconfig.xml, mediasconfig_internal.xml and filtersconfig_internal.xml to be respectively identical. And everything appears to be working correctly.

I personally use Settings/Videos/DSPlayer/Filters Management set at "Media rules and Filters configuration". Which might be part of why this has gone unnoticed so far. Maybe the majority of people are using the "internal filters" option here.

For reasons unknown, it appears that while "internal filters" works fine and, obviously, ignores customized versions of mediasconfig.xml and filtersconfig.xml in the user directory, "Media rules and Filters configuration" has problems with conflicts between the system version of those files and the customized version. I thought that if mediasconfig.xml and filtersconfig.xml existed in the user directory the ones in the system directory would be ignored... but this doesn't seem to be the case.

EDIT:

Yes, it appears that the overruling is done on a rule by rule basis. Hence, placing this in mediasconfig.xml, in the user directory, bypasses the rule in the system folder:

<rule protocols="http">
<source filter="lavsource" />
<splitter filter="alavsplitter" />
<video filter="lavvideo" />
<audio filter="lavaudio" />
</rule>

With DSPlayer automatically selecting the internal version of lavsource, again hardcoded as I explained in the previous post.
I doubt that I could have something do to with the situation, as personally I've never used cyberlink codecs... so I suppose the situation is like this from a clean install too (I always edit stuff in the user directory, not the system one).