• 1
  • 526
  • 527
  • 528(current)
  • 529
  • 530
  • 531
Kodi DSPlayer – DirectShow Player for Windows
When the movie is stopped the text color is yellow as if the movie is playing and there is no more kodi sound when I browse.

Image
Reply
new test with mpc video renderer. The files used dolbyvision and HDR.The libplacebo settings are by default.
the colors of the video and gui are bad

ImageImage

avec MPV player
Image
MPC-BE with mpc video renderer
Image
Image
Reply
(2024-06-16, 11:55)roby69 Wrote: new test with mpc video renderer. The files used dolbyvision and HDR.The libplacebo settings are by default.
the colors of the video and gui are bad
For libplacebo i most have spent 2 weeks just to build it for windows. I know about the colors its a kinda complex thing to do. I have to write a lot of code from scratch. You dont need to post bugs about the internal video renderer i still need to work a lot on it.

I really like the mpvplayer debug on screen i might take that.

For the aspect ratio i will look into it. Their a lot of code that control madvr settings that im not the one who did that. Will keep you posted about that
Reply
@ tiben20
Thank you for your feedback.I'm in no hurry, do what you can.
I prefer liblacebo instead of madvr, I keep it as a backup solution for certain videos that are difficult to tone mapping.
If you want my MPV Player stats.lua and mpv.conf file, I can send them to you by PM.

Thank you again for all your efforts and all your time in this development.
Reply
(2024-06-16, 11:23)roby69 Wrote: I did a test using Madvr video renderer and the video has the wrong format.
if I use MPC-BE with madvr the format is correct
apparently the "minimize black bars" and "display 4:3 videos as" settings affect madvr and videoplayer kodi. I tested with kodi 17 dsplayer and it works.

Image
Reply
Updates: Fixed back and forth between renderers not working
- fixed colorspace for hdr dovi every sample i found on the dolby vision website work perferctly on my hdr tv.
- Added data parsing for hdr10+
- Started the new stats display as you can see under the screen
- Fixed swapping osd stats mode, default libplacebo scaling from the video osd being saved into kodi settings
- Fixed colorspace for a lot of hdr instance will need to get samples of video and debug log if color are wrong when people are testing
@roby69: could not reproduce the gui thinking that the video is still playing even if its finish will need debug log to fix that.
- Fixed the use of the playercorefactory when the option use dsplayer by default is selected
- Fixed memory leaks and clean up of code but that i keep doing it every day

PS: Since i'm designing the stats being rendered if anybody have suggestion on what you want to have displayed i will be happy to consider them. Right now its like in the picture below. Real fps is the fps that kodi is rendering. You also have the dynamic info on all the colorspace matrix, primaries , transfert and hdr info right now
Image
Reply
I was able to produce the "staying yellow" aka still playing bug.  Debug log: https://pastebin.com/v8Ubu95D

I have been testing a little with madVR but I was unable to get anything working until I installed LAVFilters externally.  I thought it wasn't necessary when using Internal Filters.

A few more bugs I have encountered:

madvr scaling bug - debug log: https://pastebin.com/02TZ4WUv
blank internal video decoder filter options - debug log: https://pastebin.com/P7V3ZEhg

During my brief testing, madVR seemed to correctly scale 1920x1080 content and 3840x2160 content, but scaled 3840x1600 incorrectly.  Kodi also wouldn't remember resume positions.

Hope this helps.
Reply
Quote:I was able to produce the "staying yellow" aka still playing bug.  Debug log: https://pastebin.com/v8Ubu95D
Just fixed it for next release
(2024-06-23, 04:55)only1hammy Wrote: A few more bugs I have encountered:

madvr scaling bug - debug log: https://pastebin.com/02TZ4WUv
blank internal video decoder filter options - debug log: https://pastebin.com/P7V3ZEhg

During my brief testing, madVR seemed to correctly scale 1920x1080 content and 3840x2160 content, but scaled 3840x1600 incorrectly.  Kodi also wouldn't remember resume positions.

Hope this helps.
"blank internal video decoder filter options"  there no internal video decoder i m will need to strip the default xml so people dont think we have internal video decoders

