Recherche avancée

Médias (2)

Mot : - Tags -/map

Autres articles (37)

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

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (6269)

  • FFmpeg development on Eclipse on Windows

    10 juillet 2013, par Juan Ayala

    The first thing I did was to refer to tutorial on FFmpeg site.

    I set up MSYS+MinGW64, I cloned all the relevant pre-requisites (i.e OpenSSL, x264, rtmpdump),
    I successfully cross-compiled them all. I ran the configure for FFmpeg, and I was able to cross-compile that as well. And my statically linked ffmpeg.exe works to my satisfaction.

    In Eclipse I was able to create a project, load up the source code, navigate it, make some changes, even compile and step-through debug. The problem I am having is with the Eclipse design-time error, and I think this is more of an Eclipse/C++ thing than FFmpeg.

    For example in ffmpeg.c I find this error "Field 'bitstream_filters' could not be resolved" at this line :

    AVBitStreamFilterContext *bsfc = output_streams[i]->bitstream_filters;

    that output_streams is of type

    OutputStream **output_streams

    and when I try to open the declaration for OutputStream Eclipse gives me the option of two locations. Obviously Eclipse is not sure which of these declarations it is, hence the "could not be resolved" error. OutputStream is defined in the following 2 files

    • ffmpeg.h
    • libavformat/smoothstreamingenc.c

    (hmm nice to know FFmpeg can do smooth streaming...) but anyway the correct definition would of been the one in ffmpeg.h.

    So... the whole goal of getting the source into an IDE was so that I could enjoy the benefits of such things like intelisense. What can I do in Eclipse to set some sort of order or rule as to how it should resolve types in cases where the names clash like this ?

  • Unresolved externals with statically built ffmpeg on Windows

    7 juillet 2013, par user1764961

    I built ffmpeg 1.2.1 as a static lib - x64, debug. And I tried to open one of my older projects that links against it. After modifying some changed APIs and similar in my source, it compiled fine, but I have major problems with linking.

    EDITED : the complete latest build output :

    1>libavformat.a(mov.o) : error LNK2019: unresolved external symbol __imp__gmtime64 referenced in function mov_read_mvhd
    1>libavutil.a(parseutils.o) : error LNK2001: unresolved external symbol __imp__gmtime64
    1>libavformat.a(os_support.o) : error LNK2019: unresolved external symbol __imp__wsopen referenced in function ff_win32_open
    1>libavcodec.a(pthread.o) : error LNK2019: unresolved external symbol __imp__beginthreadex referenced in function ff_thread_init
    1>libavcodec.a(frame_thread_encoder.o) : error LNK2001: unresolved external symbol __imp__beginthreadex
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__localtime64 referenced in function av_parse_time
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__time64 referenced in function av_parse_time
    1>libavutil.a(parseutils.o) : error LNK2019: unresolved external symbol __imp__mktime64 referenced in function av_parse_time
    1>libmingwex.a(lib64_libmingwex_a-mingw_output_format.o) : error LNK2019: unresolved external symbol __mingw_get_msvcrt_handle referenced in function __mingw_set_output_format
    1>libmingwex.a(lib64_libmingwex_a-mingw_get_codepage.o) : error LNK2001: unresolved external symbol __mingw_get_msvcrt_handle

    What am I doing wrong ?
    What am I missing here ?
    Does ffmpeg even work today on Windows platform as a static lib, or it becomes less functional on Windows with each new version ?

  • How to compile ffmpeg-1.2.1 on windows with cygwin and android ndk r8e

    17 juin 2013, par Pratik

    I have been trying to find the solution from last few days but unfortunately not even found a single solution which provides me the right direction..! I have goggled no of posts,examples etc.Lots of developers are facing the same problem.I know these things are easy to compile on OS X or any Linux.

    so my question is that :

    How to compile ffmpeg-1.2.1 on windows with cygwin and android ndk r8e
    or
    if anybody had successfully complied the previous releases of ff-mpeg on windows they can tell me the necessary steps.

    I am using windows-7(32-bit)

    Downloaded sources :

    1) I have downloaded latest FFmpeg 1.2.1 "Magic" from FFMPEG sources.

    2) I have downloaded all the necessary packages in cygwin.

    3) I have also downloaded android-ndk-r8e from Android dev site.

    I am trying to find the solution but
    any help would be appriciated.