tags:

views:

60

answers:

3

I am trying to run lame from a php script.

I have tried these, but no luck, I don't get anything returned! Any ideas?

system('lame', $returnarr);
system('lame --help', $returnarr);
exec('lame', $returnarr);
passthru('lame', $returnarr);

even this one returns nothing:

exec('which lame', $returnarr);

I am on OSX and final deployment will be on Linux. Do you have better suggestions for an automated wav->mp3 conversion? From php, should I execute a bash script that executes Lame?

A: 

set error reporting on and check if you can do exec's. By default most systems wont allow it, it's a serious security liability. You've got to explicitly allow execs in php.ini.

mhughes
gok
A: 

Might be a $PATH problem. Try specifying the full path to lame, ie. /usr/local/bin/lame.

Adam Backstrom
nope, tried it already
gok
+1  A: 

Try something like this:

$output = array();
$result = -1;
exec('`/usr/bin/which lame` --help 2>&1', $output, $result);
var_dump($output, $result);

$output should be an array of lines contained in the output

$result should be an integer result code. 0 is typically success, >=1 is an error (specific codes are application dependant).

The 2>&1 part will redirect STDERR to STDOUT ($output) which would normally be dropped. So if it's erroring out, you should be able to see the error (hopefully).

If you get -1 for the dump of $result, there's a fundimental problem, because that's not a valid result code (it likely means that exec is disabled, or the process you're trying to run is restricted because of permissions errors or the such)...

ircmaxell
thanks a lot! it's strange that i can't get "which" working but lame works with full path.
gok
Perhaps ">=1 is an error"?
Dennis Williamson
Fixed the >=1 issue. Thanks for pointing that out Dennis...
ircmaxell