When comes the next release

[micha53]

Hello,
in the past the releases came with 1..2 months between. Now we have 2.0.0. alpha 9 since november.
I am waiting for the next release because I have a project with hyperion and a TV HAT at raspi 4 (rpi3 has not enough power to do this with the former hyperion, wich is not availabe for rpi4, only till rpi3b+).
I need the feature to change the SPI port to SPI1, wich comes with the next release.

What is the timeeline for the next relaese?

[tpmodding]

Hi,

we don't have any release time or a timeline, we provide new version when we think it is time for a new release.

If you need the latest master then you can compile it for your own, for more information have a look here:
https://github.com/hyperion-project/hyperion.ng/blob/master/CompileHowto.md

[micha53]

Thank you for the hint, I tried it today. It is not so easy to reproduce that. I am not as familiar with compiling by myself, and your link is for multiple platforms. It would be helpful, if there were a guideline to jump to the next right step.
I tried it on a raspi4b, and got 2 Errors, and I do not know if they are showstoppers for me now or not (because of the message "cc1: all warnings being treated as errors"):

pi@Medienserver:~/hyperion/build $ make -j $(nproc)
...
cc1: all warnings being treated as errors
make[2]: *** [dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/build.make:102: dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/x509.c.o] Fehler 1
make[1]: *** [CMakeFiles/Makefile2:1577: dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/all] Fehler 2
...
make: *** [Makefile:152: all] Fehler 2

before I processed the following steps, hope this was right:

sudo apt-get update

sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev

sudo apt-get install libraspberrypi-dev

export HYPERION_DIR="hyperion"

git clone --recursive --depth 1 https://github.com/hyperion-project/hyperion.ng.git $HYPERION_DIR"

cd "$HYPERION_DIR"
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..

[tpmodding]

when exactly did you try to make it?
before or after the revert?
a3c8fba

anyways: you can download the latest artefacts (compiled binarys) from LordGreys latest PR
https://github.com/hyperion-project/hyperion.ng/actions/runs/728734638#artifacts

[micha53]

I read "Lord-Grey committed 5 hours ago"
so I did it later, within the last 2 hours

[micha53]

On
https://github.com/hyperion-project/hyperion.ng/actions/runs/728734638#artifacts
I can find only Versions for Raspi 1..3, not for rpi4, or for ARMV6I and 7I, rpi4 has Arm Cortex-A72, don't know what I can use from here

[tpmodding]

armv7l

[micha53]

I got the armv7l, could extract it, and now my show stopped. Searching the net for "linux programm aus tar.gz installieren" or so brings me only not usable links, some say that there is a readme- or installation-file, or I get a huge amount of information that I am slain.
I have now 2 directories, bin and share. Where do I find an information how to deal with the to get a hyperion installation?

[micha53]

@Lord-Grey sorry, I do not know how to do this in detail...

[micha53]

for hyperion (not NG) exist packages only for rpi till rpi3, Unfortunately not for rpi4, or 4b. Is it possible to use the rpi3 installation for rpi4? There I could change the spi-port within the hyperion.config.json file before downloading it.

[tpmodding]

eine tar.gz musst du entpacken...danach gehst du in den ordner share/hyperion/bin, und dort liegt die hyperiond die du ausführen kannst.... wenn du nicht tiefgreifende linux kenntnisse hast, dann hast du zwei optionen: 1. linux kenntnisse erweitern oder 2. bisschen mehr geduld für das release aufbringen, (muss man heut zutage erwähnen: ist kein angriff und nicht böse gemeint) und hyperion(classic) wurde die entwicklung eingestellt da es .ng eine weiterentwicklung ist...

das könntest du aber auch mit der dort angegebenen compile howto selbst kompilieren

[micha53]

Na ich denke schon, daß ich meine Kenntnisse gerade erweitere, aber zum Guru werde ich es im Rest meines Lebens wohl nicht mehr schaffen :-) Beim classic Hyperion finde ich das Hypercon-Programm sehr eigenwillig, mal sehe ob ich lord-grey's version zum Leben erweckt bekomme.

[Lord-Grey]

@micha53

The following will create a separate structure for testing only.
It will not overwrite your existing installation and creates its own database.
If you have a complex config, you can export the current config and then import into the test instance via the UI.

1. Download the package to your pi's Downloads folder
2. Extract

cd $HOME
mkdir hyperion.ng-test
cd hyperion.ng-test
tar -xvf ../Downloads/Hyperion-2.0.0-alpha.9-PR#1164-Linux-armv7l.tar.gz

3. Stop hyperion standard service

systemctl stop hyperion.service

4. Start hyperion

./bin/hyperiond -d -u test &

5. Stop hyperion

pkill 'hyperiond'

5. Clean-up (if you are done with the tests...)

cd $HOME
rmdir hyperion.ng-test

Hoping that gives you a start...

[micha53]

Thank you so far..
My situation is a little bit other than you expect. I have not yet an Hyperion.ng installation, because my aim is to test if it is possible to run hyperion or ~.ng together with the Raspberry TV HAT (driven by TVHeadend software) at one rpi system. This would be a small DVB-T-Receiver with an ambilight control included. At a rpi3b+ it does not satisfy, too much artefacts at the TV screen...
The problem is, the TV HAT uses spi0 to get the video stream, this is hardwired and can not be changed. That's why I need spi1 for Hyperion, and because of that I did not yet install Hyperion.NG at my rpi4. I am afraid of conflicts with the TV HAT.

