Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-20 Thread Clemens Arth
>> I just have another question. Is there any code snippet in the test >> programs that shows how to safely destroy and restart an RTSPClient >> and/or RTSPServer without stopping the event loop? Whenever I do >> something like Medium::close(rtspServer), the event loop gets a "bad >> file descripto

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-19 Thread Ross Finlayson
> I just have another question. Is there any code snippet in the test > programs that shows how to safely destroy and restart an RTSPClient > and/or RTSPServer without stopping the event loop? Whenever I do > something like Medium::close(rtspServer), the event loop gets a "bad > file descriptor" an

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-07 Thread Clemens Arth
> OK, but what if the queue *is* empty? In this case, you’ll need to (somehow) > arrange for the code to get called again in the future, when an OPUS packet > becomes available. > Ha, yes, you are completely right ;-) I took care of this already but did not paste that part of the code. > One

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-04 Thread Ross Finlayson
One more thing: I recommend that you first test your server using “openRTSP” as your RTSP client, rather than immediately trying to use a media player (such as VLC). Run “openRTSP” on your “rtsp://“ URL. Make sure that you get a non-zero-sized audio file (it

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-04 Thread Ross Finlayson
> I did not fully get the part about the RTP packet assembly. The RTP > packet (12-byte header) is created by the RTPSink, right? Yes, we fill this in automatically. All you need to provide is the payload (in this case, one OPUS ‘packet’ each time). > So after > digging through the RFCs and the

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-04 Thread Clemens Arth
> You’re correct that “SimpleRTPSink” is the correct ‘sink’ class to > use. (You can do this because the RTP payload format for OPUS audio > - defined in RFC 7587 - is relatively straightforward.) > Note that - from RFC 7587, section 4.2 - a RTP packet contains > exactly one ‘OPUS packet’, which

Re: [Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-03 Thread Ross Finlayson
> I'm trying to stream an OPUS encoded audio signal, but I could not find > out yet how to implement this. > > I'm using a H264 encoder and a class derived from FramedSource - that > one works perfectly and I can see the stream in VLC. So I wrote my own > OPUS encoder along the same lines with "fr

[Live-devel] OPUS encoded stream via SimpleRTPSink

2017-02-03 Thread Clemens Arth
Hi, I'm trying to stream an OPUS encoded audio signal, but I could not find out yet how to implement this. I'm using a H264 encoder and a class derived from FramedSource - that one works perfectly and I can see the stream in VLC. So I wrote my own OPUS encoder along the same lines with "frames" o