Select Git revision
Search by author
- Any Author
- authors
-
Administrator root
-
Alaric Senat
asenat
-
Alexandre Janniaux alexandre-janniaux
-
Bart - The Review Bot
Bart
-
Benjamin Arnaud
bunjee
-
Christophe Massiot cmassiot
-
Claudio Cambra
claucambra
-
David dfuhrmann
-
Denis Charmet
typx
-
Fatih Uzunoğlu fuzun
-
Felix Paul Kühne
fkuehne
-
François Cartegnie
fcartegnie
-
Gabriel Lafond-Thenaille gabriel_lt
-
**** project_435_bot_867220ea9cbb40f38051abad33491375
-
**** project_435_bot
-
Ilkka Ollakka
ileoo
-
Jean-Baptiste Kempf
jbk
-
Jean-Paul Saman
jpsaman
-
Johannes Kauffmann
JohannesKauffmann
-
Konstantin Pavlov
thresh
- Mar 31, 2022
-
-
- Mar 30, 2022
-
-
This adds an additional info line to match the IPv6 implementation.
-
-
-
-
fixup 4e2f8238
-
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
-
and fix leak with the corrected logic.
-
volume is valid only if !bitexact.
-
It's really weird to call functions with a NULL pointer...
-
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.
-
-
-
This is essentially the same as timespec_to_vlc_tick() but it does not clobber the namespace, so it can be exported.
-
- Mar 29, 2022
-
-
Hugo Beauzée-Luyssen authored -
-
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.
-
It is a common design language to have the record button red. The animation provides a visual feedback when the user is currently recording.
-
-
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.
-
- Mar 28, 2022
-
-
CFLAGS is added to the linker flags and newer LLVM don't like that. CPPFLAGS is used during C compilation and C++ but not added to LDFLAGS.
-
- Mar 27, 2022
-
-
-
-
The keyword is nominally from C23, but it has been supported by GCC and Clang/LLVM for years.
-
-
Fixes #26738
-
Rémi Denis-Courmont authored
-
Hugo Beauzée-Luyssen authored
This is what the medialib now requires
-
Hugo Beauzée-Luyssen authored
-
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".
-
-
this would allow to move or update elements in "a priori" before getting the notification from the database
-
-
-
this allows to submit to the view only the changes made on the model when the database changes instead of invalidating and resetting the whole view. data cache is changed from a windowed view over the data, to a model where data is loaded from the start and loaded by chunk (append to the cache), when data is invalidated the data is reloaded in background and the difference (insertions and deletions) are propagated to the view.
-
-
-
