Recherche avancée

Médias (0)

Mot : - Tags -/publication

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

Autres articles (78)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

Sur d’autres sites (12043)

  • aacenc : implement Intensity Stereo encoding support

    2 juillet 2015, par Rostislav Pehlivanov
    aacenc : implement Intensity Stereo encoding support
    

    This commit implements intensity stereo coding support
    to the native aac encoder. This is a way to increase the efficiency
    of the encoder by zeroing the right channel’s spectral coefficients
    (in a channel pair) and rederiving them in the decoder using information
    from the scalefactor indices of special band types. This commit
    confomrs to the official ISO 13818-7 specifications, although due to
    their ambiguity certain deviations have been taken to ensure maximum
    sound quality. This commit has been extensively tested and has shown
    to not result in audiable audio artifacts unless in extreme cases.
    This commit also adds an option, aac_is, which has the value of
    0 by default. Intensity Stereo is part of the scalable aac profile
    and is thus non-default.

    The way IS coding works is that it rederives the right channel’s
    spectral coefficients from the left channel via the scalefactor
    index values left in the right channel. Since an entire band’s
    spectral coefficients do not need to be coded, the encoder’s
    efficiency jumps up and it unzeroes some high frequency values
    which it previously did not have enough bits to encode. That way
    less information is lost than the information lost by rederiving
    the spectral coefficients with some error. This is why the
    filesize of files encoded with IS do not decrease significantly.
    Users wishing that IS coding should reduce filesize are expected
    to reduce their encoding bitrates appropriately.

    This is V2 of the commit. The old version did not mark ms_mask as
    0 since M/S and IS coding are incompactible, which resulted in
    distortions with M/S coding enabled. This version also improves
    phase detection by measuring it for every spectral coefficient in
    the band and using a simple majority rule to determine whether the
    coefficients are in or out of phase. Also, the energy values per
    spectral coefficient were changed as to reflect the
    official specifications.

    Reviewed-by : Claudio Freire <klaussfreire@gmail.com>
    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavcodec/aaccoder.c
    • [DH] libavcodec/aacenc.c
    • [DH] libavcodec/aacenc.h
  • ffmpeg error during encoding : EOF timestamp not reliable

    5 décembre 2019, par Massimo Vantaggio

    I have noticed that some videos processed by the following command displays an error in the preliminary phase of the process :

    [Parsed_movie_0 @ 0x7fb06cf00d80] EOF timestamp not reliable

    All this happens while I’m testing the ffmpeg command line that generates the encoding with the specific required by dash :

    ffmpeg -y -i inputfile.mp4 -c:a aac -b:a 384k -ar 48000 -ac 2 -async 1 -c:v libx264 -x264opts keyint=60:min-keyint=60:no-scenecut -r 30 -b:v 2400k -maxrate 2400k -bufsize 1200k -t 3600 -vf "scale=-1:$size" -vf "movie=logo.png [watermark]; [in][watermark] overlay=main_w-overlay_w-10:10 [out]" format.mp4

    It work fine with some videos with small duration but by testing with some movies downloaded it give this error and i believe that could be a problem for MP4Box when dashing which other errors.
    Does anyone have any notices about it ? Is the command line suitable for dash ?
    Thanks
    Massimo

  • Screen capture with libavcodec/ffmpeg, and write it to mp4 file

    10 février 2015, par Drakkainen

    I’m trying to (programatically) record the screen with DirectShow screen driver. I wrote some quick and (very) dirty code to try to get that to work (http://pastebin.com/ZJuhZRCz) based on ffmpeg examples but I have lots of trouble figuring out what time_base/framerate to use. If i leave the time_base/framerate parts empty I only get a single still frame. If i change them to any values, the video just turns black.

    I’m guessing it has something to do with the output file settings, but I just ran out of ideas on what to try. Any pointers/help would be greatly appreciated.