Recherche avancée

Médias (91)

Autres articles (28)

  • Soumettre améliorations et plugins supplémentaires

    10 avril 2011

    Si vous avez développé une nouvelle extension permettant d’ajouter une ou plusieurs fonctionnalités utiles à MediaSPIP, faites le nous savoir et son intégration dans la distribution officielle sera envisagée.
    Vous pouvez utiliser la liste de discussion de développement afin de le faire savoir ou demander de l’aide quant à la réalisation de ce plugin. MediaSPIP étant basé sur SPIP, il est également possible d’utiliser le liste de discussion SPIP-zone de SPIP pour (...)

  • D’autres logiciels intéressants

    12 avril 2011, par

    On ne revendique pas d’être les seuls à faire ce que l’on fait ... et on ne revendique surtout pas d’être les meilleurs non plus ... Ce que l’on fait, on essaie juste de le faire bien, et de mieux en mieux...
    La liste suivante correspond à des logiciels qui tendent peu ou prou à faire comme MediaSPIP ou que MediaSPIP tente peu ou prou à faire pareil, peu importe ...
    On ne les connais pas, on ne les a pas essayé, mais vous pouvez peut être y jeter un coup d’oeil.
    Videopress
    Site Internet : (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

Sur d’autres sites (5172)

  • avfilter/dnn : Refactor DNN parameter configuration system

    7 mai 2024, par Zhao Zhili
    avfilter/dnn : Refactor DNN parameter configuration system
    

    This patch trying to resolve mulitiple issues related to parameter
    configuration :

    Firstly, each DNN filters duplicate DNN_COMMON_OPTIONS, which should
    be the common options of backend.

    Secondly, backend options are hidden behind the scene. It's a
    AV_OPT_TYPE_STRING backend_configs for user, and parsed by each
    backend. We don't know each backend support what kind of options
    from the help message.

    Third, DNN backends duplicate DNN_BACKEND_COMMON_OPTIONS.

    Last but not the least, pass backend options via AV_OPT_TYPE_STRING
    makes it hard to pass AV_OPT_TYPE_BINARY to backend, if not impossible.

    This patch puts backend common options and each backend options inside
    DnnContext to reduce code duplication, make options user friendly, and
    easy to extend for future usecase.

    For example,

    ./ffmpeg -h filter=dnn_processing

    dnn_processing AVOptions :
    dnn_backend <int> ..FV....... DNN backend (from INT_MIN to INT_MAX) (default tensorflow)
    tensorflow 1 ..FV....... tensorflow backend flag
    openvino 2 ..FV....... openvino backend flag
    torch 3 ..FV....... torch backend flag

    dnn_base AVOptions :
    model <string> ..F........ path to model file
    input <string> ..F........ input name of the model
    output <string> ..F........ output name of the model
    backend_configs <string> ..F.......P backend configs (deprecated)
    options <string> ..F.......P backend configs (deprecated)
    nireq <int> ..F........ number of request (from 0 to INT_MAX) (default 0)
    async <boolean> ..F........ use DNN async inference (default true)
    device <string> ..F........ device to run model

    dnn_tensorflow AVOptions :
    sess_config <string> ..F........ config for SessionOptions

    dnn_openvino AVOptions :
    batch_size <int> ..F........ batch size per request (from 1 to 1000) (default 1)
    input_resizable <boolean> ..F........ can input be resizable or not (default false)
    layout <int> ..F........ input layout of model (from 0 to 2) (default none)
    none 0 ..F........ none
    nchw 1 ..F........ nchw
    nhwc 2 ..F........ nhwc
    scale <float> ..F........ Add scale preprocess operation. Divide each element of input by specified value. (from INT_MIN to INT_MAX) (default 0)
    mean <float> ..F........ Add mean preprocess operation. Subtract specified value from each element of input. (from INT_MIN to INT_MAX) (default 0)

    dnn_th AVOptions :
    optimize <int> ..F........ turn on graph executor optimization (from 0 to 1) (default 0)

    Signed-off-by : Zhao Zhili <zhilizhao@tencent.com>
    Reviewed-by : Wenbin Chen <wenbin.chen@intel.com>
    Reviewed-by : Guo Yejun <yejun.guo@intel.com>

    • [DH] libavfilter/dnn/dnn_backend_common.h
    • [DH] libavfilter/dnn/dnn_backend_openvino.c
    • [DH] libavfilter/dnn/dnn_backend_tf.c
    • [DH] libavfilter/dnn/dnn_backend_torch.cpp
    • [DH] libavfilter/dnn/dnn_interface.c
    • [DH] libavfilter/dnn_filter_common.c
    • [DH] libavfilter/dnn_filter_common.h
    • [DH] libavfilter/dnn_interface.h
    • [DH] libavfilter/vf_derain.c
    • [DH] libavfilter/vf_dnn_classify.c
    • [DH] libavfilter/vf_dnn_detect.c
    • [DH] libavfilter/vf_dnn_processing.c
    • [DH] libavfilter/vf_sr.c
  • Is ffmpeg a good upscaler from SD to HD ? [closed]

    15 août 2014, par user3928079

    Is ffmpeg a good upscaler to convert SD videos to HD ?

    I use the AVANTI GUI. I installed it and put the ffmpeg and ffplay exe into the folder ffmpeg in the program folder. What I know is that you can only preserve the detail when you upscale from SD to HD. You don’t really gain any additional information. TV companies like Samsung, Sony, LG, Panasonic, Sharp, and others refuse to think so and push the boundaries of upscaling so that additional information can be added when the image is upscaled from SD to HD and HD to 4K and so on and so forth. I’ve run a test through the AVANTI ffmpeg GUI.

    Codec : XVID to H.264
    Bitrate : 1640 kbps to 6000 kbps
    Resolution : 640x480 to 1440x1080
    Format : AVI to M4V
    Audio Codec : AC3 to AAC
    Audio Bitrate : 192 kbps
    Audio Frequency : 48000 Hz
    Upscale method : Spline

    Will this upscale method work in any way with converting SD video to HD video. There’s a lot of SD content out that haven’t made the transition to, or probably never will be, HD.

  • How to change ffmpeg -threads settings [migrated]

    5 août 2014, par Jacob

    Working on a tube site. I’m running videos through ffmpeg on a linux dedicated server to convert to mp4.

    The server specs :

    Architecture:          x86_64
    CPU op-mode(s):        32-bit, 64-bit
    Byte Order:            Little Endian
    CPU(s):                8
    On-line CPU(s) list:   0-7
    Thread(s) per core:    2
    Core(s) per socket:    4
    Socket(s):             1
    NUMA node(s):          1
    Vendor ID:             GenuineIntel
    CPU family:            6
    Model:                 60
    Stepping:              3
    CPU MHz:               3491.749
    BogoMIPS:              6983.49
    Virtualization:        VT-x
    L1d cache:             32K
    L1i cache:             32K
    L2 cache:              256K
    L3 cache:              8192K
    NUMA node0 CPU(s):     0-7

    Issue during testing is that even only doing 4-5 at once, the server load skyrockets to an average of around 36. This is just a single person. I imagine when it opens, many people will be uploading at once.

    It seems ffmpeg tries to use all the resources available per conversion.

    I’ve heard there’s a -threads setting you can change, but I cannot find it. I have an 8 cpu server. It’s only used for conversions, so I’ve heard the best setting would be between 2 and 4. I can test it out.

    But how do I change this setting ? Everything I see online discusses this setting, but not the steps to change it.