Recherche avancée

Médias (91)

Autres articles (69)

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

  • Pas question de marché, de cloud etc...

    10 avril 2011

    Le vocabulaire utilisé sur ce site essaie d’éviter toute référence à la mode qui fleurit allègrement
    sur le web 2.0 et dans les entreprises qui en vivent.
    Vous êtes donc invité à bannir l’utilisation des termes "Brand", "Cloud", "Marché" etc...
    Notre motivation est avant tout de créer un outil simple, accessible à pour tout le monde, favorisant
    le partage de créations sur Internet et permettant aux auteurs de garder une autonomie optimale.
    Aucun "contrat Gold ou Premium" n’est donc prévu, aucun (...)

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

Sur d’autres sites (10758)

  • Revision 716ae78ce4 : Change initialization of static_scene_max_gf_interval. This removes an unnecess

    16 octobre 2014, par Paul Wilkins

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



    Change initialization of static_scene_max_gf_interval.

    This removes an unnecessary restriction that causes
    a problem (noticed by AWG) when the forced key frame
    interval is set to a very small value, such as 10. In this case
    we were being forced to code minimal length GF groups.

    Change-Id : I76ef5861a09638ff51f61fea02359554184ada53

  • FFMpeg : CFLAGS=-D__STDC_CONSTANT_MACROS ./configure where ?

    24 avril 2013, par olidev

    I got this problem " 'UINT64_C' was not declared in this scope" while using the ffmpeg library for Eclipse running under Ubuntu.

    After a while, I have found this solution : http://code.google.com/p/ffmpegsource/issues/detail?id=11

    But I could not know how to this :

    This should be fixed in our build system no matter what version of ffmpeg you're using. If you're still getting it, run configure like so :
    CFLAGS=-D__STDC_CONSTANT_MACROS ./configure
    and your problems should go away. This applies to other C++ programs using ffmpeg as well and not just to ffms2, but I can't guarantee that other programs won't break if you define that macro (they really shouldn't, though).

    Where can I run the configure ? from Terminal ? I tried with Terminal but it does not work.

    Anybody has an idea how to run the configure ?

    Thanks in advance and your help is much appreciate !

  • How to queue ffmpeg FIFO

    29 avril 2013, par Francois

    we build a service similar to youtube. Also converting runs fine with ffmpeg using this script from another post here :

    How do I set up an ffmpeg queue ?

    #!/bin/bash

    pipe=/tmp/ffmpeg

    trap "rm -f $pipe" EXIT

    # creating the FIFO    
    [[ -p $pipe ]] || mkfifo $pipe

    while true; do
    # can't just use "while read line" if we
    # want this script to continue running.
    read line < $pipe

    # now implementing a bit of security,
    # feel free to improve it.
    # we ensure that the command is a ffmpeg one.
    [[ $line =~ ^ffmpeg ]] && bash <<< "$line"
    done

    This works pretty good when i send one by one to the named pipe. When i send more than one at same time the second one queues the terminal to the point the first one finished. if a try more than 2 the third one will not be transcoded.

    So i tried to workaround with background sending to get the terminal free (just drop the echo command and close the ssh connection) but this doesn't work, then i played around with screen -X but also no luck. Maybe someone has a good idea to deal this.

    What i wanna do is : Every uploaded video which is needed to transcode will send a echo to the named pipe. FIFO should match but not blocking the terminal. So i think i need something to really queue ffmpeg input.

    kindest regards
    Francois