Recherche avancée

Médias (1)

Mot : - Tags -/net art

Autres articles (25)

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

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

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

Sur d’autres sites (6422)

  • Adding FFmpeg library as dependency in Visual studio project to get rid of LNK2019 error

    13 mars 2019, par MSD Paul

    While compiling a project on Microsoft visual studio (to generate dll), I am getting the following linking errors (LNK2019)

    Severity Code Description Project File Line Suppression State
    Error LNK2019 unresolved external symbol av_strerror referenced in function "private : void __cdecl DecoderFFmpeg::printErrorMsg(int)" (?printErrorMsg@DecoderFFmpeg@@AEAAXH@Z)
    Severity Code Description Project File Line Suppression State
    Error LNK2019 unresolved external symbol av_get_channel_layout_nb_channels referenced in function "private : int __cdecl DecoderFFmpeg::initSwrContext(void)"

    several other functions like av_dict_set, av_dict_free, avcodec_decode2 which is related to the ffmpeg libraries. Can anyone please tell me how to properly add "ffmpeg" as dependenciesto this project and link it properly ?

  • wmavoice : convert DCT-I/DST-I to lavu/tx

    4 août 2023, par Lynne
    wmavoice : convert DCT-I/DST-I to lavu/tx
    

    This is the very last user of any lavc transform code.

    This also *corrects* wmavoice decoding, as the previous DCT/DST
    transforms were incorrect, bringing it closer to Microsoft's
    own wmavoice decoder.

    • [DH] libavcodec/wmavoice.c
    • [DH] tests/fate/wma.mak
  • XCode 5 is not linking Static Library to Cocoa Application

    4 septembre 2014, par aaronljx

    Basically I am building a Cocoa (OSX) application that uses some of the encoding/decoding libraries from ffmpeg (e.g. libavcodec.a, libavformat.a). For these libraries, I have explicitly configured it to be compiled as static library.. there were no dylibs created when I ran the make after configuring the package. Hence I am quite certain that these libraries would work as a static library.

    As usual I added these libraries to my xcode project via the Build Phases and Framework section. The .a files are there and when I build my project, there were no linking errors. Everything is fine and dandy until I run otool against the executable file of my application and realised that it needs the ffmpeg library dylibs to run. An attempt to run the application would fail since there is no dylib installed on my machine. If I run it on another machine that has ffmpeg installed (compiled with dynamic library) the application would work.

    Therefore, my question is, am I missing out on any of the configuration on the xcode part to instruct the linker to statically link those libraries that are used in my application ? (I remember when I develop C/C++ applications in Microsoft Visual Studio, all I need to do is to just add the static libraries (*.lib) files to my project’s linker settings and it will be automatically linked to my final assembly.)

    Thanks.