Recherche avancée

Médias (1)

Mot : - Tags -/Christian Nold

Autres articles (88)

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

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

  • La gestion des forums

    3 novembre 2011, par

    Si les forums sont activés sur le site, les administrateurs ont la possibilité de les gérer depuis l’interface d’administration ou depuis l’article même dans le bloc de modification de l’article qui se trouve dans la navigation de la page.
    Accès à l’interface de modération des messages
    Lorsqu’il est identifié sur le site, l’administrateur peut procéder de deux manières pour gérer les forums.
    S’il souhaite modifier (modérer, déclarer comme SPAM un message) les forums d’un article particulier, il a à sa (...)

Sur d’autres sites (11511)

  • Need help on handling MPEG4V1 data

    14 septembre 2011, par Gediminas

    I'm in situation where I need to get a chunk of MPEG4V1 (Microsoft MPEG-4 VKI
    Codec V1
    ) data located in the beginning of a packet (that was sent by some DVR unit).

    Packet structure looks something like this :

    • Compressed MPEG4 data.
    • Long integer - Number of events and tripwires.
    • Long integer - Number of events.
    • Event - Event's sequence.
    • Long integer - Number of tripwires.
    • Tripwire - Tripwires sequence.
    • Long integer - Cyclical redundant code (CRC).

    So there is no indication of how to know where does the MPEG4 data ends (Or is there ?),
    and from where should I start reading this additional data like "Number of events and tripwires" and etc...

    I uploaded two packet's so you could see how the actual data looks like :
    recvData1.txt,
    recvData2.txt.

    I've tried to decode those packets using FFmpeg library with avcodec_decode_video function and by removing byte by byte from the end of my recvData buffer in a hope for any results,
    but FFmpeg just allways returned with an error messages like this :

    "[msmpeg4v1 @ 038865a0] invalid startcode",
    "[msmpeg4v1 @ 038865a0] header damaged".

    I'm not that good specialist on knowing of how does the MPEG4 works from the inside,
    but judging by the error messages it's clearly seen that I'm missing some data for decoding at the start of the buffer.

    So I'm not sure of what part / kind of MPEG data I'm getting here..
    Maybe it's some kind of MPEG's "frame" data with it's "end" indication or something ?

    I've even compared the start of my recvData buffer to some of MPEG4V1 encoded video files I found on the net "http://www.trekmania.net/clips/video_clips4.htm" to check if the start of my buffer really contains the MPEG data ..and not some kind of DVR vendor specific stuff..

    And I noticed that there are about 20bytes of data
    (at the start of my packet data, and in .avi files right after about 180bytes..)
    that looks like some kind of header or something..

    Please check this image : "http://ggodis.gamedev.lt/stackOverflow/recvData.jpg"

    Maybe someone knows what this part of MPEG4V1 data represents ?

    P.S. ..I've checked the CRC values for my received packets and they were correct..

  • ffmpeg metadata, multiline text into comment field

    15 avril 2013, par decss

    my question is next : i use ffmpeg to update metadata tags like this way

    ffmpeg -i "in.m4a" -acodec copy -metadata artist="artist text"
    -metadata comment="comment text" "out.m4a"

    Well, "artist text" and "comment text" is usual plain text, but comment field allow to put multiline text. Each line must have new line character to do it. Something like this :

    -metadata comment="source: lastfm \r\n tags: tag1, tag2 \r\n ..."

    But all characters that i use (\r\n, %nl%, ^N) brings no result

    So i have no idea how to put multiline text into a comment field via ffmpeg
    Hope you will help me : ) Thanks !

  • Revision e7bddba149 : new version of speed 1 This version of speed 1 only disables modes at higher re

    23 avril 2013, par Jim Bankoski

    Changed Paths : Modify /vp9/encoder/vp9_block.h Modify /vp9/encoder/vp9_rdopt.c new version of speed 1 This version of speed 1 only disables modes at higher resolution that had distortions >2x the best mode we found... The hope is that this could be a replacement for speed 0 ... Change-Id : (...)