For th project, I can give you the git project, but we wish to clean a lot of parts. It's a first version, and maybe we speak to rename a lot of thinks, first of all the library name, avTranscoder by mediaManager or mediaLib. Include also some unit test ... We have a lot of discussion about naming convention.
The origin of this project is to bind some features of the Libav/FFmpeg but with some high level features like exceptions, oriented object, etc. The second aspect is to replace some parts (like output wrapping) by a C++ library. I think a good entry point is the python sample file, as an example of transcoding tool: https://github.com/avTranscoder/avTranscoder/blob/master/app/pyProcessor/pyProcessor.py The next step is to clean some code, ans integrate more features from Libav (like filters) And after I think to speak with you to have you point of view, maybe present you the library and see what we can doing together (some Python binding are presents but not officials, also for ruby, java etc.). But now I have open the discussion here, and if you want I can plan a presentation soon about the library, features etc. (but out of this discussion around packaging). Our github is: https://github.com/avTranscoder/avTranscoder Due to a small project, we try some new open source tools, for CI, packaging etc. It use currently some open source tools like Travis (for Ubuntu and Mac build - with gcc and clang) [https://travis-ci.org/avTranscoder/avTranscoder] which validate pull request by a build on 4 platforms before acceptance. And I work on Build-OpenSUSE to package it: [ https://build.opensuse.org/package/show/home:MarcAntoineArnaud/avt-test] using also the local packaging of the libav: [ https://build.opensuse.org/package/show/home:MarcAntoineArnaud/libav] Of course the packaging requires updates, but using these tools, packagings descriptions are include in the repository (a package description match to a specific release, and for me made sense to include in it). The builder can download on every commits using a webhook, and after the clone some files can be extracted from sources to provide packaging description etc. And I think it about distributions managers to send pull requests to the project to define the packaging description, and merge competences of each distributions to create similar DEB and RPM's (like changelog inclusion, package description etc.) Of course packaging is very complicated, but maybe support "basics" platforms like 32 an 64 bits on "current" distribution is a good point I think. What do you mean by "legal concerns" ? It's about FFmpeg ? or about GPL licensing ? or an another thing ? Thanks, -- *Marc-Antoine* |e:[email protected] |tel: 06-84-71-84-45 | ohloh: http://bit.ly/1iwtlsU [image: LinkedIn] <http://s.wisestamp.com/links?url=https%3A%2F%2Fwww.linkedin.com%2Fpub%2Fmarc-antoine-arnaud%2Fb%2F7b8%2F2a3&sn=YXJuYXVkLm1hcmNhbnRvaW5lQGdtYWlsLmNvbQ%3D%3D> [image: Google Plus] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
