Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (72)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

Sur d’autres sites (12053)

  • How can I efficient process a video on a per-request basis ?

    18 décembre 2015, par mipadi

    I’m working on a web application in which a watermark must be applied to a video before it is sent to the user. Currently this watermark is static, and is created using ffmpeg when a video is updated. However, the application is changing so that a unique watermark will be added to the video for every request made for the video. This prevents a problem, as the video files may be fairly large and adding a watermark may be time-consuming (e.g., in some cases it may take over a minute to add a watermark), but the watermarks cannot be added on upload.

    I figured that streaming video could be a solution and implemented a solution using the nginx-rtmp-module, but several problems cropped up :

    1. RTMP solutions are a no-go as they appear to require Flash. This application must be supported on devices that don’t support Flash at all, or don’t (and won’t) have it installed.
    2. I have considered using MPEG-DASH, but that enjoys only limited support. Namely, it is not supported on versions of Firefox targeted by the application, nor is it supported on iOS or some versions of Safari.
    3. I have considered HLS, but that enjoys even more limited support than MPEG-DASH.
    4. Regardless, I haven’t actually been able to get Dash.js (the reference player for MPEG-DASH streams) to work, although that may be due to an encoding issue, I’m not sure.

    I wondered if there is a better (perhaps simpler) solution to this problem ; perhaps streaming video isn’t the way to go at all ? Is there an efficient way to transcode a video file on-the-fly and start sending it to the browser quickly ?

    I am not against using solutions like node.js or other platforms/frameworks, and solutions can use HTML5 <video></video> if necessary.

  • Streaming video playlist from collection of identical mp4 files

    25 mars 2019, par user2746672

    I am looking for a way to play/stream to browser tag a list of mp4 files (same size, bitrate, etc) without hickups in between the files. I am hoping the following approach would work :
    * convert mp4 files to m4s/m4v files
    * generate MPEG-Dash MPD file (xml)
    * stream MPD to dash player in browser

    Is this in any way possible ? I am aware the m4s/m4v files need special headers and an entry file must be made somehow, and there you have my roadblock.

    Bottom-line is I want to avoid to concatenate the separate videos into one big video file and avoid the hick-ups you see when sequencing via a straightforward ’ended-event’ way in JS.

    Any suggestion much appreciated !

  • How can I efficiently process a video on a per-request basis ?

    20 décembre 2015, par mipadi

    I’m working on a web application in which a watermark must be applied to a video before it is sent to the user. Currently this watermark is static, and is created using ffmpeg when a video is updated. However, the application is changing so that a unique watermark will be added to the video for every request made for the video. This prevents a problem, as the video files may be fairly large and adding a watermark may be time-consuming (e.g., in some cases it may take over a minute to add a watermark), but the watermarks cannot be added on upload.

    I figured that streaming video could be a solution and implemented a solution using the nginx-rtmp-module, but several problems cropped up :

    1. RTMP solutions are a no-go as they appear to require Flash. This application must be supported on devices that don’t support Flash at all, or don’t (and won’t) have it installed.
    2. I have considered using MPEG-DASH, but that enjoys only limited support. Namely, it is not supported on versions of Firefox targeted by the application, nor is it supported on iOS or some versions of Safari.
    3. I have considered HLS, but that enjoys even more limited support than MPEG-DASH.
    4. Regardless, I haven’t actually been able to get Dash.js (the reference player for MPEG-DASH streams) to work, although that may be due to an encoding issue, I’m not sure.

    I wondered if there is a better (perhaps simpler) solution to this problem ; perhaps streaming video isn’t the way to go at all ? Is there an efficient way to transcode a video file on-the-fly and start sending it to the browser quickly ?

    I am not against using solutions like node.js or other platforms/frameworks, and solutions can use HTML5 <video></video> if necessary.

Navigation