But if I look at your script it looks like it would work without a standard installation, I should simply let out your point 3 and I can wait with the final clean up till alpha.10. Is that right?

[Lord-Grey]

@micha53 Yes, the above is giving you the ability to test a hyperion version without interfering with other elements.
If you have not installed hyperion, you do not need step3.

Note: As this is just a test environment, it will not install hyperion to start hyperion automatically after reboot.
So everytime you would like to start hyperion newly, you need to

cd hyperion.ng-test
./bin/hyperiond -d -u test &

If everything works, of course we can discuss how to install it....

So for your objective " to test if it is possible to run hyperion or ~.ng together with the Raspberry TV HAT",
the outline above gives you the most flexibility to explore and later install it (the official release).

In case of problems or other feedback, do not hesitate coming back.

[micha53]

@Lord-Grey I still have problems:
first, I work with SSH, is this ok and possible?
doing
cd hyperion.ng-test
./bin/hyperiond -d -u test &
works only with the 2nd line:
bin/hyperiond -d -u test &
or must I call it from subdirectory share?

But I still work with the actual last version..

How to download the Version you recommend?

[Lord-Grey]

How to download the Version you recommend?

Go to and select the Artifact that you need. before transferring to the rpi, extract the zip and only transfer the tar.gz as outlined above:
https://github.com/hyperion-project/hyperion.ng/pull/1164/checks?check_run_id=2297657617

[micha53]

I really must select Debian Stretch (x86_64).. not Raspberry PI 2 &...

[Lord-Grey]

first, I work with SSH, is this ok and possible?

Yes, you need to work via a terminal on the rpi

works only with the 2nd line:

If the following does not work:

cd $HOME
cd hyperion.ng-test
./bin/hyperiond -d -u test

what is reported back from the terminal?
Do execute every command one-by-one and check, on failures

[micha53]

now it does a bit more..

