> On Nov 30, 2023, at 6:50 AM, Dmitry Bely wrote:
>
> BTW I'm curious what the purpose of std::atomic_flag? What was wrong with
> good old "volatile bool"?
FYI, that’s what you get if you compile with -DNO_STD_LIB
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
On Wed, Nov 29, 2023 at 4:09 PM Ross Finlayson
wrote:
>
> > On Nov 30, 2023, at 4:14 AM, Dmitry Bely wrote:
> >
> > Hi,
> > Recent versions of live555 use std::atomic_flag array to work with
> > event triggers. Consider the following code fragment:
> >
> > #ifndef NO_STD_LIB
> > if (fTrigger
> On Nov 30, 2023, at 2:27 AM, Ayik Ahmet wrote:
>
> Hello, I have implemented a RTSP server based on live555 from my live source
> it works well with h264 and mjpeg. My question is that is there any feature
> of live555 such as estimated bitrate for provided frames. By this way I can
> cont
> On Nov 30, 2023, at 4:14 AM, Dmitry Bely wrote:
>
> Hi,
> Recent versions of live555 use std::atomic_flag array to work with
> event triggers. Consider the following code fragment:
>
> #ifndef NO_STD_LIB
> if (fTriggersAwaitingHandling[i].test()) {
> fTriggersAwaitingHandling[i].c
Hello, I have implemented a RTSP server based on live555 from my live source it
works well with h264 and mjpeg. My question is that is there any feature of
live555 such as estimated bitrate for provided frames. By this way I can
control my codec while encoding h264 frames.
Thanks in advance
Ahm
Hi,
Recent versions of live555 use std::atomic_flag array to work with
event triggers. Consider the following code fragment:
#ifndef NO_STD_LIB
if (fTriggersAwaitingHandling[i].test()) {
fTriggersAwaitingHandling[i].clear();
#else
It is problematic in two ways: 1) it's not atomic:
