The Image you are showing looks quite similar to what is shown in other posts in relation to Tizen.
I was wondering why the Led are reacting if there is a black screen... So thats why. Good to know
The Image you are showing looks quite similar to what is shown in other posts in relation to Tizen.
I was wondering why the Led are reacting if there is a black screen... So thats why. Good to know
Like said, i only guess that this is your problem. What else capture devices do you get listed? Is framebuffer is the only one?
And second question will the USB grabber works with build in smart tv on tizen?
Unfortunately no. But there is a Tizen grabber called HyperTizen but you need at least Tizen 6.5
I guess you are facing the same "problem" like me using LibreElec:
the internal V4L grabber does not work anymore in current versions of Kodi.
What else capture devices do you get listed? If framebuffer is the onbly one then
you have to use an external USB grabber or install Rudihorn's DRM-VC4-grabber.
No problem. As you wish.
Found an issue (only a small one again)
The blue Wiki link to the blackbar detection modes is wrong.
Current link:
"https://docs.hyperion-project.org/en/user/advanced/Advanced.html#blackbar-detection"
but it should be:
"https://docs.hyperion-project.org/user/advanced/Advanced.html#blackbar-detection"
regards
Marxon
pclin I thought green means OK and red defective ![]()
But you are totally right. I overlooked the fact that all LEDs after the green one aren't working, so it's most likely defective.
Hi Lord-Grey,
sorry for my long absence, my Multi-Boot USB flash drive smoked out and i had to set up everything from zero.
It was the second one. It seems those micro flash drives are not suitable for long-term daily use.
Now i switched to a SSD...
Did you changed somthing in your install_pr script? Because it quits with an "wrong token" error now.
Best regards
Marxon
EDIT
My token simply expired... Created a new one, porblem gone.
Hi,
afaik they use the same protocol like WS2812.
So I was completely wrong about Doxygen
But in meanwhile I learned that Doxygen is for code documentation ![]()
Nevertheless editor and development server is set up and for now I just need to understand the documentations folder structure but then i can get started.
Are you talking about https://docs.hyperion-project.org/effects/API.html?
In case yes, this one should not be added to the integration API.Looks like the term API is misleading here.
Just thought for having all "coding-stuff" in one place.
…but maybe you would like to support creating some documentation which is currently missing?
How doing this?
Before i dive deeper, did i understood the general process correctly?
- clone the repo
- make edits
- generate documentation with doxygen
Mittlerweile bzw. heute hat man es geschafft auf einem Pi5 mittels kmsgrab den Framebuffer zu dumpen.
https://github.com/raspberrypi…7#issuecomment-2907692012
Glad to hear
Hi Georodin,
of course you can do that! ![]()
You just have to adjust input position (starting point), gap position and gap length.
Here i made an example for you:
If you have less leds on bottom than top (because of the gap) you have to
decrease the bottom leds count (bottom leds = top leds - gap length)
Best regards
Hi Marxon
The original post was about API.
I reworked the documentation in a more modern way.
You might want to have an early look at api.hyperion-project.org
This now includes the config related commands, too.
Lord-Grey your new Hyperion API documentation is very good!
![]()
Easy understandable and user friendly.
The code generator is awsome and helps to avoid syntax or typing errors.
Are you adding the effects api later, too? That's the only thing whats missing.
If it's desired/needed i would like to contribute a german translation somehow.
Besides: you just got your 300th forum reaction ![]()
OK i will check it.
EDIT
Effect schemas are not getting exported