The LEDs light up according to the color of the screen. But I don't know why in source the grabber turns off and on and this causes the LEDs to turn off.
Im crazy with this. Please help
The LEDs light up according to the color of the screen. But I don't know why in source the grabber turns off and on and this causes the LEDs to turn off.
Im crazy with this. Please help
2021-01-25T15:23:29.585Z [hyperiond DB] (ERROR) Previous line repeats 2 times 2021-01-25T15:23:29.586Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 240 is now active 2021-01-25T15:23:29.586Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 240 2021-01-25T15:23:29.586Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[240], previousPriority[255] 2021-01-25T15:23:29.586Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on 2021-01-25T15:23:30.672Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 240 is now inactive 2021-01-25T15:23:30.674Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255 2021-01-25T15:23:30.674Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[240] 2021-01-25T15:23:30.674Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off 2021-01-25T15:23:30.689Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 240 is now active 2021-01-25T15:23:30.689Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 240 2021-01-25T15:23:30.690Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[240], previousPriority[255] 2021-01-25T15:23:30.690Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:569:handlePriorityChangedLedDevice()) new source available -> switch LED-Device on 2021-01-25T15:23:32.515Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:251:setInputImage()) Priority 240 is now inactive 2021-01-25T15:23:32.515Z [hyperiond HYPERION] (DEBUG) (PriorityMuxer.cpp:351:setCurrentTime()) Set visible priority to 255 2021-01-25T15:23:32.515Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:559:handlePriorityChangedLedDevice()) priority[255], previousPriority[240] 2021-01-25T15:23:32.516Z [hyperiond HYPERION] (DEBUG) (Hyperion.cpp:562:handlePriorityChangedLedDevice()) No source left -> switch LED-Device off 2021-01-25T15:23:34.537Z [hyperiond COMPONENTREG] (DEBUG) (ComponentRegister.cpp:36:setNewComponentState()) Blackborder detector: enabled 2021-01-25T15:23:36.891Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.172
The LEDs light up according to the color of the screen. But I don't know why in source the grabber turns off and on and this causes the LEDs to turn off.
Im crazy with this. Please help
i would increase your USB port power,
go to config.txt ( you can do that direct via terminal or indirect on SD card) and put in a line, then save
max_usb_current=1
important (NO #) before the line!
Alles anzeigeni would increase your USB port power,
go to config.txt ( you can do that direct via terminal or indirect on SD card) and put in a line, then save
max_usb_current=1
important (NO #) before the line!
I have and continues to do the same jeroen.
I have connected the power cable to the grabber to the raspberry. Is this correct? or I have to connect it to a mobile charger for example
I have and continues to do the same jeroen.
I have connected the power cable to the grabber to the raspberry. Is this correct? or I have to connect it to a mobile charger for example
grabber gets his power out of raspi USB port, raspi gets his power from PSU
put in extra lines, put all the lines there
arm_freq=900 change the line you already have and option out # then put the lines there below, also USB line >> arm is now 700 which is slow
force_turbo=1
then, set input device not automatic but to /dev/video0
set frames a second to 15 frames
resolution 1280x720
then save and let me know what happens because Hyperion detects your USB grabber so thats okay
[QUOTE = "jeroen warmerdam, publicación: 32982, miembro: 8541"] grabber obtiene su energía del puerto USB raspi, raspi obtiene su energía de la fuente de alimentación
poner líneas adicionales, poner todas las líneas allí
arm_freq = 900 cambie la línea que ya tiene y la opción out # luego coloque las líneas allí debajo, también la línea USB >> arm ahora es 700, que es lento
force_turbo = 1
luego, configure el dispositivo de entrada no automático sino a / dev / video0
establecer fotogramas por segundo a 15 fotogramas
resolución 1280x720
luego guarde y avíseme qué sucede porque Hyperion detecta su capturador USB, así que está bien [/ QUOTE]
I have made all the changes but in the input it does not let me put / dev / video0 only a number look the picture.
I have made all the changes but in the input it does not let me put / dev / video0 only a number look the picture.
can u input 0 there? what is the possibility to fill in with arrows?
can u input 0 there? what is the possibility to fill in with arrows?
AUTO, camera1,custom but custom are a number...
i can put 0 there
AUTO, camera1,custom but custom are a number...
i can put 0 there
okay put 0 there
and PAL setting for video standard
save and then reboot the PI
you can play" with resolution settings if image apear to be slow then make your resolution smaller but make sure its in 16/9 layout
Alles anzeigenokay put 0 there
and PAL setting for video standard
save and then reboot the PI
you can play" with resolution settings if image apear to be slow then make your resolution smaller but make sure its in 16/9 layout
i do it the changes in the picture, but nothing do the same jeroen...
i do it the changes in the picture, but nothing do the same jeroen...
nothing helps? still fallout of USB grabber?
[QUOTE = "jeroen warmerdam, publicación: 32998, miembro: 8541"] ¿nada ayuda? ¿Sigue siendo consecuencia del capturador USB? [/ QUOTE]
No sé, no sé dónde atacar el problema, la verdad. Porque a primera vista parece que es poder pero me dices que no y sabrás mucho más que yo, así que no sé dónde está el problema.
el capturador funciona porque muestra la imagen. mira el dibujo.
[QUOTE = "jeroen warmerdam, publicación: 32998, miembro: 8541"] ¿nada ayuda? ¿Sigue siendo consecuencia del capturador USB? [/ QUOTE]
Jeroen i buy a new grabber to see if it works better and the problem is resolved. Do you think this will be better for a 65 '' 4K TV?
you have to make the call on that, but it looks okay.
reminder; the device can be slower in performing because off the limitations of the RPI3 >> this has only support for USB 2.0 ports/speed while your Amazon 4K splitter is asking for 3.0 USB ports/speed.
while it can work the device can not run in optimal form ( as in 3.0 USB port) so you can expect trouble when playing 4K.
i don't know this for shure but because this is a loop" device the main HDMI signal is going out to the 65" 4K TV
the only thing i am wondering if the device is capable to loop the 4K signal without quality loss ( i think not) on 60Hz when its connected to a RPI3 USB port which grabs the image on a slower port....
just test and you will see.
Alles anzeigenyou have to make the call on that, but it looks okay.
reminder; the device can be slower in performing because off the limitations of the RPI3 >> this has only support for USB 2.0 ports/speed while your Amazon 4K splitter is asking for 3.0 USB ports/speed.
while it can work the device can not run in optimal form ( as in 3.0 USB port) so you can expect trouble when playing 4K.
i don't know this for shure but because this is a loop" device the main HDMI signal is going out to the 65" 4K TV
the only thing i am wondering if the device is capable to loop the 4K signal without quality loss ( i think not) on 60Hz when its connected to a RPI3 USB port which grabs the image on a slower port....
just test and you will see.
i have a RP4 then i have 3.0 USB
tomorrow i say you the score.
i have a RP4 then i have 3.0 USB
tomorrow i say you the score.
because your hardware message in profile says RPI3 :D:pirate:
[QUOTE= "jeroen warmerdam, publicación: 33090, miembro: 8541"] porque su mensaje de hardware en el perfil dice RPI3 :RE:pirata:[/QUOTE]
Yes becouse i dont see RP4 :roflmao::roflmao::roflmao:
g
Alles anzeigenyou have to make the call on that, but it looks okay.
reminder; the device can be slower in performing because off the limitations of the RPI3 >> this has only support for USB 2.0 ports/speed while your Amazon 4K splitter is asking for 3.0 USB ports/speed.
while it can work the device can not run in optimal form ( as in 3.0 USB port) so you can expect trouble when playing 4K.
i don't know this for shure but because this is a loop" device the main HDMI signal is going out to the 65" 4K TV
the only thing i am wondering if the device is capable to loop the 4K signal without quality loss ( i think not) on 60Hz when its connected to a RPI3 USB port which grabs the image on a slower port....
just test and you will see.
Hi jeroen I have received the new graber and it is perfect without stopping and the LEDs look spectacular, thank you very much for your help from the beginning. I wish there were more people like you in the world.
thanks,
i hope you enjoy the ambilight much like me !
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!