Recherche avancée

Médias (91)

Autres articles (61)

  • 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

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

Sur d’autres sites (5062)

  • subprocess "TypeError : a bytes-like object is required, not 'str'" (Python 2 -> 3 issue maybe ?)

    8 juillet 2017, par chatbottest

    I’m using this code from a previously asked question a few years ago, however I believe this is outdated. Trying to run the code, I receive the error above. I’m still a novice in python, so I could not get much clarification from similar questions. Anyone know why this is happening ?

    import subprocess

    def getLength(filename):
     result = subprocess.Popen(["ffprobe", filename],
       stdout = subprocess.PIPE, stderr = subprocess.STDOUT)
     return [x for x in result.stdout.readlines() if "Duration" in x]

    print(getLength('bell.mp4'))

    Traceback

    Traceback (most recent call last):
     File "B:\Program Files\ffmpeg\bin\test3.py", line 7, in <module>
       print(getLength('bell.mp4'))
     File "B:\Program Files\ffmpeg\bin\test3.py", line 6, in getLength
       return [x for x in result.stdout.readlines() if "Duration" in x]
     File "B:\Program Files\ffmpeg\bin\test3.py", line 6, in <listcomp>
       return [x for x in result.stdout.readlines() if "Duration" in x]
    TypeError: a bytes-like object is required, not 'str'
    </listcomp></module>
  • avfilter/vf_overlay : remove rgb option

    24 juin 2017, par Paul B Mahol
    avfilter/vf_overlay : remove rgb option
    

    Its been deprecated for over 3 years.

    Signed-off-by : Paul B Mahol <onemda@gmail.com>

    • [DH] doc/filters.texi
    • [DH] libavfilter/vf_overlay.c
  • avcodec, avformat : deprecate anything related to side data merging

    16 mars 2017, par wm4
    avcodec, avformat : deprecate anything related to side data merging
    

    This patch deprecates anything that has to do with merging/splitting
    side data. Automatic side data merging (and splitting), as well as all
    API symbols involved in it, are removed completely.

    Two FF_API_ defines are dedicated to deprecating API symbols related to
    this : FF_API_MERGE_SD_API removes av_packet_split/merge_side_data in
    libavcodec, and FF_API_LAVF_KEEPSIDE_FLAG deprecates
    AVFMT_FLAG_KEEP_SIDE_DATA in libavformat.

    Since it was claimed that changing the default from merging side data to
    not doing it is an ABI change, there are two additional FF_API_ defines,
    which stop using the side data merging/splitting by default (and remove
    any code in avformat/avcodec doing this) : FF_API_MERGE_SD in libavcodec,
    and FF_API_LAVF_MERGE_SD in libavformat.

    It is very much intended that FF_API_MERGE_SD and FF_API_LAVF_MERGE_SD
    are quickly defined to 0 in the next ABI bump, while the API symbols are
    retained for a longer time for the sake of compatibility.
    AVFMT_FLAG_KEEP_SIDE_DATA will (very much intentionally) do nothing for
    most of the time it will still be defined. Keep in mind that no code
    exists that actually tries to unset this flag for any reason, nor does
    such code need to exist. Code setting this flag explicitly will work as
    before. Thus it’s ok for AVFMT_FLAG_KEEP_SIDE_DATA to do nothing once
    side data merging has been removed from libavformat.

    In order to avoid that anyone in the future does this incorrectly, here
    is a small guide how to update the internal code on bumps :

    - next ABI bump (probably soon) :
    - define FF_API_LAVF_MERGE_SD to 0, and remove all code covered by it
    - define FF_API_MERGE_SD to 0, and remove all code covered by it
    - next API bump (typically two years in the future or so) :
    - define FF_API_LAVF_KEEPSIDE_FLAG to 0, and remove all code covered
    by it
    - define FF_API_MERGE_SD_API to 0, and remove all code covered by it

    This forces anyone who actually wants packet side data to temporarily
    use deprecated API to get it all. If you ask me, this is batshit fucked
    up crazy, but it’s how we roll. Making AVFMT_FLAG_KEEP_SIDE_DATA to be
    set by default was rejected as an ABI change, so I’m going all the way
    to get rid of this once and for all.

    Reviewed-by : James Almer <jamrial@gmail.com>
    Reviewed-by : Rostislav Pehlivanov <atomnuker@gmail.com>
    Reviewed-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] doc/APIchanges
    • [DH] libavcodec/avcodec.h
    • [DH] libavcodec/avpacket.c
    • [DH] libavcodec/utils.c
    • [DH] libavcodec/version.h
    • [DH] libavformat/avformat.h
    • [DH] libavformat/mux.c
    • [DH] libavformat/options_table.h
    • [DH] libavformat/utils.c
    • [DH] libavformat/version.h