Browser Source ignores video autoplay unless interacted with #282

Closed
opened 2021-04-03 04:36:07 -05:00 by MadWolfDynamite · 6 comments
MadWolfDynamite commented 2021-04-03 04:36:07 -05:00 (Migrated from github.com)

Operating System Info

Windows 10

Other OS

No response

OBS Studio Version

27.0.0-rc1

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/LWWCcT-OjjcB0dmh

OBS Studio Crash Log URL

No response

Expected Behavior

When browser source is active any video tags with autoplay attribute will playback

Current Behavior

Video appears paused until source is manually interacted with via the means of interact popup. Even then, mouse has to be constantly moved to properly show playback

Steps to Reproduce

  1. Create a html page with
  2. Add browser source linking to html page to any scene
  3. Select browser source and clink on "Interact"
  4. Move cursor back and forth within the window that appears
    4a. Open html file in any web browser compatible with

Anything else we should know?

This was only tested with a local file, but URLs may also be affected by this.
The steps for this issue should be reproduceable with this Download.

### Operating System Info Windows 10 ### Other OS _No response_ ### OBS Studio Version 27.0.0-rc1 ### OBS Studio Version (Other) _No response_ ### OBS Studio Log URL https://obsproject.com/logs/LWWCcT-OjjcB0dmh ### OBS Studio Crash Log URL _No response_ ### Expected Behavior When browser source is active any video tags with autoplay attribute will playback ### Current Behavior Video appears paused until source is manually interacted with via the means of interact popup. Even then, mouse has to be constantly moved to properly show playback ### Steps to Reproduce 1. Create a html page with <Video> tag that includes "autoplay muted" attributes 2. Add browser source linking to html page to any scene 3. Select browser source and clink on "Interact" 4. Move cursor back and forth within the window that appears 4a. Open html file in any web browser compatible with <video> tag ### Anything else we should know? This was only tested with a local file, but URLs may also be affected by this. The steps for this issue should be reproduceable with this [Download](https://drive.google.com/file/d/1_6gDFdP8i3xFjts4DNJ8At_PDZzc-Im-/view?usp=sharing).
dodgepong commented 2021-04-03 10:00:45 -05:00 (Migrated from github.com)

Out of curiosity, why are you playing a video with the browser source instead of a media source?

Out of curiosity, why are you playing a video with the browser source instead of a media source?
MadWolfDynamite commented 2021-04-03 11:42:36 -05:00 (Migrated from github.com)

Out of curiosity, why are you playing a video with the browser source instead of a media source?

The media source only allows the playback for a single video file. Likewise as I do not have VLC installed I cannot use the playlist capabilities of the VLC video source so using a browser source was a workaround for this.

> Out of curiosity, why are you playing a video with the browser source instead of a media source? The media source only allows the playback for a single video file. Likewise as I do not have VLC installed I cannot use the playlist capabilities of the VLC video source so using a browser source was a workaround for this.
RytoEX commented 2021-04-03 11:48:06 -05:00 (Migrated from github.com)

This is a duplicate of https://github.com/obsproject/obs-browser/issues/182 and this belongs in the obs-browser repo. I'm going to close this as a duplicate and move it there.

This is a duplicate of https://github.com/obsproject/obs-browser/issues/182 and this belongs in the obs-browser repo. I'm going to close this as a duplicate and move it there.
RytoEX commented 2021-04-10 20:58:32 -05:00 (Migrated from github.com)

It looks like while this and #182 exhibit the same behavior and they share the same underlying cause (disabled hardware acceleration), the immediate cause of each Issue is slightly different.

#182 was because hardware acceleration for browser sources was not enabled on macOS until OBS Studio 26.1.2. That issue was reported against OBS Studio 24.0.2 on macOS, so hardware acceleration was not available. That specific issue should be resolved as of OBS Studio 26.1.2.

This issue was reported against OBS Studio 27.0.0-rc1 on Windows 10. Due to a configuration error during the build process, 27.0.0-rc1 was built without hardware acceleration support for the browser source. This specific issue should be resolved with OBS Studio 27.0.0-rc2 when that is released.

With that said, I'm going to close #182 since it should have been fixed in OBS Studio 26.1.2. I'm going to reopen this and target it to be fixed in OBS Studio 27.0.0-rc2. Sorry for the trouble with shifting issues around, and sorry for the noise.

It looks like while this and #182 exhibit the same behavior and they share the same underlying cause (disabled hardware acceleration), the immediate cause of each Issue is slightly different. #182 was because hardware acceleration for browser sources was not enabled on macOS until OBS Studio 26.1.2. That issue was reported against OBS Studio 24.0.2 on macOS, so hardware acceleration was not available. That specific issue should be resolved as of OBS Studio 26.1.2. This issue was reported against OBS Studio 27.0.0-rc1 on Windows 10. Due to a configuration error during the build process, 27.0.0-rc1 was built without hardware acceleration support for the browser source. This specific issue should be resolved with OBS Studio 27.0.0-rc2 when that is released. With that said, I'm going to close #182 since it should have been fixed in OBS Studio 26.1.2. I'm going to reopen this and target it to be fixed in OBS Studio 27.0.0-rc2. Sorry for the trouble with shifting issues around, and sorry for the noise.
RytoEX commented 2021-04-12 19:43:46 -05:00 (Migrated from github.com)

@MadWolfDynamite Can you please verify that this is fixed in OBS Studio 27.0.0-rc2?

@MadWolfDynamite Can you please verify that this is fixed in OBS Studio 27.0.0-rc2?
RytoEX commented 2021-04-15 02:32:50 -05:00 (Migrated from github.com)

I've verified that the test case now exhibits the Expected Behavior in OBS Studio 27.0.0-rc2 on Windows 10, so I'm going to close this issue.

I've verified that the test case now exhibits the Expected Behavior in OBS Studio 27.0.0-rc2 on Windows 10, so I'm going to close this issue.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-obsproject/obs-browser#282
No description provided.