Recherche avancée

Médias (1)

Mot : - Tags -/berlin

Autres articles (64)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

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

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (8517)

  • Revision fd44975bc8 : Make Rand8Extremes more extreme Previous code didn't do what was expected, we w

    19 avril 2013, par John Koleszar

    Changed Paths :
     Modify /test/acm_random.h



    Make Rand8Extremes more extreme

    Previous code didn't do what was expected, we want numbers within 16 of
    the extrema.

    Change-Id : I20c18627c482ec66e8405ddad74ca9276c0c65dc

  • ffmpeg : simple RTMP streaming over LAN

    30 mars 2013, par sajad

    I am trying to launch up a rtmp transcoder server using ffmpeg ; that receives udp MPEG-TS streams as input, transcodes it ; and generates an rtmp output to a URL, that can be accessed by users to receive and play the rtmp stream. All these are expected to be performed in a LAN and the output be accessed by all users.

    1) First I don't know where the URL should point to. Is it enought to specify the IP of the system and some optional port ? Is it neccessary that a program should be listening on that port ?

    2) How I can play the stream on the URL ?

    I use a linux ubuntu machine whith IP=10.1.1.229 and I want to transcode multicast stream on this URL : udp://@224.10.1.1:2001.

    here is the command used to transcode input stream and generate rtmp url "rtmp ://10.1.1.229:2020".

    ffmpeg -y -f mpegts -i "udp://@224.10.1.1:2001" -re -vcodec libx264 -maxrate 700k -r 25 -s 640x360 -deinterlace -acodec libfaac -ab 64k -ac 1 -ar 44100 -f flv "rtmp://10.1.1.229:2020"

    and here is the command by which I am trying to play rtmp stream :

    ffplay rtmp://10.1.1.229:2020

    Any guidance would be helpfull. Thank you.

  • Fix min/max validation. Closes gh-666. Fixes #648

    20 mars 2013, par ekonijn
    Fix min/max validation. Closes gh-666. Fixes #648

    In 1.10.0, min/max validation was supported for input type="text",
    
where min/max were interpreted as numbers.  This means min/max
    
for date would not work : min="2012-02-13" was interpreted as min="Not a Number".
    

    In 1.11.0, min/max were no longer converted to numbers.  This means
    
min/max for dates worked, but min/max for numbers failed :
    
"50" < "150" < "1000" does not hold.
    

    For an example, see http://jsbin.com/awokex/3
    

    This commit makes the behaviour of min/max dependent on input type :
    

     * input type=text (or not type attribute) has numeric min/max, as in 1.10.0
    
 * input type=date has working min/max for type date ;
    
   on mobile browsers you also get a date picker,
    
   plus the browser may reject invalid dates before
    
   javascript gets a chance to complain.
    
 * input type=number or range get numeric min/max,
    
   plus numeric keypad or slider on mobile browsers,
    
   plus browser may reject invalid input before javascript
    
   gets a chance to complain
    

    Allowing use of min/max with type=number/range/date is important
    
for mobile browsers, where the numeric keypad or date picker
    
make the input much easier to use than a generic text input field.
    
In this situation jquery-validate remains necessary to support
    
older browsers that do not do input validation based on type
    
and min/max.
    

    For situations where numeric input should be validated by jquery
    
without giving the browser a chance to validate the input format,
    
input type=text in combination with min/max can be used, as in 1.10.0.

Navigation