
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 (50)
-
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...) -
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (7133)
-
Connecting to RTSP stream via FFMpeg - 'could not find codec parameters for stream 0'
14 novembre 2013, par user2992545I'm a beginner in the FFMpeg world, so please excuse me my overall level of knowledge and any mistakes.
What I have here is a DVR, made by ITX Security. I have an SDK for it and currently I'm trying to connect to its RTSP using FFMPEG. I've been partially succesfull (i think), the best what I got was :
`(...)bin>ffplay -user-agent "ITX Security" rtsp://ADMIN:1234@192.168.2.130:5554/live/
[rtsp @ 02a242e0] UDP timeout, retrying with TCPB sq=0B f=0/0
[rtsp @ 02a242e0] method PAUSE failed: 501 Not Implemented
[rtsp @ 02a242e0] Could not find codec parameters for stream 0 (Video: h264):unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options
rtsp://ADMIN:1234@192.168.2.130:5554/live/: could not find codec parameters
nan: 0.000 fd=0 aq= 0KB vq= 0KB sq= 0B f=0/0`Is it really indicating that it has trouble in playing the stream (because it lacks a proper codec ?) - or am I just not getting the point ?
I've captured traffic between my computer and the DVR in question, and something is happening (at least that's what Wireshark says).
https://www.dropbox.com/s/j65lige244kg8jt/rtsp_ffmpeg.pcap
What am I doing wrong ?
Regards.
-
How to add a dependency for a package ?
25 septembre 2021, par Meh.I just built and installed FFmpeg (
./configure --disable-asm
).

And I need to use libavformat in my C++ project.

I use
FindFFmpeg.cmake
, and when I build, I get a bunch of undefined symbol errors so I have to find libraries :

find_package(FFmpeg COMPONENTS avcodec avformat avutil swresample swscale)
 find_library(COREMEDIA_LIBRARY CoreMedia)
 find_library(VIDEOTOOLBOX_LIBRARY VideoToolbox)
 find_library(COREVIDEO_LIBRARY CoreVideo)
 find_library(AUDIOTOOLBOX_LIBRARY AudioToolbox)
 find_library(SECURITY_LIBRARY Security)

## In another file:

 target_link_libraries(videocommon PRIVATE
 FFmpeg::avcodec
 FFmpeg::avformat
 FFmpeg::avutil
 FFmpeg::swscale
 FFmpeg::swresample
 ${COREMEDIA_LIBRARY}
 ${VIDEOTOOLBOX_LIBRARY}
 ${COREVIDEO_LIBRARY}
 ${AUDIOTOOLBOX_LIBRARY}
 ${SECURITY_LIBRARY}
 )




However, I still get errors from
libavformat.a(tls_securetransport.o)
:

"_SSLRead", referenced from:
 _tls_read in libavformat.a(tls_securetransport.o)
 "_SSLCreateContext", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLSetCertificate", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLSetIOFuncs", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLSetSessionOption", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLSetPeerDomainName", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SecIdentityCreate", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SecTrustEvaluate", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SecTrustSetAnchorCertificates", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLClose", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 _tls_close in libavformat.a(tls_securetransport.o)
 "_SSLHandshake", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLSetConnection", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)
 "_SSLCopyPeerTrust", referenced from:
 _tls_open in libavformat.a(tls_securetransport.o)



This is the
#include
part from the file in questiontls_securetransport.c
:

#include 

#include "avformat.h"
#include "avio_internal.h"
#include "internal.h"
#include "network.h"
#include "os_support.h"
#include "url.h"
#include "tls.h"
#include "libavcodec/internal.h"
#include "libavutil/avstring.h"
#include "libavutil/opt.h"
#include "libavutil/parseutils.h"

#include <security></security>Security.h>
#include <security></security>SecureTransport.h>
#include <corefoundation></corefoundation>CoreFoundation.h>



Why is this happening ?


I also get the same result if I were to build with OpenSSL or LibreSSL. What is causing the problem ? My project or incorrectly building FFmpeg ?


If I were to use LibreSSL :


#cmakelists.txt:
find_package(LibreSSL)

#linker
 target_link_libraries(videocommon PRIVATE
 FFmpeg::avcodec
 FFmpeg::avformat
 FFmpeg::avutil
 FFmpeg::swscale
 FFmpeg::swresample
 ${LIBRESSL_LIBRARIES} 
 ${COREMEDIA_LIBRARY}
 ${VIDEOTOOLBOX_LIBRARY}
 ${COREVIDEO_LIBRARY}
 ${AUDIOTOOLBOX_LIBRARY}
 )

#full error
Undefined symbols for architecture x86_64:
 "_tls_config_error", referenced from:
 _ff_tls_open in libavformat.a(tls_libtls.o)
 "_tls_config_insecure_noverifytime", referenced from:
 _ff_tls_open in libavformat.a(tls_libtls.o)
 "_tls_accept_cbs", referenced from:
 _ff_tls_open in libavformat.a(tls_libtls.o)
 "_tls_connect_cbs", referenced from:
 _ff_tls_open in libavformat.a(tls_libtls.o)



-
Evolution #4256 : Faire un signalement des mise à jour de sécu
11 janvier 2019Si on pouvait éviter de coder un truc spécifique encore, ça serait bien :)
Mais sinon, composer.json n’a aucun numéro de version pour le paquet lui-même (à part pour la déclaration des dépendances). C’est le gestionnaire de version qui les gère (les tags en Git par exemple). https://github.com/drush-ops/drush/issues/2947 indique chez Drush https://github.com/drush-ops/drush/pull/3087 qui se base sur un fichier .json de déclaration (pour vérifier des paquets composer). En l’occurrence https://raw.githubusercontent.com/drupal-composer/drupal-security-advisories/8.x/composer.json