Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (98)

  • (Dés)Activation de fonctionnalités (plugins)

    18 février 2011, par

    Pour gérer l’ajout et la suppression de fonctionnalités supplémentaires (ou plugins), MediaSPIP utilise à partir de la version 0.2 SVP.
    SVP permet l’activation facile de plugins depuis l’espace de configuration de MediaSPIP.
    Pour y accéder, il suffit de se rendre dans l’espace de configuration puis de se rendre sur la page "Gestion des plugins".
    MediaSPIP est fourni par défaut avec l’ensemble des plugins dits "compatibles", ils ont été testés et intégrés afin de fonctionner parfaitement avec chaque (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

  • How do I use ffmpeg4android in an ADT project ?

    16 janvier 2013, par mystafer

    I used the project FFmpeg4Android on sourceforge to build the FFmpeg .so shared library files. However, I am having trouble using them in an ADT Java application. I created a simple JNI call that attempts to call av_register_all and I get library errors.

    When I run the application on my Nexus 7 I am told that it is unable to load library libavformat-HEAD-1.0.so

    So I tried to load this via the System.loadLibrary method and I was unable to find libavcodec-HEAD-1.0.so. Working my way back in this manner I eventually attempted to load libavutil-HEAD-1.0.so which yielded an error 'cannot locate symbol "__strchr_chk"'.

    This is my Java class :

    public class LibavcodecTest {
    
    public static native void avRegisterAll();
    

    
    static {
    
        System.loadLibrary("avutil-HEAD-1.0");
    
        System.loadLibrary("avcodec-HEAD-1.0");
    
        System.loadLibrary("avformat-HEAD-1.0");
    
        System.loadLibrary("LibavcodecTest");
    
    }
    
}

    Update

    I contacted the developer that maintains ffmpeg4android and he was able to direct me to change the version of the android source I was building against to the same as my device which worked to allow my to call av_register_all successfully.

    However, now I get a crash calling avformat_open_input where I receive "Fatal signal 11 (SIGSEGV)".

    My search on the web makes me believe this is a memory access issue. Does anybody know if this may be resolved by loading the shared libraries differently ?

  • Using JNI in my project and geeting error "Fatal signal 11 (SIGSEGV) at 0x000000ec (code=1) "

    9 juillet 2012, par Rahul Upadhyay

    I read so many post on this que but was unable to find out my problem. I am using JNI ina my project, developing with FFMPEG library. When i start decoding video using ffmpeg it gives me an error Fatal signal 11 (SIGSEGV) at 0x000000ec (code=1) and force stop.

    Using Nexus, and it uses maxMemory : 67108864

    i know heap Size by applying this code

    Runtime rt = Runtime.getRuntime();
    
long maxMemory = rt.maxMemory();
    
Log.v("onCreate", "maxMemory:" + Long.toString(maxMemory));

  • Revision fb1f6f1db4 : Fix segment feature data type. It has a range of -255,255, so should be int16_t

    7 juin 2013, par Ronald S. Bultje

    Changed Paths :
     Modify /vp9/common/vp9_blockd.h



    Fix segment feature data type.

    It has a range of -255,255, so should be int16_t, not int8_t.

    Change-Id : I5ef4b6aefb6212b0f35f4754f3c4d73fddbc52a0

Navigation