First, as you know (because you've read the FAQ :-), you shouldn't modify the
existing code 'in place'; see:
http://www.live555.com/liveMedia/faq.html#modifying-and-extending
Instead, you should write your own new subclass(es) (perhaps using the existing
code as a model, when necessary).
Hey folks,
Here's what I have:
- An iPhone app that reads audio input and writes to audio output
- One of these threads runs a DynamicRTSPServer session which runs a
WAVAudioFileServerMediaSubsession
- When I run this session with a wav file, WAVAudioFileSource::doReadFromFile()
is called, a
Just in case anyone else was actually following this thread, I thought I'd make
my final post in this thread the conclusion of the matter:
- Setting the packet reordering threshold time very low had a noticeable
impact. I originally tried setting it to zero, but oddly my benchmarks were
sligh
> I've been using live555 to stream and record video and audio from a camera
> with a variable frame-rate. I've gotten around the issue of needing a fixed
> frame-rate by sending copies of the last received image frame to the
> quicktime file sync when the frame-rate from the camera slows down,
Hi Ross,
I've been using live555 to stream and record video and audio from a camera with
a variable frame-rate. I've gotten around the issue of needing a fixed
frame-rate by sending copies of the last received image frame to the quicktime
file sync when the frame-rate from the camera slows dow
Your problem is that you are trying to call LIVE555 code (specifically, your
"Start()" and "Stop()" functions) from two separate threads. As stated very
clearly in the FAQ - ***that you were asked to read before you posted to this
mailing list*** - you cannot do this!
Instead, you should call
Here is my a "little modified" testRTSPClient.cpp [ Check PS for
full source code].
RTSPClient* rtspClient;// global handle
void Start()
{
// Begin by setting up our usage environment:
TaskScheduler* scheduler = BasicTaskScheduler::createNew();
UsageEnvironment* env = BasicUsageEnvironment::cr
> Live555 version 2012.02.29 is not compatible with Vivotek camera digest
> authentication.
(Why do I always get these sorts of reports from 3rd parties, and never from
the camera manufacturers themselves?)
> This is what Vivotek IP8161 camera sends when it cannot authrorize the client:
>
>
Hi,
Live555 version 2012.02.29 is not compatible with Vivotek camera digest
authentication. This is what Vivotek IP8161 camera sends when it cannot
authrorize the client:
- Rtsp: RESPONSE, RTSP/1.0, Status Code = 401 - Unauthorized
- Response: Status of response : Unauthorized
Protoc
