Kodi Community Forum

@aracnoz - will any changes to the madvr dsplayer gui be needed for the latest version of Madvr?

K

Hi, please can the next build have FSE the same as DIRECT3D, have DS read from the database whether its on or off, otherwise when you put in on in DS it also turns it on in MADVR, what happens then is if you turn it off in DS, close DS and open it again it sometimes comes on again as its ticked in MADVR. This option should only be available if you have elected to use local DS settings to store MADVR settings rather than MADVR database. 

You can also now load MADVR whilst playing a move using CONTROL + S so there isnt really any need to have the MADVR settings in DS anymore unless you are storing them in DS alone.

For what it's worth, my opinion is that, in the current state, with aracnoz not being devoted to this full time and, actually, updating this only for major releases and/or emergency cases (and thank god for that and his continued support to us), it might be worth it to take a step back and stop updating the madVR implementation through Kodi's GUI.

That made sense when there was a chance for proper integration of the DSPlayer build into regular Kodi releases.

That's been shot to the ground several months ago. As such this is bound to remain a solution for dedicated users. I'd much prefer aracnoz's time being spent on smaller frequent updates to all releases rather than him throwing time at an ever moving target (madVR features to be handled through GUI).

Just my two cents, obviously what matters is how aracnoz feels on the subject.

I totally agree with ashlar and I hope we will get a DSPlayer version of Leia after its RC or final release.

@ashlar

Hi, are you suggesting that future versions will have DS just using MADVR database and not have its own onboard, and taking settings direct from MADVR like MPC and other players, and that they will not be configurable at all in DS?

If so I definitely agree for the following reasons.

1. You can now access MADVR settings using CONTROL+S within KODI DS.
2. There are some issues where settings in DS like FSE are updated back to MADVR when you dont want them to be.
3. Dev should be a bit simpler and possibly more stable
4. Less to configure in DS means it will be easier to setup and use for noobs.

As great and flawless KODI DSPlayer works for me now with MadVR + AC3Filter - i never liked the default setting meaning configuring MadVR settings from within KODI.

Even on clean setups it felt kind of wrong/clumsy for me and i always ended up with crashes while browsing the KODI DSPlayer integrated MadVR settings when using some deeper menus. (As said, i used clean setups and the correct supported MadVR version)

The moment i changed DSPlayer settings to stop configuring MadVR via KODI and start using only the native external MadVR settings - all annoyances and crashes went away.

So i'm very +1 on this one.

@aracnoz - many thanks for the update,

K

Hi

I'm using the x64 version on Windows 10 latest with AMD cpu and AMD gpu. I can say that this version works better for me than the x86 and it is super stable. The settings i'm using in madvr in x64 are much HIGHER than x86 version, without dropping a single frame. Directx11(10bit) -checked seperate device for processing- with bicubic for chroma upscaling and LANCZOS for image upscaling.

I see there are reports that DSPlayer doesn't play Live TV streams. I have this issue too.
Here is a full log.

And here are some excerpts.

In the first case I tried to start channel playback from a channel list, it's failed:

In the second case I tried to start channel playback from a channels widget (it's a history of recently used channels actually) , it's succeeded:

The obvious difference is that in the second case the CDVD* player was used instead of the CDSPlayer from the first case.

What is wrong there and how to fix it?

I have exactly the same behaviour with ArgusTv.

(2018-01-19, 13:55)mclingo Wrote: [ -> ]@ashlar

Hi, are you suggesting that future versions will have DS just using MADVR database and not have its own onboard, and taking settings direct from MADVR like MPC and other players, and that they will not be configurable at all in DS?

If so I definitely agree for the following reasons.

1. You can now access MADVR settings using CONTROL+S within KODI DS.
2. There are some issues where settings in DS like FSE are updated back to MADVR when you dont want them to be.
3. Dev should be a bit simpler and possibly more stable
4. Less to configure in DS means it will be easier to setup and use for noobs.

 Yes, that's exactly what I meant. Again, if the objective was to have DSPlayer as a regulard Kodi build, then it would make sense. But since it appears that that is no longer an option, us "AV aficionados" can use madVR native settings and save, I guess, a lot of dev time for Aracnoz, which is basically just doing us all a favour in keeping this working with new Kodi releases.

I'm guessing this will be updated for kodi18? This build has the input stream capability for things like Netflix, etc so that will be a big factor for me. Also, why is the x64 version been listed as unstable for so long? I have been praying at this for well over a year now and that hasn't changed

(2018-01-25, 18:28)Jachin99 Wrote: [ -> ]I'm guessing this will be updated for kodi18? This build has the input stream capability for things like Netflix, etc so that will be a big factor for me. Also, why is the x64 version been listed as unstable for so long? I have been praying at this for well over a year now and that hasn't changed

DSPlayer is not actively developed. It's been mantained, so far, by aracnoz, but that could change with no further notice.

I've resolved the live-stream issue by adding the playercorefactory.xml config to the userdata folder:

xml:
<playercorefactory>

    <rules action="prepend">

        <rule name="live-stream" protocols="pvr" player="VideoPlayer" />

    </rules>

</playercorefactory>

It could be useful to add the other streaming protocols, e.g. "pvr|daap|rtv|rtmp|http|https|rtmpe|mms|rtp|rtsp" as in the linked example in that post.
It would be good to add to the known issues that in the default configuration DSPlayer is incompatible with live-streams (probably, due to buffering). And there is no more "DVDPlayer", it's replaced by "VideoPlayer".

Hi All

I've been using Kodi for many years now, but only recently I installed the DSPlayer version (17.6) in order to play my 4K UHD content as it does most of the HDR settings by default.

There is just one problem I have so far, when I play a 4K UHD movie via the DSPlayer using madvr it plays perfectly fine, however as soon as I activate the subtitle while playing the movie it automatically loses HDR (I get washed colors), then when I stop the movie and start it again everything is back to normal. So basically the I lose HDR or the display goes yellow/orange every time I activate the subtitle.

Is there perhaps anybody out there that is experiencing the same or similar problem? Or do I just have the wrong setting?

Any help will be appreciated.