Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (92)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • Installation en mode standalone

    4 février 2011, par

    L’installation de la distribution MediaSPIP se fait en plusieurs étapes : la récupération des fichiers nécessaires. À ce moment là deux méthodes sont possibles : en installant l’archive ZIP contenant l’ensemble de la distribution ; via SVN en récupérant les sources de chaque modules séparément ; la préconfiguration ; l’installation définitive ;
    [mediaspip_zip]Installation de l’archive ZIP de MediaSPIP
    Ce mode d’installation est la méthode la plus simple afin d’installer l’ensemble de la distribution (...)

Sur d’autres sites (7189)

  • udpsrc doesn't work on 2 NIC & Port mirror linux setup (gstreamer/vlc/ffmpeg)

    28 janvier 2021, par kepitto

    I've tried a lot of stuff, but I can't seem to get it to work. (Same problem exists with ffmpeg/vlc)

    


    Basically, I can't get the UDP Stream directly into a videotool. I can verify the data coming in through tcpdump/wireshark etc. and i can also create the videofiles through gstreamer/ffmpeg afterwards, but I can't use the udp source as input.

    


    The current setup is the following :
The camera streams MJPEG through UDP to a fixed address & port. I port mirrored the data from the camera, so that I can verify the data coming in through wireshark on a 3rd device.

    


    The reason behind doing this is that multicast is not supported, so I need a way to get the data on 2 devices through unicast. Port mirroring seemed like a viable solution.

    


    Am I missing something here ? What do I need to do to get this working ?
I thought maybe it's due to the two networkinterface setup as I use 1x usb to ethernet for the port mirror and 1x ethernet for the web, but disconnecting the other shows no difference.
The routing seems correct too : "ip route get camera.ip" returns that the routing is through the usb to ethernet on my static ip.

    


    Example of an attempt :

    


    Gst-launch-1.0 udpsrc port=streamingport(confirmed through wireshark) ! jpegdec ! videorate ! video/x-raw,framerate=30/1 ! autovideosink (does not work)

    


    Gst-launch-1.0 filesrc location=hexdumpfile.txt ! jpegdec ! videorate ! video/x-raw,framerate=30/1 ! autovideosink (does work)

    


  • Node.js fluent-ffmpeg dependency setup

    12 mai 2016, par rpm

    I’m new to Node.js and I’m trying to work my way through using fluent-ffmpeg in my project. I have my node_modules directory setup with my dependencies that I installed with npm install. However, I’m confused with some of the wording in the fluent-ffmpeg install inst

    If the FFMPEG_PATH environment variable is set, fluent-ffmpeg will use it as the full path to the ffmpeg executable. Otherwise, it will attempt to call ffmpeg directly (so it should be in your PATH). You must also have ffprobe installed (it comes with ffmpeg in most distributions). Similarly, fluent-ffmpeg will use the FFPROBE_PATH environment variable if it is set, otherwise it will attempt to call it in the PATH.

    What does this mean ? If I’m understanding this correctly, fluent-ffmpeg will use the ffmpeg executable that is installed on my machine (if any), and that I need to set the path to that variable locally ? What if I want to use the ffmpeg executable that I have installed as a dependency in my node_modules folder of my project ?

  • avcodec/h264_slice : assert that the first slice implies unfinished setup

    27 juin 2015, par Michael Niedermayer
    avcodec/h264_slice : assert that the first slice implies unfinished setup

    If this assert fails there is very likely a bug in the code
    

    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavcodec/h264_slice.c

Navigation