Recherche avancée

Médias (91)

Autres articles (35)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (4224)

  • nvenc : De-compensate aspect ratio compensation of DVD-like content.

    28 janvier 2015, par Philip Langdale
    nvenc : De-compensate aspect ratio compensation of DVD-like content.
    

    For reasons we are not privy to, nvidia decided that the nvenc encoder
    should apply aspect ratio compensation to ’DVD like’ content, assuming that
    the content is not BT.601 compliant, but needs to be BT.601 compliant. In
    this context, that means that they make the following, questionable,
    assumptions :

    1) If the input dimensions are 720x480 or 720x576, assume the content has
    an active area of 704x480 or 704x576.

    2) Assume that whatever the input sample aspect ratio is, it does not account
    for the difference between ’physical’ and ’active’ dimensions.

    From these assumptions, they then conclude that they can ’help’, by adjusting
    the sample aspect ratio by a factor of 45/44. And indeed, if you wanted to
    display only the 704 wide active area with the same aspect ratio as the full
    720 wide image - this would be the correct adjustment factor, but what if you
    don’t ? And more importantly, what if you’re used to lavc not making this kind
    of adjustment at encode time - because none of the other encoders do this !

    And, what if you had already accounted for BT.601 and your input had the
    correct attributes ? Well, it’s going to apply the compensation anyway !
    So, if you take some content, and feed it through nvenc repeatedly, it
    will keep scaling the aspect ratio every time, stretching your video out
    more and more and more.

    So, clearly, regardless of whether you want to apply bt.601 aspect ratio
    adjustments or not, this is not the way to do it. With any other lavc
    encoder, you would do it as part of defining your input parameters or do
    the adjustment at playback time, and there’s no reason by nvenc should
    be any different.

    This change adds some logic to undo the compensation that nvenc would
    otherwise do.

    nvidia engineers have told us that they will work to make this
    compensation mechanism optional in a future release of the nvenc
    SDK. At that point, we can adapt accordingly.

    Signed-off-by : Philip Langdale <philipl@overt.org>
    Reviewed-by : Timo Rothenpieler <timo@rothenpieler.org>
    Signed-off-by : Anton Khirnov <anton@khirnov.net>

    • [DBH] libavcodec/nvenc.c
  • configure : Don’t require nonfree for nvenc

    23 avril 2016, par Timo Rothenpieler
    configure : Don’t require nonfree for nvenc
    

    As the nvEncodeApi.h header is now MIT licensed, this can be dropped.
    The loaded CUDA and NVENC libraries are part of the nvidia driver, and
    thus count as system libraries.

    Signed-off-by : Anton Khirnov <anton@khirnov.net>

    • [DBH] configure
  • nvenc : write the VUI signal properties for HEVC

    12 mai 2016, par Anton Khirnov
    nvenc : write the VUI signal properties for HEVC
    

    Bump the API version requirement to 6.

    Based on a patch by Agatha Hu <ahu@nvidia.com>.

    • [DBH] configure
    • [DBH] libavcodec/nvenc.c