
Recherche avancée
Médias (91)
-
Spoon - Revenge !
15 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
My Morning Jacket - One Big Holiday
15 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
Zap Mama - Wadidyusay ?
15 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
David Byrne - My Fair Lady
15 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
Beastie Boys - Now Get Busy
15 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Audio
-
Granite de l’Aber Ildut
9 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
Autres articles (65)
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar 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 ;
-
Dépôt de média et thèmes par FTP
31 mai 2013, parL’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 (...) -
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 (5963)
-
The neutering of Google Code-In 2011
Posting this from the Google Summer of Code Mentor Summit, at a session about Google Code-In !
Google Code-In is the most innovative open-source program I’ve ever seen. It provided a way for students who had never done open source — or never even done programming — to get involved in open source work. It made it easy for people who weren’t sure of their ability, who didn’t know whether they could do open source, to get involved and realize that yes, they too could do amazing work — whether code useful to millions of people, documentation to make the code useful, translations to make it accessible, and more. Hundreds of students had a great experience, learned new things, and many stayed around in open source projects afterwards because they enjoyed it so much !
x264 benefitted greatly from Google Code-In. Most of the high bit depth assembly code was written through GCI — literally man-weeks of work by an professional developer, done by high-schoolers who had never written assembly before ! Furthermore, we got loads of bugs fixed in ffmpeg/libav, a regression test tool, and more. And best of all, we gained a new developer : Daniel Kang, who is now a student at MIT, an x264 and libav developer, and has gotten paid work applying the skills he learned in Google Code-In !
Some students in GCI complained about the system being “unfair”. Task difficulties were inconsistent and there were many ways to game the system to get lots of points. Some people complained about Daniel — he was completing a staggering number of tasks, so they must be too easy. Yet many of the other students considered these tasks too hard. I mean, I’m asking high school students to write hundreds of lines of complicated assembly code in one of the world’s most complicated instruction sets, and optimize it to meet extremely strict code-review standards ! Of course, there may have been valid complaints about other projects : I did hear from many students talking about gaming the system and finding the easiest, most “profitable” tasks. Though, with the payout capped at $500, the only prize for gaming the system is a high rank on the points list.
According to people at the session, in an effort to make GCI more “fair”, Google has decided to change the system. There are two big changes they’re making.
Firstly, Google is requiring projects to submit tasks on only two dates : the start, and the halfway point. But in Google Code-In, we certainly had no idea at the start what types of tasks would be the most popular — or new ideas that came up over time. Often students would come up with ideas for tasks, which we could then add ! A waterfall-style plan-everything-in-advance model does not work for real-world coding. The halfway point addition may solve this somewhat, but this is still going to dramatically reduce the number of ideas that can be proposed as tasks.
Secondly, Google is requiring projects to submit at least 5 tasks of each category just to apply. Quality assurance, translation, documentation, coding, outreach, training, user interface, and research. For large projects like Gnome, this is easy : they can certainly come up with 5 for each on such a large, general project. But often for a small, focused project, some of these are completely irrelevant. This rules out a huge number of smaller projects that just don’t have relevant work in all these categories. x264 may be saved here : as we work under the Videolan umbrella, we’ll likely be able to fudge enough tasks from Videolan to cover the gaps. But for hundreds of other organizations, they are going to be out of luck. It would make more sense to require, say, 5 out of 8 of the categories, to allow some flexibility, while still encouraging interesting non-coding tasks.
For example, what’s “user interface” for a software library with a stable API, say, a libc ? Can you make 5 tasks out of it that are actually useful ?
If x264 applied on its own, could you come up with 5 real, meaningful tasks in each category for it ? It might be possible, but it’d require a lot of stretching.
How many smaller or more-focused projects do you think are going to give up and not apply because of this ?
Is GCI supposed to be something for everyone, or just or Gnome, KDE, and other megaprojects ?
-
Playing and recording a live stream from another computer webcam using VLC/FFmpeg [closed]
22 octobre 2012, par user573014I was trying lately to set a video server on one machine and play it in a differen machine, it works with me.. but the problem is that it always stuck and become jammed in the middle .. and it is very slow comparing to the original stream.. something like 5 seconds delay which is not acceptable at all !
The warning messages I get usually includes something like that :
in the client side, which is the one which is jammed[0x24d1ab0] ts demux warning: discontinuity received 0x5 instead of 0xe (pid=68)
[0x7f4340015e50] rtp demux warning: 2 packet(s) lost
reference picture missing during reorder
Missing reference picture
mmco: unref short failure
Reference 4 >= 4 (H264 - MPEG-4 AVC (part 10)) stopped
error while decoding MB 34 14, bytestream (575)and that is the picture of the streaming when it is jammed
and that is what it looks like when it is running smoothly
This is the error message I got on the server
[0x2513820] main generic debug: auto hidding mouse
[0x2296230] main mux warning: late buffer for mux input (1840085)and Finally here is my command line that I am using >
on the server :vlc -vvv v4l2:///dev/video1:v4l2-width=640:v4l2-height=480 --sout
'#duplicate{dst=display,dst="transcode{vcodec=h264,vb=800,ab=128}
:duplicate{dst=rtp{mux=ts,dst=172.22.2.87,port=50004}'on the client :
vlc -vvv rtp://@:50004
I thought that it might be from VLC or from my command .. I tried different protocol for transmission, with no luck I also tried FFmpeg and I got similar results + warning messages .. I thought then that both of them are using the same libraries in Linux
here is the command using FFMpeg :
ffmpeg -f video4linux2 -i /dev/video1 -vcodec libx264 -s 320x240 -pix_fmt
yuv420p -vb 200000 -minrate 200000 -maxrate 200000 -bufsize 2000000 -acodec
libmp3lame -ab 128k -ar 44100 -ac 2 -f mpegts udp://172.22.2.87:5544In conclusion, I would like to find a solution for the latency of the streaming (which is very high) and the jamming problem
I appreciate anyone's input, thank you -
fate : Add a —target-samples path parameter
20 mai 2013, par Martin Storsjöfate : Add a —target-samples path parameter
This allows having the samples accessible via different paths
on the target and on the host.Signed-off-by : Martin Storsjö <martin@martin.st>
- [DBH] configure
- [DBH] tests/fate.sh
- [DBH] tests/fate/aac.mak
- [DBH] tests/fate/ac3.mak
- [DBH] tests/fate/adpcm.mak
- [DBH] tests/fate/alac.mak
- [DBH] tests/fate/als.mak
- [DBH] tests/fate/amrnb.mak
- [DBH] tests/fate/amrwb.mak
- [DBH] tests/fate/atrac.mak
- [DBH] tests/fate/audio.mak
- [DBH] tests/fate/bmp.mak
- [DBH] tests/fate/cdxl.mak
- [DBH] tests/fate/cover-art.mak
- [DBH] tests/fate/demux.mak
- [DBH] tests/fate/dfa.mak
- [DBH] tests/fate/dpcm.mak
- [DBH] tests/fate/ea.mak
- [DBH] tests/fate/filter-audio.mak
- [DBH] tests/fate/filter-video.mak
- [DBH] tests/fate/flac.mak
- [DBH] tests/fate/h264.mak
- [DBH] tests/fate/image.mak
- [DBH] tests/fate/indeo.mak
- [DBH] tests/fate/lossless-audio.mak
- [DBH] tests/fate/lossless-video.mak
- [DBH] tests/fate/microsoft.mak
- [DBH] tests/fate/monkeysaudio.mak
- [DBH] tests/fate/mp3.mak
- [DBH] tests/fate/mpc.mak
- [DBH] tests/fate/pcm.mak
- [DBH] tests/fate/probe.mak
- [DBH] tests/fate/prores.mak
- [DBH] tests/fate/qt.mak
- [DBH] tests/fate/qtrle.mak
- [DBH] tests/fate/real.mak
- [DBH] tests/fate/screen.mak
- [DBH] tests/fate/utvideo.mak
- [DBH] tests/fate/video.mak
- [DBH] tests/fate/voice.mak
- [DBH] tests/fate/vorbis.mak
- [DBH] tests/fate/vpx.mak
- [DBH] tests/fate/vqf.mak
- [DBH] tests/fate/wavpack.mak
- [DBH] tests/fate/wma.mak