Recherche avancée

Médias (1)

Mot : - Tags -/stallman

Autres articles (59)

  • Gestion des droits de création et d’édition des objets

    8 février 2011, par

    Par défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

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

Sur d’autres sites (8516)

  • ffmpeg ios, decoding rtsp stream causes memory leak

    5 août 2013, par Simone M

    i have an ios application that stream a rtsp video via network using ffmpeg library.
    In random time i have a crash without error message, the only message in console is "Memory warning".
    Using instrument i detect some memory leaks, this link a screenshot about error : http://vincentvega.it/iphone/video.png, i think the problem is in the point of code where i make uiimage to show on screen :

    - (void)convertFrameToRGB
    {
       sws_scale(img_convert_ctx,
                 pFrame->data,
                 pFrame->linesize,
                 0,
                 pCodecCtx->height,
                 picture.data,
                 picture.linesize);

    }

    - (UIImage *)imageFromAVPicture:(AVPicture)pict width:(int)width height:(int)height
    {
       CGBitmapInfo bitmapInfo = kCGBitmapByteOrderDefault;
       CFDataRef data = CFDataCreateWithBytesNoCopy(kCFAllocatorDefault, pict.data[0], pict.linesize[0]*height,kCFAllocatorNull);
       CGDataProviderRef provider = CGDataProviderCreateWithCFData(data);
       CGColorSpaceRef colorSpace = CGColorSpaceCreateDeviceRGB();
       CGImageRef cgImage = CGImageCreate(width,
                                          height,
                                          8,
                                          24,
                                          pict.linesize[0],
                                          colorSpace,
                                          bitmapInfo,
                                          provider,
                                          NULL,
                                          NO,
                                          kCGRenderingIntentDefault);
       CGColorSpaceRelease(colorSpace);
       UIImage *image = [[UIImage alloc] initWithCGImage:cgImage];



       return [image autorelease];
    }

    how can i detect the function that causes memory problem ?

    SOLVED ! I just neeed to add the following code in "imagefromavcapture" :

    CGImageRelease(cgImage);
       CGDataProviderRelease(provider);
       CFRelease(data);
  • avformat/dashdec, hls : Update correct pointer to AVDictionary

    7 septembre 2020, par Andreas Rheinhardt
    avformat/dashdec, hls : Update correct pointer to AVDictionary
    

    open_url() in the DASH as well in the hls demuxer share a common bug :
    They modify an AVDictionary (i.e. set a new entry) given to them as
    AVDictionary *, yet if this new entry leads to reallocation and
    relocation of the AVDictionary, the caller's pointer will become
    dangling, leading to use-after-frees. So pass an AVDictionary **.

    (With the current implementation of AVDictionary the above can only
    happen if the AVDictionary was empty initially (in which case the
    new AVDictionary leaks) ; furthermore if the I/O is ordinary (i.e. opened
    by avio_open2() or ffio_open_whitelist()), the dict is never empty (it
    contains an rw_timeout entry from save_avio_options()). So this issue
    could only happen if the caller sets a nondefault io_open callback, but
    no AVIOContext (the AVFMT_FLAG_CUSTOM_IO flag won't be set in this
    case). In case of the HLS demuxer, it was also necessary that setting
    the "seekable" entry failed. Yet one should simply not rely on internals
    of the AVDict API.)

    Reviewed-by : Steven Liu <lq@chinaffmpeg.org>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavformat/dashdec.c
    • [DH] libavformat/hls.c
  • avfilter/vf_alphamerge : Fix double-free of AVFilterFormats on error

    7 août 2020, par Andreas Rheinhardt
    avfilter/vf_alphamerge : Fix double-free of AVFilterFormats on error
    

    The query_formats function of the alphamerge filter tries to allocate
    two lists of formats which on success are attached to more permanent
    objects (AVFilterLinks) for storage afterwards. If attaching a list
    to an AVFilterLink succeeds, the link becomes one of the owners of
    the list. Yet if attaching a list to one of its links succeeds and
    an error happens lateron, both lists were manually freed, which is wrong
    if the list is already owned by one or more links ; these links' pointers
    to their lists will become dangling and there will be a double-free/use-
    after-free when these links are cleaned up automatically.

    This commit fixes this by removing the custom freeing code ; this will
    temporarily add a leaking codepath (if attaching a list not already
    owned by a link to a link fails, the list will leak), but this will
    be fixed soon by making sure that an AVFilterFormats without owner will
    be automatically freed when attaching it to an AVFilterLink fails.
    At most one list leaks because as of this commit a new list is only
    allocated after the old list has been successfully attached to a link.

    Reviewed-by : Nicolas George <george@nsup.org>
    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>

    • [DH] libavfilter/vf_alphamerge.c