Recherche avancée

Médias (2)

Mot : - Tags -/plugins

Autres articles (53)

  • Gestion générale des documents

    13 mai 2011, par

    MédiaSPIP ne modifie jamais le document original mis en ligne.
    Pour chaque document mis en ligne il effectue deux opérations successives : la création d’une version supplémentaire qui peut être facilement consultée en ligne tout en laissant l’original téléchargeable dans le cas où le document original ne peut être lu dans un navigateur Internet ; la récupération des métadonnées du document original pour illustrer textuellement le fichier ;
    Les tableaux ci-dessous expliquent ce que peut faire MédiaSPIP (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (9371)

  • Why Do Some of the Codecs in FFMPEG's Supported Codec List Show "encoders :" or "decoders :" in Parenthesis ?

    4 mai 2020, par spaceman

    If you open the Command Prompt, and run ffmpeg -codecs,
    
you will get a long list of Codecs that FFMPEG supports.

    



    Here's a small sample of the list :

    



     DEV.L. h261                 H.261
 DEV.L. h263                 H.263 / H.263-1996, H.263+ / H.263-1998 / H.263 version 2
 D.V.L. h263i                Intel H.263
 DEV.L. h263p                H.263+ / H.263-1998 / H.263 version 2
 DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (encoders: libx264 libx264rgb)
 D.V.LS hevc                 H.265 / HEVC


    



    Now If you briefly go over the whole list,
    
you see that most Codecs in this list appear with their Name and Description,
    
but some of the Codecs also include parenthesis in the Description, and in the parenthesis,
    
they specify "encoders :" or "decoders :".

    



    For example :

    



    1)

    



     DEV.LS h264                 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (encoders: libx264 libx264rgb)


    



    2)

    



     DEVILS jpeg2000             JPEG 2000 (decoders: jpeg2000 libopenjpeg) (encoders: jpeg2000 libopenjpeg)


    



    3)

    



     DEV.L. msmpeg4v3            MPEG-4 part 2 Microsoft variant version 3 (decoders: msmpeg4) (encoders: msmpeg4)


    



    4)

    



     DEA.L. aac                  AAC (Advanced Audio Coding) (encoders: aac libvo_aacenc)


    



    5)

    



     DEA.L. amr_nb               AMR-NB (Adaptive Multi-Rate NarrowBand) (decoders: amrnb libopencore_amrnb) (encoders: libopencore_amrnb)
 DEA.L. amr_wb               AMR-WB (Adaptive Multi-Rate WideBand) (decoders: amrwb libopencore_amrwb) (encoders: libvo_amrwbenc)


    



    My question :

    



    Why do some Codecs have those parenthesis, specifying Encoders/Decoders,
    
