Recherche avancée

Médias (1)

Mot : - Tags -/ticket

Autres articles (51)

  • Other interesting software

    13 avril 2011, par

    We don’t claim to be the only ones doing what we do ... and especially not to assert claims to be the best either ... What we do, we just try to do it well and getting better ...
    The following list represents softwares that tend to be more or less as MediaSPIP or that MediaSPIP tries more or less to do the same, whatever ...
    We don’t know them, we didn’t try them, but you can take a peek.
    Videopress
    Website : http://videopress.com/
    License : GNU/GPL v2
    Source code : (...)

  • Contribute to translation

    13 avril 2011

    You can help us to improve the language used in the software interface to make MediaSPIP more accessible and user-friendly. You can also translate the interface into any language that allows it to spread to new linguistic communities.
    To do this, we use the translation interface of SPIP where the all the language modules of MediaSPIP are available. Just subscribe to the mailing list and request further informantion on translation.
    MediaSPIP is currently available in French and English (...)

  • Contribute to a better visual interface

    13 avril 2011

    MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
    Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.

Sur d’autres sites (7341)

  • Revision a801f7a295 : Increase border size from 96 to 160. This is required because upon downscaling,

    12 juillet 2013, par Ronald S. Bultje

    Changed Paths :
     Modify /vpx_scale/yv12config.h



    Increase border size from 96 to 160.

    This is required because upon downscaling, if a motion vector points
    partially into the UMV (e.g. all minus 1 of 64+7 pixels, i.e. 70),
    then we can point up to 140 pixels into the larger-resolution (2x)
    reference buffer UMV, which means the UMV for reference buffers in
    downscaling needs to be 140 rounded up to the nearest multiple of 32,
    i.e. 160.

    Longer-term, we should probably handle the UMV differently by detecting
    edge coverage on-the-fly and using a temporary buffer for edge extensions
    instead of adding 160 pixels on all sides of the image (which means a
    CIF image uses 3x its own area size for borders).

    Change-Id : I5184443e6731cd6721fc6a5d430a53e7d91b4f7e

  • How to configure B-frames (no leading P-frames) in x265

    5 mars 2020, par Alearner

    I have been rolling around with my studies in x265 encoder for days. Guess now I get better click on how x265 works than my first day. I usually use the HEVC reference software, and so think I am too comfortable with its environment because now I cannot figure out how to set the x265 encoder to code only I- and B-frames as if the Random Access or Low-Delay-B configurations in HEVC.

    I set my encoder with this CLI option to encode 500 frames of BasketballPass sequence :

    --input BasketballPass_416x240_50.yuv --input-res 416x240 --fps 50 --frames 500 --rd 4 --no-lossless --csv-log-level 2 --csv infoQP37.csv --no-wpp --psnr --ssim -b 16 --b-pyramid 0 --b-adapt 0 --keyint 48

    Instead of get only I- and B-frames encoded, P-frames also show up in my log file :

    Enc.order Type      POC
    
0         I-SLICE   0
    
**1       P-SLICE   17**
    
2         B-SLICE   9
    
3         b-SLICE   1
    
4         b-SLICE   2
    
5         b-SLICE   3
    
6         b-SLICE   4
    
7         b-SLICE   5
    
8         b-SLICE   6
    
9         b-SLICE   7
    
10        b-SLICE   8
    
11        b-SLICE   10
    
12        b-SLICE   11
    
13        b-SLICE   12
    
14        b-SLICE   13
    
15        b-SLICE   14
    
16        b-SLICE   15
    
17        b-SLICE   16
    
**18          P-SLICE   34**
    
19        B-SLICE   26
    
20        b-SLICE   18
    
21        b-SLICE   19
    
22        b-SLICE   20
    
23        b-SLICE   21
    
24        b-SLICE   22
    
25        b-SLICE   23
    
26        b-SLICE   24
    
27        b-SLICE   25
    
28        b-SLICE   27
    
29        b-SLICE   28
    
30        b-SLICE   29
    
31        b-SLICE   30
    
32        b-SLICE   31
    
33        b-SLICE   32
    
34        b-SLICE   33
    
35        i-SLICE   48
    
......

    My question is, can the x265 configure encoder as in RA or LDB of HEVC ? If yes, I’d appreciate any guidance to do it. Or How can we encode only I- and B-frame only (without P-frame) in x265 ?

  • Is there a built-in audio preprocessing within Android OS ?

    29 août 2022, par Larry lu

    I am running a dev team to build an Android application the major feature is to record a user's voice and merge it into a long movie. It's a dub film application.

    


    One struggle thing to my dev team is whether the Android OS pre-processes the recorded audio file. because we want the very original audio data from the built-in Microphone.
If there is a built-in pre-processing inside of Android OS that keeps updating some data of the recorded audio file, we want to know what is changed. We can't find any official post from Android speaking about it but would like to confirm from a professional.

    


    Many thanks

    


Navigation