Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (24)

  • 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

  • L’espace de configuration de MediaSPIP

    29 novembre 2010, par

    L’espace de configuration de MediaSPIP est réservé aux administrateurs. Un lien de menu "administrer" est généralement affiché en haut de la page [1].
    Il permet de configurer finement votre site.
    La navigation de cet espace de configuration est divisé en trois parties : la configuration générale du site qui permet notamment de modifier : les informations principales concernant le site (...)

Sur d’autres sites (8243)

  • Firefox audio tag doubles length of OGG Vorbis

    22 mai 2014, par tomysshadow

    So, here I have a demo file from my website

    http://members.shaw.ca/darolynk/breakup/html5game/snd_music.ogg

    I am running off of Firefox Beta 30.0 and this issue does not persist in Google Chrome. In Firefox, when I play the file back, the length is displayed at around twice of its actual length as 32:13 when it is only 12:52 in length. Even worse, the audio stutters, playing one second of noise, one second of silence. This issue is not persistent in Chrome nor Opera. It is not a streaming issue (the song is streamed by the time it is played back in fact).

    I am wondering if this is an issue with the codec or with Firefox’s intrepretation of the codec, but more importantly, I want to know how to fix it. Some information about the file : the file is in OGG Vorbis format, 44100 Hz, 32 kbps Mono (yes, I am running out of storage space). It was encoded with SUPER, which in turn uses FFMpeg and MEncoder as necessary.

    This does not apply to all files of this format, making the issue even stranger. Are OGG Vorbis files over a certain length not allowed or interpreted differently by Firefox ? This must be the case for someone else and not just me...

    Any help is appreciated, thanks in advance !

  • ffmpeg : setting framerate changes also length

    21 février 2020, par planetmaker

    I’m creating videos from images sequences and I’d like to set the desired framerate of the resulting video file by the -r FPS flag with commands like

    ffmpeg -i %05d.bmp -r 30 -c:v h264 -vframes 780 -qscale:v 0 output.mp4

    However it seems that it does make a difference whether I set -r 30 or -r 60 in as much that the video ends earlier (thus less than specified 780 input images are used) the higher I set the framerate.

    The folder contains thousands of sequential images which follow the specified scheme %05d.bmp and I only need the first fixed-length part of this sequence - but at a higher frame rate than the default rate of 30fps.

    What part do I miss when trying to use the frame rate ? How do I set the FPS to a higher value but retaining the input length ?

  • avformat/matroskadec : Accept more unknown-length elements

    17 mai 2019, par Andreas Rheinhardt
    avformat/matroskadec : Accept more unknown-length elements
    

    The current Matroska specifications mandate that only two elements may
    use an unknown-length length : Segments and clusters. But this was not
    always so : For the greater part of Matroska's existence, all master
    elements were allowed to make use of the unknown-length feature.

    And there were muxers creating such files : For several years
    libavformat's Matroska muxer used unknown-length for all master
    elements when the output wasn't seekable. This only stopped in March
    2010 with 2529bb30. And even afterwards it was possible (albeit
    unlikely) for libavformat to create unknown-length master elements
    that are in violation of today's specifications, namely if the master
    element was so big that the seek backwards to update the size could
    no longer be performed inside the AVIOContext's write buffer. This
    has only been fixed in October 2016 (with the patches that introduced
    support for writing CRC-32 elements).

    Libavformat's Matroska demuxer meanwhile has never really supported
    unknown-length elements besides segments and clusters. Support for the
    latter was hardcoded. This commit changes this : Now all master elements
    for which a syntax to parse them is available are supported. This
    includes the files produced by old versions of libavformat's muxer.

    More precisely, master elements that have unknown length and are about
    to be parsed (not skipped) are supported ; only a warning is emitted for
    them. For normal files, this means that level 1 elements after the
    clusters that are encountered after the clusters have been parsed (i.e.
    not because they are referenced by the seekhead at the beginning of the
    file) are still unsupported (they would be skipped at this point if
    their length were known).

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/matroskadec.c