Recherche avancée

Médias (0)

Mot : - Tags -/formulaire

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

Autres articles (43)

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

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

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

  • Is there a Mac OS X equivalent of Windows' named pipe

    14 juin 2016, par Mike Versteeg

    In windows I use named pipes to interface to a console program (ffmpeg). Thought I had a try rewriting this for the Mac, but I cannot find named pipe support in either FireMonkey or even native OS X code. Does it exist at all ?

  • Does Apple AS assembler replace certain NEON instructions with equivalent ones on iOS ?

    5 avril 2012, par Yi Wang

    I was trying to use ffmpeg on iOS and was debugging a crash in the optimized arm code. I have discovered that some unsigned (.u16, .u32) instruction have been replaced by signed ones (.i16, .i32). It's easy to see because disassembled instruction on GDB doesn't quite match the source code.

    For example,

    vrshrn.u32 -> vrshrn.i32
    
vrshrn.u16 -> vrshrn.i16
    
vadd.u16 -> vadd.i16

    My questions :

    1. Is this behavior correct and expected ? If not, how do we correct it ?
    2. If they are equivalent, why do we nee need the unsigned ones at all ? Is it because that way the code is more explicit ?
    3. Is this behavior expected with other platform's toolkit ? For example, Android's toolkit ? (I have heard Apple's AS is an ancient one)

  • Revision b90996c51b : Reset skip flag in superblock RD loop. This is the superblock equivalent of com

    30 janvier 2013, par Ronald S. Bultje

    Changed Paths : Modify /vp9/encoder/vp9_rdopt.c Reset skip flag in superblock RD loop. This is the superblock equivalent of commit 290b83a. Change-Id : Ib3945dd9e992fa9ec1fdea5a11e17a3cc0e37637

Navigation