<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">What's the chances of erlyvideo and the related libraries also being licensed with something slightly more permissive than GPL, such as LGPL or similar; we deal with a number of corporate clients where use of GPL is pretty much forbidden, so are having to replicate a number of areas of erylvideo functionality. If the licensing was different, we could instead spend such efforts contributing back to erlyvideo…<div><br></div><div>Cheers,</div><div><br></div><div>Steve</div><div><br></div><div><div><div>On 3 Aug 2011, at 22:19, Max Lapshin wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><a href="http://code.google.com/p/erlyvideo/" target="_blank">http://code.google.com/p/<wbr>erlyvideo</a> repository wasn't updated for years.<br><br>All development now is going in <a href="http://github.com/erlyvideo">http://github.com/erlyvideo</a> and private repositories.<br><br>Currently I have not only frame repacking layer for codecs h264,aac,mp3,mpeg4,vp6,h263,pcm,g.711,g.726 and such protocols as<br>mpeg-ts, rtmp, rtsp/rtp, sip, but also some device handling features and transcoding modules.<br><br>And I can say you: ffmpeg is much better when it is in erlang =) We are adding now generic libavcodec support, but such things<br>like libavformat at very badly written in C. Erlang fits this task much better.<br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>http://erlang.org/mailman/listinfo/erlang-questions<br></blockquote></div><br></div></body></html>