Recherche avancée

Médias (91)

Autres articles (111)

  • Menus personnalisés

    14 novembre 2010, par

    MediaSPIP 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 ; (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (12175)

  • avformat/avisynth : remove atexit() handler

    7 juillet 2024, par Stephen Hutchinson
    avformat/avisynth : remove atexit() handler

    The atexit() handler in the avisynth demuxer was added because
    
there was a conflict in AvxSynth that arose due to their use
    
of C++ global objects, particularly in relation to having
    
added a logging function relying on log4cpp.
    

    This conflict was responsible for causing a segfault on exit.
    
It did not affect Windows with the (at the time) upstream
    
AviSynth 2.5 and 2.6, nor does it affect AviSynth+.
    

    Unfortunately, none of this was actually shielded by ifdefs
    
indicating the fact it was only needed for AvxSynth, so four
    
years ago when AviSynth+ replaced AvxSynth as the handler
    
for AviSynth scripts on Unix-like OSes, the fact that the
    
atexit handler was no longer necessary was overlooked.
    

    Signed-off-by : Stephen Hutchinson <qyot27@gmail.com>
    • [DH] libavformat/avisynth.c

  • configure : drop yasm support

    3 octobre 2024, par Lynne
    configure : drop yasm support

    We started defauling to nasm 8 years ago.
    
We are still compatible with yasm 0.8.0, released in 2009. **15 years ago**.
    
The time has more than come to remove support for it.
    

    Maintaining compatibility started cutting into writing new code long ago.
    
We still can't have 2-argument instructions, preprocessor booleans, and all
    
AVX2 code must still be wrapped in ifdefs. Newly added code often breaks this.
    • [DH] Changelog
    • [DH] configure
    • [DH] doc/developer.texi
    • [DH] doc/optimization.txt
    • [DH] doc/platform.texi

  • What would be the simplest way to convert an IP Camera's RTSP feed to WebRTC, to be viewed on a webpage ? [closed]

    27 septembre 2024, par Sam Lomas

    I am aware that there are many questions similar to this on SO, but many of them do not fully answer the question, are outdated by 8+ years or are incredibly convoluted.

    &#xA;

    I am in possession of two IP cameras, which both serve an RTSP stream. I'd like to view the live feeds of both cameras on demand, so I am hosting a small-scale webserver from a raspberry pi 4. In the past, I tried using ffmpeg to convert the RTSP streams into HLS, but the latency of standard HLS was anywhere from 10 to 20 seconds. WebRTC is what came to mind, so I looked into some media servers to help me serve the RTSP stream in a WebRTC wrapper, and many of them are very poorly documented and require a very in-depth knowledge of WebRTC to function at all.

    &#xA;

    So my question is, what would the easiest method be for me to put these IP camera feeds on my webpage, with as little effort required and with the lowest latency possible ?

    &#xA;

Navigation