Recherche avancée

Médias (91)

Autres articles (106)

  • Soumettre bugs et patchs

    10 avril 2011

    Un logiciel n’est malheureusement jamais parfait...
    Si vous pensez avoir mis la main sur un bug, reportez le dans notre système de tickets en prenant bien soin de nous remonter certaines informations pertinentes : le type de navigateur et sa version exacte avec lequel vous avez l’anomalie ; une explication la plus précise possible du problème rencontré ; si possibles les étapes pour reproduire le problème ; un lien vers le site / la page en question ;
    Si vous pensez avoir résolu vous même le bug (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (9129)

  • Path to publish FFMPEG video files to Azure Blob Storage ?

    25 janvier 2016, par CG-Guy

    Please kindly help me get out of a bad situation with a very very unhappy client. I am using FFMPEG based app to publish video files to Azure Blob storage, but the files are not going through the network. FFMPEG app has full access to firewall ports. FFMPEG communication shell show files are published without errors. A look at TCP connections shows the app is making connection with Azure account remote address 104.208.XXX.XX and remote port 443. However, it drops the connection and starts repeating attempts over and over. It will then time out after countless attempts and crash the app. Here is my publish point. Is this the correct publish point for this kind of connection ? What is the proper connection string ? :

    https://account-name.blob.core.windows.net/video/video.flv /DestKey :account-storage-key

    I have also tried http:// without success. Same thing happens. It attempts connecting to remote address and port 80. Again, after several attempts it will timeout and crash. System is a Server 2008 R2 unit on-site, not VM. Your help is much appreciated. Thanks a lot !

  • 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

Navigation