Recherche avancée

Médias (1)

Mot : - Tags -/code

Autres articles (53)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (...)

  • XMP PHP

    13 mai 2011, par

    Dixit Wikipedia, XMP signifie :
    Extensible Metadata Platform ou XMP est un format de métadonnées basé sur XML utilisé dans les applications PDF, de photographie et de graphisme. Il a été lancé par Adobe Systems en avril 2001 en étant intégré à la version 5.0 d’Adobe Acrobat.
    Étant basé sur XML, il gère un ensemble de tags dynamiques pour l’utilisation dans le cadre du Web sémantique.
    XMP permet d’enregistrer sous forme d’un document XML des informations relatives à un fichier : titre, auteur, historique (...)

  • Configuration spécifique d’Apache

    4 février 2011, par

    Modules spécifiques
    Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
    Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
    Création d’un (...)

Sur d’autres sites (4363)

  • How should be the track ID encoded in to the media tracks / media content components available for MPEG - DASH Media Presentation ?

    2 avril 2014, par Ghanesh Babu J

    As per ISO/IEC 14496 Part 12 : ISOBMFF , the track Identifier specified in track header box "trak" and track fragment header "tfhd" box should be same and unique to each track available in an ISO file.

    Also as per ISO/IEC 23009 Part 1 , The track Identifier is same for all the representation of same content component type and unique to a media content component type( Audio / Video etc . . .) in an adaptation set.

    But , Most of the mpeg dash non multiplexed sample streams available in internet has used same track Identifier in all of the media tracks ( Audio , video etc. . . ) available for a media presentation. Say track ID for all content component type is 1.

    In this case, If a media player is supported with single mp4 demuxer means, it is not possible to demux the fragmented media sample from various track correctly for a media presentation.

    My question is,
    Having same track identifier for all media content component type in a dash media presentation is MPEG DASH Standard ?

  • Revision 3561 : On ajoute un lien pour modifier le média directement dans la page du média ...

    10 juin 2010, par kent1 — Log

    On ajoute un lien pour modifier le média directement dans la page du média (uniquement disponible pour le média pour l’instant)

  • ffmpeg : playing media files does not release processor after media ends ?

    2 septembre 2017, par Blake Senftner

    I have a commercial C++ application which uses FFMPEG’s libav series of dlls to play media in a Windows application. I basically started with the dranger tutorial about two years ago, and created a library that can playback USB cameras, IP camera / online streams, and media files on disk. (http://dranger.com/ffmpeg/)

    My question is directed at anyone who has created their own similar library :

    I recently noticed after playing a video file from disk (as opposed to a live stream from USB or IP source), my 8 core i7 workstation will show 28-29% CPU usage after a media file has ended. My application can play an unlimited number of videos, and each "virtual video panel" (not a window, just a "virtual tab" created using wxWidgets that holds an OpenGL context that I use to glDrawPixels() to the visible app panel) will play any of the three media types fine (USB, IP stream or media file) and when I stop a USB or IP stream my application’s CPU usage drops to zero. But when I "stop" a media file playing or the media file ends on its own the CPU usage does not drop - until the application quits.

    Three media files playing will take my application to 80-83% CPU, and it never drops. UNLESS I reuse that same "virtual video panel" to play a USB or IP stream. If I stop those streams, CPU usage is released.

    MP4 (h264) video files exhibit this "holding a processor" problem.

    MP4 (mpeg2) files do not.

    MP4 (h265) files do not.

    MPG (mpeg1) files do not.

    ASF (MS MPEG-4 Video v3) files do not.

    MKV (vp8) files do not.

    MOV files using h265 do not, as well as MOV (h264) files do not.

    FLV (sorensen) files do not, as well as FLV (h264) files do not.

    So it is not just the h264 codec.

    Anyone know what is going on, and how I tell libav to release CPU usage when a media file is no longer playing ?

Navigation