Recherche avancée

Médias (5)

Mot : - Tags -/open film making

Autres articles (59)

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

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

  • transform all the images from the current directory to a video [migrated]

    14 septembre 2011, par FihopZz

    I'd like to use ffmpeg to transform all images from the current directory to a video.
    the image file name is not like, image1.jpg, image2.jpg.

    Thanks,

  • Using ffmpeg to encode a high quality video

    7 janvier 2013, par CakeMaster

    I have a set of video frames saved as images in a directory, and I'm trying to encode these to a good quality video, however every setting and every format I try produces very noticeable artifacts.

    The basic command is this :

    ffmpeg -r 25 -i %4d.png myvideo.mpg

    and I've tried the minrate and maxrate flags. Any of mpg, avi, mov, flv formats will do.

    Any suggestions for settings ? Final file size is not an issue.

  • PC Video Conferencing in the Year 1999

    21 juin 2011, par Multimedia Mike — General

    Remember Intel’s custom flavor of H.263 cleverly named I.263 ? I think I have finally found an application that used it thanks to a recent thrift shop raid— Intel Video Phone :



    The root directory of the disc has 2 copies of an intro.avi video. One copy uses Intel Indeo 3 video and PCM audio. The other uses I.263 video and an undetermined (presumably Intel-proprietary) audio codec — RIFF id 0x0402 at a bitrate of 88 kbits/sec for stereo, 22 kHz audio. The latter video looks awful but is significantly smaller (like 4 MB vs. 25 MB).

    This is the disc marked as "Send it to a friend...". Here’s the way this concept was supposed to operate :

    • You buy an Intel Video Phone Camera Pack (forgotten page courtesy of the Internet Archive) which includes a camera and 2 CDs.
    • You install the camera and video phone software on your computer.
    • You send the other CD to the person whom you want to be able to see your face when you’re teleconferencing with them.
    • The other party installs the software.
    • The 2 of you may make an internet phone call presumably using commodity PC microphones for the voice component ; the person who doesn’t have a camera is able to see the person who does have a camera.
    • In a cunning viral/network marketing strategy, Intel encourages the other party to buy the physical hardware as well so that they may broadcast their own visage back to the other person.

    If you need further explanation, the intro lady does a great job :



    I suspect I.263 was the video codec driving this since Indeo 3 would probably be inappropriate for real time video applications due to its vector quantizing algorithm.

Navigation