Re: [Libav-user] 4k video decoding planner data

2016-07-28 Thread Don Moir
>y_1strow += Width; >y_2ndrow += Width; Check this to see if it is your problem. Appears you should be using the pitch for this and not the width. Normally width is width of video and pitch is the number of bytes per line and can be greater than width. On 7/27/2016 11:05 PM, Ankush Wadke wro

Re: [Libav-user] 4k video decoding planner data

2016-07-27 Thread Ankush Wadke
Thanks for the reply Harry. And yes it has something to do with the offset of U and V planes but it works perfectly fine for a FHD stream i.e. 1920x1080 but dosent seem to for a 3840x2160 stream. Does planer data require alignment to be considered? On Wed, Jul 27, 2016 at 7:51 PM, Harry wrote: >

Re: [Libav-user] 4k video decoding planner data

2016-07-27 Thread Harry
Green borders are a wrong offset / starting address for the UV planes. Harry Sent from my smartphone > On 27 Jul 2016, at 11:47, Ankush Wadke wrote: > > Hi everybody, > I am stuck with a problem to which I am not able to figure out what > exactly is wrong. > I am decoding a 4k video w

[Libav-user] 4k video decoding planner data

2016-07-27 Thread Ankush Wadke
Hi everybody, I am stuck with a problem to which I am not able to figure out what exactly is wrong. I am decoding a 4k video which gives me a YUV420P output frame. In order to convert it to UYVY I wrote a piece of code. which works fine for first frame, then second frame has a small green l