Recherche avancée

Médias (91)

Autres articles (66)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Dépôt de média et thèmes par FTP

    31 mai 2013, par

    L’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
    Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (8770)

  • Getting media duration with ffprobe after decoding with FFmpeg

    23 août 2019, par Brad

    With ffprobe, it’s possible to get the duration of a media file :

    ffprobe -show_format 1064428_cityLights_HD_BG.mp4

    [FORMAT]
    …
    duration=10.010000

    However, ffprobe only digs into the container and doesn’t decode the media. For container formats that have no inherent duration, or for broken files that play but maybe weren’t finalized, the duration isn’t available :

    [FORMAT]
    …
    duration=N/A

    The recommended solution to this problem is to use FFmpeg to decode, and then parse STDERR.

    ffmpeg -i input.webm -f null -

    frame=206723 fps=1390 q=-0.0 Lsize=N/A time=00:57:28.87 bitrate=N/A speed=23.2x

    This works well enough, but if I’m integrating this into other programs and scripts, I have to assume that the output of FFmpeg isn’t going to change from version to version. It would be much more convenient if there were a way to use ffmpeg and ffprobe together, so that I could continue to utilize the JSON output of ffprobe.

    Is there some way to force ffmpeg to decode the media and pipe it to ffprobe in some way that allows ffprobe to include the duration in its output for these types of situations ?

    (Note : I know I can just have FFmpeg output a file, and then input that into ffprobe. For convenience, I’m curious if there’s an all-in-one solution, with a pipe or equivalent.)

  • I can't find a good C# Media Transcoding Library [closed]

    11 mai 2021, par TheYoungSeth

    I am trying to find a good c# library for media transcoding, primarily video, and I don't seem to find anything good and actually usable. I do not want to use FFMpeg wrappers because I want my program to be user friendly and for public use which I can't do with FFMpeg because of the harsh usage rules that come with it.

    


    Help would be appreciated,
thanks

    


  • Introducing WebM, an open web media project

    20 mai 2010, par noreply@blogger.com (christosap)

    A key factor in the web’s success is that its core technologies such as HTML, HTTP, TCP/IP, etc. are open and freely implementable. Though video is also now core to the web experience, there is unfortunately no open and free video format that is on par with the leading commercial choices. To that end, we are excited to introduce WebM, a broadly-backed community effort to develop a world-class media format for the open web.

    WebM includes :

    • VP8, a high-quality video codec we are releasing today under a BSD-style, royalty-free license
    • Vorbis, an already open source and broadly implemented audio codec
    • a container format based on a subset of the Matroska media container

    The team that created VP8 have been pioneers in video codec development for over a decade. VP8 delivers high quality video while efficiently adapting to the varying processing and bandwidth conditions found on today’s broad range of web-connected devices. VP8’s efficient bandwidth usage will mean lower serving costs for content publishers and high quality video for end-users. The codec’s relative simplicity makes it easy to integrate into existing environments and requires less manual tuning to produce high quality results. These existing attributes and the rapid innovation we expect through the open-development process make VP8 well suited for the unique requirements of video on the web.

    A developer preview of WebM and VP8, including source code, specs, and encoding tools is available today at www.webmproject.org.

    We want to thank the many industry leaders and web community members who are collaborating on the development of WebM and integrating it into their products. Check out what Mozilla, Opera, Google Chrome, Adobe, and many others below have to say about the importance of WebM to the future of web video.


    Telestream

    Posted by Jeremy Doig, Engineering Director of video and Mike Jazayeri, Group Product Manager, Google

Navigation