<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 25 Jan 2015, at 00:46, wm4 <<a href="mailto:nfxjfg@googlemail.com" class="">nfxjfg@googlemail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On Sun, 25 Jan 2015 00:25:34 +0100<br class="">Info || Non-Lethal Applications <<a href="mailto:info@non-lethal-applications.com" class="">info@non-lethal-applications.com</a>><br class="">wrote:<br class=""><br class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><blockquote type="cite" class="">for asking design questions on the mailing list and being relegated to<br class="">reading through undocumented source code for a month “open”. Sure it is<br class="">free of licensing charges, but FFmpeg is not free — unless you have got<br class="">a vanilla use-case encapsulated in the canned examples, you are most<br class="">likely in for a deep-sea expedition, and you’ll most definitely be<br class="">investing a large amount of time trying to understand how to use it. <br class=""></blockquote><br class="">The main issue is actually that the FFmpeg API is pretty low-level,<br class="">while many users expect something higher level. (Somewhat typical: a<br class="">user wants frame N of video in a specific format. Yeah, implementing<br class="">this using the raw FFmpeg API will take some time.)<br class=""></blockquote><br class=""><br class="">I’d like to chime in on that one.<br class="">While I’m using FFmpeg on OS X only (at least right now), I wouldn’t insist of having an OS X only wrapper.<br class="">A C++ cross-platform one would work just as well for me. <br class=""></blockquote><br class="">Sure, that's kind of hard to do with Cocoa/Swift.<br class=""><br class="">(Also, C++ APIs are useful for C++ code only.)<br class=""></div></blockquote><div><br class=""></div>Not exactly. They don’t work in Swift (there are also ways to use C++ source there) but they can be used in Objective-C (then called Objective-C++) without any action on the developer’s side.</div><div>You simply need to change the file extension from m to mm. Not a big deal.</div><div><br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">Alternatively, it would be really cool to add a high-level API for the most common use cases to the roadmap:<br class="">Getting frame N of video in a specific format, getting audio samples from N to M in a specific format.<br class=""></blockquote><br class="">I don't think the FFmpeg project would be opposed to adding such a<br class="">high-level (C) API. It was often talked about, but of course nobody has<br class="">time etc….<br class=""></blockquote><br class=""></div><div>Well, then the only solution is creating a high level wrapper?</div><div><br class=""></div><div apple-content-edited="true" class=""><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; " class=""><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; " class=""><div class=""></div></span></div>
</span></div>
<br class=""></body></html>