pi@Medienserver:~/hyperion.ng-test $ ./bin/hyperiond -d -u test &
[1] 14762
pi@Medienserver:~/hyperion.ng-test $ 2021-04-10T11:57:40.771 hyperiond MAIN         : <INFO> Starting Hyperion - 2.0.0-alpha.9-PR#1164, (HEAD detached at pull/1164/merge) (GitHub-c688d245/be3d4752-1617891721), built: Apr  8 2021:15:08:21
2021-04-10T11:57:40.772 hyperiond MAIN         : <DEBUG> main.cpp:384:main() | QtVersion [5.7.1]
2021-04-10T11:57:40.772 hyperiond MAIN         : <INFO> Set user data path to '/home/pi/hyperion.ng-test/test'
2021-04-10T11:57:41.221 hyperiond DAEMON       : <DEBUG> PythonInit.cpp:40:PythonInit() | Initializing Python interpreter
2021-04-10T11:57:41.863 hyperiond SETTINGSMGR  : <ERROR> Database version [2.0.0-alpha.8] is greater that current Hyperion version [2.0.0-alpha.9-PR#1164]
2021-04-10T11:57:41.879 hyperiond SETTINGSMGR  : <DEBUG> SettingsManager.cpp:164:SettingsManager() | Settings database initialized
2021-04-10T11:57:41.880 hyperiond DAEMON       : <INFO> CEC handler created
2021-04-10T11:57:41.896 hyperiond EFFECTFILES  : <INFO> 39 effects loaded from directory :/effects/
2021-04-10T11:57:41.903 hyperiond EFFECTFILES  : <INFO> 22 effect schemas loaded from directory :/effects/schema/
2021-04-10T11:57:41.905 hyperiond EFFECTFILES  : <INFO> New Effect path "/home/pi/hyperion.ng-test/test/custom-effects/" created successfully
2021-04-10T11:57:42.704 hyperiond SETTINGSMGR  : <DEBUG> SettingsManager.cpp:164:SettingsManager() | Settings database initialized
2021-04-10T11:57:42.707 hyperiond BLACKBORDER  : <DEBUG> BlackBorderProcessor.cpp:64:handleSettingsUpdate() | Set mode to: default
2021-04-10T11:57:42.708 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Blackborder detector: enabled
2021-04-10T11:57:43.269 hyperiond DAEMON       : <INFO> set screen capture device to 'dispmanx'
2021-04-10T11:57:43.270 hyperiond DISPMANXGRAB : <DEBUG> Grabber.cpp:30:setVideoMode() | Set videomode to 0
2021-04-10T11:57:43.273 hyperiond DISPMANXGRAB : <INFO> Display opened with resolution: 1920x1080
2021-04-10T11:57:43.273 hyperiond DISPMANXGRAB : <DEBUG> Grabber.cpp:90:setWidthHeight() | Set new width: 80, height: 45 for capture
2021-04-10T11:57:43.276 hyperiond DAEMON       : <INFO> DISPMANX frame grabber created
2021-04-10T11:57:43.277 hyperiond V4L2:AUTO    : <DEBUG> Grabber.cpp:30:setVideoMode() | Set videomode to 0
2021-04-10T11:57:43.280 hyperiond V4L2:AUTO    : <INFO> Signal threshold set to: {12, 12, 12}
2021-04-10T11:57:43.281 hyperiond V4L2:AUTO    : <INFO> CEC detection is now disabled
2021-04-10T11:57:43.281 hyperiond V4L2:AUTO    : <INFO> Signal detection is now disabled
2021-04-10T11:57:43.282 hyperiond V4L2:AUTO    : <INFO> Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2021-04-10T11:57:43.282 hyperiond DAEMON       : <DEBUG> hyperiond.cpp:630:handleSettingsUpdate() | V4L2 grabber created
2021-04-10T11:57:43.284 hyperiond JSONSERVER   : <DEBUG> JsonServer.cpp:28:JsonServer() | Created instance
2021-04-10T11:57:43.285 hyperiond JSONSERVER   : <INFO> Started on port 19444
2021-04-10T11:57:43.301 hyperiond FLATBUFSERVE : <INFO> Started on port 19400
2021-04-10T11:57:43.302 hyperiond PROTOSERVER  : <INFO> Started on port 19445
2021-04-10T11:57:43.303 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
2021-04-10T11:57:43.306 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
2021-04-10T11:57:43.348 hyperiond LEDDEVICE    : <INFO> Start LedDevice 'file'.
2021-04-10T11:57:43.349 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Smoothing: enabled
2021-04-10T11:57:43.349 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-04-10T11:57:43.349 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:148:init() | deviceConfig: [{"colorOrder":"rgb","currentLedCount":1,"hardwareLedCount":1,"latchTime":0,"output":"/dev/null","rewriteTime":0,"type":"file"}]
2021-04-10T11:57:43.350 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:413:setLatchTime() | LatchTime updated to 0ms
2021-04-10T11:57:43.350 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | Previous line repeats 1 times
2021-04-10T11:57:43.350 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:444:setRewriteTime() | RewriteTime updated to 0ms
2021-04-10T11:57:43.351 hyperiond FLATBUFCONN  : <INFO> Connecting to Hyperion: 127.0.0.1:19401
2021-04-10T11:57:43.351 hyperiond LEDDEVICE    : <DEBUG> LedDeviceFile.cpp:59:open() | QIODevice::WriteOnly, /dev/null
2021-04-10T11:57:43.352 hyperiond EFFECTENGINE : <INFO> Run effect "Rainbow swirl fast" on channel 1
2021-04-10T11:57:43.354 hyperiond EFFECTENGINE : <DEBUG> EffectEngine.cpp:181:runEffectScript() | Start the effect: name [Rainbow swirl fast], smoothCfg [2]
2021-04-10T11:57:43.354 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:163:registerInput() | Register new input 'System/EFFECT' with priority 1 as inactive
2021-04-10T11:57:43.355 hyperiond HYPERION     : <INFO> Initial foreground effect 'Rainbow swirl fast' started
2021-04-10T11:57:43.356 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:163:registerInput() | Register new input 'System/GRABBER' with priority 250 as inactive
2021-04-10T11:57:43.356 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Framegrabber: enabled
2021-04-10T11:57:43.357 hyperiond Dispmanx     : <DEBUG> GrabberWrapper.cpp:48:start() | Grabber start()
2021-04-10T11:57:43.357 hyperiond BOBLIGHT     : <DEBUG> BoblightServer.cpp:28:BoblightServer() | Instance created
2021-04-10T11:57:43.357 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:91:handleSettingsUpdate() | Apply Webserver settings
2021-04-10T11:57:43.358 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:91:handleSettingsUpdate() | Apply Webserver settings
2021-04-10T11:57:43.358 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
2021-04-10T11:57:43.358 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | LED device: enabled
2021-04-10T11:57:43.358 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
2021-04-10T11:57:43.358 hyperiond WEBSERVER    : <INFO> Started on port 8090 name 'Hyperion Webserver'
2021-04-10T11:57:43.359 hyperiond HYPERION     : <INFO> Hyperion instance 'First LED Hardware instance' has been started
2021-04-10T11:57:43.365 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:175:handleSettingsUpdate() | Setup SSL certificate
2021-04-10T11:57:43.366 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:191:handleSettingsUpdate() | Setup private SSL key
2021-04-10T11:57:43.367 hyperiond WEBSERVER    : <INFO> Started on port 8092 name 'Hyperion Webserver'
2021-04-10T11:57:43.454 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:253:setInputImage() | Priority 250 is now active
2021-04-10T11:57:43.454 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:353:setCurrentTime() | Set visible priority to 250
2021-04-10T11:57:43.454 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[250], previousPriority[255]
2021-04-10T11:57:43.454 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:569:handlePriorityChangedLedDevice() | new source available -> switch LED-Device on
2021-04-10T11:57:43.576 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:253:setInputImage() | Priority 1 is now active
2021-04-10T11:57:43.576 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:353:setCurrentTime() | Set visible priority to 1
2021-04-10T11:57:43.577 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | cfg [2]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-04-10T11:57:43.577 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[1], previousPriority[250]
2021-04-10T11:57:46.423 hyperiond EFFECTENGINE : <INFO> effect finished
2021-04-10T11:57:46.515 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:317:setCurrentTime() | Timeout clear for priority 1
2021-04-10T11:57:46.516 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:353:setCurrentTime() | Set visible priority to 250
2021-04-10T11:57:46.517 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-04-10T11:57:46.518 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[250], previousPriority[1]

The line
<ERROR> Database version [2.0.0-alpha.8] is greater that current Hyperion version [2.0.0-alpha.9-PR#1164]
I do not understand, why is alpha.8 greater than alpha.9?
the last days I made
sudo apt-get install git cmake build-essential qtbase5-dev libqt5serialport5-dev libqt5sql5-sqlite libqt5svg5-dev libqt5x11extras5-dev libusb-1.0-0-dev python3-dev libcec-dev libxcb-image0-dev libxcb-util0-dev libxcb-shm0-dev libxcb-render0-dev libxcb-randr0-dev libxrandr-dev libxrender-dev libavahi-core-dev libavahi-compat-libdnssd-dev libjpeg-dev libturbojpeg0-dev libssl-dev zlib1g-dev
In accordance to [https://github.com/hyperion-project/hyperion.ng/blob/master/CompileHowto.md]

and if I call it in Firefox 192.168.178.43:8090
comes in the terminal window:
Error : incorrect HTTP headers line : "3A1%255Eo%25253Aid%25253Dn%2525253A5%25255Ewidth%25253Dn%2525253A69%255Eo%25253Aid%25253Dn%2525253A6%25255Ewidth%25253Dn%2525253A32%255Eo%25253Aid%25253Dn%2525253A7%25255Ewidth%25253Dn%2525253A32%255Eo%25253Aid%25253Dn%2525253A8%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A9%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A10%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A11%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A12%25255Ewidth%25253Dn%2525253A25%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A13%25255Ewidth%25253Dn%2525253A122%255Eo%25253Aid%25253Dn%2525253A14%25255Ewidth%25253Dn%2525253A69%255Eo%25253Aid%25253Dn%2525253A15%25255Ewidth%25253Dn%2525253A69%255Eo%25253Aid%25253Dn%2525253A16%25255Ewidth%25253Dn%2525253A46%5Esort%3Do%253Afield%253Ds%25253Astart_real%255Edirection%253Ds%25253AASC%5Efilters%3Do%253A; ys-api/access/entry=o%3Acolumns%3Da%253Ao%25253Aid%25253Dn%2525253A0%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A1%25255Ewidth%25253Dn%2525253A79%255Eo%25253Aid%25253Dn%2525253A2%25255Ewidth%25253Dn%2525253A152%255Eo%25253Aid%25253Dn%2525253A3%25255Ewidth%25253Dn%2525253A113%255Eo%25253Aid%25253Dn%2525253A4%25255Ewidth%25253Dn%2525253A48%255Eo%25253Aid%25253Dn%2525253A5%25255Ewidth%25253Dn%2525253A111%255Eo%25253Aid%25253Dn%2525253A6%25255Ewidth%25253Dn%2525253A113%255Eo%25253Aid%25253Dn%2525253A7%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A8%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A9%25255Ewidth%25253Dn%2525253A72%255Eo%25253Aid%25253Dn%2525253A10%25255Ewidth%25253Dn%2525253A48%255Eo%25253Aid%25253Dn%2525253A11%25255Ewidth%25253Dn%2525253A209%255Eo%25253Aid%25253Dn%2525253A12%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A13%25255Ewidth%25253Dn%2525253A113%255Eo%25253Aid%25253Dn%2525253A14%25255Ewidth%25253Dn%2525253A48%255Eo%25253Aid%25253Dn%2525253A15%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A16%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A17%25255Ewidth%25253Dn%2525253A45%255Eo%25253Aid%25253Dn%2525253A18%25255Ewidth%25253Dn%2525253A48%255Eo%25253Aid%25253Dn%2525253A19%25255Ewidth%25253Dn%2525253A45%5Efilters%3Do%253A; ys-api/dvr/entry/grid_upcoming=o%3Acolumns%3Da%253Ao%25253Aid%25253Ds%2525253Adetails%25255Ewidth%25253Dn%2525253A46%255Eo%25253Aid%25253Dn%2525253A1%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A2%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A3%25255Ewidth%25253Dn%2525253A91%255Eo%25253Aid%25253Dn%2525253A4%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A5%25255Ewidth%25253Dn%2525253A37%25255Ehidden%25253Db%2525253A1%255Eo%25253Aid%25253Dn%2525253A6%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A7%25255Ewidth%25253Dn%2525253A142%255Eo%25253Aid%25253Dn%2525253A8%25255Ewidth%25253Dn%2525253A73%255Eo%25253Aid%25253Dn%2525253A9%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A10%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A11%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A12%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A13%25255Ewidth%25253Dn%2525253A25%255Eo%25253Aid%25253Dn%2525253A14%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A15%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A16%25255Ewidth%25253Dn%2525253A37%255Eo%25253Aid%25253Dn%2525253A17%25255Ewidth%25253Dn%2525253A25%5Esort%3Do%253Afield%253Ds%25253Adisp_subtitle%255Edirection%253Ds%25253ADESC%5Efilters%3Do%253A\r\n"

[Lord-Grey]

a)

Database version [2.0.0-alpha.8] is greater that current Hyperion version [2.0.0-alpha.9-PR#1164]
I do not understand, why is alpha.8 greater than alpha.9?

My problem. Seems that new version compare did not consider the PR scenario.
You can ignore it, as you started with a fresh database. Thank for highlighting that I can fix it.

b)

the last days I made
sudo apt-get install...

Why? Unless you really want to compile yourself it is not required.
And if you compile yourself, there is not need to download the artifact.
The artifact downloaded should run without additional installs.

c)

I call it in Firefox 192.168.178.43:8090
comes in the terminal window:
Error : incorrect HTTP headers line :

Not sure why.... Let me try to reproduce it myself...

[micha53]

b)

