Recherche avancée

Médias (91)

Autres articles (107)

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
    Upload et récupération d’informations de la vidéo source
    Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
    Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

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

Sur d’autres sites (15971)

  • VP9 tiled encoding for view-port dependent 360-degree VR streaming

    28 janvier 2021, par Victor Coyter

    I am trying to use libvpx-vp9 to encode a 360-degree VR video and generate multi-bitrate viewport-dependent playlist, that is :

    


      

    • A video stream could be splitted in to n*m tiles (e.g., 8x8)

      • 


    • Users may fetch those high-resolution tiles which insides their view-port via HTTP webm

      • 


    • and fetch low-resolution tiles which outsides their view-port

      • 


    • Finally, combine the video (without decoding) and render with OpenGL shaders

      • 


    


    Similar ideas like OMAF has been implemented by Intel / fraunhofer hhi, but they were using H.265.

    


    Is that possible to implement in VP9 ?

    


    The tiles in VP9 is designed to accelerate the encoding process by multi-threading, but as per defined in VP9 bitstream specifications, a tile is a "rectangular region of the frame that could be able to be decoded and encoded independently"

    


    I can find that libvpx provide options : --tile-rows and --tile-column and can successfully run them, while they indeed use multi-thread to encode.

    


  • udpsrc doesn't work on 2 NIC & Port mirror linux setup (gstreamer/vlc/ffmpeg)

    28 janvier 2021, par kepitto

    I've tried a lot of stuff, but I can't seem to get it to work. (Same problem exists with ffmpeg/vlc)

    


    Basically, I can't get the UDP Stream directly into a videotool. I can verify the data coming in through tcpdump/wireshark etc. and i can also create the videofiles through gstreamer/ffmpeg afterwards, but I can't use the udp source as input.

    


    The current setup is the following :
The camera streams MJPEG through UDP to a fixed address & port. I port mirrored the data from the camera, so that I can verify the data coming in through wireshark on a 3rd device.

    


    The reason behind doing this is that multicast is not supported, so I need a way to get the data on 2 devices through unicast. Port mirroring seemed like a viable solution.

    


    Am I missing something here ? What do I need to do to get this working ?
I thought maybe it's due to the two networkinterface setup as I use 1x usb to ethernet for the port mirror and 1x ethernet for the web, but disconnecting the other shows no difference.
The routing seems correct too : "ip route get camera.ip" returns that the routing is through the usb to ethernet on my static ip.

    


    Example of an attempt :

    


    Gst-launch-1.0 udpsrc port=streamingport(confirmed through wireshark) ! jpegdec ! videorate ! video/x-raw,framerate=30/1 ! autovideosink (does not work)

    


    Gst-launch-1.0 filesrc location=hexdumpfile.txt ! jpegdec ! videorate ! video/x-raw,framerate=30/1 ! autovideosink (does work)

    


  • lavc/aarch64 : port HEVC add_residual NEON

    10 janvier 2021, par Reimar Döffinger
    lavc/aarch64 : port HEVC add_residual NEON

    Speedup is fairly small, around 1.5%, but these are fairly simple.
    

    Signed-off-by : Josh Dekker <josh@itanimul.li>
    • [DH] libavcodec/aarch64/hevcdsp_idct_neon.S
    • [DH] libavcodec/aarch64/hevcdsp_init_aarch64.c

Navigation