search

koying / SPMC

fork of xbmc/kodi
Other
635 stars 257 forks source link

16.6.0 beta3 (TEST) #706

Closed koying closed 7 years ago

koying commented 7 years ago

3rd beta: https://github.com/koying/SPMC/releases/tag/16.5.82-spmc

It has a "test" signature, so can be installed along 16.5.

Changelog for 16.6:

Changelog for beta 2:

Changelog for beta 3:

classicjazz commented 7 years ago

I have been using beta 3 for several days on 5 Shield TVs. Things are running very smoothly on Shield Experience 5.1. I think that this is the best SPMC release yet.

koying commented 7 years ago

Ok, cool. Thanks for the reports. I guess I will release this WE.

Karkas66 commented 7 years ago

I think there are still minor visual framedrops in the Video Stream if you watch a Movie for over 30 Minutes like discussed in this thread, but I still need to investigate in this (with debug). L8er!

Karkas66 commented 7 years ago

OK i´ve found a bug in the 5.1 Release. For some reason Nvidia dropped support for 24hz video resolution in my setup. SPMC Debug Log says on startup:

22:13:34.119 T:1541237024 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 59.940060 Hz 22:13:34.119 T:1541237024 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 59.940060 Hz 22:13:34.119 T:1541237024 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 60.000000 Hz 22:13:34.119 T:1541237024 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 60.000000 Hz 22:13:34.119 T:1541237024 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 50.000000 Hz 22:13:34.119 T:1541237024 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 50.000000 Hz 22:13:34.119 T:1541237024 NOTICE: Found (1920x1080@59.940060) at 16, setting to RES_DESKTOP at 16 22:13:34.119 T:1541237024 NOTICE: Checking resolution 16

The Android App TVHZ from Chainfire confirms this. Application can not see the 24p resolution support of my setup, that has been there in the 3.3 Release. Here is an old spmc log entry:

18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 23.976025 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 24.000000 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 25.000000 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 29.970030 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 30.000000 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 50.000000 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 59.940060 Hz 18:32:05.335 T:1477937456 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 60.000000 Hz 18:32:05.335 T:1477937456 NOTICE: Found (3840x2160@60.000000) at 23, setting to RES_DESKTOP at 16

I think there is not much we can do about it. Is here anyone who still has 24p resolution in a 4k Setup with an active AVR in between TV and Shield?

MrMC commented 7 years ago

08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 59.940060 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 59.940060 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 50.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 50.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 60.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 60.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 30.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 30.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 24.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 24.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 25.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 25.000000 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 29.970030 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 29.970030 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 1920 x 1080 for display 0 with 1920 x 1080 @ 23.976025 Hz 08:10:25 T:138680894544 NOTICE: Found resolution 3840 x 2160 for display 0 with 3840 x 2160 @ 23.976025 Hz

Works for me on 5.1. MrMC -> Denon W3200 -> Samsung UHDTV

JFG90 commented 7 years ago

@Karkass66 have you tried turning adjust refresh rate off? I don't have mine on as in my opinion it's not needed, everything plays perfectly for me

Karkas66 commented 7 years ago

I just tried it @JonnyGadd but sadly it brings visual shutter every 8-10 seconds on 24hz and 25hz Video Files :-( But It is better than the constant framedrop I have without it

Karkas66 commented 7 years ago

Some ppl @ the nvidia Forum posted similar hickups due to refresh rate not synced to frame rate:

https://forums.geforce.com/default/topic/994727/shield-tv/shield-experience-upgrade-5-1-for-shield-tv/post/5093356/#5093356

JFG90 commented 7 years ago

That sucks mate I can't say I've come across that myself!

Karkas66 commented 7 years ago

OK Rollback guys. I found the Problem! It was a setting in my AVR that changed the published resolutions to only 50/60hz. I revoked that and everything is at it´s supposed resolution again with refresh rate change on. I try some video files now to see if there are other problems left

ghost commented 7 years ago

https://github.com/koying/SPMC/issues/783

Using BETA3

LostEchoes commented 7 years ago

I also I copied over all the files (userdata, addons, etc.) from my working 16.5.5 folder to the latest 16.5.8 beta3 test folder. The fist time I used SPMC 16.5.8 I had a crash on exit. Just once. Unfortunately I did not keep the log. All the next times I used SPMC I did not have that crash on exit error.

p.s. Having the 16.5.8 beta3 installed, will we get the update for the stable version, or do we have to revert to 16.5.5 to get it?

Theetjuh commented 7 years ago

My 2015 Sony TV is upgraded to Marshmallow, DTS isn't working anymore. Is that because of MediaTek? Or should it still work on RAW with this test build? I read something in the passthrough topic on Kodi, that it was removed or atleast left out.

LostEchoes commented 7 years ago

Well after I watched a tv series I've got the crash on exit error again. Here is the log:

http://paste.semperpax.com/pciusboey

koying commented 7 years ago

Well after I watched a tv series I've got the crash on exit error again

Well, that's still beta2

koying commented 7 years ago

My 2015 Sony TV is upgraded to Marshmallow, DTS isn't working anymore

Should work in IEC. Doesn't it? RAW assumes working RAW DTS on Mashmallow, which is not the case on Sony and Phillips TV

Theetjuh commented 7 years ago

Should work in IEC. Doesn't it? RAW assumes working RAW DTS on Mashmallow, which is not the case on Sony and Phillips TV

Setting both on IEC only delivers static

LostEchoes commented 7 years ago

@Koying That's really strange. I'm confident I downloaded and installed Beta 3.

Edit: I probably accidentally downloaded Beta 2.

JFG90 commented 7 years ago

The latest beta has been perfect for he with no crashes after exit on playback! When will this be ready for official release?

koying commented 7 years ago

16.6.0 is released. Thanks for your feedback.