Replies: 2 comments
-
|
Hi But I'm not sure if adding an Amlogic specific FB path would solve your problem or if something else needs to be implemented also. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
A quick look into the Hyperion Sources shows that there is a bit more necessary. It's not that much, but sadly more than just adding /dev/amvideo* to the File pattern. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
I currently try to migrate from Hyperion-ng to HyperHDR (20.0.0.0
bullseyebeta1 via official deb repo) but with no luck so far. I'm not using any USB-Grabber - just software grabber. This worked so far very good with Hyperion & Vero 4K+.In HyperHDR the WebUI only detects /dev/fb0 & /dev/fb1. fb0 containst the Kodi Menü. But as soon as i start a Video then fb0 went black -> no Picture (Video plays on TV) -> no LEDs :(
Unfortunately Hyperion doesn't show which device it is capturing. They just call the Device "amlogic" with input "Display0". From what I could see in the open filedescriptors, hyperion is using /dev/fb0, /dev/amvideo and after starting a video /dev/amvideocap0. The last two are not displayed in HyperHDR.
Does anyone have a Idea what's going on here? Thanks :)
Greetings
Matthias
Beta Was this translation helpful? Give feedback.
All reactions