(2018-02-18, 04:30)toki5 Wrote: you just place it on your boot drive, not in the kodi folder and it should work. that's how it works for me.

(2018-02-18, 12:04)oldpainless Wrote: @ Fail$tyle420


Yes - download the latest LAV and install as usual. As by your post you are using the 32bit version of Dsplayer, navigate to C:\Program Files (x86)\LAV Filters\x86, and copy the files over to  C:\Program Files (x86)\Kodi\system\players\dsplayer\LAVFilters.

If however, you are using the 64bit version of Dsplayer, you need to copy over the 64bit Lav files (C:\Program Files (x86)\LAV Filters\x64)
K

(2018-02-17, 19:23)ElJimador Wrote:

(2018-02-16, 18:01)ElJimador Wrote: Hi again.  Another noob question, sorry.  I'm trying to set up VideoPlayer merits rules under the DSPlayer settings so that DSPlayer will be the default player only for 4K HEVC while the regular Kodi player will be used for everything else.  I've used the playercorefactory.xml to launch external players in the past so I'm not totally new to this and it appears this is just another way to the same thing through the GUI, however I'm not understanding the basic logic here.  Does "VideoPlayer" here refer to DSPlayer or to DVDPlayer (that's still the name of the default Kodi player, right?) -- ie. am I creating a rule for everything DSPlayer will play by default, or am I creating rules for the exceptions that DVDPlayer will open instead?  So far I've tried it both ways and DSPlayer still opens everything no matter what I enter.  

Treating VideoPlayer to mean DSPlayer (ie. affirmative rule):
rule name: 4K HEVC | file name: *.4k* | video codec: h265 | video button: on

Treating VideoPlayer to mean DVDPlayer (ie. exceptions rules):
rule name: H264 | video codec: h264 | video button: on
rule name: VC-1 | video codec: vc-1 | video button: on
rule name: MPEG2 | video codec: mpeg 2 | video button: on

As I said, either way I try it's still opening DSPlayer for everything.  So which is the right approach and what am I missing?

 Alright I figured out the logic (VideoPlayer = former DVDPlayer and the merit rules tell it what to open in that vs. DSPlayer).  However it doesn't appear the Plex for Kodi add-on will let you use both players to open up different file types.  Setting the rules by video codec didn't work at all even in DSPlayer.  Setting the rules by tags in file names, I was originally doing them incorrectly as in my first example above (ie. *.dvd*, etc.) and both in DSPlayer and through the Plex for Kodi add-on, it would then open all files with VideoPlayer regardless of the rule.  Then when I corrected them to .*dvd.* etc., DSPlayer read the rules correctly and works fine but through the Plex for Kodi add-on, everything now opens in DSPlayer only.  

So it appears no matter what that Plex for Kodi makes you use all one player or the other, not both.  So it's not a DSPlayer issue per se but if anyone here has attempted a similar setup and got it to work, I'd still appreciate any help I can get.  Otherwise I'll search around the Plex forum or if there's a Plex for Kodi board or thread here to see someone there can help me. 

(2018-02-18, 18:43)Fail$tyle420 Wrote:

(2018-02-18, 12:04)oldpainless Wrote: @ Fail$tyle420


Yes - download the latest LAV and install as usual. As by your post you are using the 32bit version of Dsplayer, navigate to C:\Program Files (x86)\LAV Filters\x86, and copy the files over to  C:\Program Files (x86)\Kodi\system\players\dsplayer\LAVFilters.

If however, you are using the 64bit version of Dsplayer, you need to copy over the 64bit Lav files (C:\Program Files (x86)\LAV Filters\x64)
K

 Thank you!  I figured it would work, but wasn't sure if it was hardcoded in some way to only accept the version that is packaged with Dsplayer! 

(2018-02-20, 14:51)Eddie Strike Wrote: I somehow broke my DSPlayer for 4K HDR playback.... had it working fine for months, but now it stutters like crazy. No idea what I changed?

MPC-BC plays back 4K HDR perfectly with the same MadVR install, but DSPlayer shits the bed instantly.

I tried wiping the install and reinstalling, but it didn't help.

Any ideas?

(2018-02-21, 00:40)mclingo Wrote: if it works fine in MPC-BE then it must be someting in DS, although i've had similar issues myself int he past.