From what I am reading regarding the VLC documentation, if you use a plugin I.E the MBS VLC plugin or in fact VLC directly itself , and play back any h264/265 media, by law you have to release your source code. Can anyone confirm or deny this?
from their website:
libVLC is a C library which can be embedded in your own applications. It works with most popular OS platforms, on both mobile and desktop. It is under the LGPL2.1 license.
LGPL doesn’t require your app to be GPL.
Do you know if this includes h264 and h265 playback,
From what I have found it seems Using hardware-accelerated H.265 decoding (DXVA2, VAAPI, NVDEC) is not under LGPL.
I think VLC may use libxvlc inside its ffmpeg libs.
Is there a way in MBS to switch this feature off or to use software decoding?
Or is the standard playback using software not hardware playback.
Not sure if I play a h265 file, if MBS uses the software / hardware or which part of the FFMPEG libs that VLC uses.
just need clarifying before I use it on software that I may have to legally release the source for.
You could try and see if VLC would load without the dylib.
Not sure about this.
Its a rabbit hole,
Customer project license relies on
MBS, MBS relies on VLC
VLC relies on FFMPEG
Does it ever end, are there more, do license rights filter to the top.
Does this mean that you have to release the source to your code?