Recherche avancée

Médias (91)

Autres articles (69)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

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

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (13229)

  • Révision 20033 : #2914 : attention a ne pas confondre un fichier temporaire (d’ecriture atomique ...

    4 décembre 2012, par cedric -

    Attention aussi : entre le preg et le moment ou l’on traite une session, celle-ci peut avoir disparue, ne pas la recréer (concurence)

  • ffMPEG "inttypes.h not found" error

    2 septembre 2013, par Nav

    While using the ffMPEG builds in Windows with Visual Studio 2010, I encountered the inttypes.h not found error.
    Since searching through the internet led me to wrong solutions, I thought I'd put up the right solution here so that people can find it easily. Will be answering my own question soon.

  • Weird and unpredictable crash when using libx264 cross-compiled with MinGW

    2 mars 2012, par Daniel

    I'm working on a C++ project using Visual Studio 2010 on Windows. I'm linking dynamically against x264 which I built myself as a shared library using MinGW following the guide at

    http://www.ayobamiadewole.com/Blog/Others/x264compilation.aspx

    The strange thing is that my x264 code is working perfectly sometimes. Then when I change some line of code (or even change the comments in the file !) and recompile everything crashes on the line

    encoder_ = x264_encoder_open(&param);

    With the message

    Access violation reading location 0x00000000

    I'm not doing anything funky at all so it's probably not my code that is wrong but I guess there is something going wrong with the linking or maybe something is wrong with how I compiled x264.

    The full initialization code :

    x264_param_t param = { 0 };
    
if (x264_param_default_preset(&param, "ultrafast", "zerolatency") < 0) {
    
  throw KStreamerException("x264_param_default_preset failed");
    
}
    

    
param.i_threads = 1;
    
param.i_width = 640;
    
param.i_height = 480;
    
param.i_fps_num = 10;
    
param.i_fps_den = 1;
    

    
encoder_ = x264_encoder_open(&param); // <-----
    
if (encoder_ == 0) {
    
  throw KStreamerException("x264_encoder_open failed");
    
}
    

    
x264_picture_alloc(&pic_, X264_CSP_I420, 640, 480);

    Edit : It turns out that it always works in Release mode and when using superfast instead of ultrafast it also works in Debug mode 100%. Could it be that the ultrafast mode is doing some crazy optimizations that the debugger doesn't like ?

Navigation