the last days I made
sudo apt-get install...

Why?

Now we come into a loop...
In the 2nd comment tpmodding recommended to compile the actual state. This I tried and I got an Error like described in the 3rd comment.
Then you recommended to take your #1164.
I'll wait now till you have a result reproducing the issue.

If somebody tells me how to avoid the errors

pi@Medienserver:~/hyperion/build $ make -j $(nproc)
...
cc1: all warnings being treated as errors
make[2]: *** [dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/build.make:102: dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/x509.c.o] Fehler 1
make[1]: *** [CMakeFiles/Makefile2:1577: dependencies/external/mbedtls/build/library/CMakeFiles/mbedx509.dir/all] Fehler 2
...
make: *** [Makefile:152: all] Fehler 2

compiling the actual state I also can continue there.

[Lord-Grey]

If somebody tells me how to avoid the errors

There is currently a problem with the mbedtls library.
Just do another pull of the branch you would like to compile (master or pr1164) and try to compile again.

[micha53]

compilation of the actual state this afternoon was successful, Got the config-site in my browser and can set my spi port here.
But in the terminal I get

2021-04-11T18:18:49.638 hyperiond LEDDEVICE    : <ERROR> Device disabled, device 'ws2801' signals error: Failed to open device (/dev/spidev1.0). Error message: No such file or directory'

