Localizations on concurrent media will be displayed at wrong time if source media has different time.

[hohonuuli]

In VARS if we are displaying concurrent annotations and the concurrent video has a different start time, the localizations will be displayed offset from their correct elapsed time on the media being annotated, Found this using the following videos:

• D1305_20201030T175912Z_prores.mov
• D1305_20201030T175919Z_h264.mp4

I add annotations to the prores , then opened the MP4, seek goes to the correct frame, but the localization is not displayed there.

[hohonuuli]

Here's the current requirements for an annotation to be editable/displayed using VARS and Sharktopoda:

• Annotation has an elapsedTime
• Annotation has same videoReferenceUuid as the opened media
• If annotation is on a difference media. Then that media must have the same start time, width, and height as the current media.

[hohonuuli]

A nice to have is that when a user opens a media, it should popup and warn them that some concurrent localizations can't be edited on the current media.

[hohonuuli]

In order to make this fast I added a CachedMediaService so we don't have to make a rest call every time we need to lookup a different media object than the currently opened one.

[hohonuuli]

I've changed the logic in VARS. If the localization is on a concurrent annotation, it can only be viewed/edited in Sharktopoda if:

1. The concurrent video has the same start time as the opened video
2. The concurrent video hast the same dimensions (width, height) as the opened video.