Recherche avancée

Médias (3)

Mot : - Tags -/pdf

Autres articles (25)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (3990)

  • avformat/matroskadec : Factor parsing content encodings out

    3 septembre 2023, par Andreas Rheinhardt
    avformat/matroskadec : Factor parsing content encodings out
    

    Namely, out of matroska_parse_tracks().

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>

    • [DH] libavformat/matroskadec.c
  • fftools/ffmpeg_filter : factor processing a single frame out of reap_filters()

    23 juillet 2023, par Anton Khirnov
    fftools/ffmpeg_filter : factor processing a single frame out of reap_filters()
    

    This is easier to read.

    • [DH] fftools/ffmpeg_filter.c
  • avfilter/formats : Factor checking for mergeability out of ff_merge_*

    14 août 2020, par Andreas Rheinhardt
    avfilter/formats : Factor checking for mergeability out of ff_merge_*
    

    The callers of the ff_merge_*() functions fall into two categories with
    quite different needs :

    One caller is can_merge_formats() which only wants to test for mergeability
    without it merging anything. In order to do so, it duplicates the lists
    it intends to test and resets their owners so that they are not modified
    by ff_merge_*(). It also means that it needs to receive the merged list
    (and not only an int containing whether the lists are mergeable) to
    properly free it.

    The other callers want the lists to be actually merged. But given the
    fact that ff_merge_*() automatically updates the owners of the lists,
    they only want the information whether the merge succeeded or not ; they
    don't want a link to the new list.

    Therefore this commit splits these functions in two : ff_merge_*() for
    the latter callers and ff_can_merge_*() for the former.
    ff_merge_*() doesn't need to return a pointer to the combined list at all
    and hence these functions have been modified to return an int, which
    allows to distinguish between incompability and memory allocation failures.

    ff_can_merge_*() meanwhile doesn't modify its arguments at all obviating
    the need for copies. This in turn implies that there is no reason to
    return a pointer to the new list, as nothing needs to be freed. These
    functions therefore return an int as well. This allowed to completely
    remove can_merge_formats() in avfiltergraph.c.

    Notice that no ff_can_merge_channel_layouts() has been created, because
    there is currently no caller for this. It could be added if needed.

    Reviewed-by : Nicolas George <george@nsup.org>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavfilter/avfiltergraph.c
    • [DH] libavfilter/formats.c
    • [DH] libavfilter/formats.h