Hi Timo Well the copyright message at the top of nvEncodeAPI.h in the 7.0 SDK is identical to that for 6.0 so it looks ok in that respect.
I agree it’s an inconvenience to have to register and wait for approval (although mine came immediately and automatically). Regards Oliver > On 27 Aug 2016, at 14:49, Timo Rothenpieler <t...@rothenpieler.org> wrote: > > On 8/25/2016 7:56 PM, Oliver Collyer wrote: >> Hi Timo >> >> Thankyou for the clarification. >> >> Attached are what should be the final versions of these patches then, with >> the support for YUV420P10 (and related conversion code) now dropped. > > While testing these patches, I noticed that you now have to go through a > lenghty registration and confirmation process(read: I wasn't able to get > the Version 7 Header/SDK yet, waiting for manual approval of my Video > SDK registration). > > I definitely hope the nvEncodeApi header is still MIT licensed, > otherwise it would force me to reject these patches, or re-introduce the > non-free flag for nvenc. > > Either way this is a horrible situation, as bumping the SDK requirement > to version 7 forces every user to go through the same registration process. > I'll push for another attempt of including the header in ffmpeg once I > get it. Provided it is still MIT licensed. > > Until that is somehow sorted, I'll wait with merging these patches. > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
