I am currenlty working on a set of classes to manipulate media files (basically video) - actually they are wrappers over command-line utilities ffmpeg and mencoder, but they support common interface so that any other backend is possible to use - you will only need to write a PHP-wrapper supporting the same interface, if you want to use, say, avidemux.

Features I have [almost] implemented:
- Read media-file information, such as used, codecs, bitrate, fps etc.
- Converting from one format to another (including flv - flash video to be viewed in a web-browser), with a possibility to convert only a selected part of original movie. Also you can change movie quality, pixel-size and other parameters.
- Snapshots generating (jpeg, but png could also be supported) - from an arbitrary position in the stream.

I am developing those classes as a part of my own web-tollkit - Naf (stands for Not A Framework). However, class-and-file-naming conventions are the same as in ZF, I also cover code with unit-tests (simpletest, but they can be easily converted to phpunit). Right now, I am heavily refactoring this code, so I can expect to have a useful version within Naf - in about a week. Then I hope I will be able to give a link to a SVN repositiory for those interested to download.

Questions and ideas are expceted in this thread, thanks.

Croc,

I am definitely interested in this library. And, I am willing to help with it if needed.

Doug

Revision 100: /trunk/Naf - this is SVN repo, you could check it out with your favourite SVN client.

What you need is Media.php, ShellCmd.php and the Media folder. But, I need to inform you: since the thread has not been answered by anyone (therefore, I just thought that it is not of interest to community) - I didn't do much with this code - and it is currently in the same state that it used to be quite a long time ago. However, it could be useful - personally, I use it regardless of the fact that the architecture is imperfect in many aspects.

Ask questions here or by email (crocodile2u [at] yandex [dot] ru).

We could also discuss changes to architecture/featurelist - and implement them together: developer access to the repo is not a problem.