Kodi Community Forum

I would love to have x64 as i only use just that one

It actually shows up as 17.4 on the splashscreen

That's normal for RC builds and in system info it will display 17.5RC1 like in the screenshot
Having some trouble with a x64 build but will try.

// Edit

Can't figure out the x64 build but best guess is something changed in static linking of Python libraries, not sure how to fix that

(2017-08-31, 22:07)RickDB Wrote: [ -> ]That's normal for RC builds and in system info it will display 17.5RC1 like in the screenshot
Having some trouble with a x64 build but will try.

// Edit

Can't figure out the x64 build but best guess is something changed in static linking of Python libraries, not sure how to fix that

There are previous posts about something that was different with the kodi video player in x64 builds. I can't remember where the posts were made though. Thank you again for taking a crack at this though.

(2017-08-31, 19:19)RickDB Wrote: [ -> ]Unofficial build based on Kodi 17.5RC1 is linked below, recommend making backups beforehand as this my first go at building Kodi so errors may occur.
This is just a stop-gap measure till the developer returns as I can only do basic patches and builds like this, after install your system information should list this version:



Fork repo used in build for reference:

https://github.com/RickDB/xbmc/commits/Krypton_dsplayer



Setup 32bit: DSPlayer 17.5RC1 Krypton - build (20170831-0b0f92fce4)
Setup 64bit: Fails to compile.

All credits go to @aracnoz as this is just a build merged with all his changes.

Hey thanks for this - seems to be very stable. I normally use the x64 version of Dsplayer, but will live with this build for a while (the whole 32 vs 64bit debate with dsplayer is overblown anyway - I never see any real differences in render times etc).

BTW, I downloaded the latest Lav nightly and overwrote lav inc in this build in order to use the new dx11 decoder.

So thanks again.

K

Yeah did the same for LAV Filters here to get DX11 offloading, once they are released as stable will include in a new build
Only downside is that it's missing the UI settings to set that in Kodi directly but might be able to make a small patch for that.

Judging by the build documentation Kodi 18 is a bit more mature when it comes to x64 support, one of the upsides is more accessible memory of course but chance of exceeding 3.5Gb is gonna be a rare case.

Thanks for sharing

I went with a fresh install and threw all my usual stuff on there and everything is working fine on my end.. Good job figuring it all out..

Added D3D11 setting so that once LAV filters are out of testing DSPlayer can support it with internal filters as well (otherwise would reset it to no HW accel), tested that here with latest LAV nightly (0.70.2.66) and working:

https://github.com/RickDB/xbmc/commit/61...167432bb73

So new build once LAV filters are marked as stable.

Awesome. I'm gonna have to give this a try tonight.

I would also suggest submitting some pull request's to aracnoz's DSPlayer branches so he doesn't lose out on feature improvement if and when he returns.

How to know if aracnoz is not dead?

(2017-09-01, 14:00)RickDB Wrote: [ -> ]Added D3D11 setting so that once LAV filters are out of testing DSPlayer can support it with internal filters as well (otherwise would reset it to no HW accel), tested that here with latest LAV nightly (0.70.2.66) and working:

https://github.com/RickDB/xbmc/commit/61...167432bb73

So new build once LAV filters are marked as stable.

Cool.

K

(2017-09-01, 07:51)oldpainless Wrote: [ -> ]

(2017-08-31, 19:19)RickDB Wrote: [ -> ]Unofficial build based on Kodi 17.5RC1 is linked below, recommend making backups beforehand as this my first go at building Kodi so errors may occur.
This is just a stop-gap measure till the developer returns as I can only do basic patches and builds like this, after install your system information should list this version:



Fork repo used in build for reference:

https://github.com/RickDB/xbmc/commits/Krypton_dsplayer



Setup 32bit: DSPlayer 17.5RC1 Krypton - build (20170831-0b0f92fce4)
Setup 64bit: Fails to compile.

All credits go to @aracnoz as this is just a build merged with all his changes.

Hey thanks for this - seems to be very stable. I normally use the x64 version of Dsplayer, but will live with this build for a while (the whole 32 vs 64bit debate with dsplayer is overblown anyway - I never see any real differences in render times etc).

BTW, I downloaded the latest Lav nightly and overwrote lav inc in this build in order to use the new dx11 decoder.

So thanks again.

K

Yes. I just tested this build and it looks very good. However I've got some MKV files that simply crashes Kodi every time. I'm looking at the Kodi log file but there isn't any interesting info there. I tried to play those files in latest MPC-HC using LAV filters and madVR and they play without any issues. I just tried to mangle all DSPlayer options and Kodi still crashes. Is there any way I can send You short version of such file(s) RickDB, so You could test/debug?

Please notice that those movies plays without any issues on normal Kodi/LibreELEC.

Certain files is odd especially if it's only with Kodi but few questions:

- Does it report a madVR crash?
- Does it crash with the last official build (17.3)?
- What graphics card and drivers?

Windows Event Viewer might show a bit more info on the application crash like reported dll at fault, what we can test as well:

- Disable any refresh rate changer (Kodi internal + madVR's)
- Use Direct3D 9 in both Kodi DSplayer and in madVR's own settings
- Disable exclusive mode in madVR
- If using Nvidia + NNEDI try NGU

MPC-HC is most likely using a more up to date LAV filter version as the one included with Kodi is a few versions behind, if all else fails you can try a manual upgrade for those:

- Make sure Kodi is not running
- Download and install latest LAV filters:

https://github.com/Nevcairiel/LAVFilters...taller.exe

- Now copy those x86 files to the Kodi dsplayer folder, in the below example from the left folder to right:

Now that is a good tech reply thanks for the hints. I'll test all of them. Stay tuned.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]Certain files is odd especially if it's only with Kodi but few questions:


- Does it report a madVR crash?

If you're asking what Windows show then no. "Kodi stopped working". Kodi.exe crashes everytime.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- Does it crash with the last official build (17.3)?

No.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- What graphics card and drivers?

GeForce GT 1030 and latest Nvidia 384.94 drivers. Pure and fresh Windows 10 with all updates. It's a PC only for Kodi. What's important. Soundcard is also from GT 1030 (comes from HDMI).

(2017-09-01, 23:18)RickDB Wrote: [ -> ]Windows Event Viewer might show a bit more info on the application crash like reported dll at fault, what we can test as well:

It shows this (in xml format):

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- Disable any refresh rate changer (Kodi internal + madVR's)

Tried that. Still crashes.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- Use Direct3D 9 in both Kodi DSplayer and in madVR's own settings

Tried that. Still crashes.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- Disable exclusive mode in madVR

I disabled it in Kodi DSPlayer settings and still crashes.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]- If using Nvidia + NNEDI try NGU

I'm using default madVR setting for Kodi DSPlayer build. I don't use NNEDI or NGU.

(2017-09-01, 23:18)RickDB Wrote: [ -> ]MPC-HC is most likely using a more up to date LAV filter version as the one included with Kodi is a few versions behind, if all else fails you can try a manual upgrade for those:

- Make sure Kodi is not running
- Download and install latest LAV filters:

https://github.com/Nevcairiel/LAVFilters...taller.exe

- Now copy those x86 files to the Kodi dsplayer folder, in the below example from the left folder to right:

Tried that already with latest build from this file https://files.1f0.de/lavf/nightly/LAVFil...0.2-66.exe and still crashes.

Edit: Maybe I'll post 30-60 seconds of such "crashing" file so You can test it on your setup?