Recherche avancée

Médias (1)

Mot : - Tags -/book

Autres articles (8)

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

  • Qu’est ce qu’un éditorial

    21 juin 2013, par

    Ecrivez votre de point de vue dans un article. Celui-ci sera rangé dans une rubrique prévue à cet effet.
    Un éditorial est un article de type texte uniquement. Il a pour objectif de ranger les points de vue dans une rubrique dédiée. Un seul éditorial est placé à la une en page d’accueil. Pour consulter les précédents, consultez la rubrique dédiée.
    Vous pouvez personnaliser le formulaire de création d’un éditorial.
    Formulaire de création d’un éditorial Dans le cas d’un document de type éditorial, les (...)

  • Selection of projects using MediaSPIP

    2 mai 2011, par

    The examples below are representative elements of MediaSPIP specific uses for specific projects.
    MediaSPIP farm @ Infini
    The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)

Sur d’autres sites (3311)

  • Warning "i686-mingw32-pkg-config not found, library detection may fail" while cross compiling ffmpeg

    1er juillet 2019, par S B

    I get the following warning while trying to cross compile ffmpeg as below

    $ ./configure --enable-gpl --enable-version3 --enable-libgsm --enable-libvorbis --enable-libtheora --enable-libspeex --enable-libmp3lame --enable-libopenjpeg --enable-libopencore_amrwb --enable-libopencore_amrnb --arch=x86 --enable-runtime-cpudetect --enable-static --disable-shared --enable-libxvid --enable-libx264 --target-os=mingw32 --enable-avisynth --enable-w32threads --cross-prefix=i686-mingw32- --cc='i686-mingw32-gcc' --enable-memalign-hack --disable-doc --enable-avfilter --disable-ffplay --disable-ffserver --disable-ffprobe

    Configure ran fine but with the following warning

    License: GPL version 3 or later
    
Creating config.mak and config.h...
    
libavutil/avconfig.h is unchanged
    

    
WARNING: i686-mingw32-pkg-config not found, library detection may fail.

    How do I provide i686-mingw32-pkg-config to configure ?

  • Cut detection with ffprobe

    8 juillet 2019, par Roman Volodin

    I’m trying to detect cuts between shots with ffprobe. I use the following command :

    ffprobe -show_frames -of compact=p=0 -f lavfi "movie=test_clip.avi,select=gt(scene\,.4)" > test_clip_cuts.txt

    It works just fine, there’s no question. But now I want to detect the cuts in certain range only. Let’s say from 3 to 8 seconds. How I could do that ?

    I tried to use -read_intervals 3%8 but it gave me an error :

    Could not seek to position 3000000: Invalid argument
    
Could not read packets in interval id:0 start:3 end:8

    Command -read_intervals %+3 (read from the very begining to 3rd second) works, but in weird way - it detects cuts up to 4th second (and over, I guess).

    So I’m confused. What are those "intervals" and how to use them ? Is it possible to set the range in regular seconds ?

    Just in case here is my test clip https://yadi.sk/i/nd-c12mYeQ2nb

  • fftools/ffprobe : add analyze_frames option for CC and grain detection

    8 décembre 2024, par Marth64
    fftools/ffprobe : add analyze_frames option for CC and grain detection

    Currently, ffprobe has two stream-level fields that do not work,
    
closed_captions and film_grain).
    

    Their value is always 0 because ffprobe cannot access the internal
    
codec properties when it is setting up its stream contexts.
    

    In this commit, add the new option -analyze_frames to ffprobe,
    
allowing the user to read frames up to the interval they have defined
    
and fill these fields based on what is exposed in AVPacketSideData.
    

    Additionally, in the same commit, don't write these fields to
    
the output unless analyze_frames is enabled. Finally, fix the
    
FATE test refs accordingly and update the docs.
    

    Signed-off-by : Marth64 <marth64@proxyid.net>
    • [DH] doc/ffprobe.texi
    • [DH] fftools/ffprobe.c
    • [DH] tests/ref/fate/cavs-demux
    • [DH] tests/ref/fate/concat-demuxer-extended-lavf-mxf
    • [DH] tests/ref/fate/concat-demuxer-extended-lavf-mxf_d10
    • [DH] tests/ref/fate/concat-demuxer-simple1-lavf-mxf
    • [DH] tests/ref/fate/concat-demuxer-simple1-lavf-mxf_d10
    • [DH] tests/ref/fate/concat-demuxer-simple2-lavf-ts
    • [DH] tests/ref/fate/ffprobe_compact
    • [DH] tests/ref/fate/ffprobe_csv
    • [DH] tests/ref/fate/ffprobe_default
    • [DH] tests/ref/fate/ffprobe_flat
    • [DH] tests/ref/fate/ffprobe_ini
    • [DH] tests/ref/fate/ffprobe_json
    • [DH] tests/ref/fate/ffprobe_xml
    • [DH] tests/ref/fate/ffprobe_xsd
    • [DH] tests/ref/fate/flv-demux
    • [DH] tests/ref/fate/hapqa-extract-nosnappy-to-hapalphaonly-mov
    • [DH] tests/ref/fate/hapqa-extract-nosnappy-to-hapq-mov
    • [DH] tests/ref/fate/mov-zombie
    • [DH] tests/ref/fate/mxf-probe-applehdr10
    • [DH] tests/ref/fate/mxf-probe-d10
    • [DH] tests/ref/fate/mxf-probe-dnxhd
    • [DH] tests/ref/fate/mxf-probe-dv25
    • [DH] tests/ref/fate/mxf-probe-j2k
    • [DH] tests/ref/fate/ts-demux
    • [DH] tests/ref/fate/ts-small-demux

Navigation