2018-12-05, 18:41
Hi,
I'm using Kodi on my nVidia Shield TV (2015).
Video files are streamed from my NAS thru NFS.
With some DVD ISOs (Star Trek DS9 and Star Trek Voyager DVDs for example), using beta versions of Leia (up until nightly of November 28th), the picture isn't completely smooth. There's a small "jump" ("stuttering" ?) approximately 2-3 times/sec. It's there constantly from beginning to the end of the file.
Since December 2nd nigthly (kodi-20181202-812855d8-master-arm64-v8a.apk), it's worse and practically unreadable : the image is freezing almost completely (but audio is ok), stepping forward every 5-10 seconds. Not really playing, just showing an image for 5-10 seconds will the sound is playing fine, then going forward to another one, etc.
Blu-ray ISOs and other video files are fine.
The stuttering problem wasn't there on Kodi v.17 and on Kodi V.18 alpha.
It appeared on beta versions of v.18 (beta 3 I think, but I'm not sure about that...)
The "unreadable" problem wasn't there before December 2nd nightly and is still there on the official RC.
Any thoughts ?
I'm using Kodi on my nVidia Shield TV (2015).
Video files are streamed from my NAS thru NFS.
With some DVD ISOs (Star Trek DS9 and Star Trek Voyager DVDs for example), using beta versions of Leia (up until nightly of November 28th), the picture isn't completely smooth. There's a small "jump" ("stuttering" ?) approximately 2-3 times/sec. It's there constantly from beginning to the end of the file.
Since December 2nd nigthly (kodi-20181202-812855d8-master-arm64-v8a.apk), it's worse and practically unreadable : the image is freezing almost completely (but audio is ok), stepping forward every 5-10 seconds. Not really playing, just showing an image for 5-10 seconds will the sound is playing fine, then going forward to another one, etc.
Blu-ray ISOs and other video files are fine.
The stuttering problem wasn't there on Kodi v.17 and on Kodi V.18 alpha.
It appeared on beta versions of v.18 (beta 3 I think, but I'm not sure about that...)
The "unreadable" problem wasn't there before December 2nd nightly and is still there on the official RC.
Any thoughts ?