
Recherche avancée
Autres articles (31)
-
Installation en mode ferme
4 février 2011, parLe mode ferme permet d’héberger plusieurs sites de type MediaSPIP en n’installant qu’une seule fois son noyau fonctionnel.
C’est la méthode que nous utilisons sur cette même plateforme.
L’utilisation en mode ferme nécessite de connaïtre un peu le mécanisme de SPIP contrairement à la version standalone qui ne nécessite pas réellement de connaissances spécifique puisque l’espace privé habituel de SPIP n’est plus utilisé.
Dans un premier temps, vous devez avoir installé les mêmes fichiers que l’installation (...) -
Emballe médias : à quoi cela sert ?
4 février 2011, parCe plugin vise à gérer des sites de mise en ligne de documents de tous types.
Il crée des "médias", à savoir : un "média" est un article au sens SPIP créé automatiquement lors du téléversement d’un document qu’il soit audio, vidéo, image ou textuel ; un seul document ne peut être lié à un article dit "média" ; -
Configuration spécifique d’Apache
4 février 2011, parModules spécifiques
Pour la configuration d’Apache, il est conseillé d’activer certains modules non spécifiques à MediaSPIP, mais permettant d’améliorer les performances : mod_deflate et mod_headers pour compresser automatiquement via Apache les pages. Cf ce tutoriel ; mode_expires pour gérer correctement l’expiration des hits. Cf ce tutoriel ;
Il est également conseillé d’ajouter la prise en charge par apache du mime-type pour les fichiers WebM comme indiqué dans ce tutoriel.
Création d’un (...)
Sur d’autres sites (5342)
-
FFmpeg proccess killed while converting .mov file
10 novembre 2020, par Vala KhosraviI'm using FFmpeg to reduce my videos file size when I give a .mov file as an input with this command :


ffmpeg -i in.mov -c:a copy -crf 20 out.mov



program start working and after a while, it gets killed. here are the last lines of the log that I get :


Output #0, mov, to '/home/ubuntu/test.mov':
 Metadata:
 major_brand : qt
 minor_version : 0
 compatible_brands: qt
 com.apple.quicktime.creationdate: 2020-08-29T15:03:17+0430
 com.apple.quicktime.make: Apple
 com.apple.quicktime.model: MacBookPro14,1
 com.apple.quicktime.software: Mac OS X 10.15.1 (19B88)
 encoder : Lavf57.83.100
 Stream #0:0(und): Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 2866x1716 [SAR 1:1 DAR 1433:858], q=-1--1, 60 fps, 15360 tbn, 60 tbc (default)
 Metadata:
 creation_time : 2020-11-10T09:04:43.000000Z
 handler_name : Core Media Data Handler
 encoder : Lavc57.107.100 libx264
 Side data:
 cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
 Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 207 kb/s (default)
 Metadata:
 creation_time : 2020-11-10T09:04:43.000000Z
 handler_name : Core Media Data Handler
Killed 23 fps=3.6 q=0.0 size= 0kB time=00:00:01.34 bitrate= 0.0kbits/s dup=1 drop=0 speed=0.21x



I tried so many different flags for FFmpeg but still getting the same error.


What's the solution ?
here is my input video file


-
What type file to pass to FFMPEG::Movie.new(file) in the gem ffmpeg (heroku)
31 août 2020, par AlbertMunichMarI have a Rails app hosted in Heroku. I am using the gem
ffmpeg
to record screenshots.

I get a video from a React App in my controller :


video = params[:video].tempfile
# #tmp/RackMultipart20200831-4-zgw094.mp4>



I try to pass this object, but does not work :


Errno::ENOENT (No such file or directory - the ffprobe binary could not be found in /app/vendor/bundle/ruby/2.5.0/bin:/app/bin:/app/vendor/bundle/bin:/usr/local/bin:/usr/bin:/bin):



I thought it should worked, since
FFMPEG::Movie.new(file)
is asking for the path, and I am providing it :

Parameters: {"video"=>#, @original_filename="89.mp4", @content_type="video/mp4", @headers="Content-Disposition: form-data; name=\"video\"; filename=\"89.mp4\"\r\nContent-Type: video/mp4\r\n">}



see :
tmp/RackMultipart20200831-4-q2yi74.mp4>
. This is the temp path right ?

Maybe it's looking for the file in the wrong path, but how can I specify it ?


I also tried :


File.open(video, 'r') do |file|
 FFMPEG::Movie.new(file.path)
end



But also wrong path. Could someone help me ?


Buildpack is installed in heroku.


I used the CLI installation :


heroku create --buildpack https://github.com/FFmpeg/FFmpeg.git



With following output :


remote: -----> ffmpeg app detected
remote: -----> Install ffmpeg
remote: DOWNLOAD_URL = https://johnvansickle.com/ffmpeg/builds/ffmpeg-git-amd64-static.tar.xz
remote: exporting PATH
remote: -----> Discovering process types
remote: Procfile declares types -> (none)



It seems to be installed.


But I keep getting this error :


2020-08-31T15:56:24.157721+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/nodes" host=wikisalsaapi.herokuapp.com request_id=35e23352-005a-4178-bda1-0bed65885c0d fwd="46.128.35.112" dyno= connect= service= status=503 bytes= protocol=https
2020-08-31T15:57:08.000000+00:00 app[api]: Build started by user albert.montolio@gmail.com
2020-08-31T15:57:31.843422+00:00 app[api]: Deploy 038e1b47 by user albert.montolio@gmail.com
2020-08-31T15:57:31.843422+00:00 app[api]: Release v76 created by user albert.montolio@gmail.com
2020-08-31T15:57:34.000000+00:00 app[api]: Build succeeded
2020-08-31T15:58:37.767157+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=POST path="/nodes" host=wikisalsaapi.herokuapp.com request_id=365fe1a2-091e-479a-b9b6-02c0b70ed754 fwd="46.128.35.112" dyno= connect= service= status=503 bytes= protocol=https



-
Getting error while deploying application with node-media-serve module and ffmpeg buildpack in heroku
16 septembre 2020, par Anurag GautamI have created a MERN app with video streaming by using
node-media-serve
module, with following configuration

trans: {
 ffmpeg: '/vendor/ffmpeg',
 tasks: [] ,
 .....
}



In local I have installed
ffmpeg
intrans.ffmpeg
. and its working fine, But how we need to install ffmpeg in heroku .

I have tried by adding heroku buildpacks

heroku buildpacks:add https://github.com/jonathanong/heroku-buildpack-ffmpeg-latest.git
but its showing me error. May be some issue with config only.

Heroku error :

2020-09-16T11:23:54.292896+00:00 app[web.1]: 9/16/2020 11:23:54 23 [ERROR] Node Media Trans Server startup failed. ffmpeg:/vendor/ffmpeg cannot be executed.


Guys can you please help me reslove this issue