The commit ca7d2ea4b6 introduced an xyzw
swizzle, whereas the previous code was using an rgba swizzle. No other
location used the xyzw swizzle for texture so unify and use rgba
everywhere.
Different version from aa5bec3b49
GL_LUMINANCE_ALPHA textures should be sampled through r and a swizzle
since it has a `(L,L,L,A)` layout.
This reverts commit 05f292874d.
Fixes#26767
Reintroduce #26735
inconsistent with that used in `coverartarchive_make_releasegroup_arturl()`.
i believe that with-dash is likely the correct form, since firstly, that
function is actually used unlike this one, and this function was also
fundamentally broken before the previous commit. also secondly, the info
at [1] seems to indicate that with-dash is correct.
[1]: https://github.com/Borewit/musicbrainz-api
Relaxed because we don't need synchronisation with other variables.
gain_factor and output_factor are write from different threads, so a
sequentially consistent ordering won't help.
- output_factor is read from aout_volume_Amplify(), called from the
input/decoder.c DecoderThread.
- output_factor is written from aout_volume_SetVolume(). It is either
called from the same thread via the start cb (OK in that case) or
from any threads via the volume_set cb.
All aout users can trigger a destroy, when releasing, if the refcount
reaches 0.
This will allow having more than one aout users (stream from decoder.c),
for gapless and later for multiple streams playback. Indeed, you prefer
not to destroy the aout from one decoder, while used by another decoder.
This introduces a patch to fix compilation on AArch64 on AppleOS, which
currently fails due to a compiler flag used by gnutls that is
unsupported by the latest version of clang (Apple clang version 13.1.6,
clang-1316.0.21.2) leading to a compiler crash if used.
This resolves the upstream tickets
https://gitlab.com/gnutls/gnutls/-/issues/1347 and
https://gitlab.com/gnutls/gnutls/-/issues/1317 for which the same patch
was already suggested.
having the three models always present, means that the data (at least the first
chuck) is loaded 3 times, and will be reloaded 3 times every time a database
event triggers a refresh of the model.
This remains is disabled by default, The extra cost isn't really worth it as
move operations originated from the database are very rare, move operations from
the user are usually handled "a priori".
