Recherche avancée

Médias (91)

Autres articles (24)

  • MediaSPIP Init et Diogène : types de publications de MediaSPIP

    11 novembre 2010, par

    À l’installation d’un site MediaSPIP, le plugin MediaSPIP Init réalise certaines opérations dont la principale consiste à créer quatre rubriques principales dans le site et de créer cinq templates de formulaire pour Diogène.
    Ces quatre rubriques principales (aussi appelées secteurs) sont : Medias ; Sites ; Editos ; Actualités ;
    Pour chacune de ces rubriques est créé un template de formulaire spécifique éponyme. Pour la rubrique "Medias" un second template "catégorie" est créé permettant d’ajouter (...)

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

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

Sur d’autres sites (4511)

  • ffmpeg (avcodeclib) & png support

    23 mai 2013, par user472155

    I'm building ffmpeg libraries on Windows with a --enable-decoder=png switch. However, after successful build, there is no png support. Any ideas what went wrong ?

  • OpenGL (GLEW) + FFMPEG + VS2010 release build

    6 décembre 2015, par rickhik

    Currently I am working on a application that uses OpenGL (GLEW) and FFMPEG (libav’s) in Visual Studio 2010. The GLEW libs are included as Additional Libraries. The libav is set via a header file with extern "c" and pragma comment lib.

    The application opens a OpenGL window which draws some quads with textures via FFMPEG. I want to use this application for my volunteer job at a TV station of a Childrens Hospital.

    The problem I have is building a release version of my project. When I am building a Debug version it all works fine. I get a OpenGL Window with the quads. When I change Debug into Release and start the Debugger, it gives me the message "entry point of procedure __GLEW_EXT_framebuffer_object not found in DLL avcodec-56.dll", which is a bit strange to me because of the fact that the GLEW is not part of the avcodec-56.dll ?

    I can solve this issue by going to the project settings -> Linker -> Optimization and switch References from Yes(/OPT:REF) to No(/OPT:NOREF). I start the debugger to build the solution and it works as well. Now when I go to the Release folder of the project and start the build executable, the OpenGL Window stays black without giving me an error message.

    I hope you guys can help me out.

    @michael-iv I saw you had a similar issue

  • linking MSVC .lib using MinGW64

    27 mai 2014, par govind

    I want to create a plugin for ffmpeg. I have compiled my plugin using MSVC 64-bit compiler (cl.exe) and i have the plugin.lib
    Now while building ffmpeg using Mingw64 the linker is not able to find any functions which are defined in plugin.lib. I have confirmed using nm.exe that the functions are definitely present in my plugin.lib.

    I have followed all the steps required for plugin-ffmpeg integration which i am sure are not causing this because on Linux, ffmpeg (built using gcc) is able to integrate with plugin (built using Intel-compiler).

    I was reading here that it is possible to link a 64bit MSVC created dynamic library(.dll) with MinGW but not a static library(.lib).

    Also this page says that it is possible to link using reimp and dlltool. But for that i need a .lib and a .dll both. Also it does not specify 32 or 64 bit.

    So my doubts :

    Is it possible to link a 32bit MSVC .lib with MinGW(32) ?

    Is it possible to link a 64bit MSVC .lib with MinGW64 ? And if yes then how ?

    Building both ffmpeg and plugin using the same compiler might work but that’s not an option for me. Also i am using C only.

Navigation