Recherche avancée

Médias (1)

Mot : - Tags -/musée

Autres articles (96)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

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

  • Participer à sa documentation

    10 avril 2011

    La documentation est un des travaux les plus importants et les plus contraignants lors de la réalisation d’un outil technique.
    Tout apport extérieur à ce sujet est primordial : la critique de l’existant ; la participation à la rédaction d’articles orientés : utilisateur (administrateur de MediaSPIP ou simplement producteur de contenu) ; développeur ; la création de screencasts d’explication ; la traduction de la documentation dans une nouvelle langue ;
    Pour ce faire, vous pouvez vous inscrire sur (...)

  • Que fait exactement ce script ?

    18 janvier 2011, par

    Ce script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
    Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
    Installation de dépendances de MediaSPIP
    Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
    Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...)

Sur d’autres sites (8428)

  • Support broadcast destination for udp protocol

    9 avril 2014, par Olivier Langlois
    Support broadcast destination for udp protocol
    

    Use the required socket option SO_BROADCAST to be able to stream to a broadcast
    address.

    Prior to the patch, trying to stream to a broadcast address was resulting to the
    following error :

    av_interleaved_write_frame() : Permission denied

    The patch has been tested with :

    ffmpeg -f v4l2 -framerate 30 -input_format yuyv422 -video_size 640x480 -i /dev/video0 \
    -c:v libx264 -profile:v high -preset ultrafast -tune zerolatency -b:v 500k -pix_fmt yuv420p \
    -f mpegts udp ://192.168.1.255:5004 ?broadcast=1

    I have added an option to let the user explicitly request broadcast in order to avoid
    ffmpeg to broadcast unintentionally.

    Signed-off-by : Olivier Langlois <olivier@trillion01.com>
    Signed-off-by : Michael Niedermayer <michaelni@gmx.at>

    • [DH] libavformat/udp.c
  • FFMPEG streaming chunk error over RTSP

    5 février 2015, par blackibiza

    I’m using an IP Camera connected over Gigabit-Ethernet which can stream the live image over RTSP.
    I’ve tried many combinations of ffmpeg and ffplay without success.

    So far, if I run vlc and open the rtsp :// address, the image comes up, but in the terminal I can read a lot of messages like :

    [mjpeg @ 0x7f70ac034d80] Found EOI before any SOF, ignoring
    [mjpeg @ 0x7f70ac034d80] No JPEG data found in image

    while, if I use ffplay or ffmpeg, I get no images but a lot of these messages :

    Last message repeated 33 times
    [rtsp @ 0x7f5c68f285a0] Reserved q value 100
    [rtsp @ 0x7f5c68f285a0] Received packet without a start chunk; dropping frame.

    The IP camera supports only UDP streaming, if I try to force the TCP streaming, It doesn’t start at all, saying :

    [rtsp @ 0x7f019a5de720] Nonmatching transport in server reply
    Invalid data found when processing input

    I’ve used also wireshark to dump the packets and see the differences between VLC and FFMPEG tools, but they are identical, so I don’t understand why VLC can still retrieve the jpeg data from this RTSP stream.

    I’m using the latest ffmpeg package available on ArchLinux.
    What could be the problem and how could I access the mjpeg image sent over the RTSP ?
    Due this FFMPEG problem, the cv::VideoCapture function of OpenCV is returning the same error of ffplay and ffmpeg tools.

    Thanks in advance

    Update :

    using the following command :

    cvlc -vvv rtsp://172.23.23.124 --noaudio --sout '#standard{access=http,mux=mpjpeg,dst=127.0.0.1:8080}'

    I’m now able to play even with ffplay the stream, but only if I use the -f mjpeg option.
    How can I force now OpenCV to access the same http address, which works with ffplay, and get the MJPEG image ? Opening VideoCapture with the address only isn’t working.

  • Revision a16794dd31 : Revert "Remove Wextra warnings from vp9_sad.c" This reverts commit 7ab9a9587b96

    15 mai 2014, par Jim Bankoski

    Changed Paths :
     Modify /test/sad_test.cc


     Modify /vp8/common/rtcd_defs.pl


     Modify /vp8/common/sad_c.c


     Modify /vp8/common/variance.h


     Modify /vp8/encoder/mcomp.c


     Modify /vp8/encoder/rdopt.c


     Modify /vp9/common/vp9_rtcd_defs.pl


     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_mbgraph.c


     Modify /vp9/encoder/vp9_mcomp.c


     Modify /vp9/encoder/vp9_rdopt.c


     Modify /vp9/encoder/vp9_sad.c


     Modify /vp9/encoder/vp9_variance.h



    Revert "Remove Wextra warnings from vp9_sad.c"

    This reverts commit 7ab9a9587b96db4edce6be916c1f02297a9555ff

    Nightly test http://build.webmproject.org/jenkins/view/libvpx-nightly-
    tests/job/libvpx%20unit%20tests%20(valgrind-2)/arch=x86_64-linux-
    gcc,filter=-*VP8* :*Large.*/276/console

    Failed

    This patch did not address all the assembly issues
    some of the vp8 assembly counts on 5 arguments being passed in to this function :

    one example : vp8_sad8x16_wmt

    Please address or split this into vp9 and vp8 patches.

    Change-Id : I78afcc171649894f887bb8ee3c66de24aaddc7ca