Cristiano Belloni wrote:
> Because it will mean creating also my own
> subclass of "MediaSubSession", and of "MediaSubsessionIterator", as far
> as I know.
Errata corrige: should be: 'Because it will mean creating also my own
subclass of "MediaSession", and of "MediaSubsessionIterator", as far
Ross Finlayson wrote:
> It sounds like you are trying to implement your own (nonstandard) RTP
> payload format - therefore I'm not able to help you. However, if you
> still wish to proceed down this route, then you will need to (i)
> implement your own subclass of "MultiFramedRTPSink" for trans
>Ok, let's say the cam sends me a pure MPEG4 stream, with no custom headers:
>
>1) Is there a way to set up a function that's called every time an RTP
>packet is received?
Yes - it already exists, in the implementation of the
"MPEG4ESVideoRTPSource" class: i.e., in the implementation of the RTP
[EMAIL PROTECTED] wrote:
>>> > I'm saying that you might not need to write any new (sub)classes at
>>>
all. Can you tell me some more about what your data looks like -
i.e., what video codec are you using, and how is the data different
from the standard?
>> > I'm saying that you might not need to write any new (sub)classes at
>>> all. Can you tell me some more about what your data looks like -
>>> i.e., what video codec are you using, and how is the data different
>>> from the standard?
>>>
>>It's MPEG-4 data, 1440 bytes a packet.
>
> MPEG-4 f
> > I'm saying that you might not need to write any new (sub)classes at
>> all. Can you tell me some more about what your data looks like -
>> i.e., what video codec are you using, and how is the data different
>> from the standard?
>>
>It's MPEG-4 data, 1440 bytes a packet.
MPEG-4 frames a
Cristiano Belloni wrote:
> Ross Finlayson wrote:
>
>>> Ross Finlayson wrote:
>>>
>>>
> However, I need some info: the camera I'm contacting does not send normal
> video frames, but custom ones. I need to unpack every RTP packet (_in
> order_), read the custom headers,
Ross Finlayson wrote:
>> Ross Finlayson wrote:
>>
However, I need some info: the camera I'm contacting does not send normal
video frames, but custom ones. I need to unpack every RTP packet (_in
order_), read the custom headers, reconstruct the frames and decode them
on
>Ross Finlayson wrote:
>>> However, I need some info: the camera I'm contacting does not send normal
>>> video frames, but custom ones. I need to unpack every RTP packet (_in
>>> order_), read the custom headers, reconstruct the frames and decode them
>>> on the fly.
>>>
>>
>> Because your
Ross Finlayson wrote:
>> However, I need some info: the camera I'm contacting does not send normal
>> video frames, but custom ones. I need to unpack every RTP packet (_in
>> order_), read the custom headers, reconstruct the frames and decode them
>> on the fly.
>>
>
> Because your 'custom hea
>However, I need some info: the camera I'm contacting does not send normal
>video frames, but custom ones. I need to unpack every RTP packet (_in
>order_), read the custom headers, reconstruct the frames and decode them
>on the fly.
Because your 'custom headers' are not RTP-specific, but are inste
Hi, parallel to my RTSP server I'm developing a client to interface with
some ip-cams.
I read openRTSP source, and I modified it to my needs, and it works
wonderfully.
However, I need some info: the camera I'm contacting does not send normal
video frames, but custom ones. I need to unpack every RT
12 matches
Mail list logo
