1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Probleme Grabber

Discussion in 'French Talk' started by Jeje33, 9 February 2020.

  1. Jeje33

    Jeje33 New Member

    Messages:
    1
    Hardware:
    RPi1/Zero, RPi3
    Bonjour,
    Récent installateur de Hypérion sur mon Rpi3 B, j'ai réussi (après des heures et des heures de galère) à faire fonctionner mes rubans led avec OSMC: lors de visionnage de vidéo tout fonctionne bien
    Maintenant je souhaiterai faire fonctionner Hyperion avec le grabber et la impossible , je ne comprend plus pourquoi.
    Mon grabber est raccordé sur Rpi3 et sur la péritel de ma TV. Je souhaite que tout ce qui apparait sur l'image soit envoyer sur Rpi


    Mon grabber "SVID2USB23"
    RPI3
    OSMC
    Ruban 46 leds WS 2801

    Quant je lance lsusb

    et dmesg | grep -i video
    [email protected]:~$ dmesg | grep -i video
    [ 0.640886] vc-sm: Videocore shared memory driver
    [ 6.578613] Linux video capture interface: v2.00
    [ 6.631936] em28xx 1-1.3:1.0: Video interface 0 found: isoc
    [ 13.122454] em28xx 1-1.3:1.0: V4L2 device video0 deregistered

    Mon fichier hyperion
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: "colorOrder" : "rgb",
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: "name" : "MyHyperionConfig",
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: "output" : "/dev/spidev0.0",
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: "rate" : 1000000,
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: "type" : "ws2801"
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: }
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Creating linear smoothing
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: EFFECTENGINE INFO: 27 effects loaded from directory /usr/share/hyperion/effects
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: EFFECTENGINE INFO: Initializing Python interpreter
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Hyperion started and initialised
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Boot sequence 'Rainbow swirl' EFFECTENGINE INFO: run effect Rainbow swirl on channel 0
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: BLACKBORDER INFO: threshold set to 0.01 (3)
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: BLACKBORDER INFO: mode:default
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: started
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Kodi checker created and started
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Json server created and started on port 19444
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Proto server created and started on port 19445
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: DISPMANXGRABBER INFO: Display opened with resolution: 1360x768
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: BLACKBORDER INFO: threshold set to 0.01 (3)
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: BLACKBORDER INFO: mode:default
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: INFO: Frame grabber created and started
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: terminate called after throwing an instance of 'std::runtime_error'
    ssh in: Feb 09 22:15:31 osmc hyperiond[3516]: what(): V4L2GRABBER ERROR: Cannot identify '/dev/video0' ERROR 2, No such file or directory
    ssh in: Feb 09 22:15:31 osmc systemd
    [1]: hyperion.service: Main process exited, code=killed, status=6/ABRT
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Failed with result 'signal'.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Service hold-off time over, scheduling restart.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: Stopped Hyperion Systemd service.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Start request repeated too quickly.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: Failed to start Hyperion Systemd service.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Unit entered failed state.
    ssh in: Feb 09 22:15:31 osmc systemd[1]: hyperion.service: Failed with result 'signal'.

    Faut il installer le driver? et comment?
    Merci par avance
     
  2. David Hequet

    David Hequet New Member

    Messages:
    21
    Hardware:
    RPi3
    Le message d'erreur indique effectivement que le rpi ne reconnait pas le grabber. Coté driver je ne peux pas t'aider, dans la plupart des projet, hyperion j'ai vu plutot un modele "compatible UTV007" comme lui https://www.amazon.fr/easycap-2-0-C...=ÅMÅŽÕÑ&keywords=utv007&qid=1581427504&sr=8-3

    Déjà un test que tu peux faire pour vérifier si le péritel fonctionne:

    Tu branche ton grabber a un pc et tu tentes d’acquérir ce qui sort de la péritel de ta TV