
Recherche avancée
Autres articles (53)
-
Mise à disposition des fichiers
14 avril 2011, parPar défaut, lors de son initialisation, MediaSPIP ne permet pas aux visiteurs de télécharger les fichiers qu’ils soient originaux ou le résultat de leur transformation ou encodage. Il permet uniquement de les visualiser.
Cependant, il est possible et facile d’autoriser les visiteurs à avoir accès à ces documents et ce sous différentes formes.
Tout cela se passe dans la page de configuration du squelette. Il vous faut aller dans l’espace d’administration du canal, et choisir dans la navigation (...) -
Use, discuss, criticize
13 avril 2011, parTalk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
A discussion list is available for all exchanges between users. -
MediaSPIP en mode privé (Intranet)
17 septembre 2013, parÀ partir de la version 0.3, un canal de MediaSPIP peut devenir privé, bloqué à toute personne non identifiée grâce au plugin "Intranet/extranet".
Le plugin Intranet/extranet, lorsqu’il est activé, permet de bloquer l’accès au canal à tout visiteur non identifié, l’empêchant d’accéder au contenu en le redirigeant systématiquement vers le formulaire d’identification.
Ce système peut être particulièrement utile pour certaines utilisations comme : Atelier de travail avec des enfants dont le contenu ne doit pas (...)
Sur d’autres sites (5220)
-
Video with music taking long time
1er octobre 2020, par Konduri Sai AdityaHi I am rendering video with filters and adding audio at the end. But while running it is taking a long time and rendering continuously. Can anyone help me where I am wrong ? below is the command


ffmpeg -i test.png -i test.mp4 -i test.mp3 -y -filter_complex "[1:v]scale=1422:800[scale1],[scale1]rotate=0:c=black@0:ow=rotw(0):oh=roth(0)[rotate0],[0:v][rotate0]overlay=258.04:107.71[mediaoverlayout0],color=black@0:451x137[c1],[c1]setsar=1,drawtext=fontfile='/Windows/fonts/Peddana-Regular.ttf':text='ADITYA':fontsize=121.199:fontcolor=#1e8bc3:line_spacing=16.91,rotate=0:ow=rotw(0):oh=roth(0):c=black@0[rottext1],[mediaoverlayout0][rottext1]overlay=x=544.63:y=263.076[out]" -vcodec libx264 -map "[out]" -map 2:a -preset veryfast -c:a copy -pix_fmt yuv420p op.mp4 



-
MXF D10 PAL encoded with FFMPEG
1er février 2019, par Kumar SwaminathanI have a MXF D10 input that I am trying to encode using FFMPEG. This input is 720x512 but its actual height is 486 (as per mediainfo). I process via FFMPEG and I see black lines at top.
Can FFMPEG interpret MXF D10 correctly ? I realize that many players have problem displaying MXF D10 but the question is does FFMPEG decode this correctly ?
Also, which players would play MXF D10 correctly without black lines at top.
I am using FFMPEG 3.2
-
ffmpeg crashes in electron on mac apple store ; no suitable image found file system sandbox blocked open() of 'libass'
20 février 2021, par MartinI am trying to release an electron app on the Mac Apple Store (mas), my electron app uses ffmpeg to render videos. In order to release my app on the mac apple store, It needs to be sandboxed, and by default ffmpeg makes calls to external libraries so I need to statically build ffmpeg and package it with my app. I have successfully built my app, submitted it to the app store, had it approved, and downloaded/used it but my ffmpeg fails with this errir :


Uncaught (in promise) Error: Command was killed with SIGABRT (Aborted): /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/9. Get Out In The Sun.flac -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/10. Golden Hues.flac -y -filter_complex concat=n=2:v=0:a=1 -c:a libmp3lame -b:a 320k /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/output-261020.mp3
dyld: Library not loaded: /usr/local/opt/libass/lib/libass.9.dylib
 Referenced from: /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg
 Reason: no suitable image found. Did find:
 file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib'
 /usr/local/opt/libass/lib/libass.9.dylib: stat() failed with errno=1
 file system sandbox blocked open() of '/usr/local/lib/libass.9.dylib'
 file system sandbox blocked open() of '/usr/local/Cellar/libass/0.15.0/lib/libass.9.dylib'
 at makeError (/Users/martinbarker/…eca/lib/error.js:59)
 at handlePromise (/Users/martinbarker/…/execa/index.js:114)
 at async file:/Users/ma…js/newindex.js:1151



I think this line is important ;
file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib'
but I'm not sure what I should change with my static ffmpeg build so that it works in production and so that I can avoid the above error.

My code is available on the branch mas-attempt-after-redesign here : https://github.com/MartinBarker/digify/tree/mas-attempt-after-redesign


Inside my package.json I have the command
download-ffmpeg
which clones the ffmpeg repo, runs a configure command with some flags, and then builds ffmpeg into a folder called 'ffmpeg-mac', this folder gets packaged with the app for the mac apple store build.

git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac && cd ffmpeg-mac && ./configure pkg_config='pkg-config --static' --pkg-config-flags='--static' --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --enable-libass --enable-libfdk-aac --enable-libmp3lame --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect && make && cd ..



You can see in the above ffmpeg command the flag
--enable-libass
, but even though I have that flag included, after I build and sign my mac apple store build by runningsudo rm -rf dist/mas/ && npm run build-mas && sh mas-sign-script.sh
, the production build (once approved) fails with the above included error.