
Recherche avancée
Médias (3)
-
MediaSPIP Simple : futur thème graphique par défaut ?
26 septembre 2013, par
Mis à jour : Octobre 2013
Langue : français
Type : Video
-
GetID3 - Bloc informations de fichiers
9 avril 2013, par
Mis à jour : Mai 2013
Langue : français
Type : Image
-
GetID3 - Boutons supplémentaires
9 avril 2013, par
Mis à jour : Avril 2013
Langue : français
Type : Image
Autres articles (71)
-
Amélioration de la version de base
13 septembre 2013Jolie sélection multiple
Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...) -
Menus personnalisés
14 novembre 2010, parMediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
Menus créés à l’initialisation du site
Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...) -
Déploiements possibles
31 janvier 2010, parDeux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
Version mono serveur
La version mono serveur consiste à n’utiliser qu’une (...)
Sur d’autres sites (12384)
-
avfilter/avfilter : Add numbers of (in|out)pads directly to AVFilter
12 août 2021, par Andreas Rheinhardtavfilter/avfilter : Add numbers of (in|out)pads directly to AVFilter
Up until now, an AVFilter's lists of input and output AVFilterPads
were terminated by a sentinel and the only way to get the length
of these lists was by using avfilter_pad_count(). This has two
drawbacks : first, sizeof(AVFilterPad) is not negligible
(i.e. 64B on 64bit systems) ; second, getting the size involves
a function call instead of just reading the data.This commit therefore changes this. The sentinels are removed and new
private fields nb_inputs and nb_outputs are added to AVFilter that
contain the number of elements of the respective AVFilterPad array.Given that AVFilter.(in|out)puts are the only arrays of zero-terminated
AVFilterPads an API user has access to (AVFilterContext.(in|out)put_pads
are not zero-terminated and they already have a size field) the argument
to avfilter_pad_count() is always one of these lists, so it just has to
find the filter the list belongs to and read said number. This is slower
than before, but a replacement function that just reads the internal numbers
that users are expected to switch to will be added soon ; and furthermore,
avfilter_pad_count() is probably never called in hot loops anyway.This saves about 49KiB from the binary ; notice that these sentinels are
not in .bss despite being zeroed : they are in .data.rel.ro due to the
non-sentinels.Reviewed-by : Nicolas George <george@nsup.org>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>- [DH] libavfilter/aeval.c
- [DH] libavfilter/af_acontrast.c
- [DH] libavfilter/af_acopy.c
- [DH] libavfilter/af_acrossover.c
- [DH] libavfilter/af_acrusher.c
- [DH] libavfilter/af_adeclick.c
- [DH] libavfilter/af_adelay.c
- [DH] libavfilter/af_adenorm.c
- [DH] libavfilter/af_aderivative.c
- [DH] libavfilter/af_aecho.c
- [DH] libavfilter/af_aemphasis.c
- [DH] libavfilter/af_aexciter.c
- [DH] libavfilter/af_afade.c
- [DH] libavfilter/af_afftdn.c
- [DH] libavfilter/af_afftfilt.c
- [DH] libavfilter/af_aformat.c
- [DH] libavfilter/af_afreqshift.c
- [DH] libavfilter/af_afwtdn.c
- [DH] libavfilter/af_agate.c
- [DH] libavfilter/af_aiir.c
- [DH] libavfilter/af_alimiter.c
- [DH] libavfilter/af_amerge.c
- [DH] libavfilter/af_amix.c
- [DH] libavfilter/af_amultiply.c
- [DH] libavfilter/af_anequalizer.c
- [DH] libavfilter/af_anlmdn.c
- [DH] libavfilter/af_anlms.c
- [DH] libavfilter/af_anull.c
- [DH] libavfilter/af_apad.c
- [DH] libavfilter/af_aphaser.c
- [DH] libavfilter/af_apulsator.c
- [DH] libavfilter/af_aresample.c
- [DH] libavfilter/af_arnndn.c
- [DH] libavfilter/af_asetnsamples.c
- [DH] libavfilter/af_asetrate.c
- [DH] libavfilter/af_ashowinfo.c
- [DH] libavfilter/af_asoftclip.c
- [DH] libavfilter/af_asr.c
- [DH] libavfilter/af_astats.c
- [DH] libavfilter/af_asubboost.c
- [DH] libavfilter/af_asupercut.c
- [DH] libavfilter/af_atempo.c
- [DH] libavfilter/af_axcorrelate.c
- [DH] libavfilter/af_biquads.c
- [DH] libavfilter/af_bs2b.c
- [DH] libavfilter/af_channelmap.c
- [DH] libavfilter/af_channelsplit.c
- [DH] libavfilter/af_chorus.c
- [DH] libavfilter/af_compand.c
- [DH] libavfilter/af_compensationdelay.c
- [DH] libavfilter/af_crossfeed.c
- [DH] libavfilter/af_crystalizer.c
- [DH] libavfilter/af_dcshift.c
- [DH] libavfilter/af_deesser.c
- [DH] libavfilter/af_drmeter.c
- [DH] libavfilter/af_dynaudnorm.c
- [DH] libavfilter/af_earwax.c
- [DH] libavfilter/af_extrastereo.c
- [DH] libavfilter/af_firequalizer.c
- [DH] libavfilter/af_flanger.c
- [DH] libavfilter/af_haas.c
- [DH] libavfilter/af_hdcd.c
- [DH] libavfilter/af_headphone.c
- [DH] libavfilter/af_join.c
- [DH] libavfilter/af_ladspa.c
- [DH] libavfilter/af_loudnorm.c
- [DH] libavfilter/af_lv2.c
- [DH] libavfilter/af_mcompand.c
- [DH] libavfilter/af_pan.c
- [DH] libavfilter/af_replaygain.c
- [DH] libavfilter/af_rubberband.c
- [DH] libavfilter/af_sidechaincompress.c
- [DH] libavfilter/af_silencedetect.c
- [DH] libavfilter/af_silenceremove.c
- [DH] libavfilter/af_sofalizer.c
- [DH] libavfilter/af_speechnorm.c
- [DH] libavfilter/af_stereotools.c
- [DH] libavfilter/af_stereowiden.c
- [DH] libavfilter/af_superequalizer.c
- [DH] libavfilter/af_surround.c
- [DH] libavfilter/af_tremolo.c
- [DH] libavfilter/af_vibrato.c
- [DH] libavfilter/af_volume.c
- [DH] libavfilter/af_volumedetect.c
- [DH] libavfilter/asink_anullsink.c
- [DH] libavfilter/asrc_afirsrc.c
- [DH] libavfilter/asrc_anoisesrc.c
- [DH] libavfilter/asrc_anullsrc.c
- [DH] libavfilter/asrc_flite.c
- [DH] libavfilter/asrc_hilbert.c
- [DH] libavfilter/asrc_sinc.c
- [DH] libavfilter/asrc_sine.c
- [DH] libavfilter/avf_abitscope.c
- [DH] libavfilter/avf_ahistogram.c
- [DH] libavfilter/avf_aphasemeter.c
- [DH] libavfilter/avf_avectorscope.c
- [DH] libavfilter/avf_showcqt.c
- [DH] libavfilter/avf_showfreqs.c
- [DH] libavfilter/avf_showspatial.c
- [DH] libavfilter/avf_showspectrum.c
- [DH] libavfilter/avf_showvolume.c
- [DH] libavfilter/avf_showwaves.c
- [DH] libavfilter/avfilter.c
- [DH] libavfilter/avfilter.h
- [DH] libavfilter/buffersink.c
- [DH] libavfilter/buffersrc.c
- [DH] libavfilter/f_bench.c
- [DH] libavfilter/f_cue.c
- [DH] libavfilter/f_drawgraph.c
- [DH] libavfilter/f_ebur128.c
- [DH] libavfilter/f_graphmonitor.c
- [DH] libavfilter/f_interleave.c
- [DH] libavfilter/f_loop.c
- [DH] libavfilter/f_metadata.c
- [DH] libavfilter/f_perms.c
- [DH] libavfilter/f_realtime.c
- [DH] libavfilter/f_reverse.c
- [DH] libavfilter/f_segment.c
- [DH] libavfilter/f_select.c
- [DH] libavfilter/f_sendcmd.c
- [DH] libavfilter/f_sidedata.c
- [DH] libavfilter/f_zmq.c
- [DH] libavfilter/fifo.c
- [DH] libavfilter/internal.h
- [DH] libavfilter/setpts.c
- [DH] libavfilter/settb.c
- [DH] libavfilter/split.c
- [DH] libavfilter/trim.c
- [D
-
tests/dnn : Make DNN tests regular libavfilter tests
15 décembre 2021, par Andreas Rheinhardttests/dnn : Make DNN tests regular libavfilter tests
They test libavfilter internal API, so they should be libavfilter
test programs (which implies : linked statically to libavfilter
to access internal APIs and linked normally (statically or dynamically
depending upon the build configuration) against all the other libs).Right now, they are always linked statically against all libs,
which is a significant size waste compared to shared libs as all
of libavcodec has been pulled in despite not being really used.
This also leads to linking failures on systems for which av_export_avutil
is intended : libavcodec does not expect to be linked statically
against the library providing avpriv_(cga|vga16)_font in this case.
This is fixed by this commit.Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
- [DH] libavfilter/Makefile
- [DH] libavfilter/tests/.gitignore
- [DH] libavfilter/tests/dnn-layer-avgpool.c
- [DH] libavfilter/tests/dnn-layer-conv2d.c
- [DH] libavfilter/tests/dnn-layer-dense.c
- [DH] libavfilter/tests/dnn-layer-depth2space.c
- [DH] libavfilter/tests/dnn-layer-mathbinary.c
- [DH] libavfilter/tests/dnn-layer-mathunary.c
- [DH] libavfilter/tests/dnn-layer-maximum.c
- [DH] libavfilter/tests/dnn-layer-pad.c
- [DH] tests/Makefile
- [DH] tests/dnn/.gitignore
- [DH] tests/dnn/Makefile
- [DH] tests/dnn/dnn-layer-avgpool-test.c
- [DH] tests/dnn/dnn-layer-conv2d-test.c
- [DH] tests/dnn/dnn-layer-dense-test.c
- [DH] tests/dnn/dnn-layer-depth2space-test.c
- [DH] tests/dnn/dnn-layer-mathbinary-test.c
- [DH] tests/dnn/dnn-layer-mathunary-test.c
- [DH] tests/dnn/dnn-layer-maximum-test.c
- [DH] tests/dnn/dnn-layer-pad-test.c
- [DH] tests/fate/dnn.mak
-
Nginx Rtmp Module - How to check resolution when pushing rtmp stream to server before redirecting stream to another application ?
22 août 2022, par bui the vuongI have a problem when developing a livestream system with nginx-rtmp-module . I have consulted some systems, there is a function that when pushing the rtmp stream, the livestream systems can recognize the resolution of the stream -> from there it will encode to hls with the corresponding profiles. For example stream 720p produces hls file with 360p -> 720p , if stream 1080p will produce hls file with 360p -> 1080p . I have tried the ways but no success. So how can I check the resolution and redirect the rtmp stream to the appropriate application for encoding. Looking forward to everyone's advice.