Yeah i noticed the resume positions wlil be fixed shortly it start correct if an old position is there but dont store new ones

 
Quote:I have been testing a little with madVR but I was unable to get anything working until I installed LAVFilters externally.  I thought it wasn't necessary when using Internal Filters.
Its important to note that internal filters will only be subtitles and mpcvideorenderer. Its going to be easier to keep up to date your codec if you have to install them. But the real reason is i don't want to provide compiled binaries.
Reply
(2024-06-23, 06:04)tiben20 Wrote:
(2024-06-23, 04:55)only1hammy Wrote: I was able to produce the "staying yellow" aka still playing bug.  Debug log: https://pastebin.com/v8Ubu95D

I have been testing a little with madVR but I was unable to get anything working until I installed LAVFilters externally.  I thought it wasn't necessary when using Internal Filters.

A few more bugs I have encountered:

madvr scaling bug - debug log: https://pastebin.com/02TZ4WUv
blank internal video decoder filter options - debug log: https://pastebin.com/P7V3ZEhg

During my brief testing, madVR seemed to correctly scale 1920x1080 content and 3840x2160 content, but scaled 3840x1600 incorrectly.  Kodi also wouldn't remember resume positions.

Hope this helps.
Thank you for the info i will work on it and keep yo posted about that
Was that with the version on github or you compiled your self?

Anything I can do to help.  Yes I was testing the precompiled version from here: https://github.com/tiben20/xbmc/releases/tag/dsplayer
Reply
Update: Fixed resume position
Right before reupdating to main branch i will post an updated compiled version on github so i can get some more bugs to fix from you guys.
I should do this later today
I'm going to reupdate to kodi main branch they moved to std c++ 20. Thats quite a big chunk of code they added so i hope it does not break too much stuff on dsplayer side
Reply
(2024-06-24, 16:28)tiben20 Wrote: Update: Fixed resume position
Right before reupdating to main branch i will post an updated compiled version on github so i can get some more bugs to fix from you guys.
I should do this later today
I'm going to reupdate to kodi main branch they moved to std c++ 20. Thats quite a big chunk of code they added so i hope it does not break too much stuff on dsplayer side

I'm looking forward to testing some more.

Just mentioning this even though it's not high priority but your build hadn't included "Joystick Support".  It seems it can't be installed like a normal addon and needs to be compiled for the build from https://github.com/xbmc/peripheral.joystick but I am not too sure.
Reply
Happy to test the next release.  Will true full screen be functional?
Reply
(2024-06-24, 19:06)only1hammy Wrote:
(2024-06-24, 16:28)tiben20 Wrote: Update: Fixed resume position
Right before reupdating to main branch i will post an updated compiled version on github so i can get some more bugs to fix from you guys.
I should do this later today
I'm going to reupdate to kodi main branch they moved to std c++ 20. Thats quite a big chunk of code they added so i hope it does not break too much stuff on dsplayer side

I'm looking forward to testing some more.

Just mentioning this even though it's not high priority but your build hadn't included "Joystick Support".  It seems it can't be installed like a normal addon and needs to be compiled for the build from https://github.com/xbmc/peripheral.joystick but I am not too sure.
Im not compiling the built-in addons i will do for the next release
Reply
(2024-06-24, 19:17)Docbeeps Wrote: Happy to test the next release.  Will true full screen be functional?

was it tested on the last releaseHuh
And just by curiosity why people would run any application in true fullscreen in 2024.

Update: I tested it made the app crash, code is fixed true fullscreen work with madvr. But still i don't see why people would use this its making any application unstable.
Its included in this ALPHA release
https://github.com/tiben20/xbmc/releases

Update 2: Swapping to std:c++20 broken a lot i been correcting compile errors for hours
Reply
Sorry, I think I misunderstood what true full screen was. I just assumed you were referencing Kodi in full screen. I was experiencing crashes at playback with the “use as default video player” option enabled, but that no longer appears to be an issue. Appreciate the work you’re doing here. Thank you
Reply
  • 1
  • 526
  • 527
  • 528(current)
  • 529
  • 530
  • 531

Logout Mark Read Team Forum Stats Members Help
Kodi DSPlayer – DirectShow Player for Windows47
This forum uses Lukasz Tkacz MyBB addons.