
Recherche avancée
Médias (1)
-
Video d’abeille en portrait
14 mai 2011, par
Mis à jour : Février 2012
Langue : français
Type : Video
Autres articles (38)
-
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...) -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...)
Sur d’autres sites (7791)
-
FFmpeg's common filter "v360" missing
26 septembre 2021, par Niklas E.I'm trying to convert a 180° fisheye video to a normal/regular video using the
v360
filter of FFmpeg.

This is the command I tried :

ffmpeg -i in.mp4 -vf "v360=input=fisheye:output=flat:iv_fov=180:v_fov=90" out.mp4


But the output says clearly
No such filter: 'v360'
, although v360 is a common filter listed in docs and other filters I used before worked just fine. I tried updating/reinstalling and looking for solutions, not fixing it.

Why is the filter missing ? How can I debug this ? Should I doe the task using another program entirely ?


Command output :


ffmpeg version 4.2.4-1ubuntu0.1 Copyright (c) 2000-2020 the FFmpeg developers
 built with gcc 9 (Ubuntu 9.3.0-10ubuntu2)
 configuration: --prefix=/usr --extra-version=1ubuntu0.1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-avresample --disable-filter=resample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librsvg --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-nvenc --enable-chromaprint --enable-frei0r --enable-libx264 --enable-shared
 libavutil 56. 31.100 / 56. 31.100
 libavcodec 58. 54.100 / 58. 54.100
 libavformat 58. 29.100 / 58. 29.100
 libavdevice 58. 8.100 / 58. 8.100
 libavfilter 7. 57.100 / 7. 57.100
 libavresample 4. 0. 0 / 4. 0. 0
 libswscale 5. 5.100 / 5. 5.100
 libswresample 3. 5.100 / 3. 5.100
 libpostproc 55. 5.100 / 55. 5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'in.mp4':
 Metadata:
 major_brand : mp42
 minor_version : 0
 compatible_brands: mp42mp41
 creation_time : 2021-09-11T14:18:33.000000Z
 Duration: 00:02:48.02, start: 0.000000, bitrate: 26056 kb/s
 Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 2160x1080 [SAR 1:1 DAR 2:1], 25924 kb/s, 50 fps, 50 tbr, 50k tbn, 100 tbc (default)
 Metadata:
 creation_time : 2021-09-11T14:18:33.000000Z
 handler_name : Mainconcept MP4 Video Media Handler
 encoder : AVC Coding
 Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)
 Metadata:
 creation_time : 2021-09-11T14:18:33.000000Z
 handler_name : Mainconcept MP4 Sound Media Handler
Stream mapping:
 Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
 Stream #0:1 -> #0:1 (aac (native) -> aac (native))
Press [q] to stop, [?] for help
[AVFilterGraph @ 0x55ee57567340] No such filter: 'v360'
Error reinitializing filters!
Failed to inject frame into filter network: Invalid argument
Error while processing the decoded data for stream #0:0
Conversion failed!



-
Input format "highpass=f=300, is not available fluent ffmpeg npm
24 juin 2022, par Sunil GargI am using [fluent-ffmpeg][1] package to convert mp3 to wav. I have installed ffmpeg on my machine as well.


Now in nodejs, I am trying following commands with options


ffmpeg(mp3FilePath)
 .inputOptions([
 '-af', '"highpass=f=300, lowpass=f=3400"',
 '-r', '8000',
 '-ac', '1'
 ])
 .output(wavFilePath)
 .on('error', (err) => {
 console.log('An error occurred: ' + err.message);
 res.json("failed");
 })
 .on('progress', (progress) => {
 // console.log(JSON.stringify(progress));
 console.log('Processing: ' + progress.targetSize + ' KB converted');
 })
 .on('end', () => {
 console.log('Processing finished !');
 res.json("done");
 }).run();



but this throws error


An error occurred: ffmpeg exited with code 1: lowpass=f=3400": Invalid argument



I am not able to figure out what is the problem. Any help ?
[1] : https://www.npmjs.com/package/fluent-ffmpeg


-
Why is "ffmpeg : command not found" in heroku, even with proper buildpack/config ?
14 novembre 2022, par JimIn a node.js app hosted on heroku, ffmpeg is used by spawning processes, but is throwing errors anytime an ffmpeg command runs


the error
ffmpeg: command not found
is thrown both in cli testheroku run ffmpeg
as well as production logs

Ive considered :


- 

- buildpack order
- buildpack clearing/re-adding/redeploying
- buildpack required env vars
- heroku-stack-20 conflicts with buildpack#1 somehow ?










Buildpack order :


- 

- https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
- https://github.com/heroku/heroku-buildpack-awscli.git
- https://github.com/timanovsky/subdir-heroku-buildpack.git
- heroku/nodejs










Buildpack configs - from watching build logs, even though i havent set ffmpeg path, a default is found.


beginning build logs (completes successfully, runs successfully - minus ffmpeg) :


-----> Building on the Heroku-20 stack
-----> Using buildpacks:
 1. https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
 2. https://github.com/xrisk/heroku-opus.git
 3. https://github.com/heroku/heroku-buildpack-awscli.git
 4. https://github.com/timanovsky/subdir-heroku-buildpack.git
 5. heroku/nodejs
-----> ffmpeg app detected
-----> Installing ffmpeg
 Variable FFMPEG_DOWNLOAD_URL isn't set, using default value
 Downloading https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
 Unpacking the archive
 Installation successful
-----> heroku-opus app detected
 exporting PATH and LIBRARY_PATH
-----> Building in /tmp/build_51b5ac83/opus
-----> Starting opus compilation
 Downloading opus-1.3.1.tar.gz
 Unpacking opus
 Running configure
 Running make install
-----> AWS CLI app detected
-----> Downloading AWS CLI
-----> Installing AWS CLI
 You can now run: /app/.awscli/bin/aws --version
 aws-cli/2.8.12 Python/3.9.11 Linux/4.4.0-1104-aws exe/x86_64.ubuntu.20 prompt/off
-----> Successfully installed AWS CLI
-----> Subdir buildpack app detected
-----> Subdir buildpack in server
 creating cache: /tmp/codon/tmp/cache
 created tmp dir: /tmp/codon/tmp/cache/subdirBuBFb
 moving working dir: server to /tmp/codon/tmp/cache/subdirBuBFb
 cleaning build dir /tmp/build_51b5ac83
 copying preserved work dir from cache /tmp/codon/tmp/cache/subdirBuBFb to build dir /tmp/build_51b5ac83
 cleaning tmp dir /tmp/codon/tmp/cache/subdirBuBFb
-----> Node.js app detected



Any suggestions to further debug this ?