Recherche avancée

Médias (1)

Mot : - Tags -/net art

Autres articles (45)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

Sur d’autres sites (4491)

  • very low latency streaminig with ffmpeg using a webcam

    22 mars 2017, par userDtrm

    I’m trying to configure ffmpeg to do a real-time video streaming using a webcam. The ffmpeg encoder command I use is as follows.

    ffmpeg -f v4l2 -input_format yuyv422 -s 640x480 -i /dev/video0 -c:v libx264 -profile:v baseline -trellis 0 -subq 1 -level 32 -preset superfast -tune zerolatency -me_method epzs -crf 30 -threads 0 -bufsize 1 -refs 4 -coder 0 -b_strategy 0 -bf 0 -sc_threshold 0 -x264-params vbv-maxrate=2000:slice-max-size=1500:keyint=30:min-keyint=10: -pix_fmt yuv420p -an -f mpegts udp://192.168.1.8:5001

    The ffplay command used to display the video feed is,

    ffplay -analyzeduration 1 -fflags -nobuffer -i udp://192.168.1.8:5001

    However, I’m experiencing a latency of 0.5 - 1.0s latency in the video stream. Is there a way to reduce this to a number less than 100ms. Also, when I replace the v4l2 camera capture with a screen capture using x11grab, the stream is almost real-time and I experience no noticeable delays. Moreover, changing the encoder from x264 to mpeg2 had no effect on the latency. In addition, the statistics from the ffmpeg shows that the encoder is performing at a 30fps rate, which I believe indicates that the encoding is real-time. This leaves me with only one reason for the experienced delay.

    • Is there a significant delay in buffers when using v4l2 during video capturing in a webcam ?
    • I don’t think the transmission delay is in effect in this case as I see no latencies when screen capture is used under the same conditions.
    • Can this latency be further reduced ?. Can someone think of a different encoder configuration to be used instead of the one that I’ve been using ?.

    Any suggestions or assistance is highly appreciated.

    Thank You.

  • pthread_frame : don’t sync items between threads for intra-only codecs.

    28 mars 2017, par Ronald S. Bultje
    pthread_frame : don’t sync items between threads for intra-only codecs.

    Intra-only codecs should either be able to read these items from the
    
bitstream, or they should be set upon codec initialization. In both
    
cases, syncing these items at runtime is unnecessary.
    

    In practice, this fixes race conditions for decoders that read these
    
values from the bitstream.
    • [DH] libavcodec/pthread_frame.c

  • h264 : revert 1189af429211ac650aac730368a6cf5b23756605.

    27 mars 2017, par Ronald S. Bultje
    h264 : revert 1189af429211ac650aac730368a6cf5b23756605.

    The patch introduces race conditions.
    • [DH] libavcodec/h264_slice.c
    • [DH] libavcodec/h264dec.c
    • [DH] libavcodec/h264dec.h

Navigation