Recherche avancée

Médias (0)

Mot : - Tags -/metadatas

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

Autres articles (21)

  • 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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (4608)

  • x86 : h264 : Don’t keep data in the redzone across function calls on 64 bit unix

    20 février 2012, par Martin Storsjö
    x86 : h264 : Don’t keep data in the redzone across function calls on 64 bit unix

    We know that the called function (ff_chroma_inter_body_mmxext)
    
doesn’t touch the redzone, and thus will be kept intact - thus,
    
this doesn’t fix any bug per se.
    

    However, valgrind’s memcheck tool intentionally assumes that the
    
redzone is clobbered on every function call and function return
    
(see a long comment in valgrind/memcheck/mc_main.c). This avoids
    
false positives in that tool, at the cost of an extra stack pointer
    
adjustment.
    

    The other alternative would be a valgrind suppression for this issue,
    
but that’s an extra burden for everybody that wants to run libavcodec
    
within valgrind.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavcodec/x86/h264_deblock.asm

  • avdevice_capabilities_create This function is deprecated, what should I replace it ?

    24 juin 2024, par 中野梓喵

    I wanted to get the support information about the device as a string, but this function was completely abolished in ffmpeg 6

    &#xA;

    int     avdevice_capabilities_create (AVDeviceCapabilitiesQuery **caps, AVFormatContext *s, AVDictionary **device_options)&#xA;void    avdevice_capabilities_free (AVDeviceCapabilitiesQuery **caps, AVFormatContext *s)&#xA;&#xA;

    &#xA;

    Alternative solutions

    &#xA;

  • libx264.dll exposes function x264_encoder_open_130, shouldnt this be x264_encoder_open ?

    18 mai 2013, par Kim Kardashian

    I checked in my version of x264 dll file that the open function is named 'x264_encoder_open_130' and 130 happens to be the specific build number of x264 that i use. I build using minGW on windows and link to it, so my program would crash if i try to use a newer dll.. is there a way to get around this ?

Navigation