Recherche avancée

Médias (1)

Mot : - Tags -/sintel

Autres articles (47)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (10367)

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

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

Navigation