Well I would not say no priority but due to the number of ATV/Crsystal HD users compared to currently other issues that impact potentially more users the prioirty might not be the highest.
So for the time being I suggest to wait till Sam finds time to look into this.
Just wanted to jump in and say I’ll lend a hand in this in any way I can, and also ask a semi-related question.
I’ve got the crystalhd driver working on Ubuntu 16.04, VLC can use it just fine, but obviously the normal version of Kodi won’t see it.
In looking at the osmc git, I see one patch pertaining to CrystalHD. I downloaded this patch and tried to run it against the current Kodi source from git and this is what I got:
crystalhd-enable.patch:79: trailing whitespace.
[ AC_DEFINE([HAVE_LIBCRYSTALHD], , [Define to 2 if you have the ‘New Broadcom Crystal HD’ library.]) ],
crystalhd-enable.patch:361: trailing whitespace.
crystalhd-enable.patch:389: trailing whitespace.
crystalhd-enable.patch:390: trailing whitespace.
crystalhd-enable.patch:391: trailing whitespace.
error: configure.ac: No such file or directory
warning: system/settings/settings.xml has type 100755, expected 100644
error: xbmc/cores/VideoPlayer/DVDCodecs/Video/Makefile.in: No such file or directory
error: patch failed: xbmc/settings/SettingConditions.cpp:29
error: xbmc/settings/SettingConditions.cpp: patch does not apply
Anyway, my question is this: if I get source for 16.1, can I just apply this patch and build a version of Kodi 16.1 that supports crystalhd? I’ve got a 2006 Mac mini that I use as a media center, and being able to use the crystalhd would really help it out
Is it possible to provide some temporary solution like replacing kodi.bin with last working version?
I remember that in Crystalbuntu days it was working this way. I don’t want reinstall whole OSMC because of files on HDD.
If it will be possible to quick replace only kodi.bin we could also test alpha builds one by one and find which one made regression.
Kodi from January package doesn’t work under latest OSMC. Did I something wrong?
/usr/lib/kodi/kodi.bin: error while loading shared libraries: libjasper.so.1: cannot open shared object file: No such file or directory
Ok, I copied also libjasper.so.1 and libjasper.so.1.0.0 and Kodi is starting but remote control doesn’t work.
If you released a new build with CrystalHD support (even if it doesn’t work completely smoothly) I, personally, would greatly appreciate it. As it is now, I can’t watch anything in HD with just the software codecs, and that makes my ATV almost useless. I would most definitely upgrade to better hardware (and that is, of course, the best solution) I just don’t have the money available at the moment. Thanks for all your work, Sam!
care to elaborate on the exact issue? Kodi Krypton has grown bigger than Jarvis and therefore even getting Crystal support back in, there is just not enough left to still work ok? Do see it working ok if certain functions (please provide list), which might not be needed, one would disable? Or any other (memory) performance one can do? (Reduce number of (specific) plug-ins?).
@Spinner - Can you create a Sticky with commands (like the brilliant error one) that allows us to downgrade to a version that does use CHD? That way until it comes through in newer we can use the older one or remain there.