i tried to implement it in the Json code ( probably i am doing something not 100% okay) but still the same thing. The rest works so it seems that this part of Json code isn't corrupting the Json file
Beiträge von Ambientheater77
-
-
i am going to put that part Json file and implement it in my config.
i let you know
-
smoothing mode for myself i use all the time, but it's matter of personal preference !
it gives the lights some easy switching and when watching tv/movie it isn't destracting.
but that is just offtopic.and its a really cool project that you guys do, so kuddos
-
this is first instance running now at this moment>
-
Yeah, I also found&corrected it too but dont have time to make pull request. The bug is caused because new scheme for smoothing doesn't care about old config and after start some things starts to break down (for example you cant save settings for smoothing in the web panel).
"required" property is missing for the new fields. Work around is to delete old config.
BTW what is the difference between "updateFrequency" and new "outputRate" for old linear smoothing?ah okay!
to be honest and clear to you and dev's in general, i never altered the "new" Json file that was implemented in new Hyperion> because of easyness and it's a working configuration i used my old backup from Json from the old build and after that tested with Json file of a friend.
that's the APA102 debug file up here i posted.
i have 2 PI's running here with the first Hyperion.NG 1.0.0 Beta
and Hyperion.NG 2.08 Alpha is running on second PIso i can see easy what's different
i don't know what is the diffrence old en new build in Smoothing is different, i noticed that with some changes in the WebUI
-
i dont get it...could you explain it a little bit more, and can you please provide logs
okay
with the setting smoothing activated ( which i can't deactivate) the SPI device is not outputting data signals,
start up effect is not showing.
when i turn off smoothing in remote control then the lights WS2801 start to work as normal .the json file is not corrupted or anything because i used (to test) a working one from my friend which has almost the same build
-
i dont get it...could you explain it a little bit more, and can you please provide logs
2020-11-06T19:31:16.048Z [hyperiond DAEMON] (INFO) CEC handler created
2020-11-06T19:31:16.086Z [hyperiond EFFECTFILES] (INFO) 39 effects loaded from directory :/effects/
2020-11-06T19:31:16.094Z [hyperiond EFFECTFILES] (INFO) 22 effect schemas loaded from directory :/effects/schema/
2020-11-06T19:31:16.099Z [hyperiond EFFECTFILES] (INFO) 0 effects loaded from directory /home/pi/.hyperion/custom-effects
2020-11-06T19:31:16.232Z [hyperiond DAEMON] (INFO) set screen capture device to 'dispmanx'
2020-11-06T19:31:16.234Z [hyperiond DISPMANXGRABBER] (INFO) Display opened with resolution: 1920x1080
2020-11-06T19:31:16.235Z [hyperiond DAEMON] (INFO) DISPMANX frame grabber created
2020-11-06T19:31:16.240Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal threshold set to: {25, 25, 25}
2020-11-06T19:31:16.241Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Cropping image: width=1920 height=1080; crop: left=15 right=20 top=4 bottom=4
2020-11-06T19:31:16.241Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) CEC detection is now disabled
2020-11-06T19:31:16.241Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal detection area set to: 0.250000,0.250000 x 0.750000,0.750000
2020-11-06T19:31:16.282Z [hyperiond JSONSERVER] (INFO) Started on port 19444
2020-11-06T19:31:16.246Z [hyperiond LEDDEVICE] (INFO) Start LedDevice 'apa102'.
2020-11-06T19:31:16.246Z [hyperiond SMOOTHING] (INFO) linear - Time: 1890587346 ms, outputRate 0.000000 Hz, interpolationRate: 25.000000 Hz, timer: 0 ms, Dithering: 1077477376, Decay: 0.000000 -> HalfTime: 6494444003133371994829286228792709889068837366450017529425326035805359511647165826838967971702911429875185859444856397241714356149979679888229216311759467623723621513131186657700892134364962403242805769811180533151734928387784011109367808.000000 ms
2020-11-06T19:31:16.246Z [hyperiond SMOOTHING] (INFO) linear - Time: 1901062580 ms, outputRate 0.000000 Hz, interpolationRate: 25.000000 Hz, timer: 0 ms, Dithering: 1077477376, Decay: 0.000000 -> HalfTime: 0.000000 ms
2020-11-06T19:31:16.246Z [hyperiond SMOOTHING] (INFO) LinearColorSmoothing sizeof floatT == 4
2020-11-06T19:31:16.251Z [hyperiond FLATBUFCONN] (INFO) Connecting to Hyperion: 127.0.0.1:19401
2020-11-06T19:31:16.285Z [hyperiond EFFECTENGINE] (INFO) Run effect "Rainbow swirl" on channel 0
2020-11-06T19:31:16.295Z [hyperiond FLATBUFSERVER] (INFO) Started on port 19400
2020-11-06T19:31:16.296Z [hyperiond PROTOSERVER] (INFO) Started on port 19445
2020-11-06T19:31:16.463Z [hyperiond HYPERION] (INFO) Initial foreground effect 'Rainbow swirl' started
2020-11-06T19:31:16.466Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) configured v4l device: /dev/video0
2020-11-06T19:31:16.529Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Started
2020-11-06T19:31:16.530Z [hyperiond HYPERION] (INFO) Hyperion instance 'First LED Hardware instance' has been started
2020-11-06T19:31:16.622Z [hyperiond SMOOTHING] (INFO) linear - Time: 1890703848 ms, outputRate 0.000000 Hz, interpolationRate: 25.000000 Hz, timer: 0 ms, Dithering: 1077477376, Decay: 0.000000 -> HalfTime: 3600753840686499744933878091410536715371439590762786953130230766234657311691981543746852769065173971510130366290417205439375444646355918547166057437618227642196252652146862838189431270791933916377175206232973045877151994919721810489655412391936.000000 ms
2020-11-06T19:31:16.695Z [hyperiond WEBSERVER] (INFO) Started on port 8090 name 'Hyperion Webserver'
2020-11-06T19:31:16.826Z [hyperiond WEBSERVER] (INFO) Started on port 8092 name 'Hyperion Webserver'
2020-11-06T19:31:18.692Z [hyperiond V4L2:/DEV/VIDEO0] (INFO) Signal lost
2020-11-06T19:31:23.628Z [hyperiond SMOOTHING] (INFO) linear - Time: -1091431936 ms, outputRate 0.000000 Hz, interpolationRate: 25.000000 Hz, timer: 0 ms, Dithering: 1077477376, Decay: 0.000000 -> HalfTime: 0.000000 ms
2020-11-06T19:53:09.289Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000
2020-11-06T19:53:10.132Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.25
2020-11-06T19:53:10.133Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.25' switch to Hyperion instance 0
2020-11-06T19:53:10.672Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1047:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.25 -
yes, but i don't know the settings > there's a bunch of forummembers who do know.
Just search the forum.the rainbow is when the grabber doesn't receive image video/input.
-
thats the screenshot, you can see here i can not save the setting or can switch it off and then save..
-
Hyperion Server:
- Build: master (GitHub-54707eff/36c05142-1604520240)
- Build time: Nov 5 2020 22:19:30Hello folks,
i made a new installation (on RPI with good hardware) with compiling new Hyperion alpha 2.08 newest build.
the smoothing section is there but i can't save or switch on/off this feature in Image Processing.only when i use Remote control then i can only switch it off,
when i switch Smoothing on in Remote control there's ZERO signal to the SPI device controller /dev/0.0/, so it'll look like ledstrip isn't working!i've tested with different Json files from last build September, but with that build @ friends house runs fine.
when i use his Json file ( or use my own) then i get this bug.
I can go back a build and deinstall and compiling different build, i just wanted to let the dev's know. -
Die topic hield ik ook in de gaten hahah
kunnen we niet met mijn componenten iets proberen?
met een 2e splitter kan je het proberen, jouw grabber en HDMI/rca converter is waarschijnlijk oke
-
Zie de foto’s
ledstrip is verbonden met jst connector. Gnd data clock naar de rpi4.
en die andere foto is de converter en splitter. Usb grabber is in de pi usb slot en de gele kabel naar de converter. Heb alleen geen source op aangesloten meer omdat ik geen ps4 pro meer heb. Die kabel zit los op de foto zoals te zien
iemand heeft ( waarschijnlijk ) de oplossing hiervoor gevonden, >> https://hyperion-project.org/threads/hdr-solution.10852/
ik ga dit morgen ook met een vriend van mij proberen, waarvan ik laatst die installatie van had gedaan.
-
Selecting PWM just fixed everything for me. Everything is working. It shouldn't, but it does XD
Only one thing I can't yet figure out: Boot animation will not work, so I disabled it and everything starts up fine. But when I power off the TV, the standby signal from the capture card has a lot of colors, is there a way to set it up so that it sets color to black or "off" when it sees a specific image for "xx" amount of seconds?
you can do that with setting Signal Detection and Treshold RGB -
i have a suggestion> by any chance, did the PWM lite it up like full white? If you deselect PWM they go off again?
i did the test myself on Hyperion.NG 2.08 , look at remote control and switch of smoothing, with me that was fixing the led's not lit up.
It looks like there's a bug in image softening ( smoothing) while it RUN's the led's don't do anything on SPI and WS2801.
you can't turn it off in my build, button SAVE is unlit... only possible with remote control option.maybe this helps you, maybe not..
anyway, i go back to my first build ( sd card) with Hyperion.NG Béta 1 which runs perfectly from the getgo.
-
I’m going to be honest, I understood about 17% of what you just said haha
I’ll play around with the signal detection levels to see if I can get it right!
aha, okay!
somewhere here on Hyperion forum there's the settings, i believe it was 0,9 en 0,98 vertical and horizontal on signal detection
-
i don't know how really, some do it with the setting Signal Detection,
default its 0.75 and 0.25 but you can set it diffrent so when tv signal is not coming into the grabber the lights shut off.
but i have to say, i didn't experiment with that only a little.
so i can't say much about thati build a box myself with relay, so when i want to watch> RPI switch on and with automatic script Hyperion starts up the lights.
very easy. -
okay thats fine then, good luck with the rest to sort it out.
-
No it's not I think
Did u mean to set priority for usb capture below 200?
I'm using mainly Proto that's why it has lower priority.
However i can switch between this to inputs in Remote Control page and turn off priority rules. That's why i think that's not the case.no i mean set protobuffer higher (image streams) > in range of 150 instead of 100. Did you see the screenshot that i borrowed from dev Paulchen Panther?
in Hyperion he said " priority is very important for running processes and devices" -
borrowed from Dev. Panther Paulchen >> https://prnt.sc/uwffdw
isn't the priority the case/ too low ??
-