That's strange...
In /boot/config.txt I set
dtoverlay=spi1-1cs #1 chip select
to activate spi 1.

In the old hyperion this was all I had to do and I could activate the spi1 in the hyperion.config.json file (manually):
"output" : "/dev/spidev1.0",
and got it to work.

[Lord-Grey]

Now we come into a loop...

Sorry, seems I missed that comment before...
I just wanted to make it easier for you....

[Lord-Grey]

@micha53 Sorry, for the inconvenience! It looks like there were problems with the build of the PRs.
Would you mind downloading the latest arifact and test again, please?

https://github.com/hyperion-project/hyperion.ng/pull/1164/checks?check_run_id=2317158321

Note: The release version compare problem should have been gone, too...

[micha53]

strange reaction

pi@Medienserver:~/hyperion.ng-test $ sudo systemctl stop hyperion.service
Failed to stop hyperion.service: Unit hyperion.service not loaded.
pi@Medienserver:~/hyperion.ng-test $ ./bin/hyperiond -d -u test &
[1] 1321
pi@Medienserver:~/hyperion.ng-test $ 2021-04-11T19:40:15.670 hyperiond MAIN         : <ERROR> The Hyperion Daemon is already running, abort start

somehow my compilation seems to be running and can not be stopped by the systemctl command,
how do I get the daemon stopped?

[micha53]

got the daemon stopped..
With your project I do not get offered spi 1 to select...only spi0.1, independent from what spi-hardware I selected before (I use WS2801)

[Lord-Grey]

Do you see the device, if you add
'dtparam=spi=on' and 'dtoverlay=spi1-1cs' to /boot/config.txt?

[Lord-Grey]

What I am showing in the UI is the equivalent to „ls -la /dev/spi*“
which you could also do. If your device is not listed there, something is still wrong in your rpi setup.

[Lord-Grey]

With your project I do not get offered spi 1 to select...only spi0.1,

This has nothing to do with the hyperion project. It is related to your rpi configuration.
I just configured it on an rpi4 myself and the devices shows up as expected.

and here is the related /boot/config

[micha53]

I had copied the line dtoverlay=spi1-1cs #1 chip select from here . This probably was not a good idea, deleting this and writing it with my own fingers brought it. I can see the spi1 now.

That was the only change I made on my system, but when I try to call the config website on my rpi, I get an
Error : incorrect HTTP headers line : in the terminal window.
both with your version and with the actual compilation.

But setting the /boot/config.txt to spi0 only did not change the bahavior back.

[Lord-Grey]

@micha53 Unfortunately, I cannot reproduce it with Firefox myself...

Would you mind
a) deleting your cookies, plus
b) Share the hyperion.db with me? You find it in the "test/db" path
c) start hyperion with a fresh database

cd $HOME
cd hyperion.ng-test
./bin/hyperiond -d -u test --deleteDatabase

and share the debug output, if it happens again?

Thank you!

[micha53]

after deleting the cookies it starts with deleting the database it starts.
hyperion.db.zip

