Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (51)

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

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

  • Encodage et transformation en formats lisibles sur Internet

    10 avril 2011

    MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
    Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
    Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)

Sur d’autres sites (8904)

  • movenc : Allow writing a DASH sidx atom at the start of files

    21 octobre 2014, par Martin Storsjö
    movenc : Allow writing a DASH sidx atom at the start of files

    This is mapped to the faststart flag (which in this case
    
perhaps should be called "shift and write index at the
    
start of the file"), which for fragmented files will
    
write a sidx index at the start.
    

    When segmenting DASH into files, there’s usually one sidx
    
at the start of each segment (although it’s not clear to me
    
whether that actually is necessary). When storing all of it
    
in one file, the MPD doesn’t necessarily need to describe
    
the individual segments, but the offsets of the fragments can be
    
fetched from one large sidx atom at the start of the file. This
    
allows creating files for the DASH ISO BMFF on-demand profile.
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DBH] libavformat/movenc.c
    • [DBH] libavformat/movenc.h

  • FFmpeg. avcodec_find_encoder(AV_CODEC_ID_H264) return false

    14 juillet 2016, par Иван Чванов

    The problem : I can not connect the h264 codec for encoding and decoding of frames.

    Description :

    I downloaded from here ffmpeg library https://ffmpeg.zeranoe.com/builds/, version dev.

    Connect it to your project QT :

    extern "C"
    
{
    
    #include 
    
    #include 
    
    #include 
    
    #include 
    
    #include 
    
}
    
    
    
#pragma comment (lib, "avcodec.lib")
    
#pragma comment (lib, "avformat.lib")
    
#pragma comment (lib, "swscale.lib")
    
#pragma comment (lib, "avutil.lib")

    Next prescribe av_register_all(); to include all codecs.

    Next, call the function : avcodec_find_encoder(AV_CODEC_ID_H264), returns false.

    In the ReadMe file, the library said that it was collected with —enable-libx264 and —enable-gpl compile the keys including h264 codec that is supposed to be.

    If the call : avcodec_find_encoder(AV_CODEC_ID_MPEG1VIDEO), it returns an object AVCodec, as it should.

    I use the MinGW compiler. OC Windows 7.

    How can I resolve or work around the problem ? Compile the library itself has not yet obtained. I understand you to connect sources and "poking" them, that too is meaningless.

    ** Once again, I will describe my problem : **

    I need to encode the codec h264 (can VP9) individual frames in one program, and then decode them in another program. You can use other libraries. The language C ++. It is necessary to use interframe compression codec, rather than simply pressed apart frames.

    Sorry for my english.

    Ideas. Advice. Suggestions.

  • FFmpeg. avcodec_find_encoder(AV_CODEC_ID_H264) return false

    14 juillet 2016, par Иван Чванов

    The problem : I can not connect the h264 codec for encoding and decoding of frames.

    Description :

    I downloaded from here ffmpeg library https://ffmpeg.zeranoe.com/builds/, version dev.

    Connect it to your project QT :

    extern "C"
    
{
    
    #include 
    
    #include 
    
    #include 
    
    #include 
    
    #include 
    
}
    
    
    
#pragma comment (lib, "avcodec.lib")
    
#pragma comment (lib, "avformat.lib")
    
#pragma comment (lib, "swscale.lib")
    
#pragma comment (lib, "avutil.lib")

    Next prescribe av_register_all(); to include all codecs.

    Next, call the function : avcodec_find_encoder(AV_CODEC_ID_H264), returns false.

    In the ReadMe file, the library said that it was collected with —enable-libx264 and —enable-gpl compile the keys including h264 codec that is supposed to be.

    If the call : avcodec_find_encoder(AV_CODEC_ID_MPEG1VIDEO), it returns an object AVCodec, as it should.

    I use the MinGW compiler. OC Windows 7.

    How can I resolve or work around the problem ? Compile the library itself has not yet obtained. I understand you to connect sources and "poking" them, that too is meaningless.

    ** Once again, I will describe my problem : **

    I need to encode the codec h264 (can VP9) individual frames in one program, and then decode them in another program. You can use other libraries. The language C ++. It is necessary to use interframe compression codec, rather than simply pressed apart frames.

    Sorry for my english.

    Ideas. Advice. Suggestions.

Navigation