Recherche avancée

Médias (91)

Autres articles (87)

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

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

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

Sur d’autres sites (11534)

  • ffmpeg - how can I get a specific channel using channel masks (e.g. : get only surround left channel)

    26 novembre 2013, par awfulcode

    I'm trying to build a mixer that allows users to toggle specific channels on and off. I know that different codecs encode those channels in different orders (it's not as simple as getting channel #3 as the center channel every time), so the challenge is to properly identify the channel position in surround audio tracks.

    ffmpeg does list the in the beginning of libavutil/channel_layout.h :

    #define AV_CH_FRONT_LEFT             0x00000001
    
#define AV_CH_FRONT_RIGHT            0x00000002
    
#define AV_CH_FRONT_CENTER           0x00000004
    
#define AV_CH_LOW_FREQUENCY          0x00000008
    
#define AV_CH_BACK_LEFT              0x00000010
    
#define AV_CH_BACK_RIGHT             0x00000020
    
#define AV_CH_FRONT_LEFT_OF_CENTER   0x00000040
    
#define AV_CH_FRONT_RIGHT_OF_CENTER  0x00000080
    
#define AV_CH_BACK_CENTER            0x00000100
    
#define AV_CH_SIDE_LEFT              0x00000200
    
#define AV_CH_SIDE_RIGHT             0x00000400
    
#define AV_CH_TOP_CENTER             0x00000800
    
#define AV_CH_TOP_FRONT_LEFT         0x00001000
    
#define AV_CH_TOP_FRONT_CENTER       0x00002000
    
#define AV_CH_TOP_FRONT_RIGHT        0x00004000
    
#define AV_CH_TOP_BACK_LEFT          0x00008000
    
#define AV_CH_TOP_BACK_CENTER        0x00010000
    
#define AV_CH_TOP_BACK_RIGHT         0x00020000
    
#define AV_CH_STEREO_LEFT            0x20000000  ///< Stereo downmix.
    
#define AV_CH_STEREO_RIGHT           0x40000000  ///< See AV_CH_STEREO_LEFT.
    
#define AV_CH_WIDE_LEFT              0x0000000080000000ULL
    
#define AV_CH_WIDE_RIGHT             0x0000000100000000ULL
    
#define AV_CH_SURROUND_DIRECT_LEFT   0x0000000200000000ULL
    
#define AV_CH_SURROUND_DIRECT_RIGHT  0x0000000400000000ULL
    
#define AV_CH_LOW_FREQUENCY_2        0x0000000800000000ULL

    But looking over the header files and whatever little documentation about ffmpeg I couldn't find anything that tells me how to assign a specific channel position (or mask, as it's described in the header file) to a specific bus in a mixer audio unit.

    Do you know how to do that ? Please let me know if you want to look at the code I'm using right now.

    And as always, thank you so much.

  • Writing linear float range to openEXR turns out non linear

    3 avril 2022, par Chryfi

    I am writing the linearized depth buffer of a game to openEXR using FFmpeg. Unfortunately, FFmpeg does not adhere to the openEXR file specification fully (like allowing unsigned integer for one channel) so I am writing one float channel to openEXR, which is put into the green channel with this command -f rawvideo -pix_fmt grayf32be -s %WIDTH%x%HEIGHT% -r %FPS% -i - -vf %DEFVF% -preset ultrafast -tune zerolatency -qp 6 -compression zip1 -pix_fmt gbrpf32le %NAME%_depth_%d.exr.

    


    The float range is from 0F to 1F and it is linear. I can confirm that the calculation and linearization is correct by testing 16 bit integer (per pixel component) PNG in Blender compositor. The 16 bit integer data is written like this short s = (short) (linearzieDepth(depth) * (Math.pow(2,16) - 1)) whereas for float the linearized value is directly written to OpenEXR without multiplying with a value.

    


    However, when viewing the openEXR file it doesn't have the same "gradient" as the 16 bit png... when viewing them side by side, it appears as if the values near 0 are not linear, and they are not as dark as they should be like in the 16 bit png.
(And yes, I set the image node to linear), and comparing it with 3d tracking data from the game I cant reproduce the depth and cant mask things using the depth buffer where as with the png I can.

    


    How is it possible for a linear float range to turn out so different to a linear integer range in an image ?

    


  • Nodebots Day 2014 Sydney

    25 juillet 2014, par silvia

    Nodebots and WebRTC Day in Sydney, NICTA http://www.meetup.com/WebRTC-Sydney/events/173234022/

    Category : Array
    Uploaded by : Silvia Pfeiffer
    Hosted : youtube

    The post Nodebots Day 2014 Sydney first appeared on ginger’s thoughts.

Navigation