> > >2. For H.264, is there any parser for the extra info returned by
>> >parseH264ConfigStr ?
>>
>> This data is a sequence of H.264 NAL units, and are therefore
>> parsed/interpreted by your H.264 decoder.
>
>Just a suggestion... For MPEG4, and H264, these infos are in the SDP
>so it is possi
Hi everyone,
Please give me an advice about this error message.
19:55:30 Groupsock(-1: 239.100.0.10, 32770, 255): failed to group
setsockopt(ID_ADD_MEMBERSHIP) error: Bad file descriptor
The problem is the "-1" - this is an invalid socket number.
For some reason, your socket didn't get crea
In RTSPServer::incomingRequestHandler1() conditional "if (bytesRead
<= 0 || (unsigned)bytesRead >= fRequestSpaceRemaining)"
Q: Is it really a failure if the number of bytes read == the amount
of space available?
Yes, because there would then be no room for us to add a trailing
'\0' character
Hi everyone,
Please give me an advice about this error message.
19:55:30 Groupsock(-1: 239.100.0.10, 32770, 255): failed to group
setsockopt(ID_ADD_MEMBERSHIP) error: Bad file descriptor
Regards.
Peter.
___
live-devel mailing list
live-devel@l
2007/12/5, Ross Finlayson <[EMAIL PROTECTED]>:
> The properties that you're asking about - video width & height, video
> frame rate, audio sampling frequency, audio number of channels are
> almost always contained within the media data themselves, and are
> therefore accessed by your decoding softw
Yes, this was the problem. I was ending with CTR+C. Now I see the ftyp box.
Then, I got a segmentaion fault in QuickTimeFileSink.cpp (line no. 1775)
char* psets =
strDup(fCurrentIOState->fOurSubsession.fmtp_spropparametersets());
size_t comma_pos = strcspn(psets, ",");
here psets returns
In RTSPServer::incomingRequestHandler1() conditional "if (bytesRead <= 0
|| (unsigned)bytesRead >= fRequestSpaceRemaining)"
Q: Is it really a failure if the number of bytes read == the amount of
space available?
I was thinking that it would be because we wouldn't know if there was more
to read
The properties that you're asking about - video width & height, video
frame rate, audio sampling frequency, audio number of channels are
almost always contained within the media data themselves, and are
therefore accessed by your decoding software (or hardware), when it
parses this media data.
Hi all,
I am implementing an RTSP Client using the livemedia and much of work
has been done successfully using the lib. Many thanks to developpers.
What I need is to discover the properties of any stream, i.e. video
width and height for audio and frequency/channels for audio in
different formats
Hi Ross,
Thanks for the prompt feedback and hints ;) It's much appreciated.
I actually came across your library via the Morgan RTP Direct Show filters ;)
Thanks again,
Ralf
--
This message is subject to the CSIR's copyright terms and conditions, e-mail
legal notice, and implemented Open Docum
>I'd just like to get a few pointers and want to know if I'm on the
>right track:
>So far it looks like I can base a simple test application on
>testMP3Streamer and testMP3Receiver?
>One major difference is that I want to control the sending of
>packets manually and it looks like the scheduler i
Hi,
I'd like to write a simple RTP/RTCP server and client using the live555
libraries. I've previously managed to do the same with jrtplib, but it looks
like the live555 libraries are more comprehensive since they offer RTSP and
other functionality too. At the same time I'm not quite sure where
Hello everyone,
I've read
http://lists.live555.com/pipermail/live-devel/2005-March/002170.html and
know that RTP retransmission is not implemented in liveMedia.
Could anyone give me some hint what I should do if I want to implement RTP
retransmission in liveMedia? Thanks
lcj
13 matches
Mail list logo
