Recherche avancée

Médias (91)

Autres articles (94)

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

  • Le profil des utilisateurs

    12 avril 2011, par

    Chaque utilisateur dispose d’une page de profil lui permettant de modifier ses informations personnelle. Dans le menu de haut de page par défaut, un élément de menu est automatiquement créé à l’initialisation de MediaSPIP, visible uniquement si le visiteur est identifié sur le site.
    L’utilisateur a accès à la modification de profil depuis sa page auteur, un lien dans la navigation "Modifier votre profil" est (...)

  • Configurer la prise en compte des langues

    15 novembre 2010, par

    Accéder à la configuration et ajouter des langues prises en compte
    Afin de configurer la prise en compte de nouvelles langues, il est nécessaire de se rendre dans la partie "Administrer" du site.
    De là, dans le menu de navigation, vous pouvez accéder à une partie "Gestion des langues" permettant d’activer la prise en compte de nouvelles langues.
    Chaque nouvelle langue ajoutée reste désactivable tant qu’aucun objet n’est créé dans cette langue. Dans ce cas, elle devient grisée dans la configuration et (...)

Sur d’autres sites (12548)

  • ffmpeg issues "501 Not Implemented" while recording an RTSP stream

    28 février 2019, par atsushi

    I have a 4K camera (Sony SNC-VB770) streaming RTSP.

    I’m trying to record the stream into files (each has handy length, say, 1hour)
    using a simple script to repeatedly launch ffmpeg (ver 4.1) :

    while : ; do
     # (set $url and $outfile, and then)
     ffmpeg -rtsp_transport tcp -t 3600 -y -i $url -c copy -map 0:0 -b:v 16000k $outfile
    done

    If I run the script on a local PC directly connected to the camera, it works (longer than a week, at least).
    However, if I do the same on a server machine located in a data center, it fails randomly with no error message.
    Sometimes it runs for a few days, sometimes it dies in one minutes.

    Typical output looks like the following :

    # devname: snc-vb770
    # url: rtsp://10.40.35.90/media/video1
    # vb: 16000k
    # datefmt %d%H
    # addtimestamp 0
    no timestamp
    ffmpeg version 4.1 Copyright (c) 2000-2018 the FFmpeg developers
     built with gcc 4.4.7 (GCC) 20120313 (Red Hat 4.4.7-18)
     configuration: --prefix=/usr/local/ffmpeg-4.1 --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-shared --enable-libx264 --enable-libvorbis --enable-filter=drawtext --enable-libfreetype --enable-libfribidi --enable-fontconfig
     libavutil      56. 22.100 / 56. 22.100
     libavcodec     58. 35.100 / 58. 35.100
     libavformat    58. 20.100 / 58. 20.100
     libavdevice    58.  5.100 / 58.  5.100
     libavfilter     7. 40.101 /  7. 40.101
     libswscale      5.  3.100 /  5.  3.100
     libswresample   3.  3.100 /  3.  3.100
     libpostproc    55.  3.100 / 55.  3.100
    Input #0, rtsp, from 'rtsp://10.40.35.90/media/video1':
     Metadata:
       title           : Sony RTSP Server
     Duration: N/A, start: 0.066667, bitrate: N/A
       Stream #0:0: Video: h264 (High), yuv420p(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 14.99 fps, 14.99 tbr, 90k tbn, 29.97 tbc
    Output #0, mp4, to './2811.mp4':
     Metadata:
       title           : Sony RTSP Server
       encoder         : Lavf58.20.100
       Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], q=2-31, 16000 kb/s, 14.99 fps, 14.99 tbr, 90k tbn, 90k tbc
    Stream mapping:
     Stream #0:0 -> #0:0 (copy)
    Press [q] to stop, [?] for help
    [mp4 @ 0x24e4ec0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
    [mp4 @ 0x24e4ec0] pts has no value
    [mp4 @ 0x24e4ec0] Non-monotonous DTS in output stream 0:0; previous: 0, current: 0; changing to 1. This may result in incorrect timestamps in the output file.
    frame=   33 fps=0.0 q=-1.0 size=    1792kB time=00:00:02.00 bitrate=7332.9kbits/s speed=3.57x
    ...
    frame=  104 fps=8.4 q=-1.0 Lsize=    6532kB time=00:00:06.74 bitrate=7939.6kbits/s speed=0.548x
    video:6531kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.023506%

    I’ve looked into RTSP packet and found an "RTSP/1.0 501 Not Implemented" is sent from ffmpeg to the camera.
    After that the camera eventually sent back "RTSP/1.0 505 RTSP Version not supported" and then ffmpeg quits shortly.

    The "501" packet seems to be generated by libavformat/rtsp.c:ff_rtsp_read_reply(),
    when ffmpeg receive a malformed RTSP packet with method=(null), status_code=0.
    I don’t know why such packets arrive at random timing and who is wrong (maybe the camera, maybe any of network switches or routers in the middle of the network path from the camera to the server machine).
    But anyway, I don’t want the recording to be stopped
    due to those malformed packets.

    Is there any workaround to make ffmpeg ignore invalid RTSP packets and just continue the recording ?

    Additional information :

    • I’ve tested the recording with both ffmpeg ver4.1 and 2.8.4 and no difference observed.

    • No difference observed at lower resolution nor at lower bitrate.

    • I have 3 cameras from various manufacturers in the same network environment.
      All of the three are working without problem for more than a month.
      Only the Sony SNC-VB770 shows the strange behavior.

  • Anomalie #4587 : Warning en php 8 "avec doublons_notes.html" dans les tests unitaire

    8 novembre 2020, par Franck D

    Pareil, cela vient de Mysql 8 en 5.7.24, il n’y a pas de problème
    https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_regexp_missing_close_bracket

    Je te laisse faire la fermeture du ticket si tu le souhaites :)

  • try...catch for dumb IE 9 Audio() "not implemented" error in server case without "desktop experience" installed, means missing HTML5 audio/video support. Hat tip : https://github.com/Modernizr/Modernizr/issues/224

    26 octobre 2011, par Scott Schiller

    m script/soundmanager2-jsmin.js m script/soundmanager2-nodebug-jsmin.js m script/soundmanager2-nodebug.js m script/soundmanager2.js try...catch for dumb IE 9 Audio() "not implemented" error in server case without "desktop experience" installed, means missing HTML5 audio/video support. Hat tip : (...)