Recherche avancée

Médias (0)

Mot : - Tags -/performance

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

Autres articles (22)

  • Déploiements possibles

    31 janvier 2010, par

    Deux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
    L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
    Version mono serveur
    La version mono serveur consiste à n’utiliser qu’une (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

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

Sur d’autres sites (5155)

  • How do I rotate yuv/rgb image using libav

    21 novembre 2014, par tan

    I want to rotate an image I just decoded using libav h.264 decoder.

    I see that ffmpeg has this option -vf transpose to do it. but I want to do it programatically. I see that there is a vf_transpose.c in libavfilter which looks like does the same thing.

    I want to know how I can exercise it in my code ?

    EDIT :

    Here is the sample code I use to do the decoding: :

    AVCodec *decHd;
    
AVCodecContext *ctxDecode = NULL;
    
AVFrame *pictureDecoded;
    
AVPacket avPkt;
    

    
/* --------
    
    setup
    
   -------- */
    

    
    avcodec_init();
    

    
    /* register all the codecs */
    
    avcodec_register_all();
    
    decHd = avcodec_find_decoder(CODEC_ID_H264);
    

    
    ctxDecode= avcodec_alloc_context();
    

    
    avcodec_get_context_defaults(ctxDecode);
    
    ctxDecode->flags2 |= CODEC_FLAG2_FAST;
    
    ctxDecode->pix_fmt = PIX_FMT_YUV420P;
    
    ctxDecode->width = CAP_WIDTH;
    
    ctxDecode->height = CAP_HEIGHT;
    

    
    if (avcodec_open(ctxDecode, decHd) < 0) 
    
    {
    
        printf("avcodec: could not open h.264 decoder\n");
    
        exit(1);
    
    }
    

    
    pictureDecoded= avcodec_alloc_frame();
    
    avcodec_get_frame_defaults(pictureDecoded);
    

    
/* --------
    
   decode
    
   -------- */
    

    
    avPkt.size = encOutLen;
    
    avPkt.data = nals[0].p_payload;
    
    len = avcodec_decode_video2(ctxDecode, pictureDecoded, &got_picture, &avPkt);
    

    
    len = avpicture_layout((AVPicture *)pictureDecoded, ctxDecode->pix_fmt
    
            , CAP_WIDTH, CAP_HEIGHT, decoderOut, PIC_SIZE);

  • checkasm/x86 : Correctly handle variadic functions

    23 septembre 2015, par Henrik Gramner
    checkasm/x86 : Correctly handle variadic functions

    The System V ABI on x86-64 specifies that the al register contains an upper
    
bound of the number of arguments passed in vector registers when calling
    
variadic functions, so we aren’t allowed to clobber it.
    

    checkasm_fail_func() is a variadic function so also zero al before calling it.
    

    Signed-off-by : Anton Khirnov <anton@khirnov.net>
    • [DBH] tests/checkasm/x86/checkasm.asm

  • How to open file name contain special characters in FFmpeg ?

    28 janvier 2015, par Alen Lee

    my project process the video by FFmpeg libarary, I test the my code with file which the file name contains special characters(like ’()+,-.09@A[]^_`a{} ®,Ѐ,ऄ, ఆ, Ⴀ,ᐁ,ᣀ,ᴀ,₠,⓪,⭙,ⶀ,㈀,啊.mp4’), but it failed to open the video stream at avformat_open_input().

    I test it via ffmpeg.exe with command line, it can open the file successfully.

    This is my code snippet :

        AVFormatContext *pFormatCtx = NULL;
    
    AVCodecContext  *pCodecCtx = NULL;
    
    AVFrame         *pFrameRGB = NULL;
    
    unsigned int    i, videoStream;
    
    AVCodec         *pCodec;
    
    AVFrame         *pFrame;
    
    AVPacket        packet;
    
    int             frameFinished;
    
    int             numBytes;
    
    uint8_t         *buffer;
    
    AVPixelFormat   ImgFmt = AV_PIX_FMT_YUV420P;
    

    
    // Register all formats and codecs
    
    av_register_all();
    

    
    // Open video file
    
    if (avformat_open_input(&amp;pFormatCtx, inputFilePath, NULL, NULL) != 0)
    
    {
    
        printf("Couldn't open file.");
    
        return -1;
    
    }

    it occur error at the avformat_open_input(), I think it failed because of the Unicode file name string

    Anybody can help me ?

    Thanks

Navigation