Recherche avancée

Médias (91)

Autres articles (54)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Problèmes fréquents

    10 mars 2010, par

    PHP et safe_mode activé
    Une des principales sources de problèmes relève de la configuration de PHP et notamment de l’activation du safe_mode
    La solution consiterait à soit désactiver le safe_mode soit placer le script dans un répertoire accessible par apache pour le site

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

Sur d’autres sites (4586)

  • creating a jack client from inside a docker container

    19 novembre 2018, par unameuname

    I use jack to route audio between multiple sound cards in my pc.
    To record the audio i use a very convenient FFmpeg command which creates a writable jack client :
    ffmpeg -f jack -i  -strict -2 -y .
    so far this works very well.

    The problem starts here :

    I also have an nginx docker which records my data and makes it available for streaming. when trying to use the same command inside the docker i get the following error :"Unable to register as a JACK client".

    I started to look in to the FFmpeg code and found out that the FFmpeg command calls the jack_client_open command from the jack API, which fails.

    Seems like there is some kind of a problem in the connection between the FFmpeg request from inside the docker to the jackd server running on the host.

    Is there a simple way to create a connection between the two [exposing ports] ?

    (I saw some solutions like netjack2, but before creating a more complex server-client architecture i’d like to find a more elegant solution).

    Thanks for the help !

  • What is the minimum amount of metadata is needed to stream only video using libx264 to encode at the server and libffmpeg to decode at the client ?

    19 mars 2012, par cloudraven

    I want to stream video (no audio) from a server to a client. I will encode the video using libx264 and decode it with ffmpeg. I plan to use fixed settings (at the very least they will be known in advance by both the client and the server). I was wondering if I can avoid wrapping the compressed video in a container format (like mp4 or mkv).

    Right now I am able to encode my frames using x264_encoder_encode. I get a compressed frame back, and I can do that for every frame. What extra information (if anything at all) do I need to send to the client so that ffmpeg can decode the compressed frames, and more importantly how can I obtain it with libx264. I assume I may need to generate NAL information (x264_nal_encode ?). Having an idea of what is the minimum necessary to get the video across, and how to put the pieces together would be really helpful.

  • What is the minimum amount of metadata is needed to stream only video using libx264 to encode at the server and libffmpeg to decode at the client ?

    19 mars 2012, par cloudraven

    I want to stream video (no audio) from a server to a client. I will encode the video using libx264 and decode it with ffmpeg. I plan to use fixed settings (at the very least they will be known in advance by both the client and the server). I was wondering if I can avoid wrapping the compressed video in a container format (like mp4 or mkv).

    Right now I am able to encode my frames using x264_encoder_encode. I get a compressed frame back, and I can do that for every frame. What extra information (if anything at all) do I need to send to the client so that ffmpeg can decode the compressed frames, and more importantly how can I obtain it with libx264. I assume I may need to generate NAL information (x264_nal_encode ?). Having an idea of what is the minimum necessary to get the video across, and how to put the pieces together would be really helpful.

Navigation