Re: [Live-devel] Buffer size on client

2010-05-22 Thread Andy Bell
On Sat, May 22, 2010 at 9:49 AM, Ross Finlayson wrote: > I hope you realize, though, that JPEG is a very poor codec for video > streaming, because each frame is so large (and so takes up many network > packets). If *any* of these network packets gets lost, then the whole frame > must be discarde

Re: [Live-devel] Buffer size on client

2010-05-22 Thread Ross Finlayson
I hope you realize, though, that JPEG is a very poor codec for video streaming, because each frame is so large (and so takes up many network packets). If *any* of these network packets gets lost, then the whole frame must be discarded. Thanks. I do realise that its a poor codec but I want to

Re: [Live-devel] Buffer size on client

2010-05-22 Thread Andy Bell
On Fri, May 21, 2010 at 10:45 PM, Ross Finlayson wrote: > I am looking at the Elphel example and I would like to stream MJPEG where > the frame size would be in the region of 200KB, I have tried increasing > the OutPacketBuffer::maxSize but I am still not able to view the stream in > VLC. If I u

Re: [Live-devel] Buffer size on client

2010-05-21 Thread Ross Finlayson
I am looking at the Elphel example and I would like to stream MJPEG where the frame size would be in the region of 200KB, I have tried increasing the OutPacketBuffer::maxSize but I am still not able to view the stream in VLC. If I use openRTSP I get the following message: MultiFramedRTPSourc

[Live-devel] Buffer size on client

2010-05-21 Thread Andy Bell
Hi, I am looking at the Elphel example and I would like to stream MJPEG where the frame size would be in the region of 200KB, I have tried increasing the OutPacketBuffer::maxSize but I am still not able to view the stream in VLC. If I use openRTSP I get the following message: MultiFramedRTPSourc