Pierre Lamot authored 5 years ago and Jean-Baptiste Kempf committed 5 years ago

  MLNetwork... classes have been renamed to Network...

  no functionnal changes

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Pierre Lamot authored 5 years ago and Jean-Baptiste Kempf committed 5 years ago

  no functionnal changes

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

Pierre Lamot authored 5 years ago and Jean-Baptiste Kempf committed 5 years ago

  no functionnal changes

Signed-off-by: Jean-Baptiste Kempf <jb@videolan.org>

We get the real DXGI_FORMAT from the video context now.

Taking in account the bitdepth and chroma subsampling.

Log the format that was picked that way.

Then we can fallback to YUV.

And the other way around if one is not found.

This is the source format we use to render, not the swapchain format which is more
likely to use RGB.

Rather than excluding formats, we might just include them.

Otherwise a callback during deletion could end up using already
destroyed member variables
Fix #23085

We only need the database to be available, which doesn't require calling
start()

- Always create the instance as part of the constructor
- Replicate the 2 initialize() & start() steps in the module
This will allow more control in later commits

Which was not failing because the pointer was implicitely converted to
boolean, and the default value was used for the pointer parameter.

To create the vout for the decoder device we can call decoder_UpdateVideoOutput
but only when we know the output format. Otherwise we need to set a usable
output format before we call decoder_GetDecoderDevice().

Prioritize the SAR from the container over the decoder one.

The video context will be released but it private data are not set yet.

It's better in the picture context.

We should not have to store the "p_sys" of the picture, it's always part of the
video context.

Don't use picture_NewFromResource() since we don't provide pixel resources.

It's better in the picture context.

We should not have to store the "p_sys" of the picture, it's always part of the
video context.

Don't use picture_NewFromResource() since we don't provide pixel resources.

The others don't allocate surfaces from that DLL.

Alexandre Janniaux authored 5 years ago and Thomas Guillem committed 5 years ago

Otherwise, we end up calling eglDestroyContext with a bad value in the
case the surface cannot be create. Not being able to create the surface
isn't even rare as it can happen if the format we required is not supported.

Harmless regression from f5a766e3

Signed-off-by: Thomas Guillem <thomas@gllm.fr>

cf. WASAPI_EXCLUSIVE_LONGTEXT

But don't use VLC_CODEC_S24N as this fourcc is not handled by any audio
filters. Instead, request VLC_CODEC_S32N to VLC and do the conversion
internally.

This commit is needed by the next commit since some sound cards only support
24bits.

The ID3D11DeviceContext is carried by the video context and is not needed.

The texture format is also stored in the video context but it wasn't used anyway.

This adds a separate target to add an SDK version of the macOS
binaries. This package is the result of a destroot'ed 'make install'

It shall serve two purposes:

1) Out of tree modules compilation: Module authors can use the included
pkgconfig files to link against libvlc(core) for their own modules.
This is similar to the existing SDK we have on Windows.

2) Packaging libvlc for our own app: If someone does not want to use
VLCKit, but links against libvlc directly, these precompiled artefacts
can be used for packaging the libs into the own app. Packaging shall
be done in the same way as with VLC.app (i.e.: lib/* and the vlc plugins
directory goes to Contents/Frameworks, share/ goes to
Contents/Resources/share/ if needed). In this case, all ressources are
found by libvlc automatically.

Users can also execute vlc directly from the extracted tarball, after
specifying LD_LIBRARY_PATH and VLC_PLUGIN_PATH. Using the macOS UI
module is not supported.

This gets rid of a prefix inside our build dir, and uses DESTDIR
when installing the content. This way, the install directory
can be reused for further packaging introduced in the next commits.