[ashlar]

I could also ask nevcairel to add an interface so we can provide our own d3ddevice. I want some suggestion about this one.

I would ask nevcariel. Today they play everything, let's say. Tomorrow? Who knows? I would prefer to have external filters, to be honest. If nevcariel cannot do it, obviously, then do what you have to do to make it work. Just my two cents.

[IT007]

I agree, having pretty much everything external is the reason I can still use 17.6.

[only1hammy]

I agree, having pretty much everything external is the reason I can still use 17.6.

IIRC 17.6 came with custom internal LAV and worked perfectly.. until it stopped being maintained.  So I guess a similar solution would be ideal here, with the option to use/override the internal with external (in case tiben would ever stop maintaining).

[Norixone]

Thanks for the reply. In the meantime I have gone down the MPC-BE + MadVR route and I must say that with a VPJ it does imprve the experience. Next step is to add the 3D LUT. Still willing to test the DSPlayer, which seams to be a much more convenient approach once integrated into Kodi

[Norixone]

Thank you for the suggestion. I do know about integration with external players and MadVr, but you do lose a lot of the functionality offered by Kodi. I just wish Kodi Team implemented madVr as other players do or a form of dynamic tone mapping.
As posted above, I have started using MPC-BE + madVr and I do like what I am seeing, but you also have to go through the hassle of playing around with playcore configurations, etc. and have to use a second remote to control MPC. I have Kodi integrated into openHab.

[tiben20]

Code:

Update: I got lavfilters working with the patch is 70 lines in kodi and 46 lines in lavfilters to make d3d11 accelerated working. Ill put the patch on the side for now until we know what were doing

[tiben20]

Code:

Update: I got lavfilters working with the patch is 70 lines in kodi and 46 lines in lavfilters to make d3d11 accelerated working. Ill put the patch on the side for now until we know what were doing

Well i posted the patch. And will post a patch for lavfilters when i cleaned it up with comments. Basically if you use the lavfilters build for kodi the hardware acceleration will work and the original one won't. Will see if he merge the change when i post them on github

[tiben20]

I worked a lot of making sure i have no problem with dll missing with the installation. Only have the subtitles library to add automatically. At the same time i fixed the subtitle streams the name were not showing.
I use mpc renderer in tandem with libplacebo. If the hdr is not supported by one i use the other and vice versa. I especially found sample from dolby website that don't work with libplacebo but work with mpc-hc shader system. All my test were done mostly on sample coming from dolby website and some others from kodi sample list.



There a lot of chance i post an alpha release tomorow. I have memory leak i need to fix before posting it.

[lechtung]

Really great work. I'm a programmer myself and I know how many hours it takes to do what you're doing. So thank you so much and I'm looking forward to trying it out!

[leamsid]

Happy to see that you're still working on this A few questions on my side though:
1) did you update the mpcvr version you are using ? Please can you test the FEL files here and confirm everythin is rendered properly
2) are you working on kodi 22 nighthy builds ? I understand that kodi 22 is 98% ready so this may be the good time to merge to master as there will be limited changes before official release.
3) did you have a look at the network (it was broken in the last version you released)

[tiben20]

Happy to see that you're still working on this A few questions on my side though:
1) did you update the mpcvr version you are using ? Please can you test the FEL files here and confirm everythin is rendered properly
2) are you working on kodi 22 nighthy builds ? I understand that kodi 22 is 98% ready so this may be the good time to merge to master as there will be limited changes before official release.
3) did you have a look at the network (it was broken in the last version you released)

1- I specify again mpcvr is highly customised. I only use the interesting stuff but its not hard to compare and get a change they made to fix something only the subtitles part is 500 times more complex in dsplayer. The funny part is im the one who the d3d11 for mpcvr. PS: Just test all 3 files function correctly
2- Im working on the master and i sync from time to time. Im around 130 commit behind which is not a lot for a Project this size
3- no i didn't look into it
here is the release i was talking about
https://github.com/tiben20/xbmc/releases....0.1-alpha
I want to know if dll are needed on start especially.
A lot of info on the osd are wrong so you dont need to tell me about those

If you want to see the change i make
https://github.com/tiben20/xbmc/commits/...march2024/
i will try to be more explicit on the comments i leave in the change

[roby69]

Hello tiben20,
I’m getting the following dll not found errors when starting kodi:
VCRUNTIME140D.dll
ucrtbased.dll
MSVCP140D.dll

[only1hammy]

Happy to see that you're still working on this A few questions on my side though:
1) did you update the mpcvr version you are using ? Please can you test the FEL files here and confirm everythin is rendered properly
2) are you working on kodi 22 nighthy builds ? I understand that kodi 22 is 98% ready so this may be the good time to merge to master as there will be limited changes before official release.
3) did you have a look at the network (it was broken in the last version you released)

1- I specify again mpcvr is highly customised. I only use the interesting stuff but its not hard to compare and get a change they made to fix something only the subtitles part is 500 times more complex in dsplayer. The funny part is im the one who the d3d11 for mpcvr. PS: Just test all 3 files function correctly
2- Im working on the master and i sync from time to time. Im around 130 commit behind which is not a lot for a Project this size
3- no i didn't look into it
here is the release i was talking about
https://github.com/tiben20/xbmc/releases....0.1-alpha
I want to know if dll are needed on start especially.
A lot of info on the osd are wrong so you dont need to tell me about those

If you want to see the change i make
https://github.com/tiben20/xbmc/commits/...march2024/
i will try to be more explicit on the comments i leave in the change

Windows 11 24H2 here.  These are the errors I get on run:

https://imgur.com/a/eRraIAW

[ZendoniR]

Could it be that you compiled in Debug mode?

The DLL files with a “D” at the end are part of the Visual Studio Debug libraries. These are not included in the standard Visual C++ Redistributables, but only in a full Visual Studio installation.

If the program was compiled in Debug mode, it must be recompiled in Release mode to run on systems without Debug libraries. Otherwise, Windows won’t be able to find VCRUNTIME140D.dll, and the program won’t start.

[tiben20]

Could it be that you compiled in Debug mode?

The DLL files with a “D” at the end are part of the Visual Studio Debug libraries. These are not included in the standard Visual C++ Redistributables, but only in a full Visual Studio installation.

If the program was compiled in Debug mode, it must be recompiled in Release mode to run on systems without Debug libraries. Otherwise, Windows won’t be able to find VCRUNTIME140D.dll, and the program won’t start.

Kodi is composed of a shit load of projects ill just track down which one is in debug mode and fix it. 99% of it is compiled in release i think the libsubs are in debug should make sense because i fixed stuff on it and i needed it on debug. will update when fixed

It was libsubs recompiled it "also cec and nhttp2 which is fixed in a new one once again"
https://github.com/tiben20/xbmc/releases/tag/v0.0.4

Ps: my next time will be to use the libplacebo scaling right its only doing 1 to 1 the hard part is done

Afterward i will see with you guys on what are the priorities