Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (50)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

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

Sur d’autres sites (8348)

  • 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 re-wrap of a TS-AAC audio transport stream file to M4A-AAC : what happens by default (no "-codec copy" etc.) ?

    22 avril 2022, par esp

    What happens if you simply do ffmpeg -i aFile.ts aFile.m4a as opposed to ffmpeg -i aFile.ts -codec copy aFile.m4a, when the TS file contains only a single stream, namely AAC, and knowing that m4a files also typically contain AAC.

    &#xA;

    Does ffmpeg - even in the absence of any filters etc. - decode the original AAC and re-encode back to AAC (with whatever default parameters ffmpeg assumes for that - not necessarily matching those of the original) ? Or does it do something else ?

    &#xA;

    I tried this both with and without "-codec copy" and the results in each case were AAC but the files were significantly different in size (Original TS : 8.5 MB, ffmpeg'd without "-codec copy" 7 MB, ffmpeg'd with latter 5.1 MB.

    &#xA;

    At https://ffmpeg.org/ffmpeg.html it is stated (under "3.2 Stream copy"...

    &#xA;

    &#xA;

    Stream copy is a mode selected by supplying the copy parameter to the&#xA;-codec option. It makes ffmpeg omit the decoding and encoding step for the specified stream, so it does only demuxing and muxing. It is&#xA;useful for changing the container format or modifying container-level&#xA;metadata.&#xA;Implied by the inverse of that situation is that, in the absence of "-codec copy", ffmpeg will carry out the decoding and encoding steps.

    &#xA;

    &#xA;

  • lavc/mediacodecdec : set codec profile and level from extradata for H264+HEVC

    13 décembre 2021, par sfan5
    lavc/mediacodecdec : set codec profile and level from extradata for H264+HEVC
    

    This value is later passed to MediaCodec and checked at decoder init.
    Notably decoding of 10-bit streams before this commit would "work" without
    returning errors but only return garbage output (on most Android devices).

    • [DH] libavcodec/mediacodecdec.c