Recherche avancée

Médias (0)

Mot : - Tags -/content

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

Autres articles (62)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (10624)

  • when ffpmeg drops frames some things aren't played back in real time

    8 février 2024, par Alex028502

    I am trying to run a bunch of ffpmeg processes that act as simulators for cameras, and something funny is happening when I the processor can't keep up with the configured frame rate.

    


    I have replaced the rtsp stream with an output file, and managed to reproduce the issue, so will just show that to keep it simple.

    


    First here is a makefile that creates my source movie :

    


    clock.mp4: Makefile
    rm -f $@
    ffmpeg -f lavfi -i color=c=black:s=4096x2160:r=25 -vf \
"drawtext=fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf:fontsize=72:fontcolor=white:x=(w-text_w)/2:y=(h-text_h)/2: \
text='%{eif\:trunc(n/25)\:d}':start_number=0:rate=25" \
-t 60 -r 25 $@


    


    that gives me a one minute long movie that prints the second number to the screen. I have tested it out and the seconds are close enough. I put a lot of pixels to make it easier to jam up my CPU.

    


    Here is the script that creates a processes similar to the one I am trying to debug (called experiment.sh)

    


    I am actually using H.264, but H.265 is easier to overwhelm the processor with

    


    #! /usr/bin/env bash

set -e

echo starting > message$1.txt

rm -f superclock$1.mp4
ffmpeg -re -stream_loop -1 -i clock.mp4 \
       -an -vcodec libx265 -preset ultrafast -sc_threshold -1 -x265-params repeat-headers=1 \
       -vf "drawtext=fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf:fontsize=24:fontcolor=white:x=10:y=10:text='%{localtime\:%X}', \
            drawtext=fontfile=/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf:fontsize=24:fontcolor=white:x=10:y=(h-text_h-10):textfile=message$1.txt:reload=1, \
            scale=1920x1080,fps=25" \
       -b:v 3M -minrate 3M -maxrate 3M \
       -bufsize 6M -g 25 superclock$1.mp4 &
pid=$!

for x in $(seq 0 10)
do
    echo $x > message$1.txt
    sleep 10
done

kill -INT $pid || true


    


    It should

    


      

    • put the second in the middle of the screen - 'cause it gets it from the source video
    • 


    • put the approximate sixth of minute in the lower left corner
(only approximate because of the sleep but close enough)
    • 


    • put the the wall clock time in the upper left corner
    • 


    


    and it works

    


    make clock.mpg
./experiment.sh 0
vlc superclock0.mp4


    


    shows something like this
working video

    


    Now here is the interesting part

    


    If I run the script in four different terminals at the same time

    


    ./experiment.sh 1
./experiment.sh 2
./experiment.sh 3
./experiment.sh 4


    


    It can't keep up with the frame rate, and I see this in the output :

    


    frame= 1515 fps= 16 q=0.0 size=     768kB time=00:00:59.96 bitrate= 104.9k


    


    I was hoping the end result would all look ok when I watch it except with fewer frames, but the timestamps of the frames would make it all work as expected

    


    However...

    


      

    • The time in the middle, that is inherited from the source video, the seconds in the middle of the screen, stays in sync with VLC's clock.
    • 


    • the wall clock in the upper left seems play at 150% speed
    • 


    • the every ten seconds incrementor in the lower left seems to increment every 7 seconds
    • 


    • the video is only 1:25 long even though it was recording for at least 1:40 according to sleeps
    • 


    • the wall clock in the upper right hand corner makes it more than 1'40" and then counter in the lower left makes it to 10.
    • 


    


    30 seconds in

    


    Here are four states to compare

    


    |                  | Start    | 30" in   | end      |
|------------------+----------+----------|----------|
| Video Time       | 00:00    | 00:30    | 01:24    |
| Wall Clock Time  | 15:05:50 | 15:06:39 | 15:07:39 |
| sixth of minute  | 0        | 4        | 10       |
| seconds counter  | 0        | 30       | 24       |


    


    end of the movie

    


    So you can see the vlc clock keeps pace with the original clock from the source movie.. even when it is only able to produce frames at 2/3 of the rate. However, the it is taking 50% long to get through the whole source movie I guess ?

    


    I am having trouble coming up with a theory that can explain exactly how this happens.

    


    Does anybody know how I can "correct" this ? (make it so that the movie is played at the same rate that it is recorded)

    


    I am thinking of using a lower frame rate and size as the input video.. but it would be nice to have something that will always work as expected, just with a lower frame rate, no matter how busy the processor is.

    


  • avutil/hwcontext_opencl : Add map from Videotoolbox to OpenCL

    23 février 2024, par Zhao Zhili
    avutil/hwcontext_opencl : Add map from Videotoolbox to OpenCL
    

    For example :
    ./ffmpeg -hwaccel videotoolbox \
    -hwaccel_output_format videotoolbox_vld \
    -i foo.mp4 \
    -vf hwmap=derive_device=opencl,transpose_opencl=dir=clock,hwmap,format=nv12 \
    -c:v hevc_videotoolbox \
    -c:a copy \
    -b:v 2M -tag:v hvc1 bar.mp4

    Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>

    • [DH] configure
    • [DH] libavutil/hwcontext_opencl.c
  • ffplay option to specify interface there to join mcast group then playing sdp [closed]

    2 mars 2024, par user3296957

    I am trying to listen mcast stream using ffplay, and I have such sdp file :

    &#xA;

    m=video 6000 RTP/AVP 96&#xA;c=IN IP4 224.0.1.107&#xA;a=rtpmap:96 H265/90000&#xA;

    &#xA;

    I am using such command to play stream

    &#xA;

    ffplay -protocol_whitelist file,udp,rtp -i rtp_265mc.sdp&#xA;

    &#xA;

    Such command succeeds in unicast mode, but in mcast mode I have several interfaces&#xA;and wrong one is used to join mcast group. In gstreamer it can be fixed by multicast-iface&#xA;option.&#xA;For example such command succeeds :

    &#xA;

    IFACE="enx00e04c31112e" &#xA;gst-launch-1.0 -v udpsrc multicast-group=224.0.1.107 auto-multicast=true port=6000 multicast-iface=$IFACE ! queue ! "application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H265, payload=(int)96" ! rtph265depay ! h265parse ! avdec_h265 ! queue ! videoconvert ! fpsdisplaysink&#xA;

    &#xA;

    The same stream that I use, can be generated using such gstreamer command :

    &#xA;

    gst-launch-1.0 videotestsrc ! video/x-raw,width=2048,height=1200 ! videoconvert !\&#xA;  nvh265enc preset=low-latency-hp rc-mode=cbr gop-size=16 max-bitrate=2000 !\   &#xA;  rtph265pay config-interval=1 pt=96 ! udpsink host=224.0.1.107 port=6000 auto-multicast=true&#xA;

    &#xA;

    How can I force ffplay to use specific interface, or can somebody show string&#xA;to play such stream using ffmpeg ?

    &#xA;