Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (40)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 is the first MediaSPIP stable release.
    Its official release date is June 21, 2013 and is announced here.
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (6819)

  • detecting a timeout in ffmpeg

    19 mai 2015, par Sean

    I am writing some software that uses ffmpeg extensively and it is multi threaded, with multiple class instances.

    If the network connection drops out ffmpeg hangs on reading. I found a method to assign a callback that ffmpeg fires periodically to check if it should abort or not :

    static int interrupt_cb(void *ctx) 
    
{ 
    

    
// do something 
    
    return 0;
    
} 
    

    
static const libffmpeg::AVIOInterruptCB int_cb = { interrupt_cb, NULL };

    ...

    AVFormatContext* formatContext = libffmpeg::avformat_alloc_context( );
    
formatContext->interrupt_callback = int_cb; 
    
if ( libffmpeg::avformat_open_input( &formatContext, fileName, NULL, NULL ) !=0 ) {...}

    This is all fine but nowhere on the web can i find what *ctx contains and how to determine whether the callback should return 1 or 0. I can’t assign a static "abort" flag as the class has many instances. I also can’t debug the code as for some reason visual studio refuses to set a breakpoint on the return 0 ; line, claiming no executable code is associated with the location. Any ideas ?

  • FFmpeg seeking in Mpeg4 streams

    4 juillet 2012, par Chris Robinson

    I am currently attempting to develop a player that can perform accurate seeking based on an mpeg4 elementary video stream. I'm in the planning stage and trying to decide how to go about things and I'd like some advice before I start.
    Some things to note are :

    • I will have complete control over the encoding of the file.
    • The original content will be I-frame only
    • FFmpeg is the encoding/decoding library
    • Audio can be disregarded for now. I will only be dealing with the video stream.
    • Frame accurate seeking must be implemented

    So, when I'm encoding the content, can I query what type of frame (I, P, B) has been encoded so I can construct an additional index stream for the seeking operation. If not, I can query the GOP after it has been encoded to find the I-frame.

    As for playback, the user needs to be able to type in a specific time and go to that frame (the nearest I-frame will be suitable for now). We can assume that the GOP is closed and the length is fairly short (e.g. 15 frames). My thoughts are to query the index stream that I created during encode and determine the relevant distance into the stream for the requested time.

    I'm not sure how to seek using the FFMpeg library when playing back files.

    Has anyone done anything similar and if so, can you give a brief explanation of how you did it ?

  • Revision 65b93c7e52 : Improved auto_partition_range. The code now takes into account temporal and spa

    27 septembre 2013, par Paul Wilkins

    Changed Paths :
     Modify /vp9/encoder/vp9_encodeframe.c


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h



    Improved auto_partition_range.

    The code now takes into account temporal and spatial
    information to determine the partition size range, but the
    frequency counts have been removed.

    The net effect is similar in quality but about 10% faster.

    Change-Id : I39a513fb79cec9177b73b2a7218f0da70963ae95

Navigation