Recherche avancée

Médias (16)

Mot : - Tags -/mp3

Autres articles (69)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

Sur d’autres sites (12961)

  • Converting video with ffmpeg from a script not in the root folder

    30 octobre 2017, par Daniel Ormerod

    I am using ffmpeg to convert videos, create thumbnails etc.

    I made the below function to convert a video and when I run it in a script in the root folder it converts ok.

    However, I am using ajax to upload the video and the script is located /ajax/upload-video.php and when I run it in that folder it fails to convert.

    I have tried sending the $src and $dest up with ../ before the filenames to go back a folder but it isn’t working.

    Can anybody help ?

    Do I need to add something to the $command line to tell it to go back a folder ?

    These are the variables being used in the function :

    $ffmpegpath = 'ffmpeg.exe';
    $src = 'videos/video1.wmv';
    $dest = 'videos/video1.mp4';

    I have tried :

    $ffmpegpath = 'ffmpeg.exe';
    $src = '../videos/video1.wmv';
    $dest = '../videos/video1.mp4';

    And the function :

    function convert_video($src, $dest) {

       global $ffmpegpath;

       if (!file_exists($src)) {

           echo '<p>The file does not exist</p>';

       } else {

           $command = "$ffmpegpath -i $src $dest";

           @exec($command, $ret);

           if (!file_exists($dest)) {

               echo '<p>The file failed to create</p>';

           } else {

               if (filesize($dest)==0) {

                   echo '<p>The file created but has not filesize</p>';

               } else {

                   echo '<p>File Created Successfully</p>';

               }

           }

       }

    }
  • configure : Separate package name and version requirements in helper functions

    16 novembre 2016, par Diego Biurrun
    configure : Separate package name and version requirements in helper functions
    

    The unadorned package name is needed to derive package-related variable names.

    • [DBH] configure
  • avcodec/h2645_sei : loosen up min luminance requirements

    25 mai 2024, par Niklas Haas
    avcodec/h2645_sei : loosen up min luminance requirements
    

    The H.265 specification is quite clear on this case :

    > When min_display_mastering_luminance is not in the range of 1 to
    > 50000, the nominal maximum display luminance of the mastering display
    > is unknown or unspecified or specified by other means not specified in
    > this Specification.

    And so the current code is correct in marking luminance data as invalid
    if min luminance is set to 0. However, this breaks playback of at least
    several real-world Blu-ray releases, for example La La Land, Planet of
    the Apes, and quite possibly a lot more. These come with ostensibly
    valid max_luminance tags (1000 nits), but min_luminance set to 0.

    Loosen up this requirement by guarding it behind FF_COMPLIANCE_STRICT.
    We still reject blatantly invalid metadata (wrong value range on
    luminance, max set to 0, max below min, min above 50 nits etc.), so this
    shouldn't cause any unintended regressions.

    Fixes : https://github.com/mpv-player/mpv/issues/14177

    • [DH] libavcodec/h2645_sei.c