Recherche avancée

Médias (0)

Mot : - Tags -/organisation

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

Autres articles (81)

  • Ajouter des informations spécifiques aux utilisateurs et autres modifications de comportement liées aux auteurs

    12 avril 2011, par

    La manière la plus simple d’ajouter des informations aux auteurs est d’installer le plugin Inscription3. Il permet également de modifier certains comportements liés aux utilisateurs (référez-vous à sa documentation pour plus d’informations).
    Il est également possible d’ajouter des champs aux auteurs en installant les plugins champs extras 2 et Interface pour champs extras.

  • Problèmes fréquents

    10 mars 2010, par

    PHP et safe_mode activé
    Une des principales sources de problèmes relève de la configuration de PHP et notamment de l’activation du safe_mode
    La solution consiterait à soit désactiver le safe_mode soit placer le script dans un répertoire accessible par apache pour le site

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (12984)

  • Reduce Bandwidth requirement for Video Streaming

    19 février 2014, par user3239282

    Please suggest some points on, how to reduce the bandwidth requirement for a video stream.

    We are actually streaming the desktop across internet, Remote Access Application.

    Encoder : libx264.lib

    Decoder : Ffmpeg

    Codec : H264

    Following is how am configuring h264 for encoding :

        x264_param_default_preset(&this->m_x264Settings, "veryfast", "zerolatency");
    
    this->m_x264Settings.i_threads = 1;
    
    this->m_x264Settings.i_width = width / 2;
    
    this->m_x264Settings.i_height = height / 2;
    
    this->m_x264Settings.i_keyint_max = 10;//fps;
    
    this->m_x264Settings.b_intra_refresh = 1;
    
    this->m_x264Settings.i_fps_num = 10;
    
    this->m_x264Settings.i_fps_den = 1;
    
    // Intra refres:
    
    this->m_x264Settings.i_keyint_max = 25;
    
    this->m_x264Settings.b_intra_refresh = 1;
    
    //Rate control:
    
    this->m_x264Settings.rc.i_rc_method = X264_RC_CRF;
    
    this->m_x264Settings.rc.f_rf_constant = 25;
    
    this->m_x264Settings.rc.f_rf_constant_max = 35;
    

    
    //For streaming:
    
    this->m_x264Settings.b_repeat_headers = 1;
    
    this->m_x264Settings.b_annexb = 1;
    
    x264_param_apply_profile(&this->m_x264Settings, "baseline");
    

    
    this->m_width = width;
    
    this->m_height = height;
    
    this->m_encoder = x264_encoder_open(&this->m_x264Settings);
    
    x264_picture_alloc(&this->m_picIn,X264_CSP_I420,(width / 2),(height / 2));
    
    int sws_flags = SWS_BICUBIC;
    
    m_imgConverCtx = sws_getContext(width, height, PIX_FMT_RGB32, (width/2), (height/2), PIX_FMT_YUV420P,sws_flags, NULL, NULL, NULL);

    Thanks in advance,
    Paul.

  • ppc : reduce overreads when loading 8 pixels in altivec dsp functions

    13 février 2014, par Janne Grunau
    ppc : reduce overreads when loading 8 pixels in altivec dsp functions

    Altivec can only load naturally aligned vectors. To handle possibly
    
unaligned data a second vector is loaded from an offset of the original
    
location and the data is recovered through a vector permutation.
    
Overreads are minimal if the offset for second load points to the last
    
element of data. This is 7 for loading eight 8-bit pixels and overreads
    
are reduced from 16 bytes to 8 bytes if the pixels are 64-bit aligned.
    
For unaligned pixels the overread is reduced from 23 bytes to 15 bytes
    
in the worst case.
    • [DH] libavcodec/ppc/dsputil_altivec.c

  • ppc : reduce overreads when loading 8 pixels in altivec dsp functions

    13 février 2014, par Janne Grunau
    ppc : reduce overreads when loading 8 pixels in altivec dsp functions

    Altivec can only load naturally aligned vectors. To handle possibly
    
unaligned data a second vector is loaded from an offset of the original
    
location and the data is recovered through a vector permutation.
    
Overreads are minimal if the offset for second load points to the last
    
element of data. This is 7 for loading eight 8-bit pixels and overreads
    
are reduced from 16 bytes to 8 bytes if the pixels are 64-bit aligned.
    
For unaligned pixels the overread is reduced from 23 bytes to 15 bytes
    
in the worst case.
    • [DBH] libavcodec/ppc/dsputil_altivec.c

Navigation