obsproject / obs-browser

CEF-based OBS Studio browser plugin
GNU General Public License v2.0
789 stars 227 forks source link

Webm in Browser source local file cannot use currenttime #415

Open Spo-oky opened 1 year ago

Spo-oky commented 1 year ago

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

29.1.3

OBS Studio Version (Other)

No response

OBS Studio Log URL

NA

OBS Studio Crash Log URL

No response

Expected Behavior

Cannot use a video in webm and set the currenttime. Always go to the beginning of the video and does not assume the currenttime. if we use other video codec it works, only webm doesn't.

In this case the video should forward to 5s and on local file starts from the beginning, on internet file starts on 5s.

Problem In the last versions 29.x, 28.x and 27.x. It works on 26.x

This works on chrome versions tested on v75 and v114. Only fails on OBS.

Just need's to comment the local file and uncomment the internet file to test it.

Tks

Current Behavior

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
</head>
<body>
    <video width="100%" height="100%" muted="muted">
        <!-- Same Video on the Web -->
        <!-- <source src="https://test-videos.co.uk/vids/bigbuckbunny/webm/vp9/1080/Big_Buck_Bunny_1080_10s_1MB.webm"> -->
        <!-- Same Video Local file -->
        <source src="video/Big_Buck_Bunny_1080_10s_1MB.webm">
    </video>
    <script>
        var video = document.querySelector('video');
        video.currentTime = 5.00;
        video.play();
        console.log(video.currentTime);
    </script>
</body>
</html>

Steps to Reproduce

  1. Use the html example.
  2. Just need's to comment the local file and uncomment the internet file to test it. to see the different behaver.
  3. ...

Anything else we should know?

No response

Warchamp7 commented 1 year ago

Can confirm this happens with a locally loaded mp4 in a local html file as well.

I do not believe it is a webm specific problem.

Spo-oky commented 2 months ago

Is there any news on this subject or can we do any workaround?

Tks

WizardCM commented 2 months ago

Good news, our upcoming upgrade to Chromium 126+ seems to fix the issue, so it was likely an issue outside of our control.

I will report in this ticket (and a number of others) when a Beta with the changes goes out to users to try.

Spo-oky commented 2 months ago

That's great news! tks