Recherche avancée

Médias (1)

Mot : - Tags -/bug

Autres articles (45)

  • La file d’attente de SPIPmotion

    28 novembre 2010, par

    Une file d’attente stockée dans la base de donnée
    Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
    Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...)

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

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

Sur d’autres sites (7167)

  • lavu/riscv : CPU flag for the Zbb extension

    2 octobre 2022, par Rémi Denis-Courmont
    lavu/riscv : CPU flag for the Zbb extension
    

    Unfortunately, it is common, and will remain so, that the Bit
    manipulations are not enabled at compilation time. This is an official
    policy for Debian ports in general (though they do not support RISC-V
    officially as of yet) to stick to the minimal target baseline, which
    does not include the B extension or even its Zbb subset.

    For inline helpers (CPOP, REV8), compiler builtins (CTZ, CLZ) or
    even plain C code (MIN, MAX, MINU, MAXU), run-time detection seems
    impractical. But at least it can work for the byte-swap DSP functions.

    • [DH] libavutil/cpu.c
    • [DH] libavutil/cpu.h
    • [DH] libavutil/riscv/cpu.c
    • [DH] tests/checkasm/checkasm.c
  • Compiling FFMPEG with libvpx on Mac OS X

    26 août 2014, par Dalvik

    I’m having hard timed trying to manually compile FFMPEG on my MAC. I’m trying to compile it with —enable-libvpx but keep getting this annoying error :

    ERROR: libvpx decoder version must be >=0.9.1"

    I’m compiling FFMPEG using this guide by ROMAN10 and this link from the FFMPEG official documentation. You can find the build script I’m using in ROMAN’s web page.

    Note : I’m working with HomeBrew because I found it easier and more convenient tool from which I can install all the core packages that ffmpeg requires(yasm,libogg,libvorbis and more).

    In an efforts to solve it I’ve try to fix ffmpeg’s ./configure file and notice that the link to libvpx is as follow :

    enabled libvpx            && {
    enabled libvpx_vp8_decoder && { check_lib2 "vpx/vpx_decoder.h vpx/vp8dx.h" vpx_codec_dec_init_ver -lvpx ||
                                   die "ERROR: libvpx decoder version must be >=0.9.1"; }
    enabled libvpx_vp8_encoder && { check_lib2 "vpx/vpx_encoder.h vpx/vp8cx.h" "vpx_codec_enc_init_ver VP8E_SET_MAX_INTRA_BITRATE_PCT" -lvpx ||
                                   die "ERROR: libvpx encoder version must be >=0.9.7"; }
    enabled libvpx_vp9_decoder && { check_lib2 "vpx/vpx_decoder.h vpx/vp8dx.h" "vpx_codec_vp9_dx" -lvpx || disable libvpx_vp9_decoder; }
    enabled libvpx_vp9_encoder && { check_lib2 "vpx/vpx_encoder.h vpx/vp8cx.h" "vpx_codec_vp9_cx VP9E_SET_AQ_MODE" -lvpx || disable libvpx_vp9_encoder; } }

    You can see that the method check_lib2 receives 2 params - the header path and the function’s name. Unfortunately even when I’m changing the path to a downloaded version of libvpx(which is much newer than 0.9.1) I’m still getting this error. Any help would be much appreciated.

  • opencv3.1 python VideoCapture black screen

    3 mai 2017, par alex

    i’m trying to use opencv3.1 with python3.5
    following this official)tutorial
    http://docs.opencv.org/3.0-beta/doc/py_tutorials/py_gui/py_video_display/py_video_display.html#display-video

    the camera led is "on" but the window doesn’t show any image (black)

    my current enviroment :
    - windows 10
    - python 3.5.2 (32bit)
    - numpy 1.12.0b1 (32bit) binaries downloaded from : http://www.lfd.uci.edu/ gohlke/pythonlibs/
    - opencv 3.1.0 (32bit) binaries downloaded from : http://www.lfd.uci.edu/ gohlke/pythonlibs/

    they seem installed correctly !

    as the tutorial says :

    Note Make sure proper versions of ffmpeg or gstreamer is installed. Sometimes, it is a headache to work with Video Capture mostly due to wrong installation of ffmpeg/gstreamer.

    i’ve no ffmpeg installed !!! so i suppose this is the cause of my problem
    so the questions are :
    1) which version of ffmpeg is needed ?
    2) how install ffmpeg on windows ? it seems a setup doesn’t exist(there is a binary section with a zip file ? how to use it after unzipped ?)
    3) is possible to see(in some way) if the opencv binaries(that i’ve downloaded) were compiled with ffmpeg support(flag ?)

    PS : i’ve tried to add the ffmpeg folder path the the PATH enviroment variable but nothing change