Recherche avancée

Médias (0)

Mot : - Tags -/optimisation

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

Autres articles (35)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

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

Sur d’autres sites (4549)

  • avformat/vpcc : Calculate VP9 level from Luma's Sample rate and Picture size

    23 avril 2018, par Karthick Jeyapal
    avformat/vpcc : Calculate VP9 level from Luma's Sample rate and Picture size
    • [DH] libavformat/vpcc.c
    • [DH] libavformat/vpcc.h

  • avformat/mxfenc : Write Audio Ref Level for D10

    6 avril 2018, par Michael Niedermayer
    avformat/mxfenc : Write Audio Ref Level for D10

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/mxfenc.c
    • [DH] tests/ref/fate/copy-trac4914
    • [DH] tests/ref/fate/mxf-reel_name
    • [DH] tests/ref/fate/time_base
    • [DH] tests/ref/lavf/mxf
    • [DH] tests/ref/lavf/mxf_d10
    • [DH] tests/ref/lavf/mxf_dv25
    • [DH] tests/ref/lavf/mxf_dvcpro50
    • [DH] tests/ref/lavf/mxf_opatom
    • [DH] tests/ref/lavf/mxf_opatom_audio

  • How can I optimize MP4 file encoding in openRTSP to the same level as FFmpeg ?

    2 juillet 2018, par Wolfgang Klenk

    I currently receive and store a RTSP stream from a camera with openRTSP with a command like this :

    openRTSP -4 "rtsp://192.168.41.185/rtsp_tunnel?h26x=4&amp;line=1&amp;inst=2" > movie.mp4

    I can do the same using FFmpeg :

    ffmpeg -i "rtsp://192.168.41.185/rtsp_tunnel?h26x=4&amp;line=1&amp;inst=2" -vcodec copy movie.mp4

    The video frames from the camera are 1280x720 (H.264) at around 30 fps and have a milliseconds timestamp stamped in. When I view the movie.mp4 created by ffmpeg it looks pretty nice, the seconds stamped into the video stream seem rather accurate. On the contrary, if I view the movie.mp4 created by openRTSP, the seconds in the video timestamp last definitively longer than the ones in reality. So one second on video could last two seconds in reality. I made several tests, and it is not an issue of network performance or of handling the messages received from the camera. The reason seems to be the part where the messages are encoded into this MP4 container.

    Is FFmpeg so much faster doing this than openRTSP ?

    Can I optimize the MP4 encoding in openRTSP somehow ?

Navigation