[aracnoz]

I have tested both x32 and x64. In my case the x64 is very stable. I never have had a crash. One issue with my skin i use (Madnox) i get an error in module PIL

Code:

File "C:\Program Files (x86)\Kodi17_ds_x64\addons\script.module.pil\lib\PIL\Image.py", line 66, in <module>
                                                from PIL import _imaging as core
                                            ImportError: DLL load failed: %1 ist keine zul崳ige Win32-Anwendung.

In the x32 version the module load fine. So i guess it's because of x64 but i have deactivated the script.toolbox and all is fine. At the moment i use the x64 only.

probably I left pillow at 32bit version in the package of the dependecies at 64bit, I will fix this with the upcoming bugfix release

From what I read here, it seems the x64 Version requires a 32b bit Version to also be installed,
Installing a only a x64 version didn't work for me. It also only installs into "Program Files" and seems to be missing stuff it expects to be in "Program Files (x86)"

if the installer finds somewhere a previous installation of kodi it will use that path to update the program

p.s.

it's not necessary to install both version x86 and x64, you have to install only the one you will use

At this point, audio no longer works in Kodi and it must be restarted to regain audio.

Is it possible that DSPlayer is not shutting down the extra filters correctly, specifically FFDShow, and it is not allowing WASAPI to close properly thus the CAESinkWASAPI::InitializeExclusive: Failed to initialize WASAPI in exclusive mode -2004287478 - (AUDCLNT_E_DEVICE_IN_USE).?

My next step is to try to setup the system use Media Rules for Filter Management and see if there is any difference in performance.

Doug

I am seeing the same exact behavior when I use the media rules for filter management. Does anyone else have any experience using ffdshow as an audio filter with DSPlayer? Any help or suggestions are greatly appreciated!

Doug

I'm not able to reproduce this issue, but I haven't your hardware to make my test attendible, anyway the problem is with the ArcSoft Audio Renderer + FFDShow Audio (and maybe the ASUS Xonar HDAV1.3 Slim) , I saw some older discussion where this renderer + ffdshow was causing the audio device locked up to require a restart of the application, so the problem should not be in dsplayer