Recherche avancée

Médias (0)

Mot : - Tags -/content

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

Autres articles (22)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

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

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

Sur d’autres sites (3301)

  • Unable to build solution in Visual Studio 2019 : The BaseOutputPath/OutputPath property is not set for project

    23 juillet 2022, par mhadi

    In an effort to integrate FFmpeg with Unity, I have been trying to build a solution file in Visual Studio 2019. However, I am currently unable to resolve the following error when I try to build in Visual Studio :

    


    


    The BaseOutputPath/OutputPath property is not set for project
'FFmpegUnityInterop.vcxproj'. Please check to make sure that you have
specified a valid combination of Configuration and Platform for this
project. Configuration='Release' Platform='x64'. This error may
also appear if some other project is trying to follow a
project-to-project reference to this project, this project has been
unloaded or is not included in the solution, and the referencing
project does not build using the same or an equivalent Configuration
or Platform.

    


    


    I have tried a number of solutions, including :

    


      

    1. Manually adding the OutputPath in 'FFmpegUnityInterop.vcxproj'&#xA;<outputpath>bin/Build/</outputpath>.
    2. &#xA;

    3. In the FFmpegUnityInterop.vcxproj file, moving the ProjectProperty with my preferred configuration and platform combination to the very top of the list of ProjectProperties (there are 8 of them).
    4. &#xA;

    5. Building with different configuration and platforms.
    6. &#xA;

    7. Trying to build from VS Dev Command prompt using the following command :&#xA;MSbuild.exe "FFmpegUnityInterop.sln" /p:Configuration=Release /p:Platform="x64", as well as from the Visual Studio IDE.
    8. &#xA;

    9. Tried setting the OutputPath in the command line command&#xA;(>MSbuild.exe FFmpegUnityInterop.sln /p:Configuration=Release /p:Platform="AnyCPU" /p:OutputPath = bin\Debug), only to have&#xA;MSbuild throw error MSB1008 (MSBUILD : error MSB1008 : Only one&#xA;project can be specified.)
    10. &#xA;

    11. Setting the configuration and platform manually in the Configuration Manager GUI in&#xA;Visual Studio.
    12. &#xA;

    &#xA;

    I may have missed an attempted solution or two above, but I've tried most of the suggestions I found online, only to get the error pasted above. Part of me suspects that my compilation of FFmpeg libraries didn't execute fully, but I unfortunately do not have enough experience to verify that. Any suggestions to resolve this would be much appreciated.

    &#xA;

    PS. The project was developed privately by a private entity that is currently unreachable

    &#xA;

  • Setup FFMpegCore in Visual Studio 2019

    27 juillet 2022, par DsiakMondala

    I am confused on the basics of using a library. I understand that there is a library called FFMpeg and a wrapper called FFMpegCore so we can use FFMpeg with C#, correct ? I downloaded both FFMpeg and FFMpegCore and I have them in my project's folder. Although I didn't perceive any class named FFMpegOptions in either of the file's folders.&#xA;I am stuck on how to actually set it up so I can use it in my little project, I never downloaded someone's library before. Can somebody please walk me though the motions of connecting the three of them together ?

    &#xA;

    So far I experimented with :

    &#xA;

      &#xA;
    • Add a reference to my project, but there doesn't seem to be any .dll, .tlb, .olb, .ocx or .exe files to add
    • &#xA;

    • Add an existing project to my solution. There is a project called FFMpegCore.csproj but adding it raises a missing SDK error. Weirdly enough, opening the same project as a standalone doesn't raise any issues which makes me thing the operation I am trying is inadequate.
    • &#xA;

    &#xA;

    I am sure this is a silly and easy setup to perform but I just don't know enough to find a solution.

    &#xA;

  • Can't link FFMPEG dynamically to VS 2019 project

    10 février 2021, par Maya Sela

    I downloaded the source code of FFMPEG 3.4.8 and built with MSVC as such :
    &#xA;After unzipping, open x86_x64 Cross Tools Command Prompt for VS 2019 and run msys2_shell.cmd. From there, run
    &#xA;./configure --toolchain=msvc --arch=x86_64 --enable-yasm --enable-asm --enable-shared --disable-static&#xA;and&#xA;make&#xA;
    &#xA;I then created a new project in VS 2019.
    &#xA;In Properties > C/C++ > General > Additional Include Directories :
    &#xA;(Where all the headers are)

    &#xA;

    E:\ffmpeg-3.4.8\libavutil&#xA;E:\ffmpeg-3.4.8\libavcodec&#xA;E:\ffmpeg-3.4.8\libavdevice&#xA;E:\ffmpeg-3.4.8\libavfilter&#xA;E:\ffmpeg-3.4.8\libavresample&#xA;E:\ffmpeg-3.4.8\libpostproc&#xA;E:\ffmpeg-3.4.8\libswscale&#xA;E:\ffmpeg-3.4.8\libswresample&#xA;E:\ffmpeg-3.4.8\libavformat&#xA;

    &#xA;

    In Properties > Linker > General > Additional Library Directories :
    &#xA;(Where the .lib files are)

    &#xA;

    E:\ffmpeg-3.4.8\libavutil&#xA;E:\ffmpeg-3.4.8\libavcodec&#xA;E:\ffmpeg-3.4.8\libavdevice&#xA;E:\ffmpeg-3.4.8\libavfilter&#xA;E:\ffmpeg-3.4.8\libavresample&#xA;E:\ffmpeg-3.4.8\libpostproc&#xA;E:\ffmpeg-3.4.8\libswscale&#xA;E:\ffmpeg-3.4.8\libswresample&#xA;E:\ffmpeg-3.4.8\libavformat&#xA;

    &#xA;

    In Properties > Linker > Input > Additional Dependencies :

    &#xA;

    avcodec.lib&#xA;avdevice.lib&#xA;avfilter.lib&#xA;avformat.lib&#xA;swresample.lib&#xA;swscale.lib&#xA;

    &#xA;

    For good measure, I copied the .dll files of each library to the Release folder of the project. There is one source file I am trying to build and run :

    &#xA;

    &#xA;extern "C" {&#xA;#include <libavformat></libavformat>avformat.h>&#xA;}&#xA;&#xA;int main() {&#xA;    AVFormatContext* pFormatContext = avformat_alloc_context();&#xA;}&#xA;

    &#xA;

    The result is as follows :

    &#xA;

    1>------ Build started: Project: FFMPEG_example, Configuration: Release x64 ------&#xA;1>Source.cpp&#xA;1>Source.obj : error LNK2001: unresolved external symbol avformat_alloc_context&#xA;1>C:\Users\maya.s\source\repos\FFMPEG_example\x64\Release\FFMPEG_example.exe : fatal error LNK1120: 1 unresolved externals&#xA;1>Done building project "FFMPEG_example.vcxproj" -- FAILED.&#xA;========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========&#xA;

    &#xA;

    Does anyone have an idea ?
    &#xA;Thanks !

    &#xA;