Coverity complains about that (CID 472128), possibly rightfully - it
seems like the init of atomic variable doesn't need to be necessarily
atomic (while the asignment is).
current FFmpeg version dd2976b9 doesn't compile with SVT-AV1 commit
9485b939 with following error:
```
libavcodec/libsvtav1.c:240:14: error: ‘EbSvtAv1EncConfiguration’ has no member named ‘enable_adaptive_quantization’
240 | param->enable_adaptive_quantization = 0;
```
- for bool, nullptr compat, the comparison to 202311L should be <, not <=
- separate bool/nullptr compat for clarity
- improved countof compat - if c23, check stdcountof.h presence with
__has_include and use if present rather than defining the macro always
Because many of files didn't include messaging.h and used to have included
it indirectly, in all of them, the correct messaging.h include must have
been added.
It requires _POSIX_TIMEOUTS to be defined (as it isn't in macOS) but
unistd.h was never included so it wasn't used even on platforms where
pthread_mutex_timedlock() is implemented.
Included with debug.h (for logger) so it would leak the definitions to
almost all compilation units.
Just STRINGIFY is required so rather make a local copy of the macro
(prefixed COLOR_OUT).
+ include macro.h in files that should include that but didn't include
it directly
technically it will be C2Y but the c23.h can be perhaps used for both
in c++, std::size() is rather used
This fixes compilation of pano_gl, where its implementation
of countof clashes with the macro (leaked through
debug.h->color_out.h->utils/macros.h, which no longer contains that
define).
With v5, NDI doesn't compile because of NDIlib_frame_type_source_change
missing. According to the NDI license, the most recent version should
be used, anyways.
If --enable-screen is used in Linux without specifying explicitly
x11 or pipewire, require both. The user may need to have the PipeWire
implementation and end up with X11 or vice versa.
Also fix the check for implementation - checked X11 only if
--enable-screen=x11 (without PW) and vice versa for Pipewire. But not
eg. --enable-screen=x11,pipewire.
Also changed configure.ac so that Pipewire screen cap requirements
are checked only in Linux (in other platform currently perhaps not
expected the use of Pipewire screen capture).
set the given <preset> as AVCaptureSessionPreset<Preset> (first letter
converted explicitly to upper-case for backward compatibility when there
has been "low" option not "Low")
If the desktop is 2880x1800, the main profile would capture 480x300, which
is perhaps unexpected - even though the resolution doesn't necessarily
need to be native, 480x300 is perhaps too small. For the FaceTime HD Camera
480x360 so it is better to keep the default (deskotp native, FaceTime 720p).
- suggest also AVCaptureSessionPreset1920x1080
- do not advertise HD - it was actually 720p, users may expect 1080p
(but still allow the setting)
- updated examples - added the "long" preset option, some opts now
use shortcuts
This is handled differently and may trigger unexpected decode to HW_VDPAU
if gl display advertises that, eg. `uv -t testcard -c lavc:c=MJPG -d gl`.
This fixes the commit 647d8627 (2025-06-25) that unintentionally
enabled that.
The HW accel is hanndled actually separately ahd snouldn't be "enabled"
in this way.
