Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (45)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

  • 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

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (9312)

  • avformat_open_input fails only with a custom IO context

    19 janvier 2017, par Tim

    Running into an odd issue with avformat_open_input, it is failing with :

    Invalid data found when processing input

    But this only happens when I attempt to read the file using a custom AVIOContext.

    My custom code is as follows (error checking omitted for clarity) :

    auto fmtCtx = avformat_alloc_context();
    
auto ioBufferSize = 32768;
    
auto ioBuffer = (unsigned char *)av_malloc(ioBufferSize);
    
auto ioCtx = avio_alloc_context(ioBuffer,
    
                                ioBufferSize,
    
                                0,
    
                                reinterpret_cast<void>(this),
    
                                &amp;imageIORead,
    
                                NULL,
    
                                &amp;imageIOSeek));
    

    
fmtCtx -> pb = ioCtx;
    
fmtCtx -> flags |= AVFMT_FLAG_CUSTOM_IO;
    

    
int err = avformat_open_input(&amp;fmtCtx, NULL, NULL, NULL);
    
</void>

    imageIOSeek is never called, but properly handles the whence parameter including the AVSEEK_SIZE option. My file data is already loaded in memory, so imageIORead is trivial (returning 0 at EOF) :

    int imageIORead(void *opaque, uint8_t *buf, int buf_size) {
    
    Image *d = (Image *)buf;
    
    int rc = std::min(buf_size, static_cast<int>(d->data.size() - d->pos));
    

    
    memcpy(buf, d->data.data() + d->pos, rc);
    
    d->pos += rc;
    
    return rc;
    
}
    
</int>

    The data being read is loaded from a file on disk :

    /tmp/25.jpeg

    The following code is able to open and extract the image correctly :

    auto fmtCtx = avformat_alloc_context();
    
int err = avformat_open_input(&amp;fmtCtx, "/tmp/25.jpeg", NULL, NULL);

    The project is using a minified version of libavformat including only the formats we need. I don’t believe this is the cause of the problem since the file can be open and handled properly when the path is specified. I haven’t seen any configure options specifically targeting support for custom IO contexts.

    This is the image in question : 25.jpeg

  • avformat_open_input fails only with a custom IO context

    2 juin 2017, par Tim

    Running into an odd issue with avformat_open_input, it is failing with :

    Invalid data found when processing input

    But this only happens when I attempt to read the file using a custom AVIOContext.

    My custom code is as follows (error checking omitted for clarity) :

    auto fmtCtx = avformat_alloc_context();
    
auto ioBufferSize = 32768;
    
auto ioBuffer = (unsigned char *)av_malloc(ioBufferSize);
    
auto ioCtx = avio_alloc_context(ioBuffer,
    
                                ioBufferSize,
    
                                0,
    
                                reinterpret_cast<void>(this),
    
                                &amp;imageIORead,
    
                                NULL,
    
                                &amp;imageIOSeek));
    

    
fmtCtx -> pb = ioCtx;
    
fmtCtx -> flags |= AVFMT_FLAG_CUSTOM_IO;
    

    
int err = avformat_open_input(&amp;fmtCtx, NULL, NULL, NULL);
    
</void>

    imageIOSeek is never called, but properly handles the whence parameter including the AVSEEK_SIZE option. My file data is already loaded in memory, so imageIORead is trivial (returning 0 at EOF) :

    int imageIORead(void *opaque, uint8_t *buf, int buf_size) {
    
    Image *d = (Image *)buf;
    
    int rc = std::min(buf_size, static_cast<int>(d->data.size() - d->pos));
    

    
    memcpy(buf, d->data.data() + d->pos, rc);
    
    d->pos += rc;
    
    return rc;
    
}
    
</int>

    The data being read is loaded from a file on disk :

    /tmp/25.jpeg

    The following code is able to open and extract the image correctly :

    auto fmtCtx = avformat_alloc_context();
    
int err = avformat_open_input(&amp;fmtCtx, "/tmp/25.jpeg", NULL, NULL);

    The project is using a minified version of libavformat including only the formats we need. I don’t believe this is the cause of the problem since the file can be open and handled properly when the path is specified. I haven’t seen any configure options specifically targeting support for custom IO contexts.

    This is the image in question : 25.jpeg

  • avformat/mxfenc : allow more bits for variable part in uuid generation

    14 mars 2022, par Marton Balint
    avformat/mxfenc : allow more bits for variable part in uuid generation

    Also make sure we do not change the product UID.
    

    Signed-off-by : Marton Balint <cus@passwd.hu>
    • [DH] libavformat/mxfenc.c
    • [DH] tests/ref/fate/copy-trac4914
    • [DH] tests/ref/fate/mxf-d10-user-comments
    • [DH] tests/ref/fate/mxf-opatom-user-comments
    • [DH] tests/ref/fate/mxf-reel_name
    • [DH] tests/ref/fate/mxf-user-comments
    • [DH] tests/ref/fate/time_base
    • [DH] tests/ref/lavf/mxf
    • [DH] tests/ref/lavf/mxf_d10
    • [DH] tests/ref/lavf/mxf_dv25
    • [DH] tests/ref/lavf/mxf_dvcpro50
    • [DH] tests/ref/lavf/mxf_opatom
    • [DH] tests/ref/lavf/mxf_opatom_audio

Navigation