while other (in fact : most) codecs don't have these parenthesis ?

    


  • avformat/matroskadec : Improve forward compability

    25 mars 2020, par Andreas Rheinhardt
    avformat/matroskadec : Improve forward compability
    

    Matroska is built around the principle that a reader does not need to
    understand everything in a file in order to be able to make use of it ;
    it just needs to ignore the data it doesn't know about.

    Our demuxer typically follows this principle, but there is one important
    instance where it does not : A Block belonging to a TrackEntry with no
    associated stream is treated as invalid data (i.e. the demuxer will try
    to resync to the next level 1 element because it takes this as a sign
    that it has lost sync). Given that we do not create streams if we don't
    know or don't support the type of the TrackEntry, this impairs this
    demuxer's forward compability.

    Furthermore, ignoring Blocks belonging to a TrackEntry without
    corresponding stream can (in future commits) also be used to ignore
    TrackEntries with obviously bogus entries without affecting the other
    TrackEntries (by not creating a stream for said TrackEntry).

    Finally, given that matroska_find_track_by_num() already emits its own
    error message in case there is no TrackEntry with a given TrackNumber,
    the error message (with level AV_LOG_INFO) for this can be removed.

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskadec.c
  • clang++ : error : linker command failed with exit code 1 (use -v to see invocation) in cpp with ffmpeg

    6 avril 2020, par Pradeep Simba
    clang&#x2B;&#x2B;: error: linker command failed with exit code 1 (use -v to see invocation)&#xA;

    &#xA;&#xA;

    I saw this link and link2. But, it not done.

    &#xA;&#xA;

    My jni folder :

    &#xA;&#xA;

    enter image description here

    &#xA;&#xA;

    Android.mk file

    &#xA;&#xA;

    LOCAL_PATH := $(call my-dir)&#xA;include $(CLEAR_VARS)&#xA;LOCAL_C_INCLUDES &#x2B;= ./include&#xA;LOCAL_MODULE     := native-lib&#xA;LOCAL_CFLAGS := -DSTDC_HEADERS -std=c99&#xA;LOCAL_CFLAGS := -Wno-pointer-sign&#xA;LOCAL_ARM_MODE := arm&#xA;APP_OPTIM := release&#xA;LOCAL_SRC_FILES  := \&#xA;./native-lib.cpp&#xA;LOCAL_LDLIBS := -llog&#xA;include $(BUILD_SHARED_LIBRARY)&#xA;

    &#xA;&#xA;

    native-lib.cpp file

    &#xA;&#xA;

    #include &#xA;#include <string>&#xA;&#xA;extern "C"&#xA;{&#xA;#include "libavcodec/avcodec.h"&#xA;#include "libavformat/avformat.h"&#xA;#include "libavutil/opt.h"&#xA;}&#xA;&#xA;extern "C" JNIEXPORT jstring JNICALL&#xA;Java_com_example_m_MainActivity_stringFromJNI(&#xA;JNIEnv* env,&#xA;jobject /* this */) {&#xA;std::string hello = "Hello from C&#x2B;&#x2B;";&#xA;av_register_all();&#xA;return env->NewStringUTF(hello.c_str());&#xA;}&#xA;</string>

    &#xA;&#xA;

    When I build ndk this error occurs.

    &#xA;&#xA;

    D:\Github\n>ndk-build&#xA;Android NDK: APP_PLATFORM not set. Defaulting to minimum supported version android-16.&#xA;[arm64-v8a] Compile&#x2B;&#x2B;      : native-lib &lt;= native-lib.cpp&#xA;[arm64-v8a] SharedLibrary  : libnative-lib.so&#xA;./obj/local/arm64-v8a/objs/native-lib/./libmp3lame/native-lib.o: In function `Java_com_example_m_MainActivity_stringFromJNI&#x27;:&#xA;D:\Github\n/jni/./libmp3lame/native-lib.cpp:16: undefined reference to `av_register_all&#x27;&#xA;clang&#x2B;&#x2B;: error: linker command failed with exit code 1 (use -v to see invocation)&#xA;make: *** [D:/install/sdk/ndk/21.0.6113669/build//../build/core/build-binary.mk:725: obj/local/arm64-v8a/libnative-lib.so] Error 1&#xA;&#xA;D:\Github\n>ndk-build -v&#xA;GNU Make 4.2.1&#xA;Built for x86_64-w64-mingw32&#xA;Copyright (C) 1988-2016 Free Software Foundation, Inc.&#xA;License GPLv3&#x2B;: GNU GPL version 3 or later /gnu.org/licenses/gpl.html>&#xA;This is free software: you are free to change and redistribute it.&#xA;There is NO WARRANTY, to the extent permitted by law.&#xA;&#xA;D:\Github\n>&#xA;

    &#xA;&#xA;

    why it comes like this native-lib.cpp:16: undefined reference av_register_all ?

    &#xA;&#xA;

    I added all the required libs in my jni folder but, why this error and this native-lib.cpp:16: undefined reference av_register_all comes ?&#xA;How can I solve this ?

    &#xA;