[Live-devel] Stair or Zig-Zag view with Mjpeg codec

[Saurabh Modi via live-devel]

--- Begin Message ---
Hi All,
I am working on an IPCamera project and use live555 library for RTSP
streaming of media. We have recently introduced option for user to select
resolution of their choice. There seems to be an issue with RTSP streaming
with custom resolution in MJPEG codec. Whenever the width is set to
180/230/260/310/340 pixels and so on the view is staired or cut and forms a
zig-zag pattern. The issue doesn't seem to exist for H264/H265 codecs. So
is there any limitation of the library for these widths for MJPEG? The
encoder is perfectly encoding the frames. When I send the encoded frames
directly to other decoders they are able to decode them properly and view
is normal. So maybe is there something that live555 adds in the packet
which is creating the issue?

-- 
Matrix Comsec Pvt. Ltd.
#394, GIDC Makarpura - 390010. Dist: Vadodara, 
Gujarat, India
 

IP Video Surveillance |  
People Mobility Management |  
Unified Communications 

1 Million+ Customers | 2,500+ Partners | 
60+ Products | 50+ Countries
We put more in the box, so your business can 
think more out of the box.
  
 
 
 




--- End Message ---
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Re: [Live-devel] live-devel Digest, Vol 186, Issue 10

[Saurabh Modi via live-devel]

--- Begin Message ---
Hi Ross,
Since the JPEG RTP payload header has only 8 bits for storing width and
height, therefore it will not be able to store resolution greater than 2048
or 3MP. Is there a way we can stream JPEG having resolution greater than
3MP.

On Wed, May 22, 2019 at 12:34 AM  wrote:

> Send live-devel mailing list submissions to
> live-devel@lists.live555.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.live555.com/mailman/listinfo/live-devel
> or, via email, send a message with subject or body 'help' to
> live-devel-requ...@lists.live555.com
>
> You can reach the person managing the list at
> live-devel-ow...@lists.live555.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of live-devel digest..."
>
>
> Today's Topics:
>
>1. Re: MJPEG2000 support (.mj2) (Ross Finlayson)
>2. Stair or Zig-Zag view with Mjpeg codec (Saurabh Modi)
>3. Re: Stair or Zig-Zag view with Mjpeg codec (Ross Finlayson)
>
>
> --
>
> Message: 1
> Date: Mon, 20 May 2019 19:16:21 -0700
> From: Ross Finlayson 
> To: LIVE555 Streaming Media - development & use
> 
> Subject: Re: [Live-devel] MJPEG2000 support (.mj2)
> Message-ID: 
> Content-Type: text/plain;   charset=utf-8
>
> I?ve just installed a new version (2019.05.21) of the ?LIVE555 Streaming
> Media? code that includes implementations of ?JPEG2000VideoRTPSink? and
> ?JPEG2000VideoRTPSource? for sending/receiving JPEG 2000 RTP packets.
> (Note that these differ a little from the patch that you sent, because they
> include the proper 8-byte payload header, as specified in RFC 5371.)
>
> I haven?t yet installed your ?JPEG2000VideoFileServerMediaSubsession? (and
> ?Framer? and ?Parser?) classes, because these are still a mess, and will
> need a lot of work to clean up.  (However, if you wish, you can use your
> own implementation of these with the new ?JPEG2000VideoRTPSink? and
> ?JPEG2000VideoRTPSource? classes, and they should still work for you.)
>
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
>
>
> --
>
> Message: 2
> Date: Tue, 21 May 2019 12:18:09 +0530
> From: Saurabh Modi 
> To: live-de...@us.live555.com
> Subject: Stair or Zig-Zag view with Mjpeg codec
> Message-ID:
> <
> calwmldbywxedbdrbnqttudszzdez5jec_kqjjjkhtsbqkhw...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
> I am working on an IPCamera project and use live555 library for RTSP
> streaming of media. We have recently introduced option for user to select
> resolution of their choice. There seems to be an issue with RTSP streaming
> with custom resolution in MJPEG codec. Whenever the width is set to
> 180/230/260/310/340 pixels and so on the view is staired or cut and forms a
> zig-zag pattern. The issue doesn't seem to exist for H264/H265 codecs. So
> is there any limitation of the library for these widths for MJPEG? The
> encoder is perfectly encoding the frames. When I send the encoded frames
> directly to other decoders they are able to decode them properly and view
> is normal. So maybe is there something that live555 adds in the packet
> which is creating the issue?
>
> --
> Matrix Comsec Pvt. Ltd.
> #394, GIDC Makarpura - 390010. Dist: Vadodara,
> Gujarat, India
>  
>
> IP Video Surveillance |?
> People Mobility Management |?
> Unified Communications
> 
> 1 Million+ Customers | 2,500+ Partners |
> 60+ Products | 50+ Countries
> We put more in the box, so your business can
> think more out of the box.
>  
> 
> 
> 
> 
>
>
>
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://lists.live555.com/pipermail/live-devel/attachments/20190521/e0fff25b/attachment-0001.htm
> >
>
> --
>
> Message: 3
> Date: Tue, 21 May 2019 00:05:10 -0700
> From: Ross Finlayson 
> To: LIVE555 Streaming Media - development & use
> 
> Subject: Re: [Live-devel] Stair or Zig-Zag view with Mjpeg codec
> Message-ID: 
> Content-Type: text/plain;   charset=us-ascii
>
> > I am working on an IPCamera project and use live555 library for RTSP
> streaming of media. We have recently introduced option for user to select
> resolution of their choice. There seems to be an issue with RTSP streaming
> with custom resolution in MJPEG codec. Whenever the width is set to
> 180/230/260/310/340 pixels and so on the view is staired or cut and forms a
> zig-zag pattern. The issue doesn't seem to exist for H264/H265 codecs. So
> is there any limitat

[Live-devel] Use of fTCPStreams

[Saurabh Modi via live-devel]

--- Begin Message ---
Hi,
We have a tcpStreamRecord type variable in the RTPInterface class. What is
it actually used for? In the sendPacket method, we have used this to send
the RTP packet over each of the TCP streams that it points to but what
could be the case for these multiple streams requiring the same RTP packet
to be sent? Whenever I start streaming video through two or more clients a
new RTPInterface object is created and I have seen that in every instance
the fTCPStreams only points to a single address, so I am a bit confused
regarding the actual use case of this.
--- End Message ---
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

[Live-devel] Use of fTCPStreams

[Saurabh Modi via live-devel]

--- Begin Message ---
Hi,

Thanks for the quick response
I have not modified live555 code. I am going through the sending logic over
tcp in live555 library. I found the below code in RTPInterface.cpp file.

Boolean RTPInterface:sendPacket(unsigned char* packet, unsigned packetsize)
{
Boolean success = True;
if(!fGS->output(env(), packet, packetSize)) success = False;
tcpStreamRecord* nextStream;
for(tcpStreamRecord* stream=fTCPStreams; stream != NULL; stream =
nextStream) {
nextStream = stream->fNext;
if(!sendRTPorRTCPPacketOverTCP(packet, packetSize,
stream->fStreamSocketNum, stream->fStreamChanelId)) {
success =False;
}
}
return success;
}

>From above logic, " sendRTPorRTCPPacketOverTCP" function will be called for
each socket of " fTCPStreams".
" sendRTPorRTCPPacketOverTCP" sends the same packet for each of the "
fTCPStreams ".

*In which condition same RTP/RTCP packet needs to be sent to each
socket(fTCPStreams)? or*
*What is the use case of same RTP/RTCP packet needs to be sent to each
socket(fTCPStreams)?*
--- End Message ---
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel