[FFmpeg-devel] [PATCH v2] HEVC: Export motion vectors to frame side data.

[Paul B Mahol]

On 2/13/20, Asaf Kave <kaveasaf at gmail.com> wrote:
> On Wed, Feb 12, 2020 at 4:02 PM Paul B Mahol <onemda at gmail.com> wrote:
>
>> On 2/12/20, Asaf Kave <kaveasaf at gmail.com> wrote:
>> > On Wed, Feb 12, 2020 at 11:35 AM Paul B Mahol <onemda at gmail.com> wrote:
>> >
>> >> On 2/12/20, Asaf Kave <kaveasaf at gmail.com> wrote:
>> >> > On Sun, Feb 9, 2020 at 10:59 AM Asaf Kave <kaveasaf at gmail.com> wrote:
>> >> >
>> >> >>
>> >> >>
>> >> >> On Thu, Feb 6, 2020 at 4:10 PM Lynne <dev at lynne.ee> wrote:
>> >> >>
>> >> >>> Feb 6, 2020, 11:17 by kaveasaf at gmail.com:
>> >> >>>
>> >> >>> > On Sun, Feb 2, 2020 at 11:15 AM Asaf Kave <kaveasaf at gmail.com>
>> >> wrote:
>> >> >>> >
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> On Tue, Jan 28, 2020 at 11:44 PM Asaf Kave <kaveasaf at gmail.com>
>> >> wrote:
>> >> >>> >>
>> >> >>> >>>
>> >> >>> >>>
>> >> >>> >>> On Sun, Jan 26, 2020, 12:31 Asaf Kave <kaveasaf at gmail.com>
>> wrote:
>> >> >>> >>>
>> >> >>> >>>>
>> >> >>> >>>>
>> >> >>> >>>> On Wed, Jan 22, 2020 at 1:09 PM Asaf Kave <kaveasaf at gmail.com>
>> >> >>> wrote:
>> >> >>> >>>>
>> >> >>> >>>>>
>> >> >>> >>>>>
>> >> >>> >>>>> On Tue, Jan 21, 2020 at 8:17 PM Lynne <dev at lynne.ee> wrote:
>> >> >>> >>>>>
>> >> >>> >>>>>> Jan 20, 2020, 08:42 by kaveasaf at gmail.com:
>> >> >>> >>>>>>
>> >> >>> >>>>>> > Ping
>> >> >>> >>>>>> >
>> >> >>> >>>>>>
>> >> >>> >>>>>>
>> >> https://ffmpeg.org/pipermail/ffmpeg-devel/2019-August/248836.html
>> >> >>> >>>>>>
>> >> >>> >>>>>>
>> >> >>> >>>>>> I've okayed it, its just not been pushed yet.
>> >> >>> >>>>>> You'll need to add the vectors to the block struct. int16_t
>> [2]
>> >> >>> will
>> >> >>> >>>>>> do.
>> >> >>> >>>>>>
>> >> >>> >>>>>
>> >> >>> >>>>> Thanks Lynne,
>> >> >>> >>>>> I didn't find the 'libavutil: AVEncodeInfo data structures'
>> >> >>> >>>>> commit\patch, even i try searching the code on the latest
>> >> 'master'
>> >> >>> branch.
>> >> >>> >>>>> Where can i get the new API ?
>> >> >>> >>>>>
>> >> >>> >>>>
>> >> >>> >>>> Hi,
>> >> >>> >>>> Can someone accelerate this?
>> >> >>> >>>> Thanks
>> >> >>> >>>>
>> >> >>> >>>>
>> >> >>> >>>
>> >> >>> >>> Ping
>> >> >>> >>>
>> >> >>> >>
>> >> >>> >> Pinging it again.
>> >> >>> >>
>> >> >>> >
>> >> >>> > Hello,
>> >> >>> > Can someone push this to master or if not than give me a
>> >> >>> > feedback,
>> >> >>> > Thanks
>> >> >>> >
>> >> >>>
>> >> >>> You need to download the patch and apply it yourself.
>> >> >>>
>> >> >>
>> >> >> Thanks, but i getting this error :
>> >> >> > git push
>> >> >>  fatal: unable to access 'https://git.ffmpeg.org/ffmpeg.git/': The
>> >> >> requested URL returned error: 403
>> >> >>
>> >> >> I think i am not approval to push.
>> >> >>
>> >> > can someone push it?
>> >>
>> >> Your patch can not be pushed as is.
>> >> Instead it needs to be combined with another patch.
>> >>
>> > OK thank you, do i need to do something or only wait that somebody will
>> > combine it?
>>
>> Very unlikely somebody will combine your patch with another for free.
>> So it all is up to you.
>>
>
> Thanks,
> So just to to be sure on what i need to do:
> 1. Download this patch '[FFmpeg-devel,1/3] libavutil: AVEncodeInfo data
> structures' (
> https://ffmpeg.org/pipermail/ffmpeg-devel/2019-August/248836.html), and
> apply it locally.
> 2. Then i need to apply again my patch locally, and
>
>> *add the vectors to the block struct. int16_t [2] will do*
>
>  as Lynne mention before.
>
> Now how i can push my patch?(i am not have the right permission) do i need
> to push both patch's? or to combine them to one commit patch?
>
> I looked at patch ' libavutil: AVEncodeInfo data structures', and i wasn't
> convinced that both patch are so dependent, can you motivate me or direct
> me to info why i need to add vectors at the 'AVEncodeInfoBlock' structure?

Mostly because other developers want to use that new API instead of
current old one to export motion vectors.

> Thanks for your time.
>
>
>> >
>> >>
>> >> >
>> >> >>
>> >> >>
>> >> >>> _______________________________________________
>> >> >>> ffmpeg-devel mailing list
>> >> >>> ffmpeg-devel at ffmpeg.org
>> >> >>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>> >> >>>
>> >> >>> To unsubscribe, visit link above, or email
>> >> >>> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>> >> >>
>> >> >>
>> >> > _______________________________________________
>> >> > ffmpeg-devel mailing list
>> >> > ffmpeg-devel at ffmpeg.org
>> >> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>> >> >
>> >> > To unsubscribe, visit link above, or email
>> >> > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>> >> _______________________________________________
>> >> ffmpeg-devel mailing list
>> >> ffmpeg-devel at ffmpeg.org
>> >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>> >>
>> >> To unsubscribe, visit link above, or email
>> >> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>> > _______________________________________________
>> > ffmpeg-devel mailing list
>> > ffmpeg-devel at ffmpeg.org
>> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>> >
>> > To unsubscribe, visit link above, or email
>> > ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel at ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".