Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (21)

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

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (7695)

  • How can I prettify my compiled binary of FFmpeg ?

    2 avril 2019, par Hashim

    After many weeks and a lot of effort, I finally managed to use a Cygwin and MinGW-w64 toolchain to cross-compile a working binary of FFmpeg for Windows, complete with the superior but elusive fdk_aac encoder.

    However, comparing my newly-compiled binary with the official pre-compiled build for Windows makes me feel a little... lacking (first run is the Zeranoe build, second is my own) :

    enter image description here

    Notice how the Zeranoe build’s banner is missing all of the unseemly-looking configure options apart from the external libraries. Along with that, it also has the date that the program was built on inserted right after the GCC version.

    How were the compilers of this build able to add these enhancements to their binary, and how can I do the same ? I’m assuming these are simply GCC or preprocessor options that I can’t find any information on, or maybe there’s more to it than that.

    N.B : I’m aware of the --no-banner switch for FFmpeg, and that’s not what I’m trying to do here.

  • Flutter : How to use flutter_ffmpeg to add overlays like watermarks and texts to a video ?

    29 septembre 2022, par Ryan Wang

    I try to implement the video_editing feature to my app, and I'd tried the Tapioca Package and the Video_Manipulation package but found that they both do not meet my criteria, so I put my last hope on the flutter_ffmpeg package.

    


    But as I read through its official doc on pub.dev, not a thing on my mind but "WHAT THE HECK", I can't understand what those commands are used for, and though I can't find anything related to add widget overlays to a video. And almost no tutorial on the web that explains how to use it.

    


    So if you successfully implemented adding watermarks/texts to a video with the ffmpeg package, please show me how. Thanks ! 

    


  • 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