
Recherche avancée
Autres articles (51)
-
Organiser par catégorie
17 mai 2013, parDans MédiaSPIP, une rubrique a 2 noms : catégorie et rubrique.
Les différents documents stockés dans MédiaSPIP peuvent être rangés dans différentes catégories. On peut créer une catégorie en cliquant sur "publier une catégorie" dans le menu publier en haut à droite ( après authentification ). Une catégorie peut être rangée dans une autre catégorie aussi ce qui fait qu’on peut construire une arborescence de catégories.
Lors de la publication prochaine d’un document, la nouvelle catégorie créée sera proposée (...) -
Encoding and processing into web-friendly formats
13 avril 2011, parMediaSPIP automatically converts uploaded files to internet-compatible formats.
Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
All uploaded files are stored online in their original format, so you can (...) -
MediaSPIP Core : La Configuration
9 novembre 2010, parMediaSPIP Core fournit par défaut trois pages différentes de configuration (ces pages utilisent le plugin de configuration CFG pour fonctionner) : une page spécifique à la configuration générale du squelettes ; une page spécifique à la configuration de la page d’accueil du site ; une page spécifique à la configuration des secteurs ;
Il fournit également une page supplémentaire qui n’apparait que lorsque certains plugins sont activés permettant de contrôler l’affichage et les fonctionnalités spécifiques (...)
Sur d’autres sites (7361)
-
Looking for a free alternative RTSP server for Node.js [closed]
2 juin 2020, par MaorationI'm looking at running my node.js server as an RTSP streaming server, as well as an http server. the ability to get some ffmpeg video output to stream as rtsp to 'localhost' (which will be the server listening), and for multiple clients to request a stream from the server via the rtsp ://... protocol



The most common online implementation is :
https://www.npmjs.com/package/rtsp-streaming-server



However, this is licensed under GPL-3.0, meaning my product would have to be open-source, or I'll be violating the terms of use. I'm afraid thats not possible..



Other common results when searching for a solution are :



https://www.npmjs.com/package/rtsp-server
which just seems to wrap to lower level rtsp protocol messages.



https://www.npmjs.com/package/node-media-server
which provides solutions to many use cases, but I couldnt figure out how to configure it as an RTSP server, or if this would even be possible.



So, any alternatives ? other suggestions ?


-
ffmpeg timeout with rtsp
17 janvier 2024, par eSlavkoI have script that capture image from wifi camera with ffmpeg.
It works fine until camera is not reachable due to network troubles.
The script stuck in ffmpeg capture and never exit. Is it possible to have some kind of timeout ? -stimeout (in miliseconds) seems not working.


There is part of script that capture images. (there are some manipulation after that)


#!/bin/bash
week="$(date '+%Y_%U')"
ts="$(date '+%Y-%m-%d_%H:%M:%S')"
ffmpeg -rtsp_transport tcp -y -i "rtsp://192.168.64.101" -frames:v 1 $week/$ts.jpg -stimeout 3000 -y



I did test on other camera and results are :


ffmpeg -y -i "rtsp://192.168.64.112:8554/profile0" -frames:v 1 Ilatest.jpg



Does work OK, but with timeout of 5 seconds as


ffmpeg -timeout 5000000 -y -i "rtsp://192.168.64.112:8554/profile0" -frames:v 1 Ilatest.jpg



doesn't and I got error report as :


ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
...
...
[rtsp @ 0x55d250488740] Unable to open RTSP for listening
rtsp://192.168.64.112:8554/profile0: Cannot assign requested address



-
How to listen to 2 rtsp streams at the same time with FFMpeg
19 mai 2017, par Alexander UshakovI can listen and receive one rtsp stream with FFMpeg library using this code :
AVFormatContext* format_context = NULL
char* url = "rtsp://example.com/in/1";
AVDictionary *options = NULL;
av_dict_set(&options, "rtsp_flags", "listen", 0);
av_dict_set(&options, "rtsp_transport", "tcp", 0);
int status = avformat_open_input(&format_context, url, NULL, &options);
av_dict_free(&options);
if( status >= 0 )
{
status = avformat_find_stream_info( format_context, NULL);
if( status >= 0 )
{
AVPacket av_packet;
av_init_packet(&av_packet);
for(;;)
{
status = av_read_frame( format_context, &av_packet );
if( status < 0 )
{
break;
}
}
}
avformat_close_input(&format_context);
}But if I try to open another similar listener (in another thread with another url) at the same time, I get error :
Unable to open RTSP for listening
rtsp ://example.com/in/2 : Address already in useIt looks like
avformat_open_input
tries to open socket which is already opened by previous call ofavformat_open_input
. Is there any way to share this socket between 2 threads ? May be there is some dispatcher in FFMpeg for such task.