[FFmpeg-user] Regarding ./configure and nonfree

[Top Secret]

Still looking for thoughts on the matter. 

 Oliver’s seems to point to more of the intricacies of the reasons. It’s odd that nvidia has cuda sdk then say use gstreamer or ffmpeg to use their stuff for decoding. Perhaps removing non free but allowing the rest of it will work. And if it doesn’t disable the parts of configure that break as a result.

Even in doing such a thing could result in compile or linker errors it wouldn’t come from nvidia but something else and then it’s a matter of what that is. If it’s something silly like oh we used this library with license issues so we make are whole use of nvidias as non free then simply supplying other functions to do it. 

> On Sep 10, 2024, at 4:59 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
> 
> 
> 
>> Am 10.09.24 um 18:02 schrieb Top Secret:
>> Hello All,
>> When I use "--enable-cuda --enable-cuvid --enable-nvdec --enable-nonfree" for configure string I aim to use some of the nvidia cuda decoders h264 for example to decode on gpu. I want to use this commercially is there a issue with this in terms of licensing?
> 
> What exactly in "nonfree" is not clear?
> You must not distribute the resulting binary - period
> 
> "I want to use this commercially" is unclear - If it means you share your binary you can't - If you are running the binary on your servers and it never leaves your house itÄs a nobrainer
> 
> 
> 
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".