Skip to content

libvmaf/motion: support motion in addition to motion2#594

Closed
kylophone wants to merge 1 commit intomasterfrom
libvmaf_motion
Closed

libvmaf/motion: support motion in addition to motion2#594
kylophone wants to merge 1 commit intomasterfrom
libvmaf_motion

Conversation

@kylophone
Copy link
Collaborator

Some published VMAF models require a feature called motion which is similar, but has no look-ahead like motion2. This PR adds the motion feature to both the float/integer motion feature extractors.

<VMAF version="85b492c">
  <params qualityWidth="1920" qualityHeight="1080" />
  <fyi fps="60.80" />
  <frames>
    <frame frameNum="0" motion="0.000000" motion2="0.000000" integer_motion="0.000000" integer_motion2="0.000000" />
    <frame frameNum="1" motion="4.913140" motion2="4.828127" integer_motion="4.913157" integer_motion2="4.828149" />
    <frame frameNum="2" motion="4.828127" motion2="4.678761" integer_motion="4.828149" integer_motion2="4.678786" />
    <frame frameNum="3" motion="4.678761" motion2="4.678761" integer_motion="4.678786" integer_motion2="4.678786" />
  </frames>
</VMAF>

@1480c1
Copy link
Contributor

1480c1 commented Jun 23, 2020

It seems the appveyor issues come from msys2/MSYS2-packages#2022, so it would be okay to ignore appveyor for now

@kylophone
Copy link
Collaborator Author

It seems the appveyor issues come from msys2/MSYS2-packages#2022, so it would be okay to ignore appveyor for now

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants