
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (104)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...)
Sur d’autres sites (7044)
-
compile own ffmpeg filter
20 juin 2023, par lfkI'm trying compile my own ffmpeg filter using official tutorial. My filter uses C++ code. I made header file and adapted my C++ function definition for C. Now I'm trying compile with command
make -j<libavfilter> ffmpeg</libavfilter>
, but receiving an error message



gcc -Llibavcodec -Llibavdevice -Llibavfilter -Llibavformat
-Llibavresample -Llibavutil -Llibpostproc -Llibswscale -Llibswresample -Wl,—as-needed -Wl,-z,noexecstack -Wl,—warn-common -Wl,-rpath-link=libpostproc:libswresample:libswscale:libavfilter:libavdevice:libavformat:libavcodec:libavutil:libavresample
-o ffmpeg_g fftools/ffmpeg_opt.o fftools/ffmpeg_filter.o fftools/ffmpeg_hw.o fftools/cmdutils.o fftools/ffmpeg.o -lavdevice
-lavfilter -lavformat -lavcodec -lswresample -lswscale -lavutil -lm -pthread -lm -lm -lz -pthread -lm -lz -lm -lm -pthread -lm libavfilter/libavfilter.a(vf_foobar.o) : In function `filter_frame' :
/home/joeyes/ffmpeg_sources/ffmpeg/libavfilter/vf_foobar.c:302 :
undefined reference to MyFunction.c
collect2 : ld returned 1 exit status
*** [ffmpeg_g] Error 1




For compilation I added
OBJS-$(CONFIG_FOOBAR_FILTER) += vf_foobar.o MyCode.o
to /libavfilter/makefile

Also I put MyCode.h & MyCode.cpp to /libavfilter folder


-
On ALAC’s Open Sourcing
1er novembre 2011, par Multimedia Mike — Codec TechnologyApple open sourced their lossless audio codec last week. Pretty awesome ! I have a theory that, given enough time, absolutely every codec will be open source in one way or another.
I know I shouldn’t bother reading internet conversation around any news related to multimedia technology. And if I do read it, I shouldn’t waste any effort getting annoyed about them. But here are some general corrections :
- ALAC is not in the same league as — nor is it a suitable replacement for — MP3/AAC/Vorbis or any other commonly used perceptual audio codec. It’s not a matter of better or worse ; they’re just different families of codecs designed for different purposes.
- Apple open sourced ALAC, not AAC– easy mistake, though there’s nothing to ‘open source’ about AAC (though people can, and will, argue about its absolute ‘open-ness’).
- There’s not much technical room to argue between ALAC and FLAC, the leading open source lossless audio compressor. Both perform similarly in terms of codec speeds (screamingly fast) and compression efficiency (results vary slightly depending on source material).
- Perhaps the most frustrating facet is the blithe ignorance about ALAC’s current open source status. While this event simply added an official “open source” status to the codec, ALAC has effectively been open source for a very long time. According to my notes, the ALAC decoding algorithm was reverse engineered in 2005 and added into FFmpeg in March of the same year. Then in 2008, Google — through their Summer of Code program — sponsored an open source ALAC encoder.
From the multimedia-savvy who are versed in these concepts, the conversation revolves around which would win in a fight, ALAC or FLAC ? And who between Apple and FFmpeg/Libav has a faster ALAC decoder ? The faster and more efficient ALAC encoder ? I contend that these issues don’t really matter. If you have any experience working with lossless audio encoders, you know that they tend to be ridiculously fast to both encode and decode and that many different lossless codecs compress at roughly the same ratios.
As for which encoder is the fastest : use whatever encoder is handiest and most familiar, either iTunes or FFmpeg/Libav.
As for whether to use FLAC or ALAC — if you’ve already been using one or the other for years, keep on using it. Support isn’t going to vanish. If you’re deciding which to use for a new project, again, perhaps choose based on software you’re already familiar with. Also, consider hardware support– ALAC enjoys iPod support, FLAC is probably better supported in a variety of non-iPod devices, though that may change going forward due to this open sourcing event.
For my part, I’m just ecstatic that the question of moral superiority based on open source status has been removed from the equation.
Code-wise, I’m interested in studying the official ALAC code to see if it has any corner-case modes that the existing open source decoders don’t yet account for. The source makes mention of multichannel (i.e., greater than stereo) configurations, but I don’t know if that’s in FFmpeg/Libav.
-
Error while saving a matplotlib animation, missing 'dpi' argument
27 septembre 2020, par aarcasI'm trying to save an animation of matplotlib.animation.AnimationFunc and I get an error saying 'dpi' argument missing. Obviously, I have the dpi set so I don't understand where this error comes from.



I'm running python 3.6 and matplotlib 3.0.3, I also just installed ffmpeg from ubuntu official repositories (Ubuntu 18.04).



This is the part of my code that should affect that, although I think it should be something of the system :



Writer = writers['ffmpeg']
writer = Writer(fps=15, metadata=dict(artist='Me'), bitrate=1800,)
ani = FuncAnimation(fig, anime, interval=time_step *
 10**3, frames=F, repeat=False,) 
ani.save('standard_map.mp4', writer=Writer, dpi=100)




The errors is :



with writer.saving(self._fig, filename, dpi):
File "/usr/lib/python3.6/contextlib.py", line 159, in helper
 return _GeneratorContextManager(func, args, kwds)
File "/usr/lib/python3.6/contextlib.py", line 60, in __init__
 self.gen = func(*args, **kwds) TypeError: saving() missing 1 required positional argument: 'dpi'




I tried both adding the lines they suggested there and the error stills the same.



plt.rcParams['animation.ffmpeg_path'] = '/usr/bin/ffmpeg'




I also tried changing the writer to 'imagemagick' the one set on Ubuntu by default and the error persists.