Recherche avancée

Médias (0)

Mot : - Tags -/api

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (49)

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

  • Les formats acceptés

    28 janvier 2010, par

    Les commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
    ffmpeg -codecs ffmpeg -formats
    Les format videos acceptés en entrée
    Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
    Les formats vidéos de sortie possibles
    Dans un premier temps on (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (8089)

  • Transcoding fMP4 to HLS while writing on iOS using FFmpeg

    29 avril 2017, par bclymer

    TL ;DR

    I want to convert fMP4 fragments to TS segments (for HLS) as the fragments are being written using FFmpeg on an iOS device.

    Why ?

    I’m trying to achieve live uploading on iOS while maintaining a seamless, HD copy locally.

    What I’ve tried

    1. Rolling AVAssetWriters where each writes for 8 seconds, then concating the MP4s together via FFmpeg.

      What went wrong - There are blips in the audio and video at times. I’ve identified 3 reasons for this.

      1) Priming frames for audio written by the AAC encoder creating gaps.

      2) Since video frames are 33.33ms long, and audio frames 0.022ms long, it’s possible for them to not line up at the end of a file.

      3) The lack of frame accurate encoding present on Mac OS, but not available for iOS Details Here

    2. FFmpeg muxing a large video only MP4 file with raw audio into TS segments. The work was based off the Kickflip SDK

      What Went Wrong - Every once in a while an audio only file would get uploaded, with no video whatsoever. Never able to reproduce it in-house, but it was pretty upsetting to our users when they didn’t record what they thought they did. There were also issues with accurate seeking on the final segments, almost like the TS segments were incorrectly time stamped.

    What I’m thinking now

    Apple was pushing fMP4 at WWDC this year (2016) and I hadn’t looked into it much at all before that. Since an fMP4 file can be read, and played while it’s being written, I thought that it would be possible for FFmpeg to transcode the file as it’s being written as well, as long as we hold off sending the bytes to FFmpeg until each fragment within the file is finished.

    However, I’m not familiar enough with the FFmpeg C API, I only used it briefly within attempt #2.

    What I need from you

    1. Is this a feasible solution ? Is anybody familiar enough with fMP4 to know if I can actually accomplish this ?
    2. How will I know that AVFoundation has finished writing a fragment within the file so that I can pipe it into FFmpeg ?
    3. How can I take data from a file on disk, chunk at a time, pass it into FFmpeg and have it spit out TS segments ?
  • avformat/aviobuf : fix flushing write buffers after seeking backward or forward

    3 juin 2017, par Marton Balint
    avformat/aviobuf : fix flushing write buffers after seeking backward or forward
    

    This patch makes aviobuf work more like traditinal file IO, which is how people
    think about it.

    For example, in the past, aviobuf only flushed buffers until the current buffer
    position, even if more data was written to it previously, and a backward seek
    was used to reposition the IO context.

    From now, aviobuf will keep track of the written data, so no explicit seek will
    be required till the end of the buffer, or till the end of file before flushing.

    This fixes at least one regression, fate-vsynth3-flv was broken if
    flush_packets option was set to false, an explicit seek was removed in
    4e3cc4bdd8acedbcc703607ed0efbb64bb5c3cc4.

    Also from now on, if a forward seek in the write buffer were to cause a gap
    between the already written data and the new file position, a flush will
    happen.

    The must_flush varable is also removed, which might have caused needless
    flushes with multiple seeks whithin the write buffer. Since we know the amount
    of data written to it, we will know when to flush.

    Signed-off-by : Marton Balint <cus@passwd.hu>

    • [DH] libavformat/avio.h
    • [DH] libavformat/aviobuf.c
    • [DH] libavformat/version.h
  • failed to run ffmpeg player on android

    14 juin 2014, par Hogun

    I get source from AndroidFFmpeg.
    and I succeeded to build FFmpegLibrary project and FFmpegExample.
    When I installed a app on G2 phone, ran the app well.
    but when I installed it on Galaxy S3, the app is killed by failed ffmpeg-neon.so load.

    I have environments blow,

    • Ubuntu 12.04 LTS 64bit
    • Android NDK r9d
    • Android Toolchain 4.6
    • FFmpeg 2.2
    06-14 16:22:05.181: D/dalvikvm(26430): Trying to load lib /data/app-lib/com.example.ffmpegbasic-1/libnativetester-jni.so 0x42dbfb58
    06-14 16:22:05.181: D/dalvikvm(26430): Added shared lib /data/app-lib/com.example.ffmpegbasic-1/libnativetester-jni.so 0x42dbfb58
    06-14 16:22:05.181: D/dalvikvm(26430): Trying to load lib /data/app-lib/com.example.ffmpegbasic-1/libffmpeg-neon.so 0x42dbfb58
    06-14 16:22:05.186: A/libc(26430): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 26430 (ple.ffmpegbasic)

    and i also try on android toolchain 4.8 but i see the same error.
    What do i try now ? Help me please...