Recherche avancée

Médias (0)

Mot : - Tags -/clipboard

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

Autres articles (39)

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

  • Initialisation de MediaSPIP (préconfiguration)

    20 février 2010, par

    Lors de l’installation de MediaSPIP, celui-ci est préconfiguré pour les usages les plus fréquents.
    Cette préconfiguration est réalisée par un plugin activé par défaut et non désactivable appelé MediaSPIP Init.
    Ce plugin sert à préconfigurer de manière correcte chaque instance de MediaSPIP. Il doit donc être placé dans le dossier plugins-dist/ du site ou de la ferme pour être installé par défaut avant de pouvoir utiliser le site.
    Dans un premier temps il active ou désactive des options de SPIP qui ne le (...)

Sur d’autres sites (4860)

  • ffmpeg error "Could not write header for output file #0 (incorrect codec parameters ?) : Operation not permitted Error initializing output stream 0:0"

    27 juillet 2022, par DevSharma

    I am running FFmpeg in my app and specifically in "Android 11" I am getting this error from several users

    


    I have researched a lot but no solution found.

    


    I thought there is something wrong with the codec parameter that is being passed since it is saying "incorrect codec parameters" but most of the parameters looks good.

    


    also verified if all the required file permission are granted and those are good too

    


    now I m unable to find the problem,

    


    please help, thanks

    


    Command:&#xA;/data/app/~~hyrHVcslcfdQcguX0rauRA==/<apppackage>-QbDCul7FXU4tVniSDeP1Sg==/lib/arm64/libffmpeg.so -i /storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Media/WhatsApp Video/VID-20220414-WA0010.mp4 -c:v libx264 -crf 23 -map 0:V -map 0:a? -map 0:s? -c:s mov_text -segment_time 26 -g 26 -sc_threshold 0 -force_key_frames expr:gte(t,n_forced*26) -reset_timestamps 1 -f segment -preset ultrafast /storage/emulated/0/Movies/splitVideoFolder/split_video%03d.mp4&#xA;&#xA;Error:&#xA;ffmpeg version v4.4-dev-416 Copyright (c) 2000-2020 the FFmpeg developers&#xA;  built with Android (6454773 based on r365631c2) clang version 9.0.8 (https://android.googlesource.com/toolchain/llvm-project 98c855489587874b2a325e7a516b99d838599c6f) (based on LLVM 9.0.8svn)&#xA;  configuration: --cross-prefix=aarch64-linux-android- --sysroot=/Users/admin/AndroidStudioProjects/android-ndk-r21d/toolchains/llvm/prebuilt/darwin-x86_64/sysroot --prefix=/Users/admin/AndroidStudioProjects/Tanner/mobile-ffmpeg/prebuilt/android-arm64/ffmpeg --pkg-config=/usr/local/bin/pkg-config --enable-version3 --arch=aarch64 --cpu=armv8-a --cc=aarch64-linux-android21-clang --cxx=aarch64-linux-android21-clang&#x2B;&#x2B; --extra-libs=&#x27;-L/Users/admin/AndroidStudioProjects/Tanner/mobile-ffmpeg/prebuilt/android-arm64/cpu-features/lib -lndk_compat&#x27; --target-os=android --enable-neon --enable-asm --enable-inline-asm --enable-cross-compile --enable-pic --enable-jni --enable-optimizations --enable-swscale --disable-shared --disable-ffplay --enable-v4l2-m2m --disable-outdev=fbdev --disable-indev=fbdev --enable-small --disable-openssl --disable-xmm-clobber-test --disable-debug --enable-lto --disable-neon-clobber-test --disable-postproc --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --enable-static --disable-sndio --disable-schannel --disable-securetransport --disable-xlib --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --disable-videotoolbox --disable-audiotoolbox --disable-appkit --disable-alsa --disable-cuda --disable-cuvid --disable-nvenc --disable-vaapi --disable-vdpau --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libass --enable-iconv --enable-libx264 --enable-gpl --disable-sdl2 --enable-zlib --enable-mediacodec&#xA;  libavutil      56. 55.100 / 56. 55.100&#xA;  libavcodec     58. 96.100 / 58. 96.100&#xA;  libavformat    58. 48.100 / 58. 48.100&#xA;  libavdevice    58. 11.101 / 58. 11.101&#xA;  libavfilter     7. 87.100 /  7. 87.100&#xA;  libswscale      5.  8.100 /  5.  8.100&#xA;  libswresample   3.  8.100 /  3.  8.100&#xA;Input #0, mov,mp4,m4a,3gp,3g2,mj2, from &#x27;/storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Media/WhatsApp Video/VID-20220414-WA0010.mp4&#x27;:&#xA;  Metadata:&#xA;    major_brand     : mp42&#xA;    minor_version   : 0&#xA;    compatible_brands: mp42isom&#xA;  Duration: 00:01:30.53, start: 0.000000, bitrate: 671 kb/s&#xA;    Stream #0:0(und): Video: h264 (avc1 / 0x31637661), yuv420p(tv, smpte170m/bt470bg/smpte170m), 576x1024 [SAR 1:1 DAR 9:16], 539 kb/s, 30 fps, 30 tbr, 15360 tbn, 60 tbc (default)&#xA;    Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)&#xA;Stream mapping:&#xA;  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))&#xA;  Stream #0:1 -> #0:1 (aac (native) -> aac (native))&#xA;Press [q] to stop, [?] for help&#xA;[libx264 @ 0xb400007727c64800] using SAR=1/1&#xA;[libx264 @ 0xb400007727c64800] using cpu capabilities: ARMv8 NEON&#xA;[libx264 @ 0xb400007727c64800] profile Constrained Baseline, level 3.1, 4:2:0, 8-bit&#xA;[libx264 @ 0xb400007727c64800] 264 - core 160 - H.264/MPEG-4 AVC codec - Copyleft 2003-2020 - http://www.videolan.org/x264.html - options: cabac=0 ref=1 deblock=0:0:0 analyse=0:0 me=dia subme=0 psy=1 psy_rd=1.00:0.00 mixed_ref=0 me_range=16 chroma_me=1 trellis=0 8x8dct=0 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=0 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=0 weightp=0 keyint=26 keyint_min=2 scenecut=0 intra_refresh=0 rc=crf mbtree=0 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=0&#xA;[segment @ 0xb400007727c28800] Opening &#x27;/storage/emulated/0/Movies/splitVideoFolder/split_video000.mp4&#x27; for writing&#xA;[segment @ 0xb400007727c28800] Failed to open segment &#x27;/storage/emulated/0/Movies/splitVideoFolder/split_video000.mp4&#x27;&#xA;Could not write header for output file #0 (incorrect codec parameters ?): Operation not permitted&#xA;Error initializing output stream 0:0 --&#xA;[aac @ 0xb400007727c65700] Qavg: 18220.703&#xA;[aac @ 0xb400007727c65700] 2 frames left in the queue on closing&#xA;Conversion failed!&#xA;</apppackage>

    &#xA;

  • FFMPEG on MACOSX is complaining "no matches found"

    15 juin 2022, par Byte Player

    I have a FFMPEG command line function that works perfectly on Windows but on Mac produces the following error :

    &#xA;

    "no matches found [1:a]adelay=15000:all=1[aud2]"
    &#xA;"no matches found [2:a]adelay=5000:all=1[aud3]"

    &#xA;

    Here is the command (less the full paths which just made it very hard to read). I've verified that the files exist at the paths specified by copying the file path from the command line and going into terminal, typing "open" then pasting in the copied path and pressing enter. In all cases they played.

    &#xA;

    ffmpeg -loglevel warning -hide_banner -y -i "file1.mp3" -t 5 -i "file2.mp3" -i "file3.mp3" -i "file4.mp3" -ss 25 -t 15 -i "file5.mp3" -ss 15 -t 5 -i "file6.mp3" -filter_complex [1:a]adelay=15000:all=1[aud1];[2:a]adelay=5000:all=1[aud2];[4:a]adelay=25000:all=1[aud4];[5:a]adelay=5000:all=1[aud5];[aud1][aud2][aud4][aud5]amix=inputs=6:duration=longest:dropout_transition=0:normalize=0 "output.mp3"&#xA;

    &#xA;

    I know the immediate response (as it should be), is update your FFMPEG but I got the latest build (built on 2022-06-12) and here's what it reports...

    &#xA;

    ffmpeg version N-107092-g843c4346b1-tessus Copyright (c) 2000-2022 the FFmpeg developers&#xA;  built with Apple clang version 11.0.0 (clang-1100.0.33.17)&#xA;  configuration: --cc=/usr/bin/clang --prefix=/opt/ffmpeg --extra-version=tessus --enable-avisynth --enable-fontconfig --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libfreetype --enable-libgsm --enable-libmodplug --enable-libmp3lame --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopus --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-version3 --pkg-config-flags=--static --disable-ffplay&#xA;  libavutil      57. 26.100 / 57. 26.100&#xA;  libavcodec     59. 33.100 / 59. 33.100&#xA;  libavformat    59. 24.100 / 59. 24.100&#xA;  libavdevice    59.  6.100 / 59.  6.100&#xA;  libavfilter     8. 40.100 /  8. 40.100&#xA;  libswscale      6.  6.100 /  6.  6.100&#xA;  libswresample   4.  6.100 /  4.  6.100&#xA;  libpostproc    56.  5.100 / 56.  5.100&#xA;Hyper fast Audio and Video encoder&#xA;usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...&#xA;

    &#xA;

    Any insight or help would be GREATLY appreciated.

    &#xA;

  • FFMPEG creating mp3 with "Junk" at the end

    13 juillet 2022, par Johnaras

    I have a web application which converts WebM files to mp3 using FFMPEG.js in the Client-Side. Once the mp3 conversion finishes, users are prompted to download their file.

    &#xA;

    Lately, I realized that a lot of mp3 files which I tried to converted have a different duration value than the original WebM file. The duration is usually longer. For instance, a WebM file with duration of 2:16 gets converted to an mp3 file with a duration of 2:29. Once the player reaches at 2:16 it just goes back to the start.

    &#xA;

    I have tried to open the file in Audacity but it keeps saying that this MP3 file seems to be "Malformed".

    &#xA;

    I also tried to use MP3val and it says the file has junk at the end.

    &#xA;

    Code Snippets :

    &#xA;

    const worker = new Worker("/ffmpeg-worker-mp4.js");&#xA;import { fetchFile } from "@ffmpeg/ffmpeg"; // https://www.npmjs.com/package/@ffmpeg/ffmpeg&#xA;&#xA;const convertSong = async (title, id, bitrate) => {&#xA;    setProgress("Initializing...")&#xA;    ffmpegVars = [title]&#xA;    &#xA;    worker.postMessage({&#xA;      type: "run",&#xA;      arguments: ["-i", `input.webm`, "-c:a", "libmp3lame",  "-vn", "-ab", `${bitrate ? bitrate : 256}k`, "-ar", "44100", "-f", "mp3", `output.mp3`],&#xA;      MEMFS: [{ name: "input.webm", data: await fetchFile(`/api/download/stream?video=${id}`) }]&#xA;    });&#xA;}&#xA;&#xA;convertSong(data.title, data.id, data.bitrate)&#xA;

    &#xA;

    I'm literally willing to pay anyone who helps me fix this.

    &#xA;