Recherche avancée

Médias (1)

Mot : - Tags -/ipad

Autres articles (63)

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

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    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 (...)

Sur d’autres sites (11764)

  • Hide file names on mobile devices.

    16 avril 2019, par blueimp
    Hide file names on mobile devices.
    

    Detect mobile devices by the existence of the window.orientation property.

  • lavf : reorganize URLProtocols

    19 février 2016, par Anton Khirnov
    lavf : reorganize URLProtocols
    

    Instead of a linked list constructed at av_register_all(), store them
    in a constant array of pointers.

    Since no registration is necessary now, this removes some global state
    from lavf. This will also allow the urlprotocol layer caller to limit
    the available protocols in a simple and flexible way in the following
    commits.

    • [DBH] configure
    • [DBH] libavformat/Makefile
    • [DBH] libavformat/allformats.c
    • [DBH] libavformat/avio.c
    • [DBH] libavformat/concat.c
    • [DBH] libavformat/crypto.c
    • [DBH] libavformat/file.c
    • [DBH] libavformat/gopher.c
    • [DBH] libavformat/hlsproto.c
    • [DBH] libavformat/http.c
    • [DBH] libavformat/icecast.c
    • [DBH] libavformat/librtmp.c
    • [DBH] libavformat/md5proto.c
    • [DBH] libavformat/mmsh.c
    • [DBH] libavformat/mmst.c
    • [DBH] libavformat/protocols.c
    • [DBH] libavformat/rtmpcrypt.c
    • [DBH] libavformat/rtmphttp.c
    • [DBH] libavformat/rtmpproto.c
    • [DBH] libavformat/rtpproto.c
    • [DBH] libavformat/sctp.c
    • [DBH] libavformat/srtpproto.c
    • [DBH] libavformat/tcp.c
    • [DBH] libavformat/tls_gnutls.c
    • [DBH] libavformat/tls_openssl.c
    • [DBH] libavformat/udp.c
    • [DBH] libavformat/unix.c
    • [DBH] libavformat/url.h
  • Problem with Linking FFMPEG Libraries in Visual Studio on Windows 10 [closed]

    14 mars 2024, par Dentricky73

    I'm facing an issue while trying to link FFMPEG libraries in Visual Studio on a Windows 10 OS. Specifically, Visual Studio seems to locate the headers correctly, but encounters difficulties in finding the associated libraries. Initially, I attempted to compile the FFMPEG SDK myself, but encountered problems with the library extensions, which ended with a Linux .o file instead of a Windows .lib. Subsequently, I downloaded a prebuilt version from here, but I'm still encountering errors.

    


    In Visual Studio 2022, I've configured the following settings :

    


    


    Property > Configuration Properties > C/C++ > General > Additional Include Directories
C :\cmder\c++SDK\ffmpeg\include

    


    


    


    Property > Configuration Properties > Linker > General > Additional Library Directories
C :\cmder\c++SDK\ffmpeg\lib

    


    


    


    Property > Configuration Properties > Linker > Input > Additional Dependencies
avcodec.lib, avdevice.lib, avfilter.lib, avformat.lib, avutil.lib, postproc.lib, swresample.lib, swscale.lib

    


    


    Despite these configurations, Visual Studio fails to locate the FFMPEG libraries during the linking process. Could someone please provide guidance on how to resolve this issue and correctly link the FFMPEG libraries in Visual Studio on Windows ? Any help or insights would be greatly appreciated.

    


    Specific Issues Encountered :

    


    During the compilation and linking process in Visual Studio 2022, I encountered the following errors :

    


    Error 1 : A value of type "const AVCodec *" cannot be used to initialize an entity of type "AVCodec *".
Error 2 : Identifier "av_free_packet" is undefined.
Error 3 : Class "AVStream" has no member "codec".
Error 4 : Class "AVFrame" has no member "owner".
Despite configuring the project settings to include the correct include directories and library dependencies, these errors persist.

    


    Why Previous Attempts Didn't Meet My Needs :

    


    My previous attempts to resolve these issues were unsuccessful because I couldn't pinpoint the root cause of the compilation and linking errors. While I ensured that the include directories and library dependencies were correctly configured in Visual Studio, the errors persisted, indicating that there may be underlying issues with the setup or compatibility between the FFMPEG SDK and Visual Studio environment.