Usually contains picture

No need to multiply it for each pixel

No need to multiply the alpha value, we're not using the result.

We can do the primaries transformation before the linear conversion, it's
just translating from one coordinate system to another.

We still have the sampled value before we return.

No need to do the operation for each pixel each time.

In older shader models it reduces the amount of operations needed.

We can only convert to/from studio range once. The special case where the YUV
to RGB conversion is handled by the matrix can be handled before deciding the
range conversion to apply.

In the case of YUV full range the YUV->RGB will convert it to "extra full" so
we must scale back the range.

The maximum range of HLG is 1000 nits.

No need for an extra step, which is only used in one case.

It works by just using Texture2D with the proper resource view. We don't use a
texture index anyway.

And rename D3D11_CompilePixelShader to D3D11_CompilePixelShaderBlob for
consistency.

LIBVLC_VIDEO_UPDATE_OUTPUT doesn't exist.

In some cases the decoder might ask for a decoder device that will use the
setup callback. But in the end it's not using the decoder device. Then the
display module is created, without knowing about that decoder device (via a
video context) and calls the setup callback again.

Unless the decoder device that is created in the vout is passed to the display
module, we need to allow those multiple calls per session.

Fix the D3D11 sample to take this in account. The D3D9 sample already takes
care of it.

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

This patch updates the style of play button according to the latest changes in the design.

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

blendColors(text, bg, 0.6) does not provide enough contrast with textInactive

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

>From Qt 5.14.0, Qt::SplitBehavior enum is available and QString::split function causes warning when QString::SplitBehavior enum is used.

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

This patch fixes the SortControl close animation which was not working when Qt 5.15 was used.

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

This patch fixes the OverlayMenu open animation not working when Qt 5.15 is used.

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

This patch fixes the race condition in the playlist regarding symmetric drop indication. The race condition was causing problems when Qt 5.15 was being used.

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

Fatih Uzunoğlu authored 4 years ago and Pierre Lamot committed 4 years ago

Signed-off-by: Pierre Lamot <pierre@videolabs.io>

This is a quick fix for #25296 actually reverting the commit
a708c988, replacing the Hold/Release
lifecycle used there by an ad-hoc Hold/Release which actually defer the
actual release by blocking instead of releasing in the preparser thread.

Indeed, libvlc_media is holding the instance used to create it, though
it only needs it for preparsing. If the last reference of the media is
hold by the preparser, libvlc_media will be released by the preparser
thread and the libvlc_instance potentially released from there too.
Since killing the libvlc_instance will join the preparser thread, it
cannot be done from the preparser thread, or would lead to the failure
detailed in #25296. Written differently, only the final client should
make use of Hold/Release, directly through the adequate function or
indirectly through the creation of new objects.

In addition, a708c988 cannot just be
reverted as it was fixing cases where the libvlc_media_t object were
released before preparsing is finished, and the libvlc application
cannot just wait for the preparsing event to arrive since it must still
typically unlock the event manager and manage subitems.

Ideally, the libvlc_media would just not have a strong reference to the
libvlc instance, which would allow detaching the libvlc state from the
libvlccore state, but it cannot be done just yet, since the preparsing
API must be splitted from libvlc_media first.

Fix #25296

...and remove the obsolete comment, the cases have been fixed and should
be fixed if it happens again.

We don't need "proper event handling" as most errors are coming from
programmation errors, except in a few tests (like 16bit texture test)
which have been fixed already.