Recherche avancée

Médias (0)

Mot : - Tags -/auteurs

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

Autres articles (42)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

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

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

Sur d’autres sites (8815)

  • Speed Up Creation of M3U8 - FFMPEG

    6 septembre 2017, par Kenny Johnson

    we are using ffmpeg to take rtsp video and create an m3u8 so we can stream the video to phones and computers via HLS using Clappr player.

    It works but it takes about 15 seconds for the m3u8 to be created.

    We have tried everything we can think of to speed it up. Just trying to get the video to start quicker.

    Right now it takes about 15 seconds for the video to start. We need to cut it in half.

    Our keyframe and chunk size are both set to 3 right now.

    Anyone have any suggestions ?
    Thanks for your time !

  • Revision 9f427bfe98 : Best_rd breakout in rd partition search. About 15% faster for bus (speed 0) fir

    17 juillet 2013, par Ronald S. Bultje

    Changed Paths :
     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_rdopt.c


     Modify /vp9/encoder/vp9_rdopt.h



    Best_rd breakout in rd partition search.

    About 15% faster for bus (speed 0) first 50 frames @ 1500kbps, which
    goes from 1min36 to 1min24. Results become slightly better (+0.2% on
    derf/yt, +0.4% on hd), probably because of a bugfix for skipmode in
    super_block_yrd(). Overall speed change (on derfraw300) is roughly
    - 13%. This can probably be improved further by caching best_yrd
    between partition searches. Also, we might be able to get more
    speedups by always doing PARTITION_NONE before PARTITIONS_SPLIT, not
    just at the sb8x8 level.

    Change-Id : I83736949ebd5b4a3b400ee688d7661913fefc98b

  • Revision fe5e2a91bb : Auto min and max partition size experiment. Speed feature experiment to set an

    24 juillet 2013, par Paul Wilkins

    Changed Paths :
     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h



    Auto min and max partition size experiment.

    Speed feature experiment to set an upper and lower
    partition size limit based on what has been seen
    in spatial neighbors.

    This seems to gives quite reasonable speed gains in local
    (10-15%) and when used with speed 0 the losses are small
    (0.25% derf, 0.35% stdhd). However, for now I am only
    enabling it on speed 1 as there may be clashes with the existing
    temporal partition selection in speed 2.

    Using a tighter min / max around the range derived from the
    neighbors increases speed further but at the cost of a
    bigger quality loss. However, I think this spatial method could
    be combined with data from either the last frame or a variance
    method (or both) to refine the range of minimum and maximum
    partition size. I.e. consider the min and max from spatial and
    temporal neighbors and the variance recommendation.

    Change-Id : I1b96bf8b84368d6aad0c7aa600fe141b4f07435f

Navigation