
Recherche avancée
Autres articles (67)
-
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 est la première version de MediaSPIP stable.
Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
MediaSPIP version 0.1 Beta
16 avril 2011, parMediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...) -
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs
Sur d’autres sites (7387)
-
github actions ffmpeg gem cannot find ffprobe
27 octobre 2022, par Ilovebathroomlightsso, we have been using a gem called streamio-ffmpeg, and it has been working well. We have been using github actions to to integration and E2E testing for our front end. We also had to add python for another dependency we are using. now, when we run the E2E suite on github actions, streamio-ffmpeg cannot find the ffprobe binary since python has also been installed on the actions runner.


we get the following message :


Body: Puma caught this error: No such file or directory - the ffprobe binary could not be found in /home/runner/work/folder_name/another_folder_name/server/vendor/bundle/ruby/2.7.0/bin:/opt/hostedtoolcache/Python/3.10.8/x64/bin:/opt/hostedtoolcache/Python/3.10.8/x64:/opt/hostedtoolcache/Ruby/2.7.6/x64/bin:/home/runner/.local/bin:/opt/pipx_bin:/home/runner/.cargo/bin:/home/runner/.config/composer/vendor/bin:/usr/local/.ghcup/bin:/home/runner/.dotnet/tools:/snap/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games (Errno::ENOENT)



and streamio-ffmpeg says :


Specify the path to ffmpeg
By default, the gem assumes that the ffmpeg binary is available in the execution path and named ffmpeg and so will run commands that look something like ffmpeg -i /path/to/input.file .... Use the FFMPEG.ffmpeg_binary setter to specify the full path to the binary if necessary:

FFMPEG.ffmpeg_binary = '/usr/local/bin/ffmpeg'



so, how can i find out where ffprobe binary is and tell github actions this information ?? I have tried manually installing ffmpeg within the github actions runner but this does not help.


-
Piping cURL output to FFmpeg doesn't work with mp4 files
8 novembre 2015, par KonstantinI would like to pipe cURL output to FFmpeg the following way in my Ruby script to strip off metadata, chapters and maybe set other metadata too in the future :
#!/usr/bin/ruby
url=ARGV[0]
fname=url.split("/").last
extension=File.extname(fname)
options=""
case extension
when /mp4/i
format="mp4"
options=" -movflags frag_keyframe+empty_moov "
when /avi/i
format="avi"
when /mkv/i
format="matroska"
when /wmv/i
format="asf"
else
format="matroska"
end
cmd=%Q{ curl -b cookie-file.txt #{url} -L -o - | ffmpeg -y -i - -map 0:v -map 0:a -c:v copy -c:a:0 copy -map_metadata -1 -map_chapters -1 #{options} -f #{format} - | cat > #{fname} }
system cmdWhen the url (ARGV[0]) points to an .avi, .wmv or .mkv file the script do its job. However when it points to an .mp4 or .mov file it doesn’t work, because the input isn’t seekable and FFmpeg at first try to read the whole input. When url points to an mp4 file, output to stdout even doesn’t work, only when options " -movflags frag_keyframe+empty_moov " is used for the output format. Otherwise I got an error message : "muxer does not support non seekable output". Last cat command is needed because this command pipe will work in a CGI script, and will write its output to STDOUT with appropriate HTTP headers. What options should I use for the input pipe to make my script work with mp4 files too ?
-
How to change ffmpeg filters on the fly
28 avril 2015, par wieIs it possible with ffmpeg, on the commandline, to change filters such as brightness, saturation or gamma, while ffmpeg is running, from outside ffmpeg (e.g. from a php/node/ruby script) ? (on the fly / dynamically)