Given the repeated issues with initial compilation/installation I’ve put together a repo and script for this purpose. This is now compiling directly on the Vero 4K, rather than a cross-compile from the RPi3 as I’d done originally (I realise some new users won’t have another box to work from). It works.
The final test will be to run it from a clean OSMC reinstallation which I should be doing next week, to ensure I’ve not missed any depends etc for a new user to stumble over.
My one concern is that anyone using all internal grabbers needs 2 entries in the config, for both “framegrabber” and for “amlgrabber”, as @nrosier pointed out to me. This needs to be addressed or there will still be the traffic to this thread over basic installation issues which I was trying to avoid.
There doesn’t seem to be an option in HyperCon.jar to allow for this. The “Internal Frame Grabber” is enabled or not and that’s it. So they would have to manually edit /etc/hyperion/hyperion.config.json if that’s their thing. I could insert the:
"amlgrabber" :
{
"width" : 70,
"height" : 40,
"frequency_Hz" : 24.0,
"priority" : 799
},
portion using sed into the default config file, but this would be overwritten when they send their config over from HyperCon.
Do I just point out the pitfall in the README? Will they read it?!