Recherche avancée

Médias (91)

Autres articles (35)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

Sur d’autres sites (3178)

  • stream usb webcam via http using vlc without transcoding using mjpeg signal from webcam

    10 novembre 2020, par Peter Nußreiner

    I wanna stream my (Microsoft live) USB webcam using vlc from a raspberry.
While it works perfectely fine with transcoding my raspberry does not have enough power.

    


    So I checked the output formats of my webcam using :

    


    ffmpeg -f v4l2 -list_formats all -i /dev/video0


    


    wich gives me the following output :

    


    [video4linux2,v4l2 @ 0x559d5aee36c0] Raw       :     yuyv422 :           YUYV 4:2:2 : 640x480 1280x720 960x544 800x448 640x360 424x240 352x288 320x240 800x600 176x144 160x120 1280x800
[video4linux2,v4l2 @ 0x559d5aee36c0] Compressed:       mjpeg :          Motion-JPEG : 640x480 1280x720 960x544 800x448 640x360 800x600 416x240 352x288 176x144 320x240 160x120
/dev/video0: Immediate exit requested


    


    when running my streaming command :

    


    cvlc v4l2:///dev/video0:chroma=h264:width=1280:height=720 --sout '#standard{access=http,mux=ts,dst=192.168.178.27:8080,name=stream,mime=video/ts}' -vvv


    


    I get the following error :

    


    mux_ts mux warning: rejecting stream with unsupported codec YUY2
main mux error: cannot add this stream
main decoder error: cannot create packetizer output (YUY2)


    


    along with many other lines of information.
As far as I can interpret the error, vlc wants to use the YUY2 RAW signal of my webcam.
Is there any way I can force vlc to use the mjpg output of my camera ?

    


    I've already tried to use 'chroma=mjpg' without success.
Transcoding is not an alternative as my raspi has by far not enough power.

    


    I've also read about using ffmpeg for streaming, maybe someone has an alternative solution since I'm very new to the whole topic of websites and stuff

    


    It will (or should) be used as a live webcam for a windsurfing spot.
Therefore I need a fluent video with at least 10fps to judge the situation. A delay of a minute or so is no problem.
The basic idea was to stream the video to a webserver and embed the image in a website. I've got good internet connection at the spot.

    


    But for now I want to try it locally on my pc.

    


  • Merge pull request #3486 from cubiclesoft/master

    27 août 2017, par blueimp
    Merge pull request #3486 from cubiclesoft/master

    Allow maxChunkSize to be a function for dynamic chunk size support

  • Why do .bss/.rodata symbols stay in binary after strip ?

    15 novembre 2014, par BlahGeek

    As far as I know, there’s only one kind of symbols in executable binary that is really needed, which is dynamic symbols. These symbols is used in relocation operation because they are dynamic linked. Static linked functions/variables, in the other hand, is not needed so can be stripped.

    However, when I was examining the stripped ffmpeg binary, this is what I got :

    >nm -D ffmpeg
    
...
    
                 U __vfprintf_chk
    
                 U __vsnprintf_chk
    
                 U write
    
00000000018fa880 B x264_cabac_contexts
    
0000000001052a40 R x264_cabac_range_lps
    
0000000001052940 R x264_cabac_transition
    
0000000001970580 B x264_cabac_transition_unary
    
0000000001056820 R x264_last_coeff_flag_offset
    
0000000001056860 R x264_significant_coeff_flag_offset
    
0000000001056900 R x264_significant_coeff_flag_offset_8x8
    
                 U __xpg_strerror_r
    
                 U __xstat64
    
...

    I can verify that libx264 is static linked to ffmpeg :

    > ldd ffmpeg
    
linux-vdso.so.1 =>  (0x00007fff26d61000)
    
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f7c707e7000)
    
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7c704e1000)
    
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f7c702be000)
    
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007f7c700ae000)
    
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f7c6fe95000)
    
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7c6fc76000)
    
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7c6f8b0000)
    
/lib64/ld-linux-x86-64.so.2 (0x00007f7c70b0a000)
    
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f7c6f69a000)
    
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7c6f495000)

    So, I don’t understand why symbols like x264_cabac_contexts is not stripped. (It’s defined in libx264/.../cabac.c) :

    uint8_t x264_cabac_contexts[4][QP_MAX_SPEC+1][1024];

    It bothered me for several hours and I’ve found nothing on google... Hope someone would explain this... Thanks in advance !

Navigation