Recherche avancée

Médias (16)

Mot : - Tags -/mp3

Autres articles (59)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

Sur d’autres sites (7271)

  • UnsatisfiedLinkError using JavaCV maven dependency in Gradle on Android

    28 juillet 2015, par Michael Garner

    I am getting this error when trying to call the start() method of an instance of FFmpegFrameGrabber :

    java.lang.UnsatisfiedLinkError: org.bytedeco.javacpp.avutil
    
    at java.lang.Class.classForName(Native Method)
    
    at java.lang.Class.forName(Class.java:309)
    
    at org.bytedeco.javacpp.Loader.load(Loader.java:390)
    
    at org.bytedeco.javacpp.Loader.load(Loader.java:358)
    
    at org.bytedeco.javacpp.avformat$AVFormatContext.<clinit>(avformat.java:2539)
    
    at org.bytedeco.javacv.FFmpegFrameGrabber.startUnsafe(FFmpegFrameGrabber.java:383)
    
    at org.bytedeco.javacv.FFmpegFrameGrabber.start(FFmpegFrameGrabber.java:377)
    
</clinit>

    These are the dependencies I am referring to per the READMES for the projects javacpp and javacv :

    compile group: 'org.bytedeco', name: 'javacpp', version: '1.0'
    
compile group: 'org.bytedeco', name: 'javacv', version: '1.0'

    I did not add any .so files to the project, but I was expecting those to come with the dependencies. When I tried adding them previously I started getting gradle errors for duplicate files so I assume that they come with the dependencies.

    I think what is happening is that it can’t load the .so files for whatever reason, but I don’t know how to solve this problem.

    I have tried setting the systemProperty for dependencies mentioned in the GitHub READMEs like so :

    task execute(type: JavaExec) {
    
    systemProperty "platform.dependencies", true
    
}

    It doesn’t help as written.

    Why is this error seen and what can be done to handle it ?

    Any guidance on this issue would be greatly appreciated. The overall goal is to use the FFmpegFrameGrabber to crop video the user has taken with their device. I am open to all solutions.

  • x86inc : Support arbitrary stack alignments

    9 février 2014, par Henrik Gramner
    x86inc : Support arbitrary stack alignments

    Change ALLOC_STACK to always align the stack before allocating stack space for
    
consistency. Previously alignment would occur either before or after allocating
    
stack space depending on whether manual alignment was required or not.
    • [DH] libavcodec/x86/h264_deblock.asm
    • [DH] libavutil/x86/x86inc.asm

  • movenc : Place the sidx index after the initial moov/mdat pair

    9 août 2015, par Martin Storsjö
    movenc : Place the sidx index after the initial moov/mdat pair

    For fragmented files with non-empty moov, with a fragment index
    
(sidx), place the index after the initial moov/mdat pair.
    

    Previously, for this pathological case, the index was written
    
at the start of the file.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/movenc.c

Navigation