It is possible to also have proprietary plugins around VLC, as long as you can comply to the LGPL, for all libraries involved.Īgain, in layman's terms, if you have a proprietary plugin, you should: It is however strongly advised to only use LGPL plugins. Also, you need to separate clearly your app from libVLC (use of dynamic linking makes it much easier). What it means, in layman's terms, is that you can use libVLC in your app, without open sourcing it, as long as the modifications to the VLC core and plugins are re-shared to the users and community. One must comply with the LGPL terms, for libVLCcore, VLC plugins and libVLC. Since libVLC is licensed under LGPLv2, one can do applications based on libVLC which are not licensed under the GPL (different open source licenses, or non-open source applications).
LibVLC, license and proprietary applications Able to cast and stream to distant renderers, like Chromecast and UPnP renderers.Support for 360/VR video and 3D audio playback, including Ambisonics.Support for complex video and audio filters.Audio passthrough with SPDIF and HDMI, including for Audio HD codecs, like DD+, TrueHD or DTS-HD.Support for 8K and HDR, including tonemapping for SDR streams.
Playback of Audio CD, DVD and Bluray with menu navigation.Network browsing for distant filesystems (SMB, FTP, SFTP, NFS.) and servers (UPnP, DLNA).Hardware and efficient decoding on every platform, up to 8K.
0 kommentar(er)
