Recherche avancée

Médias (0)

Mot : - Tags -/objet éditorial

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (64)

  • Demande de création d’un canal

    12 mars 2010, par

    En fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
    Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...)

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

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, 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 (15424)

  • Video Conversion ? with ffmpeg

    10 août 2017, par Lee Brindley

    I’m building a react native app for both Android and IOS, the back-end API is written with NodeJS.

    Users may upload video from their phones, once uploaded the user and their friends will be able to view the video - so the videos need to be stored in a format which is playable on both Android & IOS.

    My question relates to the conversion of video, uploaded by the user. I have developed a similar app a couple of years ago, I used the repo node-fluent-ffmpeg which provides a nice API to interact with ffmpeg.

    In the previous project (which was a web app), I converted the uploaded videos into two files, one .mp4 and one .webm - if a user uploaded a mp4, then I would skip the mp4 step, likewise if they uploaded a .webm.

    This was kind of slow. Now i’ve come across the same requirement years later, after some research I think I was wrong to convert the videos in the last project.

    I’ve read that I can simply use ffmpeg to change the container format of the videos, which is a much faster process than converting them from scratch.

    The video conversion code I used last time went something along the lines of :

    var convertVideo = function (source, format, output, success, failure, progress) {

       var converter = ffmpeg(source);

       var audioCodec = "libvorbis";

       if (format.indexOf("mp4") != -1) {
           audioCodec = "aac";
       }

       converter.format(format)
           .withVideoBitrate(1024)
           .withAudioCodec(audioCodec)
           .on('end', success)
           .on('progress', progress)
           .on('error', failure);

       converter.save(output);
    };

    Usage :

    Convert to mp4 :

    convertVideo("PATH_TO_VIDEO", "mp4", "foo.mp4", () => {console.log("success");});

    Convert to webm :

    convertVideo("PATH_TO_VIDEO", "webm", "foo.webm", () => {console.log("success");});

    Can anyone point out a code smell here regarding performance of this operation ? Is this code doing a lot more than it should to achieve cross platform compatibility between IOS and Android ?

    Might be worth mentioning that support for older OS versions is not such a big deal in this project.

  • How do you generate a looping animated gif for Facebook with ffmpeg

    7 février 2020, par Alan W. Smith

    When I paste a giphy url (like this one) into a facebook post or comment, the gif plays immediately and loops indefinitely. When I upload ones I make from ffmpeg, neither of those things happen. You have to click a play button to start the animation and then it ends after one time through.

    I have a couple of ffmpeg commands I use to create the gifs. They are :

    ffmpeg -ss 10 -t 5  -i input.m4v -vf "fps=15,scale=800:-2:flags=lanczos,palettegen" -y palette.png

    and

    ffmpeg -ss 10.6 -t 5 -i input.m4v -i palette.png -filter_complex "fps=15,scale=800:-1:lanczos[video];[video][1:v]paletteuse" output.gif

    The first one generates a custom color pallet that’s used by the second one to create a high quality animated gif. I’ve also tried adding -loop 0 (i.e. ffmpeg -ss 10.6 -t 5 -i input.m4v -i palette.png -filter_complex "fps=15,scale=800:-1:lanczos[video];[video][1:v]paletteuse" -loop 0 output.gif) but that didn’t work either.

    I also tried uploading the ffmpeg generated images to a personal website and calling them from there but those didn’t load at all.

    In case it helps, here’s a copy of one of the gifs (which autostarts and loops on StackOverflow for me but not on FB)

    enter image description here

    How does one go about creating a gif that will autostart and loop indefinitely for facebook ?

    (Note : I’ve got no problem if I need to do something with a personal website, but I don’t want to use Giphly or the other animated gif sites directly if at all possible. Also worth pointing out that I discovered if I download the image from giphly and upload it, it doesn’t autostart either. So, this may be something internal to FB, but I’d still like to figure that out.)

  • Curator of the Samples Archive

    13 mai 2011, par Multimedia Mike — General

    Remember how I mirrored the world-famous MPlayerHQ samples archive a few months ago ? Due to a series of events, the original archive is no longer online. However, me and the people who control the mplayerhq.hu domain figured out how to make samples.mplayerhq.hu point to samples.multimedia.cx.

    That means... I’m the current owner and curator of our central multimedia samples repository. Such power ! This should probably be the fulfillment of a decade-long dream for me, having managed swaths of the archive, most notably the game formats section.

    How This Came To Be

    If you pay any attention to the open source multimedia scene, you might have noticed that there has been a smidge of turmoil. Heated words were exchanged, authority was questioned, some people probably said some things they didn’t mean, and the upshot is that, where once there was one project (FFmpeg), there are now 2 projects (also Libav). And to everyone who has wanted me to mention it on my blog— there, I finally broke my silence and formally acknowledged the schism.

    For my part, I was just determined to ensure that the samples archive remained online, preferably at the original samples.mplayerhq.hu address. There are 10 years worth of web links out there pointing into the original repository.

    Better Solution

    I concede that it’s not entirely optimal to host the repository here at multimedia.cx. While I can offer a crazy amount of monthly bandwidth, I can’t offer rsync (invaluable for keeping mirrors in sync), nor can the server provide anonymous FTP or allow me to offer accounts to other admins who can manage the repository.

    The samples archive is also mirrored at samples.libav.org/samples. I understand that service is provided by VideoLAN. Right now, both repositories are known to be static. I’m open to brainstorms about how to improve the situation.