Closed GoogleCodeExporter closed 8 years ago
Hmmm, which version of FreeBSD, I'll download and install a copy on Vmware and
see if we can get this sorted.
By output redirect you mean the >& yes? Any ideas on how to overcome this?
Original comment by bugged...@gmail.com
on 12 Apr 2008 at 9:14
Original comment by bugged...@gmail.com
on 12 Apr 2008 at 9:14
I think that is not dependent on OS version. Instead the shell used matters. In
(t)csh (default in FreeBSD) you should use ">&" or simply ">". I managed to
make your
code work, just changed in 2 places. Btw, I thought, why use files to get
output. I
am not a great PHP developer, but why can't you capture output in PHP and
analyze it
instead of writing file, then reading it and then unlinking it... That way the
code
will be dependent on PHP realization only... Just a thought... ;)
Anyway, thank you for your work.
Original comment by alex.pog...@gmail.com
on 14 Apr 2008 at 8:54
thanks for the feed back. On certain system it is not possible to get the
information from the exec call to ffmpeg
through capturing the output, but I shall check with the changes you suggested
to see if that makes a difference,
and will post here to let you know.
Cheers.
Original comment by bugged...@gmail.com
on 15 Apr 2008 at 7:40
quick question for you. if you ran this
exec("/usr/local/bin/ffmpeg -i '/Users/ollie/Sites/@Projects/ffmpeg/www/examples/to-be-
processed/MOV00007.3gp' -s '320x240' -sameq -acodec 'mp3' -ab '64kb' -ar
'44100' -f 'flv' -y
/Users/ollie/Sites/@Projects/ffmpeg/www/examples/tmp/1208817919-480d18fff0ed0.fl
v >&", $output,
$return_var);
var_dump($output, $return_var);
obviously changing the pathways an files, do you get any content returned by
the var_dump? on os x nothing
is returned.
Original comment by bugged...@gmail.com
on 21 Apr 2008 at 10:51
under freebsd what is returned by PHP_OS?
Original comment by bugged...@gmail.com
on 21 Apr 2008 at 10:53
this issue should have been resolved as of 0.1.5
Original comment by bugged...@gmail.com
on 6 Jun 2008 at 9:42
Original comment by bugged...@gmail.com
on 6 Jun 2008 at 9:43
Original issue reported on code.google.com by
alex.pog...@gmail.com
on 11 Apr 2008 at 10:40