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 <img> element inside FFmpegVideo fetched getFrame on the server twice with the same key seg11_raw.mkv, presumably due to time being different. Suspect that for some reason React first fetched seg11_raw but with the wrong time value (maybe from the previous segment/frame). Then it fetched the frame again 200ms later (presumably with time: 0). This caused the first ffmpeg to be killed (killed: true), as intended, but the browser element never reported an error, and the render finished with a blank (white) video for that one frame.
The
<img>
element insideFFmpegVideo
fetched getFrame on the server twice with the same keyseg11_raw.mkv
, presumably due totime
being different. Suspect that for some reason React first fetchedseg11_raw
but with the wrong time value (maybe from the previous segment/frame). Then it fetched the frame again 200ms later (presumably withtime: 0
). This caused the first ffmpeg to be killed (killed: true
), as intended, but the browser element never reported an error, and the render finished with a blank (white) video for that one frame.Full log:
The text was updated successfully, but these errors were encountered: