Recherche avancée

Médias (0)

Mot : - Tags -/page unique

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

Autres articles (107)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

Sur d’autres sites (15740)

  • Running FFMPEGJS in a React Project

    23 mars 2020, par beek

    I’m trying to get https://github.com/ffmpegjs/ffmpeg.js/ running in a Create React App build project.

    import {createWorker} from '@ffmpeg/ffmpeg';

    When I import the library the build fails with

    ./node_modules/@ffmpeg/ffmpeg/src/createWorker.js
    Module parse failed: Unexpected token (21:4)
    You may need an appropriate loader to handle this file type.
    |     logger,
    |     progress,
    |     ...options
    |   } = resolvePaths({
    |     ...defaultOptions,

    I’m not sure how to handle this, or where the problem might be. Is this a Webpack issue ?

  • Can't compile dll from C++ project - Visual Studio

    11 octobre 2017, par FlowRyan

    I’m trying to play a RTSP stream in Unity 5.

    For that I found a RTSP-plugin for Unity on Github that I want to try, but unfortunatelly it comes with no Readme or installation guide whatsoever.

    So far I found out that I’m dealing with a C++ Visual Studio project that needs to be compiled into a DLL in order to add it to Unity. But when I try to build the project I get the following Error for the header file "ffmpegenv.h" :

    Error C1083 Cannot open include file : ’libavutil\opt.h’ : No such file or directory - (Screenshot)

    Here’s the code from the header file

    #pragma once

    //=============================
    // Includes
    //-----------------------------
    // FFMPEG is writen in C so we need to use extern "C"
    //-----------------------------
    extern "C" {
       //#define INT64_C(x) (x ## LL)
       //#define UINT64_C(x) (x ## ULL)

    #include
    #include <libavutil></libavutil>mathematics.h>
    #include <libavformat></libavformat>avformat.h>
    #include <libswscale></libswscale>swscale.h>
    #include <libswresample></libswresample>swresample.h>
    #include <libavutil></libavutil>imgutils.h>
    #include <libavcodec></libavcodec>avcodec.h>

    }

    I’m aware that the header includes source code from the FFmpeg libraries which doesn’t come with the plugin I’m trying to compile. So I downloaded the FFmpeg source code from their GitHub page and copied all the code files (with its original folder structure) inside the plugin’s project folder.

    However when I then try to compile the plugin, it still doesn’t find the #includes an shows the same error as mentioned above.

    How I can I get the plugin to compile ? What am I missing ?

    Thanks in advance

    P.S. : I’m using Visual Studio Community 2017 with C++ support and Win 10 SDK as well as Win 8.1 SDK.

  • Emscripten : Linking library to project

    13 avril 2021, par locust

    I'm trying to build a small project that uses ffmpeg library to WebAssembly, with use of Emscripten. Before that, I tried it out by transpiling some simple program from C into Wasm and it worked fine, but that time I was not using any additional libraries.

    &#xA;

    For C++ I'm working with Visual Studio and FFmpeg I linked in project's "Properties" as follows :

    &#xA;

      &#xA;
    1. all .h header files I placed in "include" catalog and I added it as "Additional Include Directories" in "C/C++" section

      &#xA;

    2. &#xA;

    3. all .lib and .dll.a (for example avcodec.lib or libavcodec.dll.a) files I placed in "lib" and added as "Additional Library Directories" in "Linker" section

      &#xA;

    4. &#xA;

    &#xA;

    All includes and the program itself works fine, so now I was trying to prepare a Wasm module with Emscripten with the same same command that I used earlier, but already knowing that is not going to work :

    &#xA;

    em&#x2B;&#x2B; cut_video.cpp -Os -g1 -L lib -I include -s WASM=1 -s FORCE_FILESYSTEM=1 -s ALLOW_MEMORY_GROWTH=1 -s EXPORT_ES6=1 -s MODULARIZE=1 -s "EXPORT_NAME=&#x27;Editor&#x27;" -s "ENVIRONMENT=&#x27;web&#x27;" -s EXPORTED_FUNCTIONS="[&#x27;_doubler&#x27;, &#x27;_cut_video&#x27;, &#x27;_cut_video1&#x27;]" -s ERROR_ON_UNDEFINED_SYMBOLS=0  -s ASSERTIONS=1 --bind -o cutter.js&#xA;

    &#xA;

    I added the "-I include" parameter which is suppose to be pointing to the same header files, that I mentioned above, and it seems to be fine for Emscripten, because the initial error was solved by it.&#xA;Emscripten already found out the problem with functions from ffmpeg library, so I added "ERROR_ON_UNDEFINED_SYMBOLS=0" just to see what will happen when I will add this module to front-end app. Obviously it end up with error "missing function : av_register_all", which is first ffmpeg function within my code.

    &#xA;

    All explanations that can be helpful I found really unclear for me, because generally I'm not working with C++ or Linux environment, so I'm not fimilliar with Makefile or so.

    &#xA;

    Is there a way, basing on what I described and how my project was prepared with Visual Studio, to tell the Emscripten to use those pre-build .dll.a or .lib files of FFmpeg for my app ? Or how should I modify my project to make it acceptable for Emscripten ?

    &#xA;

    Edit : Since cut_video.cpp file is quite big, maybe it's a better idea to just paste here a link to this file on github instead of the big block of code.

    &#xA;