Posts: 363
Joined: Nov 2014
Reputation:
16
Nice I hadn't tracked that one down yet. Good to know it'll be fixed in the next build.
Denon X6500H 7.2.4 -> LG OLED65C9P
Main: NVIDIA Shield Pro (2019)
Other Devices: Apple TV 4K, FireStick 4K Max (2023), Homatics Box R 4K
Retired devices: Zidoo X9S, Xiaomi Mi Box, All the old RPi’s
Posts: 400
Joined: Jun 2015
4-13 build did all sorts of crazy things to the skin and display and just seemed to break more and more as it sat idle. Is this the issue with Kodi 17 build that's being addressed?
Also, does anyone know how to get a custom skin to work (or at least be switchable to) in K17? The default is um, well, less then desirable.
On the positive it did seem to have better SBS 3D playback though possibly a slight audio sync issue. Difficult to tell with the few tests I ran on quick cutting trailers.
Posts: 2,510
Joined: Dec 2012
Reputation:
216
In the beginning, my testing issues with logs were addressed and all was well.
Somewhere along the line, all that changed.
I was the 1st to promptly detail issues as soon as a new build was released, complete with proper log(s).
Those issues and logs were met with less than desirable responses and just plain wrong accusations regarding my competence providing them.
Perhaps that was my fault due to information overload, bad communication skills, or simply because I'm not a techy like so many others.
Attempts were made to turn back the clock and represent the same detailed issues with proper logs.
Due to any possible communication gap, the words were changed but the meaning remained relevant while details were simplified.
Again the responses were directed at my ignorance and incompetence which were incorrect hasty replies avoiding the input provided altogether.
I assume that's because I am an Intel/Nvidia user and not a mainstream tester providing biased input regarding NUC boxes which is 99% of the Windows posts here and other threads regarding 3D MVC coming to KODI some day.
This build still does not work for me using anything after the 4/1 build.
Something changed for the worse in the following build and the snowball continued to roll into the builds after that.
Although this issue was reported immediately, it fell on deaf ears and attention was diverted to who knows what now that I can't test anymore.
This weekend I reinstalled a fresh Windows just to rule out any Microsoft clashes due to customization and adjustments in place previously.
I installed all the latest builds that didn't work in the past, and naturally they still didn't work.
As soon as I installed the 4/1 build, everything worked perfectly, just as before.
The way I see it, if it worked in the 4/1 build, it should still be working in all these later builds.
"It works for me" and "It's an Alpha, expect problems" mean nothing to a user that had a working build and no longer does, many weeks and many builds later.
I see no point in providing logs here and now anymore.
I would again if they were actually dissected so that a solution could actually be realized or at least considered.
I agree with 'the minion'.
Hostility and disdain has crept it's way in here due in part to the treatment of minorities who desire to be included.
The 4/1 build works so perfectly for me, I would be ecstatic if this was updated only with v.17 Krypton changes from time to time.
There could be (2) builds for Windows 3D MVC.
1 which is the current development (Intel HD Graphics) and the other for (Intel/Nvidia only).
The Nvidia would only need 4/1 build with v.17 updates added.
At the very least, more users, minority or not, could be included.
I would be very pleasured to enjoy the KODI experience as much as the majority are now and in the future.
Thank you for understanding the nature of my post, the reason I wrote it, and consideration of it.