Recherche avancée

Médias (1)

Mot : - Tags -/epub

Autres articles (66)

  • Personnaliser les catégories

    21 juin 2013, par

    Formulaire de création d’une catégorie
    Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
    Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
    On peut modifier ce formulaire dans la partie :
    Administration > Configuration des masques de formulaire.
    Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
    Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

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

  • dnxhddec : decode and use interlace mb flag

    25 septembre 2015, par Christophe Gisquet
    dnxhddec : decode and use interlace mb flag
    

    This bit is 1 in some samples, and seems to coincide with interlaced
    mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    is 11 bits. This looks oversized, but may help larger bitdepths.

    Currently, it leads to an obviously incorrect qscale value, meaning
    its syntax is shifted by 1. However, reading 11 bits also leads to
    obviously incorrect decoding : qscale seems to be 10 bits.

    However, as most profiles still have 11bits qscale, the feature is
    restricted to the CID1260 profile.

    The encoder writes 12 bits of syntax, last and first bits always 0,
    which is now somewhat inconsistent with the decoder, but ends up with
    the same effect (progressive + reserved bit).

    Partially fixes ticket #4876.

    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/dnxhddec.c
  • dnxhddec : Decode and use interlace mb flag

    26 septembre 2015, par Christophe Gisquet
    dnxhddec : Decode and use interlace mb flag
    

    This bit is 1 in some samples, and seems to coincide with interlaced
    mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    is 11 bits. This looks oversized, but may help larger bitdepths.

    Currently, it leads to an obviously incorrect qscale value, meaning
    its syntax is shifted by 1. However, reading 11 bits also leads to
    obviously incorrect decoding : qscale seems to be 10 bits.

    However, as most profiles still have 11bits qscale, the feature is
    restricted to the CID1260 profile (this flag is dependent on
    a higher-level flag located in the header).

    The encoder writes 12 bits of syntax, last and first bits always 0,
    which is now somewhat inconsistent with the decoder, but ends up with
    the same effect (progressive + reserved bit).

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>

    • [DBH] libavcodec/dnxhddec.c
  • dnxhddec : Decode and use interlace mb flag

    26 septembre 2015, par Christophe Gisquet
    dnxhddec : Decode and use interlace mb flag
    

    This bit is 1 in some samples, and seems to coincide with interlaced
    mbs and CID1260. 2008 specs do not know about it, and maintain qscale
    is 11 bits. This looks oversized, but may help larger bitdepths.

    Currently, it leads to an obviously incorrect qscale value, meaning
    its syntax is shifted by 1. However, reading 11 bits also leads to
    obviously incorrect decoding : qscale seems to be 10 bits.

    However, as most profiles still have 11bits qscale, the feature is
    restricted to the CID1260 profile (this flag is dependent on
    a higher-level flag located in the header).

    The encoder writes 12 bits of syntax, last and first bits always 0,
    which is now somewhat inconsistent with the decoder, but ends up with
    the same effect (progressive + reserved bit).

    Signed-off-by : Vittorio Giovara <vittorio.giovara@gmail.com>

    • [DH] libavcodec/dnxhddec.c