Recherche avancée

Médias (1)

Mot : - Tags -/pirate bay

Autres articles (89)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • Tips for encoding a live stream to IIS Media Services (or Azure Live Media Services) with FFMPEG ?

    6 mars 2014, par user3104748

    We're trying to encode assets, either live or static, in a live stream to IIS Media Services using ffmpeg. Can anyone provide pointers for exactly what kinds of parameters we should be using and setting ?

    As part of our test, just to see if we can get things to work, we have a standard plain-old MP4 video static asset that we're trying to stream to the server. It seems to work on the client side, but when we try to view the video on the receiving end, we get nothing.

    Here's an example of the command we're using, where gg.mp4 is the static MP4 video (obviously (hostname) is the name of our host and not the actual word in parenthesis :)...

    ffmpeg -y -re -i gg.mp4 -movflags isml+frag_keyframe -f ismv -threads 0 -c:a libvo_aacenc -ac 2 -b:a 64k -c:v libx264 -preset fast -profile:v baseline -g 48 -keyint_min 48 -map 0:v -b:v:0 477k -s:v:0 368x152 -map 0:v -b:v:1 331k -s:v:1 288x120 -map 0:v -b:v:2 230k -s:v:2 224x92 -map 0:a:0 http://(hostname)/ingest.isml/Streams(video)
  • Node.js Webm live stream server : issues with tag

    10 décembre 2013, par breathe0

    I'm using Node.js as stream server to stream realtime Webm videos that is sent by FFMPEG (executed from another application, the stream is done via HTTP) and received by a webapp that uses the tag.

    This is what I'm doing : FFMPEG streams the received frames using the following command :

    ffmpeg -r 30 -f rawvideo  -pix_fmt bgra -s 640x480
    -i \\.\pipe\STREAM_PIPE -r 60
    -f segment  -s 240x160 -codec:v libvpx  -f webm
    http://my.domain.com/video_stream.webm

    (the stream comes from an application that uses the Kinect as source and communicates with FFMPEG through a pipe, sending one frame after another)

    When the webapp connects, it receives immediately this response from the server :

    HTTP/1.1 200 OK
    X-Powered-By: Express
    content-type: video/webm
    cache-control: private
    connection: close
    Date: Fri, 06 Dec 2013 14:36:31 GMT

    and a Webm header (previously stored on the server, with the same resolution and frame rate of the source stream and tested as working on VLC) is immediately appended. Then the webapp starts to receive the data streamed by FFMPEG. Here is a screenshot of Mkvinfo GUI showing the fields of the header :

    Header screenshot

    However, even if the Network tab of the Chrome console shows that there is an actual stream of data (meaning that what is streamed is not completely garbage, otherwise the connection would be dropped), the player doesn't display anything. We tried to manually prepend our header to the dumped video received by the webapp and VLC plays it just fine, but this is not happening with the tag.

    What can cause this problem ? Are we missing something about the encoding on the FFMPEG side or we stored wrong values on the header (or they're not enough) ?

    PS : I cannot rely on an extern stream server.

    PPS : We tried the following experiments :

    • substituting the video header with the one stored in the server makes the video playable on both vlc and video tag
    • if we dump the video that is already started (without an header) and we prepend the video header stored in the server or even its original header, the video is playable in VLC but not on the tag (we're carefully prepending the header just before the beggining of the cluster).
  • Queuing up videos for live stream

    5 avril 2014, par Abdul Ali

    Would first like to tell that am new to streaming and ffmpeg.

    Would try to explain scenario as much as possible.

    A web service is intended to receive chunks of video from a user. those chunks need to be simultaneously sent to the web for live streaming for a seamless viewing.

    So the videos need to be queued up for streaming to the web so that it looks like a long single video. and the strict requirement is not to make any temp file on disk.

    Did read something about pipes but am completely alien to that concept as well.

    Kindly tell how / whether this can be achieved from FFMPEG or any other free tool .

    Language used is PHP . The received videos also need to be saved to disk in parallel for new users to see from start.