
Recherche avancée
Autres articles (65)
-
List of compatible distributions
26 avril 2011, parThe table below is the list of Linux distributions compatible with the automated installation script of MediaSPIP. Distribution nameVersion nameVersion number Debian Squeeze 6.x.x Debian Weezy 7.x.x Debian Jessie 8.x.x Ubuntu The Precise Pangolin 12.04 LTS Ubuntu The Trusty Tahr 14.04
If you want to help us improve this list, you can provide us access to a machine whose distribution is not mentioned above or send the necessary fixes to add (...) -
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...)
Sur d’autres sites (5518)
-
Pass exif data to image scaling call.
9 juin 2020, par blueimpPass exif data to image scaling call.
This allows the loadImage library to apply the correct orientation based on Exif data and the given orientation option.
-
python3.6 ffmpeg call MacOSX
8 avril 2017, par AwazleonI’m using Python 3.6 on MacOSX. I would like to use FFmpeg as Python sub-process. Everything works fine when using the OSX embedded Python 2.7 but using 3.6, this doesn’t work.
I’ve got an error message because it doesn’t find FFmepg.raise FFExecutableNotFoundError("Executable ’0’ not found".format(self.executable))
ffmpy.FFExecutableNotFoundError : Executable ’ffmpeg’ not foundAs you can se I tried with ffmpy but I also got the same result by invoking FFmpeg directly
from subprocess import call
call(["ffmpeg"])
Traceback (most recent call last) :
File "", line 1, in
call(["ffmpeg"])
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 267, in call
with Popen(*popenargs, **kwargs) as p :
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 707, in init
restore_signals, start_new_session)
File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/subprocess.py", line 1326, in _execute_child
raise child_exception_type(errno_num, err_msg)
FileNotFoundError : [Errno 2] No such file or directory : ’ffmpeg’I installed the FFmpeg lib. by using Brew through Terminal. It was well installed but only visible by Python 2.7, not 3.6.
Calling it from terminal is working :
iMac-de-xxxxx : utilisateur$ ffmpeg
ffmpeg version 3.2.4 Copyright (c) 2000-2017 the FFmpeg developers
built with Apple LLVM version 8.0.0 (clang-800.0.42.1)
configuration : —prefix=/usr/local/Cellar/ffmpeg/3.2.4 —enable-shared —enable-pthreads —enable-gpl —enable-version3 —enable-hardcoded-tables —enable-avresample —cc=clang —host-cflags= —host-ldflags= —enable-libmp3lame —enable-libx264 —enable-libxvid —enable-opencl —disable-lzma —enable-vdaI’m not (yet) a Linux specialist but I think that a path is missing for 3.6 to find FFmpeg.
Any clue to solve this annoying issue ? -
Can I call multiple FFMPEG processes on a multi-core LAMP machine from PHP ?
12 décembre 2012, par undefinedI am using PHP to call an FFMPEG command using exec(). The script that initiates this command is called from another PHP script using
proc_close(proc_open('php /phpdirectory/process.php &', array(), $foo));
This works great. The ffmpeg command is called and runs 'in the background' leaving the first script to return to the user and in this case carry on uploading files. What if I am using a machine with multiple cores ? How would I go about optimizing things so that I could call an ffmpeg process for each core ? Or will a multicore machine process split the work between cores anyway and get through a single process faster ?
Anyone ?