Fischer Daniel | 2 May 2011 09:08
Picon
Favicon

How to bypass streamlimit causes by EventTriggerIDs

xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">

Hello,

 

I am using live555 to stream several network cameras. For that I generate one RTSP-Server and for every camera a subsession on this server with a new URL. To signal the TaskScheduler, that there is a new frame for a stream, I use a EventTriggerID. Every stream has his own EventTriggerID. Now I got the problem, that the EventTriggerID is generated by a bitmask (0x80000000), and the line

 

“m_EventTriggerId = envir().taskScheduler().createEventTrigger(deliverFrame0);”

 

generates only 32 EventTriggerID´s, so that I have a maximum of 32 stream receivers.

Now my question: Is it possible to solve that problem without generating more RTSP-Server with different TaskScheduler on different ports? Can you make me a suggestion how I bypass these limit of maximum stream receivers?

 

Thank you for your efforts

 

With greet

Daniel Fischer

 

Viele Grüße / Best regards
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Dipl.-Inf. (FH)
Daniel Fischer
iGuard - Development

IDS Imaging Development Systems GmbH
Dimbacher Strasse 6-8
D-74182 Obersulm
Handelsregister: Stuttgart HRB 106225
Geschäftsführer: Jürgen Hartmann, Armin Vogt, Torsten Wiesinger
T :        +49 (0)7134 / 961 96-0
F :        +49 (0)7134 / 961 96-99
E :        d.fischer <at> ids-imaging.de


Web: www.ids-imaging.com  -  www.iguard.de
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 P   Please consider the environment before printing this e-mail

 

_______________________________________________
live-devel mailing list
live-devel@...
http://lists.live555.com/mailman/listinfo/live-devel
Chuck Hess | 2 May 2011 21:42
Favicon

wis-streamer and the -d option for DarwinInjector



 

I was looking at the wis-streamer source and I'm intrigued by the -d option, but I can't seem to get it to work.

I can use wis-streamer as-is and view the live stream from a remote quicktime player, but not a cell phone.   I'm guessing that this is due to the lack of rtsp over http support.

I'm able to use the test utility in the live project to stream and view a test.m4e file via DarwinInjector.
When I use wis-streamer with the -d option, I get a test.sdp file in my movies directory, but both quicktime, cell phones, and vlc say that the file is not found after buffering.

Any ideas?

Thanks.

 


_______________________________________________
live-devel mailing list
live-devel@...
http://lists.live555.com/mailman/listinfo/live-devel
Álvaro Rodríguez Pérez | 3 May 2011 12:14
Picon

RTSP decoding

Hello,

I´m trying to receive a RTSP Stream with live555 and decode the stream 
with ffmpeg. I´ve seen on some messages that there is information about 
this issue in the FAQ but I can´t find the correct reference. ¿Can 
someone help me?

Thank you very much.

Álvaro.

--

-- 
Álvaro Rodríguez
SoftTelecom
www.softtelecom.es
UPM Campus de Montegancedo
PARQUE CIENTÍFICO Y TECNOLÓGICO UPM
28223 POZUELO
MADRID
Bruno Abreu | 3 May 2011 12:21
Picon
Favicon

RTSPServer crash with simultaneous identical requests

Hello,

we've been using the RTSPServer to stream both live and stored video.

Because of our client's specific needs, particularly when asking for stored videos,
sometimes we get identical requests from 2 clients simultaneously (i.e. a few
milliseconds apart) and, whenever that happens, the server crashes.

Because we've extended the RTSPServer (as in the DynamicRTSPServer of the Media Server
app) to parse the clients' requests, we went back to test some basic things to make sure
that the error was not introduced by our enhancements.

So we ran testOnDemandRTSPServer with some of the videos you supply for tests and
created a simple shell script with the following lines for the clients:

#!/bin/sh
./openRTSP -F "0-" rtsp://127.0.0.1:8554/h264ESVideoTest > openRTSP-0.log 2>&1 &
./openRTSP -F "1-" rtsp://127.0.0.1:8554/h264ESVideoTest > openRTSP-1.log 2>&1 &

