[Live-devel] VS2022 compilation issue

2023-11-30 Thread Dmitry Bely
rator\.conan2\p\b\live5372ee00a453a7\b\src\liveMedia\MPEGVideoStreamFramer.cpp(132,14): while trying to match the argument list '(TimeCode, TimeCode)' - Dmitry Bely ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

Re: [Live-devel] Use of std::atomic_flag

2023-11-29 Thread Dmitry Bely
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: >

[Live-devel] Use of std::atomic_flag

2023-11-29 Thread Dmitry Bely
tomic: the value can be changed elsewhere between test() and clear() and 2) it requires C++>=20. This can be easily fixed by replacing std::atomic_flag with std::atomic_bool, that needs just C++11. The patch is attached, maybe you find it useful. - Dmitry Bely --- a/BasicUsageEnv

Re: [Live-devel] H.264 PPS/SPS for the second client

2021-05-18 Thread Dmitry Bely
should pass them as parameters to the > call to “H264VideoRTPSink::createNew()”. If you do this, then the proper > "a=fmtp:” line containing "sprop-parameter-sets” will automatically appear in > your SDP description. Yes, that helped. I created an H.264 encoder beforehand, encoded

[Live-devel] SDP ntp range attribute for live streams

2021-05-17 Thread Dmitry Bely
t; than the stored or time-delayed version. This is needed since neither > absolute time nor zero time are appropriate for this case. I see no way to set this via inheritance without changing the library. - Dmitry Bely ___ live-devel mailing list

Re: [Live-devel] H.264 PPS/SPS for the second client

2021-05-17 Thread Dmitry Bely
ady > >> noted, this is not something that receivers should be relying on anyway. > > > > No, it's based on H264LiveServerMediaSubsession > > I don’t know what “H264LiveServerMediaSubsession” is. We have no class with > that name,. Sorry, copy/paste error. Actually H264

Re: [Live-devel] H.264 PPS/SPS for the second client

2021-05-17 Thread Dmitry Bely
On Mon, May 17, 2021 at 7:20 PM Ross Finlayson wrote: > > > > > On May 17, 2021, at 9:53 AM, Dmitry Bely wrote: > > > > On Mon, May 17, 2021 at 6:18 PM Ross Finlayson > > wrote: > >> > >> A receiver of a H.264 RTSP/RTP stream cannot rely on r

Re: [Live-devel] H.264 PPS/SPS for the second client

2021-05-17 Thread Dmitry Bely
g frames. Is it absolutely impossible to discard all NALs for the given RTP stream on the server side until SPS/PPS arrive? - Dmitry Bely ___ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] Fwd: H.264 PPS/SPS for the second client

2021-05-17 Thread Dmitry Bely
ly is not called when the second client connects (I double-checked that in debugger). Can you provide more detail on how to make the second concurrent client start its RTP session from correct PPS/SPS NALs? - Dmitry Bely ___ live-devel mailing list live-dev