(2017-06-06, 22:37)Soliver84 Wrote: DVBviwer Backend Not Funk.

(2017-06-06, 20:30)Cinder Wrote:

(2017-06-06, 19:43)Warner306 Wrote: You have to use SMB shares.

I was starting to suspect something like that because the nfs shares are extremely slow on windows, they work superbly on my Arch Linux installation. But why are samba shares required over nfs which I assume can be tuned to be faster?

I'm trying to share settings between Linux and Windows, is this feasible? Also, can I have the windows machines link samba shares and Linux point to nfs shares if they point to the same folders, ie movies or something, or will the database interpret the sources as different and scrape duplicates of everything - one samba path and one nfs path file?

Quote:[global]
workgroup = WORKGROUP
netbios name = (a name...)
server string = Samba Server
;interfaces = (put here the IP/24 of your interface, and remove ";" , facultative)
security = USER
map to guest = Bad User
log file = /var/log/samba/%m.log
name resolve order = wins lmhosts hosts bcast
dns proxy = No
idmap config * : backend = tdb
create mask = 0664
force create mode = 0664
directory mask = 0775
force directory mode = 0775
printing = bsd
printcap name = /dev/null
load printers = no
disable spoolss = yes


[homes]
comment = Home Directories
read only = No
browseable = No


[fichier]
comment = repertoire fichier
path = /srv/samba/share
read only = No
create mask = 0775
guest only = Yes
guest ok = Yes

(2017-06-02, 19:50)SALAMINOMACHOS Wrote: May i run Ds Player Krypton 17.3 with Kodi Krypton 17.0?
The main problem is that i can not install Kodi Krypton 17.3
It crashes

(2017-06-06, 21:59)Warner306 Wrote:

(2017-06-05, 19:22)Warner306 Wrote:

(2017-06-05, 09:45)tingtong5 Wrote: Yes! I am. I once tried the other option but I did not give me the amount of control I liked to configure madvr , or at least not as easy. Do you suggest this might be the cause of the increased average frame render time?

No, rendering times should be the same.

No one else can comment on this? I'm still using 16.1 and I'm curious, too, if this is a problem with 17.3? Are frame rendering times increased?

(2017-06-07, 20:41)tingtong5 Wrote:

(2017-06-06, 21:59)Warner306 Wrote:

(2017-06-05, 19:22)Warner306 Wrote: No, rendering times should be the same.

No one else can comment on this? I'm still using 16.1 and I'm curious, too, if this is a problem with 17.3? Are frame rendering times increased?

I did some extensive testing today, using the same scene of some 1080P movie.

Average frame render time Kodi DSplayer 16.1 around 18 ms.
Average frame render time Kodi DSplayer 17.3 around 38 ms!!!!!! About twice as much!

CTRL-J during playback shows exactly the same going on in Madvr (except for the queue numbers).
O in Kodi shows low CPU usage for both versions.

All madvr settings exactly the same.
All kodi settings exactly the same.

Also upgraded nvidia driver to the latest, did not make any difference. Installed both (32 bit) versions several times, exact same results!

Something seems to be awfully wrong with this 17.3 version, unless of course I am overseeing something, which I hope is the case ;-)

Can anyone confirm this behaviour? I am on windows 7 64 bits by the way.

(2017-06-07, 23:20)Warner306 Wrote:

(2017-06-07, 20:41)tingtong5 Wrote:

(2017-06-06, 21:59)Warner306 Wrote: No one else can comment on this? I'm still using 16.1 and I'm curious, too, if this is a problem with 17.3? Are frame rendering times increased?

I did some extensive testing today, using the same scene of some 1080P movie.

Average frame render time Kodi DSplayer 16.1 around 18 ms.
Average frame render time Kodi DSplayer 17.3 around 38 ms!!!!!! About twice as much!

CTRL-J during playback shows exactly the same going on in Madvr (except for the queue numbers).
O in Kodi shows low CPU usage for both versions.

All madvr settings exactly the same.
All kodi settings exactly the same.

Also upgraded nvidia driver to the latest, did not make any difference. Installed both (32 bit) versions several times, exact same results!

Something seems to be awfully wrong with this 17.3 version, unless of course I am overseeing something, which I hope is the case ;-)

Can anyone confirm this behaviour? I am on windows 7 64 bits by the way.

Try the 32-bit version?

(2017-06-07, 23:20)Warner306 Wrote:

(2017-06-06, 21:59)Warner306 Wrote: No one else can comment on this? I'm still using 16.1 and I'm curious, too, if this is a problem with 17.3? Are frame rendering times increased?

Try the 32-bit version?

(2017-06-08, 12:59)ashlar Wrote:

(2017-06-07, 23:20)Warner306 Wrote:

(2017-06-06, 21:59)Warner306 Wrote: No one else can comment on this? I'm still using 16.1 and I'm curious, too, if this is a problem with 17.3? Are frame rendering times increased?

Try the 32-bit version?

I'm using 17.3 x86. Yesterday I installed madVR 0.91.10 to give this a go (before I was on an old release, prior to NGU's introduction). Rendering times seem pretty identical to me. I did *not* install Creator's Update, as I read on madVR's thread on Doom9 that it could cause problems. Using a GTX 660 on my HTPC I can use NGU Anti-Alias or NGU Sharp set at medium or high (depending on starting resolution and number of pixels to be processed, as we know 4:3 or 2.35:1 sources are easier than 16:9 ones).

(2017-06-09, 12:56)mrdogman Wrote: I have a problem: ReClock is not showing up as a selectable Audio Renderer in the DSPlayer settings in Kodi.

I tried reinstalling ReClock and rebooting and that hasn't helped matters... am I missing a step?
I notice the WASAPI options aren't showing up either.

I've been following this guide for it: https://forum.kodi.tv/showthread.php?tid=222576

My OS is Windows 7 Ultimate SP1 x64. I tried both 1.9.0.0 and the 1.9.0.6 Beta of ReClock. Kodi version is the DSPlayer version Krypton 1.73 x86. Thanks for any help.