
Recherche avancée
Médias (1)
-
SWFUpload Process
6 septembre 2011, par
Mis à jour : Septembre 2011
Langue : français
Type : Texte
Autres articles (74)
-
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
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 v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)
Sur d’autres sites (4520)
-
Why is exec('which ffmpeg') returning nothing in my application ?
28 avril 2015, par EchoLogicI’m trying to deal with FFMpeg for my application, but I’m encountering some difficulty in getting it set up. To instantiate or create an instance of FFMpeg, I need to call a
create()
method and pass through the operating locations of FFMpeg and FFProbe. To do this, I was hoping to be able to write :$ffmpeg = FFMpeg\FFMpeg::create([
'ffmpeg.binaries' => exec('which ffmpeg'),
'ffprobe.binaries' => exec('which ffprobe')
]);But, sadly, the command
exec('which ffmpeg')
returns an empty string. If I run the ’which ffmpeg’ command in Terminal, I get a response :/usr/local/bin/ffmpeg
So why does it work in my terminal, but not when my PHP script tries to execute it ?
I’ve tried a few solutions, such as appending
2>&1
to the end of the command, which did not help, running the command inshell_exec()
, and placing the output in the second parameter ofexec()
which also did not solve my issue.I feel like this may be some sort of weird permissions issue...
Addendum
It has been brought to my attention that PHP cannot see my
$PATH
variable. From the console,echo $PATH
produces :/Applications/MAMP/bin/php/php5.6.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/git/bin:/opt/ImageMagick/bin
While calling the same from my application with
exec()
produces :/usr/bin:/bin:/usr/sbin:/sbin237.671000
-
How to run one script after another in Apple Script
19 juillet 2015, par mskx4I’m trying with Apple Script to run three different scripts that would alow me to :
- Convert a purchased m4a file into an "anonymized" m4a file and extract its artwork (with ffmpeg)
- Attach the artwork to the file previously converted, since the converted file won’t maintain its artwork (with AtomicParsley)
- Remove the artwork from his path
I don’t have any kind of programming knowledge, I’ve collected different script from the web and tried to make an app that could do these 3 simple task :
on open argv
set paths to ""
repeat with f in argv
set paths to paths & quoted form of POSIX path of f & " "
end repeat
tell application "Terminal"
do script "for f in " & paths & "; do ffmpeg -i \"$f\" -acodec copy -y \"$f\" output.jpg; done"
activate
do script "for f in " & paths & "; do AtomicParsley \"$f\" --artwork output.jpg; done"
activate
do script "rm output. jpg"
activate
end tell
end openThe problem is that, when I drop a file on the app, it opens three terminal windows at once and it runs the three tasks in the same time, with the obvious result that the conversion fails : the first task overwrites the input file, and the second script should use the output of the first one as its input file. So I need the three scripts to be executed successively, one after another.
-
Using FFMPEG in Java (developing on Mac)
1er mai 2012, par Luuk D. JansenI am trying to evoke FFMPEG directly in my Java code (running under the Playframework !).
The final product will run on a Linux/Debian distro, but I first need to test on my Mac (I don't know if it works on Debian yet).I try to execute the simple code :
Process pr = Runtime.getRuntime().exec(new String[]{"bash","-c", "ffmpeg"});
or simpler :
Process pr = Runtime.getRuntime().exec("ffmpeg")
or using ProcessBuilder :
Process pr = new ProcessBuilder("/opt/local/bin/ffmpeg").start();
What I get is an error code 133, but I cannot find what this means.
In the terminal the command gives the normal output. I can also replace 'ffmpeg' with e.g. 'ls -la' and get the directory listing. But I don't know what the problem is that ffmpeg does not work.Anybody any clues ?
Thanks !UPDATE :
I looked at the error stream. These are the errors I get. How is it that it works in the terminal, but not in using Java ?14:43:19,619 DEBUG ~ FFMPEG: dyld: Library not loaded: /opt/local/lib/libogg.0.dylib
14:43:19,619 DEBUG ~ FFMPEG: Referenced from: /opt/local/bin/ffmpeg
14:43:19,619 DEBUG ~ FFMPEG: Reason: Incompatible library version: ffmpeg requires version 9.0.0 or later, but libogg.0.dylib provides version 6.0.0