You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Funscripts can optionally include a metadata tag "duration". When xbvr generates a heatmap it assumes the value is in seconds. However, the convention is to use the same units as the rest of the funscript - milliseconds. This results in the generated heatmap having all the action squished to the left/beginning, since the duration is 1000x longer than it should be.
The text was updated successfully, but these errors were encountered:
OpenFunscripter apparently uses seconds for duration, but both Funscript.io and FunscriptToolbox use milliseconds. xbvr could ignore the duration completely. This means funscripts which have actions for only part of the video may not have correct heatmaps however. So the ideal solution may be a ruleset to decide when to use the duration tag as seconds, milliseconds, or to ignore it.
Funscripts can optionally include a metadata tag "duration". When xbvr generates a heatmap it assumes the value is in seconds. However, the convention is to use the same units as the rest of the funscript - milliseconds. This results in the generated heatmap having all the action squished to the left/beginning, since the duration is 1000x longer than it should be.
The text was updated successfully, but these errors were encountered: