Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (67)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • 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

Sur d’autres sites (8632)

  • Crash in ffmpeg avcodec_free_context in one application but not in other

    5 novembre 2017, par geekowl

    I am building an application in C++ on Windows 10 using Microsoft Visual Studio 2012 Professional.

    I have created a wrapper library around ffmpeg (libavcodec) to encode video in H.264 format using libx264. This wrapper contains following functions :

    Initialize()
    
Open()
    
EncodeFrame()
    
Close()
    
Uninitialize()

    I created a test application to test the wrapper library. The test application works perfectly fine.

    When I use the wrapper library in my actual main application, the main application crashes in Close() API. Inside close, it crashes in avcodec_free_context(). The difference between the main application and the test application is that the main application links with some more dependent libraries that test application does not link with.

    To debug the problem in the main application, I put avcodec_free_context() in Open() after the context is allocated. The crash occurs if avcodec_free_context() is put at a certain point as shown below.

    pCodecContext = avcodec_alloc_context3(pCodec);
    

    
// <---- No crash here.
    

    
pCodecContext->bit_rate = 200000;
    
pCodecContext->width = 320;
    
pCodecContext->height = 240;
    
.
    
.
    
.
    
if (pCodec->id == AV_CODEC_ID_H264)
    
{
    
    av_opt_set(pCodecContext->priv_data, "preset", "slow", 0);
    
    av_opt_set(pCodecContext->priv_data, "tune", "zerolatency", 0);
    
}
    

    
pCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER;
    

    
// <-- No crash here
    

    
if (avcodec_open2(pCodecContext, pCodec, NULL) < 0)
    
{
    
    return -1;
    
}
    

    
// <-- Crash here [avcodec_free_context(&pCodecContext);]

    What is a correct approach to identify and resolve this problem ?

    Thanks in advance.

    Update

    I found out that ffmpeg was built using gcc. That was causing the crash. I rebuilt ffmpeg using Visual Studio. That solved problem.

  • Crash in ffmpeg avcodec_free_context in one application but not in other

    5 novembre 2017, par geekowl

    I am building an application in C++ on Windows 10 using Microsoft Visual Studio 2012 Professional.

    I have created a wrapper library around ffmpeg (libavcodec) to encode video in H.264 format using libx264. This wrapper contains following functions :

    Initialize()
    
Open()
    
EncodeFrame()
    
Close()
    
Uninitialize()

    I created a test application to test the wrapper library. The test application works perfectly fine.

    When I use the wrapper library in my actual main application, the main application crashes in Close() API. Inside close, it crashes in avcodec_free_context(). The difference between the main application and the test application is that the main application links with some more dependent libraries that test application does not link with.

    To debug the problem in the main application, I put avcodec_free_context() in Open() after the context is allocated. The crash occurs if avcodec_free_context() is put at a certain point as shown below.

    pCodecContext = avcodec_alloc_context3(pCodec);
    

    
// <---- No crash here.
    

    
pCodecContext->bit_rate = 200000;
    
pCodecContext->width = 320;
    
pCodecContext->height = 240;
    
.
    
.
    
.
    
if (pCodec->id == AV_CODEC_ID_H264)
    
{
    
    av_opt_set(pCodecContext->priv_data, "preset", "slow", 0);
    
    av_opt_set(pCodecContext->priv_data, "tune", "zerolatency", 0);
    
}
    

    
pCodecContext->flags |= CODEC_FLAG_GLOBAL_HEADER;
    

    
// <-- No crash here
    

    
if (avcodec_open2(pCodecContext, pCodec, NULL) < 0)
    
{
    
    return -1;
    
}
    

    
// <-- Crash here [avcodec_free_context(&pCodecContext);]

    What is a correct approach to identify and resolve this problem ?

    Thanks in advance.

    Update

    I found out that ffmpeg was built using gcc. That was causing the crash. I rebuilt ffmpeg using Visual Studio. That solved problem.

  • avformat/wtvenc : pad judiciously when writing mpeg2 extradata

    30 mars 2014, par Peter Ross
    avformat/wtvenc : pad judiciously when writing mpeg2 extradata

    Padding rule described here http://msdn.microsoft.com/en-us/library/windows/desktop/dd390707(v=vs.85).aspx
    

    Signed-off-by : Peter Ross <pross@xvid.org>
    
Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavformat/wtvenc.c
    • [DH] tests/ref/lavf/wtv
    • [DH] tests/ref/seek/lavf-wtv

Navigation