Recherche avancée

Médias (91)

Autres articles (13)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

  • List of compatible distributions

    26 avril 2011, par

    The table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
    If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...)

Sur d’autres sites (2960)

  • vaapi_encode : Support configurable slices

    23 septembre 2018, par Mark Thompson
    vaapi_encode : Support configurable slices
    

    This adds common code to query driver support and set appropriate
    address/size information for each slice. It only supports rectangular
    slices for now, since that is the most common use-case.

    • [DH] doc/encoders.texi
    • [DH] libavcodec/vaapi_encode.c
    • [DH] libavcodec/vaapi_encode.h
  • Set path while installing [duplicate]

    12 janvier 2021, par Education 4Fun

    My requirement is to set a path(C :/ffmpeg) while installing the software itself for my application(which I made)
    
A reference that it's possible(While installing python 3.8.0 we have check box by ticking it we can add the path of python automatically)
    
This is the main requirement which I wanna do with my application

    


    enter image description here

    


    About My application :
    
My application is a simple video editing application that runs on cmd as it uses FFmpeg its path should be set only then the application will work
The application is coded in python and the GUI is made using pyqt5 The application runs on cmd like the commands and all here is a reference image for observation enter image description here

    


    enter image description here

    


    So it's mandatory to add the path else FFmpeg will not recognize. If there is any way to do in building setup like how python can add the path as per user requirement refer to the image (1st image)

    


    About Files in C :/ffmpeg
Files in FFmpeg folder refer to image for that info

    


    enter image description here

    


    Hope the query is a bit clear.
Thanks a lot

    


  • Can I stream a static image feed into a video with Node.js ?

    5 juillet 2022, par Quentin Lamotte

    I want to create a small PoC where I can stream a static image source into a video. The idea behind that is that I have an (old) IP camera that only serves snapshots on an HTTP endpoint. When calling that endpoint, you get a static JPEG picture. Let's say, the URL I want to "convert" is : http://mycamera.local/live.jpg

    


    Now, I want to create a script using Node.js to quickly call that URL over and over in order to form some sort of video stream. I'm not an expert into media encoding and stuff, but I guess that the variable refresh rate induced by HTTP latency, the camera's FPS... would make it a bit trickier to pipe images into a video response ?

    


    I thought I'd go with Express and Axios to serve and query HTTP content. I've also read that FFmpeg could play a role in there. But, I am open to any suggestion. I could even switch languages if that's required. This question is so specific I think, that any response would do.

    


    A couple of requirements I cannot change :

    


      

    • The camera can only serve static pictures on a single endpoint.
    • 


    • I have no other protocol than HTTP on the camera.
    • 


    • I am not buying or modifying the existing hardware, even though I know there are very cheap units out there.
    • 


    • My server must serve a live video that could be streamed by VLC for instance.
    •