(2020-01-22, 03:11)ayeroff Wrote: Thanks for the suggestion. I appreciate the help. But actually, the video files play correctly regardless of what resolution is selected. As I understand it, the GUI resolution setting in Kodi doesn't control playback, and only controls the resolution of the Kodi interface, and Kodi then switched to the correct video playback resolution. The problem is that when the file stops playing, there is some problem switching back to the GUI resolution. 

(2020-01-20, 20:13)ayeroff Wrote: Hi.  I'm hoping someone might be able to help me solve an annoying .....

------------------------------------------------------------------------------------------------------------------------------------------

Hi, this might be something you have to live with as I still get it from time to time, ssuming you are using win10?

few things to try:

Turn on or off FSE in MADVR
use full screen window off or on in KODI DS
set gui to 2160p like you desktop, removed all 1080p display modes from MADVR, you dont need to add one for 3D as this is forced to 1080p anyway.

Personally I just live with the issue, I can solve it more or less but I have other issues if I do which I wont bore you with.



Thanks for the help.

(2020-01-26, 12:13)Warner306 Wrote: That is what is output from the GPU, which can be different than the output from madVR.

madVR can dither HDR content from 10-bits to 8-bits without any consequences or banding, so there is nothing wrong with that. But you should set madVR to 8-bits to match the GPU, or otherwise the GPU is doing the dithering from 10-bits to 8-bits rather than madVR.

(2020-01-27, 00:07)Warner306 Wrote: madVR uses high-quality dithering to convert 10-bits to 8-bits and the result is virtually indistinguishable from 10-bits or 12-bits.

The Lumagen Radiance Pro does the same trick. Read this quote from the lead software engineer, Jim, who claims there is no visual difference between dithered 8-bit and dithered 10-bit. madVR has proven this several times over and is no different:

https://www.avsforum.com/forum/26-home-theater-computers/2215490-madvr-player-support-thread-39.html#post58353702

(2020-01-27, 18:17)ashlar Wrote: While always hoping for some kind, capable and gentle soul to update DSPlayer, I'm starting to wonder what would be needed to keep on using it in the future. And the only thing that could be a showstopper, as far as I can imagine, are scrapers for media and subtitles.

I personally use TVDB, TMDB, OpenSubtitles and Addic7ed Subtitles. How complex would it be to keep those up to date in Python 2, when development switches to Python 3? Anybody knows?

(2020-01-27, 10:29)ayeroff Wrote: I've been using Kodi DSPlayer for a couple of years now, and had my HTPC running pretty well.  I use my HTPC exclusively to play Bluray and UHD MKV files ripped from my movie disc collection.

Recently, my NVIDIA driver got updated accidentally (I've avoided updating most drivers once I got my system working the way I wanted) which started causing some problems.  So I downloaded my previous NVIDIA driver and rolled back to that version (390.77).  Everything is working again, except I can't get my system to play any lossless audio (Dolby TrueHD, DTS-HD MA, or Dolby Atmos).  Now, when I play a MKV movie that has Dolby TrueHD, DTS-HD MA, or Dolby Atmos, I get no sound from the movie.  If I play a MKV movie with DD or DTS, the sound plays fine.  I have WASAPI selected for both direct and passthrough, and all audio formats supported by my A/V receiver (Yamaha RX-A2070) are selected. 

Any idea what might have gotten broken during the Driver rollback, or how I can get lossless audio to play again?  Thanks for the help!

(2020-02-01, 02:36)spencerjford Wrote:

(2020-01-27, 10:29)ayeroff Wrote: I've been using Kodi DSPlayer for a couple of years now, and had my HTPC running pretty well.  I use my HTPC exclusively to play Bluray and UHD MKV files ripped from my movie disc collection.

Recently, my NVIDIA driver got updated accidentally (I've avoided updating most drivers once I got my system working the way I wanted) which started causing some problems.  So I downloaded my previous NVIDIA driver and rolled back to that version (390.77).  Everything is working again, except I can't get my system to play any lossless audio (Dolby TrueHD, DTS-HD MA, or Dolby Atmos).  Now, when I play a MKV movie that has Dolby TrueHD, DTS-HD MA, or Dolby Atmos, I get no sound from the movie.  If I play a MKV movie with DD or DTS, the sound plays fine.  I have WASAPI selected for both direct and passthrough, and all audio formats supported by my A/V receiver (Yamaha RX-A2070) are selected. 

Any idea what might have gotten broken during the Driver rollback, or how I can get lossless audio to play again?  Thanks for the help!

sometimes you need to reselect the device in the dsplayer section of players, scroll down and make sure your device is still selected.  sometimes when it upgrades video it changes something about the audio device the the original device is now not listed in dsplayer

(2020-01-12, 13:26)curael Wrote:

(2020-01-12, 12:39)CyberVillain Wrote: I'm looking at getting madVR to integrate with Kodi, why isnt this branch of Kodi pulled into master? It seems its unmaintained too, master is now at 18.x

The project has had no maintainer since 17.x. Maintaining DSplayer and to build/port it into Leia branch is not an easy feat and sadly no one has had the combination of time and skill required to do so.