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
The first segment is portrait, the 2nd is landscape. Let it play until it changes to landscape, then try to seek somewhere < 5 seconds, notice that the it remains in landscape. Seeking to :00 will rotate it back to portrait.
The text was updated successfully, but these errors were encountered:
i tracked it down to findVideoSegmentIndex in utils.tsx returning the wrong segment index (it was returning 1 instead of 0 which is why the wrong segment was loaded when you seek), so i console logged trackList to see what was going on.
it looks like the first 2 + last 2 attachments have the same exact timestamp, which is why it was getting confused:
so i don't think it's the code, but rather something weird happened with the attachment timestamps -- seeking works normally with other replays with proper timestamps:
@michellewzhang good catch, I'm going to guess @romtsn was testing something and we got bad data. Don't think we need the UI to handle this type of bad data.
Example Replay
The first segment is portrait, the 2nd is landscape. Let it play until it changes to landscape, then try to seek somewhere < 5 seconds, notice that the it remains in landscape. Seeking to :00 will rotate it back to portrait.
The text was updated successfully, but these errors were encountered: