Recherche avancée

Médias (91)

Autres articles (60)

  • Installation en mode ferme

    4 février 2011, par

    Le mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
    C’est la méthode que nous utilisons sur cette même plateforme.
    L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
    Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...)

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

  • Upgraded Adobe Flex SDK (4.5.1.21328) for V2.97a.20110705 release ; apparently made bad Flash 9 SWFs that would stop or not completely init under *some* Windows machines running Firefox and IE 7 - so, rolling back to older Flex SDK which has worked. (4.1.0.16076)

    7 juillet 2011

    m swf/soundmanager2.swf m swf/soundmanager2_debug.swf m swf/soundmanager2_flash9.swf m swf/soundmanager2_flash9_debug.swf m swf/soundmanager2_flash_xdomain.zip Upgraded Adobe Flex SDK (4.5.1.21328) for V2.97a.20110705 release ; apparently made bad Flash 9 SWFs that would stop or not completely (...)

  • V2.97a.20110706 - version bump for fixing intermittent broken Flash 9 SWF issue on *some* Windows machines with Firefox and/or IE 7, due to use of latest Adobe Flex SDK. (Rolled back to old SDK, fixed.) Weird. http://getsatisfaction.com/schillmania/topics/flashversion_9_fails_to_initialize_but_only_on_windows

    7 juillet 2011

    m doc/download/index.html m doc/index.html m script/soundmanager2-jsmin.js m script/soundmanager2-nodebug-jsmin.js m script/soundmanager2-nodebug.js m script/soundmanager2.js m src/SoundManager2.as m src/SoundManager2_AS3.as V2.97a.20110706 - version bump for fixing intermittent broken Flash 9 (...)

  • ffplay : how does it calculate the fps for playback ?

    21 octobre 2020, par Daniel

    I'm trying to playback a live media (h264) which is produced by a hardware encoder.

    


    The actual desired FPS on the encoder is set to 20, and when checking the logs of the encoder it prints "FPS statistics" every minute :

    


    2020-10-21 17:26:54.787 [  info] video_stream_thread(),video chn 0, fps: 19.989270
2020-10-21 17:27:54.836 [  info] video_stream_thread(),video chn 0, fps: 19.989270
2020-10-21 17:28:54.837 [  info] video_stream_thread(),video chn 0, fps: 20.005924
2020-10-21 17:29:54.837 [  info] video_stream_thread(),video chn 0, fps: 19.989270
2020-10-21 17:30:54.888 [  info] video_stream_thread(),video chn 0, fps: 19.989274
2020-10-21 17:31:54.918 [  info] video_stream_thread(),video chn 0, fps: 19.989264


    


    You can see it's varying, but not too much around 20.

    


    Question1 : Is this normal ? Or it should be exactly 20 every time ? To avoid confusion : I'd like to know if by the standard of H264, can this be accepted as a valid stream or this violates some
rule ?

    


    I'm trying to playback this stream with ffplay :

    


    $ ffplay rtsp://this_stream
Input #0, rtsp, from 'xyz'
  Metadata:
    title           : 
    comment         : substream
  Duration: N/A, start: 0.040000, bitrate: N/A
    Stream #0:0: Video: h264 (Constrained Baseline), yuv420p(progressive), 640x360, 25 fps, 25 tbr, 90k tbn, 180k tbc


    


    The thing is that ffplay thinks this is a stream with 25fps. And it also plays 25 frames each sec, causing the stream to stall and buffer in every few seconds.

    


    I believe the fps is calculated by some pts/dts values in the stream itself, and it's not hardcoded. Am I wrong here ?

    


    If I'm not wrong, why does ffplay thinks this stream runs at 25fps, whereas it only runs at (around) 20 ?

    


Navigation