Recherche avancée

Médias (91)

Autres articles (85)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • 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

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

  • Revision 60f9ebc3f1 : Enable variable block size test in non-RD mode decision This is an initial atte

    19 mars 2014, par Jingning Han

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


     Modify /vp9/encoder/vp9_onyx_if.c


     Modify /vp9/encoder/vp9_onyx_int.h


     Modify /vp9/encoder/vp9_pickmode.c



    Enable variable block size test in non-RD mode decision

    This is an initial attempt to allow variable block size partition
    in non-RD coding flow. It tests 8x8, 16x16 and 32x32 block size per
    64x64 block, all using non-RD mode decision and the associated rate
    distortion costs from modeling, then selects the best block size to
    encode the entire 64x64 block. Such operations are triggered every
    other 3 frames. The blocks of intermediate frames will reuse the
    collocated block's partition type.

    It improves the compression performance by 13.2%. Note that the gains
    are not evenly distributed. For many hard clips, the compression
    performance is improved by 20% to 28%. Local speed test shows that
    it will also increase runtime by 50%, as compared to speed -7. It is
    now enabled in speed -6 setting.

    Change-Id : Ib4fb8659d21621c9075b3c369ddaa9ecb0a4b204

  • Revision 74593c1eae : Directly split the block in partition search This patch allows the encoder to d

    5 août 2014, par Pengchong Jin

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



    Directly split the block in partition search

    This patch allows the encoder to directly split the block
    in partition search, therefore skip searching NONE. It
    computes a score which measures whether 16x16 motion vectors
    from the first pass in the current block are consistent with
    each others. If they are inconsistent and we have enough Q
    to encode, split the block directly, and skip searching NONE.

    This feature is under flag CONFIG_FP_MB_STATS. In speed 2,
    it further gives a speedup of 3-8% on sample yt clips as
    compared to the previous version under the same flag. Overall,
    the features under the flag will give 7-15% on typical yt
    clips at up to 6000kbps data rate. The speedup at very high
    data rate is not significant.

    For hard stdhd clips :
    park_joy_1080p @ 15000kbps : 504541ms -> 506293ms (-0.35%)
    pedestrian_area_1080p @ 2000kbps : 326610ms -> 290090ms (+11.2%)

    The compression performance using the features under the flag :
    derf : -0.068%
    yt : -0.189%
    hd : -0.318%
    stdhd :-0.183%

    To use the feature, set CONFIG_FP_MB_STATS and turn on
    cpi->use_fp_mb_stats.

    Change-Id : Iad58a2966515c8861aa9eb211565b1864048d47f

  • Can I use avcodec_free_context() on an opened context ?

    23 mars 2017, par Ashe the human

    The latest documentation says here that opening a context that’s closed again is not supported any more. I see why. Some codecs don’t work properly when they’re reopened. So after finding this bug, I decided to not use avcodec_close() and call avcodec_free_context() on the contexts right away instead.

    But I’m not sure if it’s safe to do so with 2.8.4, the version that I linked to my program. The documentation from that time doesn’t clarify. Does anyone know ? At least empirically ?

    ffmpeg version 2.8.4 Copyright (c) 2000-2015 the FFmpeg developers
    
built with Microsoft (R) C/C++ 최적화 컴파일러 버전 18.00.31101(x64)
    
configuration: --toolchain=msvc --enable-gpl --enable-nonfree --enable-nvenc --enable-libvorbis --enable-libmp3lame --enable-libtheora --enable-libx264 --enable-libx265 --enable-libxvid --enable-libopus --enable-libvpx --enable-static --disable-shared --disable-debug --extra-cflags=-MT --extra-cxxflags=-MT --extra-ldflags='/nodefaultlib:msvcrt.lib' --extra-libs='zlib.lib libogg_static.lib libvorbis_static.lib libmpghip-static.lib libmp3lame-static.lib libtheora_static.lib libx264.lib x265-static.lib libxvidcore.lib silk_fixed.lib silk_common.lib silk_float.lib celt.lib opus.lib vpxmt.lib'
    
libavutil      54. 31.100 / 54. 31.100
    
libavcodec     56. 60.100 / 56. 60.100
    
libavformat    56. 40.101 / 56. 40.101
    
libavdevice    56.  4.100 / 56.  4.100
    
libavfilter     5. 40.101 /  5. 40.101
    
libswscale      3.  1.101 /  3.  1.101
    
libswresample   1.  2.101 /  1.  2.101
    
libpostproc    53.  3.100 / 53.  3.100

    I know there’s a bunch of forums I could post on but I’d felt like to ask it here first.

Navigation