Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (38)

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

  • Menus personnalisés

    14 novembre 2010, par

    MediaSPIP utilise le plugin Menus pour gérer plusieurs menus configurables pour la navigation.
    Cela permet de laisser aux administrateurs de canaux la possibilité de configurer finement ces menus.
    Menus créés à l’initialisation du site
    Par défaut trois menus sont créés automatiquement à l’initialisation du site : Le menu principal ; Identifiant : barrenav ; Ce menu s’insère en général en haut de la page après le bloc d’entête, son identifiant le rend compatible avec les squelettes basés sur Zpip ; (...)

  • Emballe médias : à quoi cela sert ?

    4 février 2011, par

    Ce plugin vise à gérer des sites de mise en ligne de documents de tous types.
    Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ;

Sur d’autres sites (5783)

  • Nginx Live transcoding with ffmpeg

    9 juillet 2017, par Stian Tofte

    I’m live streaming video to my server(It’s external somewhere in the world).
    And what I’m trying to do here, is that my server will transcode the input to a lower bitrate before it pushes it to the video site like twitch and so on.

    And I’m doing this on windows. I have tried to google around watched youtube videos. and so on.. But couldn’t find any solution for it. So here is what I have at this moment(not working).

    In my nginx.conf :

    rtmp {
    server {
       listen 1935;
       chunk_size 8192;

       application code {
           live on;

       }

       application twitch {
           push rtmp://live-ams.twitch.tv/app/live_xxxxxxxxxxxxxxxxx;
       }
    }

    So here the application code is receving the stream from my computer at home. I’m using ffmpeg to transcode it.

    And here is my batch file(That I have to start manualy. Can’t start it within the config of nginx on windows.)

    ffmpeg -i rtmp://localhost/code -vcodec flv -acodec copy -s 1280x720 -f flv rtmp://localhost/twitch
    pause

    Right now It’s just downscaling but that is okay. So this is supposed to send the stream back to the "twitch" application in my nginx config. And then nginx will stream it to twitch.

    But when I launch my ffmpeg bat file.. I get this :
    enter image description here

    So it’s here my road ends. Anyone knows how to do this ?

    Thanks in advance :) Stian

  • Recording usb cam on raspberry pi with ffmpeg - usb troubleshooting

    18 septembre 2017, par Hwy2Hell

    I want to save video from an external usb cam on the raspberry pi 3. In order to avoid voltage drop issues, I use the offical raspberry power supply (2.5 Amp) and connected all usb devices by a separetely powered usb hub :

    pi@raspi:~/appdev/ffmpeg $ lsusb
    Bus 001 Device 037: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
    Bus 001 Device 036: ID 046d:c03f Logitech, Inc. M-BT85 [UltraX Optical Mouse]
    Bus 001 Device 035: ID 04d9:1503 Holtek Semiconductor, Inc. Shortboard Lefty
    Bus 001 Device 012: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    When I try to test the functionality by running the following bash script (snippet) :

    function capture
    {
       capfile=$(date +%F_%Hh%Mm%Ss)
       echo saving to $wdir/$capfile.mp4
       echo $PATH
       ffmpeg -video_size 320x240 -i /dev/video0 \
       -vf drawtext="fontsize=18:x=10:y=220:fontcolor=red:\
       fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf:\
       text=%{localtime}" -t 10 $wdir/$capfile.mp4
       # change -t to 3600 = 1h
    }

    for i in $(seq 1 10)
    do
       echo
       echo Pass $i ...
       capture
    done

    After a few loop-runs I always see device errors :

    Pass 5 ...
    saving to /home/pi/appdev/ffmpeg/2017-09-16_13h31m00s.mp4
    /usr/local/bin:/usr/bin/ffmpeg:/usr/bin:/bin:/sbin
    ffmpeg version 3.3.3 Copyright (c) 2000-2017 the FFmpeg developers
     built with gcc 4.9.2 (Raspbian 4.9.2-10)
     configuration: --arch=armhf --target-os=linux --enable-gpl --enable-libfreetype --enable-mmal --enable-nonfree --enable-omx --enable-omx-rpi
     libavutil      55. 58.100 / 55. 58.100
     libavcodec     57. 89.100 / 57. 89.100
     libavformat    57. 71.100 / 57. 71.100
     libavdevice    57.  6.100 / 57.  6.100
     libavfilter     6. 82.100 /  6. 82.100
     libswscale      4.  6.100 /  4.  6.100
     libswresample   2.  7.100 /  2.  7.100
     libpostproc    54.  5.100 / 54.  5.100
    /dev/video0: Input/output error

    The kernel message log shows that the usb cam has been resetted :

    pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
    [ 4497.358195] usb 1-1.2.4: new high-speed USB device number 37 using dwc_otg
    [ 4497.573440] usb 1-1.2.4: New USB device found, idVendor=046d, idProduct=09a1
    [ 4497.573466] usb 1-1.2.4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
    [ 4497.573481] usb 1-1.2.4: SerialNumber: A032D310
    [ 4497.605698] input: UVC Camera (046d:09a1) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.0/input/input15
    [ 4497.625582] usb 1-1.2.4: Warning! Unlikely big volume range (=3072), cval->res is probably wrong.
    [ 4497.625606] usb 1-1.2.4: [5] FU [Mic Capture Volume] ch = 1, val = 4608/7680/1
    [ 5268.123764] usb 1-1.2.4: reset high-speed USB device number 37 using dwc_otg

    Next time I start the script, the usb cam gets disconnected and /dev/viedo0 disappears :

    pi@raspi:~/appdev/ffmpeg $ dmesg | grep usb
    [ 5621.216896] usb 1-1.2.4: USB disconnect, device number 37
    [ 5621.586804] usb 1-1.2.4: new full-speed USB device number 38 using dwc_otg
    [ 5621.686694] usb 1-1.2.4: device descriptor read/64, error -32
    [ 5621.896583] usb 1-1.2.4: device descriptor read/64, error -32
    [ 5622.106572] usb 1-1.2.4: new full-speed USB device number 39 using dwc_otg
    [ 5622.206574] usb 1-1.2.4: device descriptor read/64, error -32
    [ 5622.416577] usb 1-1.2.4: device descriptor read/64, error -32
    [ 5622.626586] usb 1-1.2.4: new full-speed USB device number 40 using dwc_otg
    [ 5623.046583] usb 1-1.2.4: device not accepting address 40, error -32
    [ 5623.146583] usb 1-1.2.4: new full-speed USB device number 41 using dwc_otg
    [ 5623.566603] usb 1-1.2.4: device not accepting address 41, error -32
    [ 5623.566670] usb 1-1.2-port4: unable to enumerate USB device

    Has anybody experienced similar problems and can provide a fix for it ?

    What tools can I use to troubleshoot the usb communication on the pi ?

  • ffmpeg broadcast to rtmp and get stream name

    29 septembre 2017, par blast1987

    i am trying to make a simple ffmpeg streaming server, i broadcast the stream to my server as RTMP stream and my server does 3 steps :
    1) convert to hls stream
    2) save to disk as mkv
    3) broadcast to twitch

    my config is as follows :

    Ubuntu 17.04 64bit base system

    /lib/system/systemd/ffmpeg-rtmp.service => this systemd script keep my ffmpeg script alive

    /home/user/bin/ffmpeg-rtmp :

    date="$(date +'%d%m%Y%H%M%S')"
    /home/user/bin/ffmpeg -loglevel error -stats -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -threads 0 -listen 1 -rtmp_live live -i rtmp://127.0.0.1:1935 \
    -vf "format=nv12,hwupload" -c:v h264_vaapi -crf 35 -preset ultrafast -c:a libfdk_aac -tune zerolatency -flags -global_header -hls_time 0.1 -hls_list_size 1 -hls_flags delete_segments -start_number 0 /media/Disk/http/hls/stream.m3u8 \
    -vf "format=nv12,hwupload" -c:v h264_vaapi -crf 35 -preset ultrafast -c:a libfdk_aac -f flv rtmp://live-fra.twitch.tv/app/live_XXXXXXX \
    -vf "format=nv12,hwupload" -c:v h264_vaapi -crf 35 -preset ultrafast -c:a libfdk_aac -segment_time 300 -f segment /media/Disk/recordings/recording-$date-%04d.mkv

    Now i’ve found that broadcasting to rtmp ://127.0.0.1:1935 or rtmp ://127.0.0.1:1935/name is the same (not 100% sure about that.. if anyone can confirm..).

    How can i get this $name param and save the recording using this name (or store it in a bash var) ?

    For example if i’m playing PUBG i want to broadcast to rtmp ://127.0.0.1:1935/PUBG and have my stream saved on disk to /media/Disk/recordings/PUBG-$date-%04d.mkv etc...

    If i’m playing Battlefield1 i want to broadcast to rtmp ://127.0.0.1:1935/BF1 and have my stream saved on disk to /media/Disk/recordings/BF1-$date-%04d.mkv etc...

    is it possible ?

    Thanks in advance