Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (109)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • 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 (...)

Sur d’autres sites (10856)

  • Anomalie #2362 (En cours) : SPIP Security Vulnerability Notification

    5 octobre 2011, par High-Tech Bridge

    Hello, High-Tech Bridge Security Research Lab has discovered a security issue in SPIP. Developers can contact us by email advisory (at) htbridge.ch for details. Preview : https://www.htbridge.ch/advisory/path_disclosure_in_spip.html For any questions related to this notification email - (...)

  • Probing an RTMP address for streaming to check if it's in use

    20 juillet 2020, par hedgehog90

    I need a quick, lightweight method to probe rtmp addressses in Windows and Ubuntu to see if they are 'free' for upload.

    


    One possible way of checking is to simply send a dummy video stream to an rtmp address with a simple ffmpeg command :

    


    ffmpeg -re -f lavfi -i color=c=black:s=2x2:r=1 -f lavfi -i anullsrc=cl=mono:r=44100 -c:v h264 -c:a aac -t 10 -f flv -y rtmp://streaming.service.com/live/1234567890

    


    If the rtmp address is in use, depending on the streaming service's rtmp server, I'll get an error response from ffmpeg like

    


    [rtmp @ 000002a908997cc0] Server error: Stream name is already in use: 1234567890
rtmp://streaming.service.com/live/1234567890: Operation not permitted


    


    However, if the rtmp address is free then it will publish my dummy video stream, which I don't want to do.

    


    Preferably I'd just like to probe the rtmp server without encoding a dummy video stream.

    


    I've tried using ffprobe and rtmpdump but for streaming services they usually won't allow playback from the rtmp address they assign you, the request will be rejected.

    


    I'm programming in javascript for a NodeJS application, so if there's a node package available then that would be very useful to know.

    


  • What are all the codecs and formats not supported by FFmpeg ?

    4 mars 2020, par Alexander Swann

    We are building a service where we do not know what format/codec a video uploaded by a user is in. Due to the nature of the application, we expect input video formats to be very fragmented, diverse and niche. We are currently using FFmpeg to transcode input formats to a consistent output (e.g. mp4).

    Due to the above scenario, I would like to establish a general list of what formats and codecs are not currently supported by FFmpeg. This is so I can research other open source video transcoding tools which I can utilise to fill in the gaps and allow our service to be more reliable for the user.

    Are there resources online that can help at least get a general idea of what might not be supported by FFmpeg ?

Navigation