
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (73)
-
Participer à sa documentation
10 avril 2011La documentation est un des travaux les plus importants et les plus contraignants lors de la réalisation d’un outil technique.
Tout apport extérieur à ce sujet est primordial : la critique de l’existant ; la participation à la rédaction d’articles orientés : utilisateur (administrateur de MediaSPIP ou simplement producteur de contenu) ; développeur ; la création de screencasts d’explication ; la traduction de la documentation dans une nouvelle langue ;
Pour ce faire, vous pouvez vous inscrire sur (...) -
Supporting all media types
13 avril 2011, parUnlike 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, parThe 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 (11178)
-
avcodec/vp3 : Move work after ff_thread_finish_setup
11 août 2022, par Andreas Rheinhardt -
configure : fix —disable-v4l2-m2m can't work
4 septembre 2019, par Jun Zhao -
bindProcessToNetwork does not work for live555's rtspclient
19 février 2020, par apanWhen my phone is connected to the WiFi camera, the Android system will recognise the WiFi network as an unavailable network, and then automatically switch to mobile data, so I use bindProcessToNetwork to bind the network to the WiFi connection. When I use ffmpeg’s rtsp module to connect to the WiFi camera, bindProcessToNetwork works well, but when I port live555 to the android platform, bindProcessToNetwork does not work when using rtspclient, it looks like rtspclient is still using mobile data connection instead of WiFi connection. How should I solve this problem ?