Yes, you're not aligning these presentation times with 'wall clock'
time - i.e., the time that you would get by calling "gettimeofday()".
So, the sample times I get from my encoder start at 0 and increase
(i.e. a relative timestamp); when you say 'wall clock' time, does
this mean I should be
Thank you for the clarification. One question about 'wall clock' time:
In the server, my samples come to me timestamped with a REFERENCE_TIME,
>> which is an __int64 value with 100 nanosecond units. So to convert from this
>> to the timeval, I do the following:
>>
>>// Our samples are 10
My problem is fPresentationTime; the values I hand off to Live555 on
the server side are not the values I get on the client side.
The presentation times that you generate at the server end *must be
aligned with 'wall clock' time - i.e., the times that you would
generate by calling "gettimeofda
I have an OnDemand RTSP server based around Live555 that streams out live
H.264; I implemented a subsession and framer. On the client side, I have a
receiver application based loosely around openRTSP, but with my own custom
H264 MediaSink class.
My problem is fPresentationTime; the values I hand
