Recherche avancée

Médias (1)

Mot : - Tags -/copyleft

Autres articles (67)

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

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
    Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
    Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
    Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)

Sur d’autres sites (10916)

  • Seeking with the activeX VLC plugin has a bad response rate

    24 juin 2017, par Vitalis Hommel

    I am using axVLCPlugin.input.time = pos; where pos is the new time to browse through a video clip in small resolution (240p) in a VLC activeX part of my program using a slider, which updates pos.

    On an older laptop this worked flawlessly, with no delay. On my new laptop, this works only with significant delay, meaning that once I enter a new position, it takes about 1 second to show this position of the video on screen in the VLC activeX plugin. Previously it was instant.

    Is this

    1. a VLC issue(2.2.6 umbrella) ?
    2. a Visual Studio issue(VS 2017) ?
    3. a video encoding issue(ffmpeg version N-86482-gbc40674 - ffmpeg -i inputfile.extension output.mp4) ?
    4. a video codec issue ?

    EDIT : fortunately I found that the activex-plugin has an output. This is what it gives me : https://pastebin.com/GEKb22Gg - still unclear what that means

    How to track down the cause and solve it ?

  • How are ARM GPUs supported by Video display/decoding/encoding Programs ?

    7 juillet 2020, par John Allard

    I often see ARM-based chips advertising onboard GPUs, like the RPI3 that came with "Broadcom VideoCore IV @ 250 MHz" and the OdroidC2 that comes with a "Mali-450 GPU". These chips advertise stuff like "Decode 4k/30FPS, Encode 1080p,30FPS" as the capabilities of the GPU for encoding and decoding videos.

    


    My question is this - how does a program like Kodi, VLC, or FFMPEG come to make use of these GPUs for actual encoding and decoding ? When I do research on how to make use of the Mali-450 GPU, for example, I find some esoteric and poorly documented C-examples of sending compressed frames to the GPU and getting decoded frames back. If I were to use a device like the OdroidC2 and install VLC on it, how does VLC make use of the GPU ? Did someone have to write logic into VLC to use the specific encoding/decoding API exposed by the Mali GPU in order to use it or do these GPUs follow some sort of consistent API that is exposed by all GPUs and VLC/Kodi can just program against this system API ?

    


    The reason I ask this question is that VLC and Kodi tend to support these GPUs out of the Box, but a very popular program like FFMPEG that prides itself on supporting as many codecs and accelerators as possible has no support for decoding and encoding with the Mali GPU series. Why would VLC/Kodi support encoding/decoding and not FFMPEG ? Why do these manufacturers claim wild decoding and encoding support if these GPUs are difficult to program against and one must use their custom esoteric APIs instead of something like libavcodec ?

    


    I hope my question makes sense, I guess what I'm curious about is that GPUs on most systems whether it be the Intel HD Graphics, Nvidia cards, AMD cards, etc seem to be used automatically by most video players but when it comes to using something like FFMPEG against these devices the process becomes much more process and you need to custom compile the build and give special flags to use the device as intended. Is there something I'm missing here ? Is VLC programmed to make use of all of these different type of GPUs ? And why, in that case, does FFMEPG not support Mali GPUs out of the Box ?

    


  • Why does HTML5 video with very large mp4 (with +faststart, ie metadata at beginning), take ages to load ?

    8 septembre 2015, par Tom Jenkinson

    The video is rendered with ffmpeg with the "faststart" flag added meaning the metadata should be at the start of the file, and the server appears to be handling partial content requests correctly, so why does it need to have downloaded so much of the video before the player becomes enabled and can play the video ? I am testing it in Google Chrome.

    Once the player becomes enabled I can seek around to various points in the video pretty instantly and see the new partial content requests being made.

    Here is a link to the video : http://iptv.la1tv.co.uk/unibrass.mp4

    Here is a jsbin with the video tag : https://jsbin.com/rahewidoru . It takes a few minutes but does work after it loads.

    Any suggestions ?

    I realise there are other methods like HLS and dash which use chunks, but I would like to know why it isn’t working this way because I can’t find anywhere that provides a reason as to why it doesn’t work well.