Recherche avancée

Médias (1)

Mot : - Tags -/portrait

Autres articles (98)

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

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

  • Correcting the variable name in an ffmpeg subtitle script

    21 juin 2017, par Steven Foong

    I have 175 mp4 video files and subtitle files with the extension .ass. Unfortunately, my smart TV is not able to read those subtitles. I plan to burn (hardcode) the subtitles into the video.

    I use this command :

    ffmpeg -i orgvideo.mp4 -vf subtitles="subtitle.ass" newvideo.mp4     <br />

    It works. So I plan to use a bash script to automate the process.

    Everything in the script is working but the ffmpeg command line isn’t able to retrieve the subtitle variable.

    After googling around, I found that my file name has special character and space, that causes my script to fail. If the video file name and the subtitle file is simple, then the script should be no problem.

    This is my script :

    for f in *.mp4
    do
       new="${f%%.mp4} (CHT).mp4"
       subtitle="${f%%.mp4}.chi.ass"
       &lt; /dev/null ffmpeg -i "$f" -vf subtitles="$subtitle" "$new"
    done

    The ffmpeg line is having problems reading the subtitle file variable. Can anyone help ?

  • Cloud Functions for Firebase : completing long processes without touching maximum timeout

    17 février, par Scott Ewing

    I have to transcode videos from webm to mp4 when they're uploaded to firebase storage. I have a code demo here that works, but if the uploaded video is too large, firebase functions will time out on me before the conversion is finished. I know it's possible to increase the timeout limit for the function, but that seems messy, since I can't ever confirm the process will take less time than the timeout limit.

    &#xA;&#xA;

    Is there some way to stop firebase from timing out without just increasing the maximum timeout limit ?

    &#xA;&#xA;

    If not, is there a way to complete time consuming processes (like video conversion) while still having each process start using firebase function triggers ?

    &#xA;&#xA;

    If even completing time consuming processes using firebase functions isn't something that really exists, is there some way to speed up the conversion of fluent-ffmpeg without touching the quality that much ? (I realize this part is a lot to ask. I plan on lowering the quality if I absolutely have to, as the reason webms are being converted to mp4 is for IOS devices)

    &#xA;&#xA;

    For reference, here's the main portion of the demo I mentioned. As I said before, the full code can be seen here, but this section of the code copied over is the part that creates the Promise that makes sure the transcoding finishes. The full code is only 70 something lines, so it should be relatively easy to go through if needed.

    &#xA;&#xA;

    const functions = require(&#x27;firebase-functions&#x27;);&#xA;const mkdirp = require(&#x27;mkdirp-promise&#x27;);&#xA;const gcs = require(&#x27;@google-cloud/storage&#x27;)();&#xA;const Promise = require(&#x27;bluebird&#x27;);&#xA;const ffmpeg = require(&#x27;fluent-ffmpeg&#x27;);&#xA;const ffmpeg_static = require(&#x27;ffmpeg-static&#x27;);&#xA;

    &#xA;&#xA;

    (There's a bunch of text parsing code here, followed by this next chunk of code inside an onChange event)

    &#xA;&#xA;

    function promisifyCommand (command) {&#xA;    return new Promise( (cb) => {&#xA;        command&#xA;        .on( &#x27;end&#x27;,   ()      => { cb(null)  } )&#xA;        .on( &#x27;error&#x27;, (error) => { cb(error) } )&#xA;        .run();&#xA;    })&#xA;}&#xA;return mkdirp(tempLocalDir).then(() => {&#xA;    console.log(&#x27;Directory Created&#x27;)&#xA;    //Download item from bucket&#xA;    const bucket = gcs.bucket(object.bucket);&#xA;    return bucket.file(filePath).download({destination: tempLocalFile}).then(() => {&#xA;      console.log(&#x27;file downloaded to convert. Location:&#x27;, tempLocalFile)&#xA;      cmd = ffmpeg({source:tempLocalFile})&#xA;               .setFfmpegPath(ffmpeg_static.path)&#xA;               .inputFormat(fileExtension)&#xA;               .output(tempLocalMP4File)&#xA;      cmd = promisifyCommand(cmd)&#xA;      return cmd.then(() => {&#xA;        //Getting here takes forever, because video transcoding takes forever!&#xA;        console.log(&#x27;mp4 created at &#x27;, tempLocalMP4File)&#xA;        return bucket.upload(tempLocalMP4File, {&#xA;            destination: MP4FilePath&#xA;        }).then(() => {&#xA;          console.log(&#x27;mp4 uploaded at&#x27;, filePath);&#xA;        });&#xA;      })&#xA;    });&#xA;  });&#xA;

    &#xA;

  • Bash - Not able to replace the variable in ffmpeg subtitle

    20 juin 2017, par Steven Foong

    I have 175 mp4 video files and subtitle file with extension ass. Unfortunately my smart TV not able to read the subtitle title. I plan to burn (hardcode) the subtitle into the video.

    I use this command

    ffmpeg -i orgvideo.mp4 -vf subtitles="subtitle.ass" newvideo.mp4

    it work. So I plan to use bash shell script to automate the process.

    Everything is the script is working , but the ffmpeg command line wouldn’t able to retrieve the subtitle variable.

    After google around, I found that my file name has special character and space, that cause my script not working. If the video file name and the subtitle file is simple, then the script should be no problem.

    This is my script.

    for f in *.mp4
    do
    new="${f%%.mp4} (CHT).mp4"
    subtitle="${f%%.mp4}.chi.ass"
    &lt; /dev/null ffmpeg -i "$f" -vf subtitles="$subtitle" "$new"
    done

    The ffmpeg having problem reading the subtitle file variable. Anyone can help ?