Recherche avancée

Médias (0)

Mot : - Tags -/serveur

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (57)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

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

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (6994)

  • ffmpeg ... "Impossible to convert between the formats supported by the filter"

    27 novembre 2017, par hydra3333

    Using the latest ffmpeg master built as at 2017.11.26, I’m having trouble deciphering what the error messages means and, more importantly, what to do about them.

    Changing from -vf to -filter_complex did nothing (I had to try).
    The main error message seems to be

    Impossible to convert between the formats supported by the filter

    I have tried to insert "format=" and "scale" before/between/after yadif and unsharp_opencl but to no avail.

    I wonder, could it be something to do with needing hwupload/hwdownload/hwmap or is that a red herring ?

    What am I doing wrong ?

    ".\ffmpeg_3.latest_master.exe" -hide_banner -v verbose -init_hw_device opencl=ocl:1.0 -filter_hw_device ocl -i ".\test_01.mpg" -an -map_metadata -1 -sws_flags lanczos+accurate_rnd+full_chroma_int+full_chroma_inp -filter_complex "[0:v]yadif=0:0:0,scale=flags=lanczos+accurate_rnd+full_chroma_int+full_chroma_inp,unsharp_opencl=lx=3:ly=3:la=0.5:cx=3:cy=3:ca=0.5,setdar=dar=16/9" -r 25 -c:v h264_nvenc -preset slow -bf 2 -g 50 -refs 3 -rc:v vbr_hq -rc-lookahead:v 32 -cq 22 -qmin 16 -qmax 25 -coder cabac -movflags +faststart -profile:v high -level 4.1 -pixel_format yuv420p -y ".\test_01.newest.MP4"
    [AVHWDeviceContext @ 0000020e229aad40] 1.0: NVIDIA CUDA / GeForce GTX 750 Ti
    [AVHWDeviceContext @ 0000020e229aad40] DXVA2 to OpenCL mapping function found (clCreateFromDX9MediaSurfaceKHR).
    [AVHWDeviceContext @ 0000020e229aad40] DXVA2 in OpenCL acquire function found (clEnqueueAcquireDX9MediaSurfacesKHR).
    [AVHWDeviceContext @ 0000020e229aad40] DXVA2 in OpenCL release function found (clEnqueueReleaseDX9MediaSurfacesKHR).
    [AVHWDeviceContext @ 0000020e229aad40] The cl_khr_d3d11_sharing extension is required for D3D11 to OpenCL mapping.
    [AVHWDeviceContext @ 0000020e229aad40] D3D11 to OpenCL mapping not usable.
    [mpeg @ 0000020e229ae240] max_analyze_duration 5000000 reached at 5000000 microseconds st:0
    Input #0, mpeg, from '.\test_01.mpg':
     Duration: 00:06:29.96, start: 0.240000, bitrate: 2799 kb/s
       Stream #0:0[0x1e0]: Video: mpeg2video (Main), 1 reference frame, yuv420p(tv, top first, left), 720x576 [SAR 64:45 DAR 16:9], 25 fps, 25 tbr, 90k tbn, 50 tbc
       Stream #0:1[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16p, 256 kb/s
    [Parsed_scale_1 @ 0000020e29951a20] w:iw h:ih flags:'lanczos+accurate_rnd+full_chroma_int+full_chroma_inp' interl:0
    Stream mapping:
     Stream #0:0 (mpeg2video) -> yadif
     setdar -> Stream #0:0 (h264_nvenc)
    Press [q] to stop, [?] for help
    [Parsed_scale_1 @ 0000020e29cccda0] w:iw h:ih flags:'lanczos+accurate_rnd+full_chroma_int+full_chroma_inp' interl:0
    [graph 0 input from stream 0:0 @ 0000020e29ccc980] w:720 h:576 pixfmt:yuv420p tb:1/90000 fr:25/1 sar:64/45 sws_param:flags=2
    [auto_scaler_0 @ 0000020e29ccc580] w:iw h:ih flags:'bilinear' interl:0
    [Parsed_unsharp_opencl_2 @ 0000020e29ccc4a0] auto-inserting filter 'auto_scaler_0' between the filter 'Parsed_scale_1' and the filter 'Parsed_unsharp_opencl_2'
    Impossible to convert between the formats supported by the filter 'Parsed_scale_1' and the filter 'auto_scaler_0'
    Error reinitializing filters!
    Failed to inject frame into filter network: Function not implemented
    Error while processing the decoded data for stream #0:0
    Conversion failed!
  • dashenc : Don't output frameRates at both AS and Representation-level. Only output...

    29 octobre 2017, par Anton Schubert
    dashenc : Don't output frameRates at both AS and Representation-level. Only output maxFrameRate at AS-level.
    

    Fix conformance regarding section "3.2.4. Presence of Attributes and
    Element" of the "Guidelines for Implementation : DASH-IF Interoperability
    Points V4.1" (http://dashif.org/guidelines/)

    Signed-off-by : Anton Schubert <ischluff@mailbox.org>
    Signed-off-by : Peter Große <pegro@friiks.de>
    Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>

    • [DH] libavformat/dashenc.c
  • How to avoid the "text relocation" error by ffmpeg library on Android x86

    16 octobre 2017, par Tank2005

    My environment is Qt 5.9 for Android on Windows 10 64bit. NDK is r10e and SDK Level is 16(Those sdks are recommended version by Qt development team).

    I built a ffmpeg 3.4 source code as .so files on Ubuntu 16.04.3 LTS. Those library has no error on ARM architecture Android. But, on x86 Emulator, "Text realocations" alart is shown like this.

    text relocations

    I rewrite configure with "disable-asm, disable-yasm" referd from this site’s old posts.

    This hereby removed some errors. But only one library has a problem.
    text relocations

    I also tried the method of deleting "strtod.o", But it seems no effect. My current build configure is that. Does anyone know a better way ?

    #!/bin/bash
    NDK=/home/my/data/ndk
    SYSROOT=$NDK/platforms/android-14/arch-x86/
    TOOLCHAIN=$NDK/linux-x86-48
    CPU=x86
    PREFIX=$(pwd)/android/x86
    PATH=$TOOLCHAIN/bin:$PATH

    function build_one
    {
    ./configure \
       --cc="$TOOLCHAIN/bin/i686-linux-android-gcc-4.8" \
       --enable-cross-compile \
       --target-os=linux \
       --arch=x86 \
       --prefix=$PREFIX \
       --enable-shared \
       --disable-static \
       --disable-avdevice \
       --disable-doc \
       --disable-encoders \
       --disable-decoders \
       --enable-decoder=h264 \
       --enable-decoder=aac \
       --disable-protocols \
       --disable-demuxers \
       --disable-muxers \
       --disable-filters \
       --disable-network \
       --disable-ffplay \
       --disable-ffmpeg \
       --disable-ffprobe \
       --disable-ffserver \
       --enable-parsers \
       --cross-prefix=i686-linux-android- \
       --enable-cross-compile \
       --target-os=linux \
       --arch=x86 \
       --disable-doc \
       --sysroot=$SYSROOT \
       --disable-x86asm -disable-yasm --enable-pic \
       --extra-cflags="-std=c99 -O3 -Wall -fpic -pipe -DANDROID -DNDEBUG -march=atom -msse3 -ffast-math -mfpmath=sse" \
       --extra-ldflags='-lm -lz -Wl,--no-undefined -Wl,-z,noexecstack' \
       $ADDITIONAL_CONFIGURE_FLAG
    make clean
    rm -f $(pwd)/compat/strtod.o
    rm -f $(pwd)/compat/strtod.d
    make
    make install
    }
    build_one