This should launch (almost simultaneously) two instances of openRTSP that ask for the
same video segment from the server. And we got similar results to our app.

Either the server crashes with a segfault or it delivers the video correctly to one of
the clients but it delivers a SDP description containing errors to the 2nd (or so
openRTSP complains). From that point on every new request from a client receives a
corrupted SDP description.

Below is the stack trace from one of the server crashes:

gdb ./testOnDemandRTSPServer core
...
Core was generated by `./testOnDemandRTSPServer'.
Program terminated with signal 11, Segmentation fault.
#0  0xb73bc000 in ?? ()
(gdb) bt
#0  0xb73bc000 in ?? ()
#1  0x08069969 in MultiFramedRTPSink::ourHandleClosure (clientData=0x89124d8) at
MultiFramedRTPSink.cpp:413
#2  0x0804f9a8 in H264VideoFileServerMediaSubsession::checkForAuxSDPLine1 (this=0x8905bf8)
    at H264VideoFileServerMediaSubsession.cpp:61
#3  0x0804f9f9 in checkForAuxSDPLine (clientData=0x8905bf8) at
H264VideoFileServerMediaSubsession.cpp:57
#4  0x08077f5f in AlarmHandler::handleTimeout (this=0x8912780) at BasicTaskScheduler0.cpp:34
#5  0x08076a72 in DelayQueue::handleAlarm (this=0x32482036) at DelayQueue.cpp:180
#6  0x080760e5 in BasicTaskScheduler::SingleStep (this=0x8905008, maxDelayTime=0) at
BasicTaskScheduler.cpp:189
#7  0x08077617 in BasicTaskScheduler0::doEventLoop (this=0x8905008, watchVariable=0x0)
at BasicTaskScheduler0.cpp:80
#8  0x0804a011 in main (argc=<value optimized out>, argv=<value optimized out>) at
testOnDemandRTSPServer.cpp:264

And here is the part of the log from one of the openRTSP clients:

Opened URL "rtsp://127.0.0.1:8554/h264ESVideoTest", returning a SDP description:
v=0^M
o=- 1304352757340991 1 IN IP4 10.10.9.211^M
s=Session streamed by "testOnDemandRTSPServer"^M
i=h264ESVideoTest^M
t=0 0^M
a=tool:LIVE555 Streaming Media v2011.03.14^M
a=type:broadcast^M
a=control:*^M
a=range:npt=0-^M
a=x-qt-text-nam:Session streamed by "testOnDemandRTSPServer"^M
a=x-qt-text-inf:h264ESVideoTest^M
m=video 0 RTP/AVP 96^M
c=IN IP4 0.0.0.0^M
b=AS:500^M
a=rtpmap:96 H264/90000^M
øfË^H^XdË^HliveMedia33a=control:track1^M

Failed to create a MediaSession object from the SDP description: Invalid SDP line:
øfË^H^XdË^HliveMedia33a=control:track1^M

I'd like to point out that we're using the latest version of live555 and that, for these
tests, not a single line of code as been touched.

We would like to know if this is a bug that will get fixed in the future or, simply,
something that is not allowed.

Any help would be appreciated
Thank you

Bruno Abreu

--
Living Data - Sistemas de Informação e Apoio à Decisão, Lda.

Rua Luís de Camões, Nº 133, 1º B      Phone:  +351 213622163
1300-357 LISBOA                       Fax:    +351 213622165
Portugal                              URL: www.livingdata.pt
Guillaume Ferry | 3 May 2011 13:40
Picon
Favicon

Questions about MPEG2 transport streams

Hi Ross,

I'm currently using openRTSP to receive MPEG2 transport streams.
I'd rather have N subsessions for N streams, but I'm not responsible for these servers, so I must stick with TS packets.

And here are my two questions :
  • Is it possible, in a RTSP client, to select a specific stream among the others, and only receive this one ? I think it's not possible, but maybe you have some code to so in liveMedia APIs ?
  • Otherwise, are there some methods available, always on client' side, to parse a TS packet, list its inner streams, and extract one ?
I think I could do the job with FFmpeg, but it would be lighter / simpler if I could avoid it !

Thanks in advance for your insights,

Best regards,
Guillaume.
--
Guillaume FERRY
Bertin Technologies
Département Bertin Conseil
Activité Traitement de l'Information et du Contenu
Tél 01.39.30.62.09
Fax 01.39.30.62.45
Mail ferry-hx6lN0jroRVQFI55V6+gNQ@public.gmane.org
Web www.bertin.fr
_______________________________________________
live-devel mailing list
live-devel@...
http://lists.live555.com/mailman/listinfo/live-devel
Felix Radensky | 11 May 2011 08:27

Strange problem with h264 streaming

Hi,

I have a strange problem with latest version of live555.
I'm streaming h264 via RTSP. The video is produced by
hardware encoder. In my code I use H264VideoStreamDiscreteFramer
class and event triggers to notify the streamer thread about
the availability of new h264 buffer. I use VLC as a viewer.

The streaming can run four hours without problems, but at some point
streamer starts sending tons of RTCP Receiver Report messages,
which hang the CPU and the viewer completely.

Any ideas what can cause such behaviour will be greatly appreciated.

Thanks a lot.

Felix.
Bruno Filipe Basilio | 11 May 2011 15:35
Picon
Favicon

Re: Strange problem with h264 streaming

Hi Felix,

I have a similar problem.
After 3 days playing I couldn't access the RTP/RTCP server PC anymore. Pinging didn't work either. Only
after a reboot everything is ok.
A few days later the same happened.

And now I discovered something even stranger:
I sniffed the network traffic going to and going from the server to see if I was missing anything:

Analyzing the traffic I saw a stream coming from the server that was 35Mbps analyzing it some more it is a RTCP
stream -> this doesn't seems OK (a rtcp stream that is 20 times bigger than the actual video stream)

Seeing this I did some more experiments:
1)      first I power off power on the server and put it in a separate lan.
After sniffing the network I found 4 multicast streams coming out of it:
-       232.29.51.215:18888 -> rtp video stream from 2Mbps
-       232.29.51.215:18889 -> rtcp sender reports (a few of them)
-       232.218.63.39:18890 -> rtp video stream from about 200kbps
-       232.218.63.39:18891 -> rtcp sender reports (just a few of them)
2)      A placed a 2 decoders in the network and ask the rtsp multicast stream for both of them
I received the stream and could decode it (the stream was 232.29.51.215:18888)
But the rtcp stream 232.29.51.215:18889 suddenly became enormous about 35 Mbps
I think this is a bug and this is causing eventually the strange behavior I mention earlier (not reacting on
ping anymore)

Best regards,
Bruno Basilio
Brisa Inovação e Tecnologia, S.A.

--------------------------------------------------------------------------------

Declaração:
A informação contida nesta mensagem, e os ficheiros anexos, é privilegiada e confidencial,
destinando-se exclusivamente ao(s) destinatário(s).Se não é o destinatário (ou o responsável
pela sua entrega ao destinatário) e recebeu a mesma por engano, fica notificado que é estritamente
proibido reproduzir, guardar ou distribuir toda ou qualquer parte desta mensagem e ficheiros
anexos.Por favor reencaminhe a mensagem para o responsável pelo seu envio ou contacte-nos por telefone
e elimine a mensagem e ficheiros anexos do seu computador,sem os reproduzir.

Disclaimer:
The information contained in this message, and any files attached, is privileged and confidential, and
intended exclusively for the included addresses.If you are not the intended recipient (or the person
responsible for delivering to the intended recipient) and received this message by mistake, be aware
that copy, storage, distribution or any other use of all or part of this message and the files attached is
strictly prohibited. Please notify the sender by reply e-mail or contact us by telephone and delete this
message and the files attached, without retaining a copy.

--------------------------------------------------------------------------------
Bruno Filipe Basilio | 11 May 2011 18:30
Picon
Favicon

Re: Strange problem with h264 streaming

>> I'm streaming h264 via RTSP. The video is produced by
>> hardware encoder. In my code I use H264VideoStreamDiscreteFramer
>> class and event triggers to notify the streamer thread about
>> the availability of new h264 buffer.

> What is your video source ? Is it h264 or something else ?

My video source is also a live encoder with h264.
But instead of using event triggers to notify new frames we are waiting for it using TaskScheduler::turnOnBackgroundReadHandling().

Bruno

--------------------------------------------------------------------------------

Declara??o:
A informa??o contida nesta mensagem, e os ficheiros anexos, ? privilegiada e confidencial,
destinando-se exclusivamente ao(s) destinat?rio(s).Se n?o ? o destinat?rio (ou o respons?vel pela sua
entrega ao destinat?rio) e recebeu a mesma por engano, fica notificado que ? estritamente proibido
reproduzir, guardar ou distribuir toda ou qualquer parte desta mensagem e ficheiros anexos.Por favor
reencaminhe a mensagem para o respons?vel pelo seu envio ou contacte-nos por telefone e elimine a
mensagem e ficheiros anexos do seu computador,sem os reproduzir.

Disclaimer:
The information contained in this message, and any files attached, is privileged and confidential, and
intended exclusively for the included addresses.If you are not the intended recipient (or the person
responsible for delivering to the intended recipient) and received this message by mistake, be aware
that copy, storage, distribution or any other use of all or part of this message and the files attached is
strictly prohibited. Please notify the sender by reply e-mail or contact us by telephone and delete this
message and the files attached, without retaining a copy.

--------------------------------------------------------------------------------
Felix Radensky | 11 May 2011 17:59

Re: Strange problem with h264 streaming

Hi Bruno,

On 05/11/2011 04:35 PM, Bruno Filipe Basilio wrote:
> Hi Felix,
>
> I have a similar problem.
> After 3 days playing I couldn't access the RTP/RTCP server PC anymore. Pinging didn't work either. Only
after a reboot everything is ok.
> A few days later the same happened.
>
> And now I discovered something even stranger:
> I sniffed the network traffic going to and going from the server to see if I was missing anything:
>
> Analyzing the traffic I saw a stream coming from the server that was 35Mbps analyzing it some more it is a
RTCP stream ->  this doesn't seems OK (a rtcp stream that is 20 times bigger than the actual video stream)
>
> Seeing this I did some more experiments:
> 1)      first I power off power on the server and put it in a separate lan.
> After sniffing the network I found 4 multicast streams coming out of it:
> -       232.29.51.215:18888 ->  rtp video stream from 2Mbps
> -       232.29.51.215:18889 ->  rtcp sender reports (a few of them)
> -       232.218.63.39:18890 ->  rtp video stream from about 200kbps
> -       232.218.63.39:18891 ->  rtcp sender reports (just a few of them)
> 2)      A placed a 2 decoders in the network and ask the rtsp multicast stream for both of them
> I received the stream and could decode it (the stream was 232.29.51.215:18888)
> But the rtcp stream 232.29.51.215:18889 suddenly became enormous about 35 Mbps
> I think this is a bug and this is causing eventually the strange behavior I mention earlier (not reacting on
ping anymore)
>
>

What is your video source ? Is it h264 or something else ?

Felix.
Felix Radensky | 11 May 2011 19:15

Re: Strange problem with h264 streaming

Hi Bruno,

On 05/11/2011 07:30 PM, Bruno Filipe Basilio wrote:
>>> I'm streaming h264 via RTSP. The video is produced by
>>> hardware encoder. In my code I use H264VideoStreamDiscreteFramer
>>> class and event triggers to notify the streamer thread about
>>> the availability of new h264 buffer.
>> What is your video source ? Is it h264 or something else ?
> My video source is also a live encoder with h264.
> But instead of using event triggers to notify new frames we are waiting for it using TaskScheduler::turnOnBackgroundReadHandling().

Thanks. BTW, in my case the problem is immediately reproducible with 
smplayer.

Felix.

Gmane