(2017-02-08, 20:20)aracnoz Wrote:

(2017-02-08, 17:11)Slurm Wrote:

(2017-02-08, 15:58)_Andy_ Wrote: To confirm the issue with PVR and DSPlayer build install the official build of Kodi 17 and try and if the error is the same make a bug report for the Kodi team. If they don't know the issue they can't fix.

Just tested vanilla kodi and there channel switching works. So it belongs in this thread.

my bad,

it should never happen that DSPlayer creates problems in VideoPlayer, I never wrote a line of code for the PVR because I don't have the possibility to test this part

anyway I think that I figured out where is the problem, but you have to test this fix to have a confirmation before to update the releases at first page

http://www.mediafire.com/file/7jjrkoxrpueft18/fixPVR_x86.rar
http://www.mediafire.com/file/yvd1b9zfv50nfmm/fixPVR_x64.rar

(2017-02-08, 19:47)Warner306 Wrote:

(2017-02-08, 12:11)powermarcel10 Wrote: Hi,

Thanks for the new build! Really nice!

Only I have 2 issues..

Biggest one is that external filters are nog working for me.. Im using dsplayer because I have a license for SVP (smooth video project) Normaly I choose ffdshow raw video filter to use SVP. But I cant get it to work..

Another one is that when I change a PVR channel, the stream Just stops and I have to enable a different channel manually. But everytime I try to change to another channel it stops.. For the record, Im not using dsplayer for PVR.

Does anyone have sugestions for this 2 issues?

Verstuurd vanaf mijn MI 5 met Tapatalk

Did you try adding an extra external filter to the internal filters?

(2017-02-08, 20:56)DougShuffield Wrote: 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

(2017-02-08, 22:56)_Andy_ Wrote: 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.

(2017-02-09, 13:20)yamcenutzer Wrote: 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)"

(2017-02-10, 16:07)DougShuffield Wrote:

(2017-02-08, 20:56)DougShuffield Wrote: 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

(2017-02-10, 16:46)aracnoz Wrote: 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