Recherche avancée

Médias (91)

Autres articles (72)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Ecrire une actualité

    21 juin 2013, par

    Présentez les changements dans votre MédiaSPIP ou les actualités de vos projets sur votre MédiaSPIP grâce à la rubrique actualités.
    Dans le thème par défaut spipeo de MédiaSPIP, les actualités sont affichées en bas de la page principale sous les éditoriaux.
    Vous pouvez personnaliser le formulaire de création d’une actualité.
    Formulaire de création d’une actualité Dans le cas d’un document de type actualité, les champs proposés par défaut sont : Date de publication ( personnaliser la date de publication ) (...)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (11266)

  • FFmpeg - concat videos error, do not match the corresponding output link ?

    18 février 2021, par wensefu

    I'm trying to concat some video into one single video using ffmpeg.

    



    input information :

    



    a.mp4 1920x808 , b.mkv 1280x720

    



    First I tried command below and it works fine :

    



    


    ffmpeg -i a.mp4 -i b.mkv -f lavfi -t 0.1 -i anullsrc -filter_complex [1:v]scale=1920:808:force_original_aspect_ratio=decrease,pad=1920:808 :(ow-iw)/2 :(oh-ih)/2[v1] ; [0:v][0:a][v1][1:a]concat=n=2:v=1:a=1[outv][outa] -map [outv] -map [outa] -vcodec libx264 -crf 27 -preset ultrafast -threads 2 out.mp4

    


    



    And then I put 'b.mkv' first :

    



    


    ffmpeg -i b.mkv -i a.mp4 -f lavfi -t 0.1 -i anullsrc -filter_complex [0:v]scale=1920:808:force_original_aspect_ratio=decrease,pad=1920:808 :(ow-iw)/2 :(oh-ih)/2[v0] ; [v0][0:a][1:v][1:a]concat=n=2:v=1:a=1[outv][outa] -map [outv] -map [outa] -vcodec libx264 -crf 27 -preset ultrafast -threads 2 out.mp4

    


    



    but this time I got error :

    



    


    Input link in1:v0 parameters (size 1920x808, SAR 0:1) do not match the corresponding output link in0:v0 parameters (1920x808, SAR 3232:3231)

    


    



    I don't understand why ?

    



    Any ideas anyone ?

    



    Many thanks in advance.

    


  • avcodec/ituh263dec : Make the condition for the studio slice start code match between...

    14 septembre 2019, par Michael Niedermayer
    avcodec/ituh263dec : Make the condition for the studio slice start code match between ff_h263_resync() and ff_mpeg4_decode_studio_slice_header()
    

    If they mismatch an infinite loop can occur
    Fixes : Timeout (infinite loop)
    Fixes : 17043/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_MPEG4_fuzzer-5695051748868096

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavcodec/ituh263dec.c
  • lavu/pixdesc : favour formats where depth and subsampling exactly match

    8 septembre 2022, par Philip Langdale
    lavu/pixdesc : favour formats where depth and subsampling exactly match
    

    Since introducing the various packed formats used by VAAPI (and p012),
    we've noticed that there's actually a gap in how
    av_find_best_pix_fmt_of_2 works. It doesn't actually assign any value
    to having the same bit depth as the source format, when comparing
    against formats with a higher bit depth. This usually doesn't matter,
    because av_get_padded_bits_per_pixel() will account for it.

    However, as many of these formats use padding internally, we find that
    av_get_padded_bits_per_pixel() actually returns the same value for the
    10 bit, 12 bit, 16 bit flavours, etc. In these tied situations, we end
    up just picking the first of the two provided formats, even if the
    second one should be preferred because it matches the actual bit depth.

    This bug already existed if you tried to compare yuv420p10 against p016
    and p010, for example, but it simply hadn't come up before so we never
    noticed.

    But now, we actually got a situation in the VAAPI VP9 decoder where it
    offers both p010 and p012 because Profile 3 could be either depth and
    ends up picking p012 for 10 bit content due to the ordering of the
    testing.

    In addition, in the process of testing the fix, I realised we have the
    same gap when it comes to chroma subsampling - we do not favour a
    format that has exactly the same subsampling vs one with less
    subsampling when all else is equal.

    To fix this, I'm introducing a small score penalty if the bit depth or
    subsampling doesn't exactly match the source format. This will break
    the tie in favour of the format with the exact match, but not offset
    any of the other scoring penalties we already have.

    I have added a set of tests around these formats which will fail
    without this fix.

    • [DH] libavutil/pixdesc.c
    • [DH] libavutil/pixdesc.h
    • [DH] libavutil/tests/pixfmt_best.c
    • [DH] libavutil/version.h
    • [DH] tests/ref/fate/pixfmt_best