>Using either VLC or an inhouse decoder/client, we make an RTSP play
>request to the server for playback of a file at normal (1x) speed. We
>have a variety of compliant transport streams, and for most of them, the
>playback is extremely slow.
>With live555mediaserver version 0.15 we see the first f
Using either VLC or an inhouse decoder/client, we make an RTSP play
request to the server for playback of a file at normal (1x) speed. We
have a variety of compliant transport streams, and for most of them, the
playback is extremely slow.
With live555mediaserver version 0.15 we see the first frame
1. Is there specific reasoning that LIVE555 does not use STL?
Basically, because I want this software to be useful for environments
(e.g., embedded systems) for which STL might not be available, or
might incur an excessive memory footprint if it were used.
2. I saw in the online "todo" li
A couple of general design questions, if you please:
1. Is there specific reasoning that LIVE555 does not use STL? I have not
worked with the STL before, so I can't really answer this question when it
comes up.
2. I saw in the online "todo" list that there was an item to change
certain data
>We have a multithreaded application (using live555 / linux)
I hope you've read the FAQ about threads.
>Under circumstances, some of our customers want to use for their video
>sources two different multicast addresses (let's say 239.61.87.46 and
>239.61.87.46)
FWIW, those are the same multicast
Hi,
We have a multithreaded application (using live555 / linux) acquiring
many video streams (RTP/multicast) and displaying them on differents
video outputs (monitors).
Under circumstances, some of our customers want to use for their video
sources two different multicast addresses (let's say 239.