Thank you so far. This week I'll get the last plug to connect the led-strip to the raspi 4. I give you more feedback then.

[micha53]

Hallo,
today I connected the LED strip. It works, but blue and green are reversed. In te old hyperion there was a smart possibility to change them. This possibility I miss here, so I must change it here

and keep in mind that blue is green and green is blue.

Is this intended or is the color change field simply forgotten?

[Lord-Grey]

Hi
if you would like to set the byteorder per LED-Device you find it per LED Controller.
To see the RGB byte order element, you must switch to Settings level = Expert (use the wrench at the top right of the screen).

If you want to change the order generally, you can use the Byte Order wizard

[micha53]

Hi Lord Grey,
I now have all together working, but it could do it better. I am not fully satisfied with the whole system.
At first I habe one question more:
once you told me to install your test structure to

Stop hyperion standard service

systemctl stop hyperion.service

So I assume I can start my actual translation with

systemctl start hyperion.service

but I get an error:

pi@Medienserver:~ $ sudo systemctl start hyperion.service
Failed to start hyperion.service: Unit hyperion.service not found.

I translated the program following
https://github.com/hyperion-project/hyperion.ng/blob/master/CompileHowto.md

and installed it into my system doing
sudo make install/strip

This seems not to be enough to start the daemon at startup.

Do you have a hint for me how to install it as service that it starts with the rpi startup?

My second question relates to something other:
I would like to start a thread showing my experience with my setup: Kodi with TH Head/TVHeadend and Hyperion to find other interested people
The are 3 possibilities to place the theme, at a tvh, kodi or hyperion forum. I think most interesting would it be placed at the hyperion forum, but I do not find the right place within the forum.
Kodi hat a Hardware Showcase Discussion part, that's interesting.
If something like this would exist at hyperion, I would start it there.
tvh I would exclude...

Where would you start such a discussion?

[Lord-Grey]

@micha53 Let‘s finish the day with the easier answer.
I would suggest you start the thread in „Hyperion General
All things that don´t fit at another category could be dicussed here.“

https://hyperion-project.org/forum/index.php?board/30-hyperion-general/

Alternatively, if you would like to share your setup and get feedback , you can go here: „ Hyperion Setup Showcase“. This section might correspond to the showcase one from Kodi you mentioned above.

https://hyperion-project.org/forum/index.php?board/14-hyperion-setup-showcase/

I personally, would go the the general section, if you ask me.

[micha53]

Hi,
I just did it here. Maybe you are interested in having a look there.

Thanks again for the help to this point.

Michael

[Lord-Grey]

On the installation part...
The initial intend was just to give you the ability to test the PR without side-effects on your existing installation and confirm it is working and addressed your problem . Hoping this is only point, why you are not satisfied. ;)
Please note, PRs are still versions in development.

To install a PR you can follow the process described in the following thread:
https://hyperion-project.org/forum/index.php?thread/10768-test-hyperion-ng-pull-requests-on-raspbian-hyperbian-osmc-libreelec/

Then there is no need for you to compile yourself.

[micha53]

there's seems to be a misunderstanding...
I am not satisfied with the result of my experiment to join TVHeadend, kodi and hyperion at one rpi4b. The 3 part seem to influence each other.
But I will go on trying to improve this in a new thread, (my 2nd question yesterday).

In the link you sent me yesterday paulchen spoke about open PRs, yours (1112) is closed. Can I do paulchens procedure as well?
Trying it I got
---> Pull Request 1112 not found -> abort

[Lord-Grey]

Use the PR number I provided to you before which is 1164.
In PP‘s thread it is only a sample number...

[micha53]

Hi,
I'm coming back once again.
Because my trial to join Hyperion together with tvheadend and kodi at one rpi4 was not successfull, I just distributed it. Tvheadend now has an own rpi3.
But if I try to to call your test instance from my browser, I get errors like some weeks before:

I started Hyperiond using
pi@Medienserver:~/hyperion.ng-test $ ./bin/hyperiond -d -u test & (actual log below)
or ./bin/hyperiond -d -u test --deleteDatabase
log:

