Recherche avancée

Médias (0)

Mot : - Tags -/organisation

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

Autres articles (32)

  • MediaSPIP Player : problèmes potentiels

    22 février 2011, par

    Le lecteur ne fonctionne pas sur Internet Explorer
    Sur Internet Explorer (8 et 7 au moins), le plugin utilise le lecteur Flash flowplayer pour lire vidéos et son. Si le lecteur ne semble pas fonctionner, cela peut venir de la configuration du mod_deflate d’Apache.
    Si dans la configuration de ce module Apache vous avez une ligne qui ressemble à la suivante, essayez de la supprimer ou de la commenter pour voir si le lecteur fonctionne correctement : /** * GeSHi (C) 2004 - 2007 Nigel McNie, (...)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (3490)

  • Using ffmpeg static libraries in an visual studio explress C++ 2010 project

    29 octobre 2015, par Yvo Götz

    As the title says, I have been trying to get ffmpeg/libav libraries to work in MSVC++ 2010.
    However, I keep running in the following error while coding on debug mode.

    code :

    extern "C"
    {
       #ifndef __STDC_CONSTANT_MACROS
       #define __STDC_CONSTANT_MACROS
       #endif
       #include
       #include
       #include
       #include
    }
    int main( int argc, char* argv[] )
    {
       av_register_all();
       return 0;
    }

    console :

    1>------ Build started: Project: ffmpeg, Configuration: Debug Win32 ------
    1>ffmpeg.obj : error LNK2019: unresolved external symbol _av_register_all referenced in       function _main
    1>C:\Users\okki\documents\visual studio 2010\Projects\ffmpeg\Debug\ffmpeg.exe : fatal    error LNK1120: 1 unresolved externals
    ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

    I used zeranoe’s latest build git-56ba331 (2013-05-14).

    And I have tried the following to fix this :

    • configuring the project to look for both the x64 and x86 libraries.
    • Add the DLLs from the ’shared’ package to both library folders.
    • Add the library directory to both the linker options and VC++ Directories.

    I have been stuck on this for a while, and any suggestion can help.
    If any extra info is needed I will happily provide.

  • Building with Visual Studio 2010, MFC, and FFmpeg

    11 janvier 2013, par spurgeon

    I'm working on building a Windows MFC application in Visual Studio 2010 using FFmpeg and SDL. However, I can't get the project to build after creating an MFC project from scratch and including the FFmpeg development libraries (avcodec.lib, avdevice.lib, avformat.lib, etc.). I'm using the development build from Zeranoe FFmpeg. I have configured the following in the Project Properties :

    1. Set VC++ Directories -> Include Directories (added the FFmpeg "include" directories)
    2. Set VC++ Directories -> Library Directories (to the FFmpeg "lib" directory)
    3. Set Linker -> Input -> Additional Dependencies (to include avcodec.lib, etc.)

    For what it's worth, the build succeeds when I omit FFmpeg's "include\libavutil" include from the VC++ Directories -> Include Directories.

    Below are some of the first build errors I'm receiving (I won't post all, since it's long). Any help would be appreciated.

    ClCompile:
    stdafx.cpp

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\atltime.h(371): error C3861: '_mktime64': identifier not found

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\atltime.h(386): error C3861: '_localtime64_s': identifier not found

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\atltime.h(409): error C3861: '_gmtime64_s': identifier not found

    c:\program files\microsoft sdks\windows\v7.0a\include\intsafe.h(144): warning C4005: 'INT8_MIN' : macro redefinition

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\afxtaskspane.h(279): error C2146: syntax error : missing ';' before identifier 'm_nLastAnimTime'

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\afxribboncategory.h(282): error C2146: syntax error : missing ';' before identifier 'm_ActiveTime'

    c:\program files\microsoft visual studio 10.0\vc\atlmfc\include\afxdockingmanager.h(353): error C2146: syntax error : missing ';' before identifier 'm_clkLastTime'

    Build FAILED.

    I've referenced both of these articles, which were of help :

  • libx264 in Visual Studios 2010 - Memory error in Release Build

    21 décembre 2011, par DeusAduro

    I am building an application and using the x264 library as an encoder. I have built the library for my windows system using MSys/MingW. The library works fine under debug build (note both debug and release builds are using the default VS2010 settings). However, under release an access violation error is thrown at the first call to the x264 library, specifically :

     Unhandled exception at 0x00905a4d in StreamTest.exe:
     0xC0000005: Access violation.

    The error is thrown at this line :

    x264_param_default_preset((params), "veryfast", "zerolatency");

    While I was figuring out how to compile the library I came across a lot of talk about memory alignment in Windows/Visual Studios and how it wasn't particularly compatible with the alignment expected by x264. For example when compiling in MSys I had to enable —enable-memalign-hack. I am wondering if the source of this error might stem from a memory alignment issue which only manifests itself through some setting in my release build. Unfortunately I know almost nothing about the specifics and so have come here.

    Can anyone give me some more information regarding the memory alignment issues and any Visual Studio settings which might cause this ? Any other tips/pointers to fix this issue are very welcome.

    Thanks.

    Edit

    From answer below :

    1. From the linked SO question I get the impression he added "build with debugger info" to the OpenCV build ? Since I'm building the x264 library through MSys with G++ I'm not sure I can do this. I have checked the build settings for my project, and under both release and debug it has debugger info. Not sure if I missed something in that post, please let me know.
    2. I tried the application verifier. It seems that x264 is trying to execute code from non-executable memory as per the App verifier output :

      VERIFIER STOP 0000000000000650: pid 0x1B18:

      Attempt to execute code in non-executable memory (first chance).

      0000000000905A4D : Address being accessed.
      0000000000905A4D : Code performing invalid access.
      000000000021EA90 : Exception record. Use .exr to display it.
      000000000021E5A0 : Context record. Use .cxr to display it.

    Anything to be gathered from this output ?

    Thanks again.