[1] 1514
pi@Medienserver:~/hyperion.ng-test $ 2021-05-10T14:55:15.917 hyperiond MAIN         : <INFO> Starting Hyperion - 2.0.0-alpha.9-PR#1164, (HEAD detached at pull/1164/merge) (GitHub-c688d245/be3d4752-1617891721), built: Apr  8 2021:15:08:21
2021-05-10T14:55:15.918 hyperiond MAIN         : <DEBUG> main.cpp:384:main() | QtVersion [5.7.1]
2021-05-10T14:55:15.918 hyperiond MAIN         : <INFO> Set user data path to '/home/pi/hyperion.ng-test/test'
2021-05-10T14:55:16.034 hyperiond DAEMON       : <DEBUG> PythonInit.cpp:40:PythonInit() | Initializing Python interpreter
2021-05-10T14:55:16.149 hyperiond SETTINGSMGR  : <ERROR> Database version [2.0.0-alpha.8] is greater that current Hyperion version [2.0.0-alpha.9-PR#1164]
2021-05-10T14:55:16.162 hyperiond SETTINGSMGR  : <DEBUG> SettingsManager.cpp:164:SettingsManager() | Settings database initialized
2021-05-10T14:55:16.162 hyperiond DAEMON       : <INFO> CEC handler created
2021-05-10T14:55:16.180 hyperiond EFFECTFILES  : <INFO> 39 effects loaded from directory :/effects/
2021-05-10T14:55:16.186 hyperiond EFFECTFILES  : <INFO> 22 effect schemas loaded from directory :/effects/schema/
2021-05-10T14:55:16.188 hyperiond EFFECTFILES  : <INFO> 0 effects loaded from directory /home/pi/hyperion.ng-test/test/custom-effects/
2021-05-10T14:55:16.212 hyperiond SETTINGSMGR  : <DEBUG> SettingsManager.cpp:164:SettingsManager() | Settings database initialized
2021-05-10T14:55:16.214 hyperiond BLACKBORDER  : <DEBUG> BlackBorderProcessor.cpp:64:handleSettingsUpdate() | Set mode to: default
2021-05-10T14:55:16.214 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Blackborder detector: enabled
2021-05-10T14:55:16.268 hyperiond DAEMON       : <INFO> set screen capture device to 'dispmanx'
2021-05-10T14:55:16.268 hyperiond DISPMANXGRAB : <DEBUG> Grabber.cpp:30:setVideoMode() | Set videomode to 0
2021-05-10T14:55:16.270 hyperiond DISPMANXGRAB : <INFO> Display opened with resolution: 4096x2160
2021-05-10T14:55:16.270 hyperiond DISPMANXGRAB : <DEBUG> Grabber.cpp:90:setWidthHeight() | Set new width: 80, height: 45 for capture
2021-05-10T14:55:16.270 hyperiond DAEMON       : <INFO> DISPMANX frame grabber created
2021-05-10T14:55:16.271 hyperiond V4L2:AUTO    : <DEBUG> Grabber.cpp:30:setVideoMode() | Set videomode to 0
2021-05-10T14:55:16.273 hyperiond LEDDEVICE    : <INFO> Start LedDevice 'file'.
2021-05-10T14:55:16.274 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Smoothing: enabled
2021-05-10T14:55:16.274 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | cfg [0]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-05-10T14:55:16.274 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:148:init() | deviceConfig: [{"colorOrder":"rgb","currentLedCount":1,"hardwareLedCount":1,"latchTime":0,"output":"/dev/null","rewriteTime":0,"type":"file"}]
2021-05-10T14:55:16.274 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:413:setLatchTime() | LatchTime updated to 0ms
2021-05-10T14:55:16.275 hyperiond LEDDEVICE    : <DEBUG> LedDevice.cpp:444:setRewriteTime() | RewriteTime updated to 0ms
2021-05-10T14:55:16.275 hyperiond V4L2:AUTO    : <INFO> Signal threshold set to: {12, 12, 12}
2021-05-10T14:55:16.275 hyperiond LEDDEVICE    : <DEBUG> LedDeviceFile.cpp:59:open() | QIODevice::WriteOnly, /dev/null
2021-05-10T14:55:16.275 hyperiond V4L2:AUTO    : <INFO> CEC detection is now disabled
2021-05-10T14:55:16.276 hyperiond V4L2:AUTO    : <INFO> Signal detection is now disabled
2021-05-10T14:55:16.276 hyperiond V4L2:AUTO    : <INFO> Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2021-05-10T14:55:16.276 hyperiond DAEMON       : <DEBUG> hyperiond.cpp:630:handleSettingsUpdate() | V4L2 grabber created
2021-05-10T14:55:16.284 hyperiond JSONSERVER   : <DEBUG> JsonServer.cpp:28:JsonServer() | Created instance
2021-05-10T14:55:16.284 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | Previous line repeats 1 times
2021-05-10T14:55:16.285 hyperiond FLATBUFCONN  : <INFO> Connecting to Hyperion: 127.0.0.1:19401
2021-05-10T14:55:16.294 hyperiond JSONSERVER   : <INFO> Started on port 19444
2021-05-10T14:55:16.295 hyperiond EFFECTENGINE : <INFO> Run effect "Rainbow swirl fast" on channel 1
2021-05-10T14:55:16.302 hyperiond FLATBUFSERVE : <INFO> Started on port 19400
2021-05-10T14:55:16.302 hyperiond PROTOSERVER  : <INFO> Started on port 19445
2021-05-10T14:55:16.303 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
2021-05-10T14:55:16.303 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:33:initServer() | Initialize Webserver
2021-05-10T14:55:16.360 hyperiond EFFECTENGINE : <DEBUG> EffectEngine.cpp:181:runEffectScript() | Start the effect: name [Rainbow swirl fast], smoothCfg [2]
2021-05-10T14:55:16.361 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:163:registerInput() | Register new input 'System/EFFECT' with priority 1 as inactive
2021-05-10T14:55:16.361 hyperiond HYPERION     : <INFO> Initial foreground effect 'Rainbow swirl fast' started
2021-05-10T14:55:16.362 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:163:registerInput() | Register new input 'System/GRABBER' with priority 250 as inactive
2021-05-10T14:55:16.362 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | Framegrabber: enabled
2021-05-10T14:55:16.362 hyperiond Dispmanx     : <DEBUG> GrabberWrapper.cpp:48:start() | Grabber start()
2021-05-10T14:55:16.362 hyperiond BOBLIGHT     : <DEBUG> BoblightServer.cpp:28:BoblightServer() | Instance created
2021-05-10T14:55:16.363 hyperiond COMPONENTREG : <DEBUG> ComponentRegister.cpp:36:setNewComponentState() | LED device: enabled
2021-05-10T14:55:16.363 hyperiond HYPERION     : <INFO> Hyperion instance 'First LED Hardware instance' has been started
2021-05-10T14:55:16.424 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:91:handleSettingsUpdate() | Apply Webserver settings
2021-05-10T14:55:16.424 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:91:handleSettingsUpdate() | Apply Webserver settings
2021-05-10T14:55:16.424 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
2021-05-10T14:55:16.424 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:109:handleSettingsUpdate() | Set document root to: :/webconfig
2021-05-10T14:55:16.425 hyperiond WEBSERVER    : <INFO> Started on port 8090 name 'Hyperion Webserver'
2021-05-10T14:55:16.437 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:175:handleSettingsUpdate() | Setup SSL certificate
2021-05-10T14:55:16.438 hyperiond WEBSERVER    : <DEBUG> WebServer.cpp:191:handleSettingsUpdate() | Setup private SSL key
2021-05-10T14:55:16.438 hyperiond WEBSERVER    : <INFO> Started on port 8092 name 'Hyperion Webserver'
2021-05-10T14:55:16.459 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:253:setInputImage() | Priority 250 is now active
2021-05-10T14:55:16.459 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:353:setCurrentTime() | Set visible priority to 250
2021-05-10T14:55:16.459 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[250], previousPriority[255]
2021-05-10T14:55:16.459 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:569:handlePriorityChangedLedDevice() | new source available -> switch LED-Device on
2021-05-10T14:55:16.475 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:253:setInputImage() | Priority 1 is now active
2021-05-10T14:55:16.475 hyperiond HYPERION     : <DEBUG> PriorityMuxer.cpp:353:setCurrentTime() | Set visible priority to 1
2021-05-10T14:55:16.475 hyperiond SMOOTHING    : <DEBUG> LinearColorSmoothing.cpp:701:selectConfig() | cfg [2]:  Type: linear - Time: 200 ms, outputRate 25.000000 Hz, interpolationRate: 25.000000 Hz, timer: 40 ms, Dithering: 0, Decay: 1.000000 -> HalfTime: 100.000000 ms
2021-05-10T14:55:16.475 hyperiond HYPERION     : <DEBUG> Hyperion.cpp:559:handlePriorityChangedLedDevice() | priority[1], previousPriority[250]
2021-05-10T14:55:19.412 hyperiond EFFECTENGINE : <INFO> effect finished

and calling it from my browser, I do not reach the site and in my putty terminal comes:
Error : incorrect HTTP headers line : "id%25253Dn%2525253A16%25255Ewidth%25253Dn%2525253A103%255Eo%25253Aid%25253Dn%2525253A17%25255Ewidth%25253Dn%2525253A25%5Esort%3Do%253Afield%253Ds%25253Astart_real%255Edirection%253Ds%25253AASC%5Efilters%3Do%253A\r\n"

Any idea?

I also could use now the actual release, because spi0 now is free again for hyperion, but I am confused doing the installation. I find paulchen-panthers thread
https://hyperion-project.org/forum/index.php?thread/10463-install-hyperion-ng-on-libreelec-x86-64-rpi-inoffiziell-unofficially/&pageNo=1 but this works only with libreelec; I use Raspberry OS.
and https://docs.hyperion-project.org/en/user/Installation.html#requirements recommends Hyperbian for Raspi.

Do you know where I find an installation guide for raspberry OS?

[tpmodding]

SEE ALSO doesnt mean ONLY...

https://docs.hyperion-project.org/en/user/Installation.html#install-hyperion-2

Raspberry Pi you can use HyperBian for a fresh start. Or use the install system
We provide installation packages (.deb) to install Hyperion with a single click on Debian/Ubuntu based systems.

edit: hyperbian IS rpi OS with hyperion preinstalled...

[micha53]

Hello,
thanks for your answer. But still I am not much more wise.
The page we speak about shows 4 lines, Windows and Mac OSX lines are not relevant
the first for rpi:
okay, HyberBian ist rpi OS with hyperion installed, this I didn't know before, but it is no smart solution for me, because my OS is configured and I would lose all my configuration settings.
Then I read there Or use the install system . As install system I understand the add/remove Software feature within the rpi's graphical interface. Maybe I'm wrong.. But searching here for a package named hyperion brings me no relvant result. I think it would be good to have a little bit more explanation here.

The 2nd line refers to Debian/Ubuntu.
As far as I know, rpi OS is based on Debian, so I ask myself if I can use the Instruction here with rpi? And if, so we have here the link to the Release Page where I shall download the installation package from. But there I did not find any file for download, until I got the idea to follow the link at the last release. A little bit more information at this page - a block for rpi as shown for Debian/Ubuntu - would be very helpful. I am sure, not only for me.