Browser Source ignores video autoplay unless interacted with #282
Labels
No labels
area/accessibility
area/dependency
Confirmed
Crash Report
Delayed
Design Issue
Duplicate
Feedback required
Good first issue
kind/bug
kind/cleanup
kind/enhancement
platform/linux
platform/macos
platform/windows
priority/high
Question
Request for Comments
Seeking Other Contributors
Seeking Testers
Won't Fix / By Design
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-obsproject/obs-browser#282
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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.
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.
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.
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.
@MadWolfDynamite Can you please verify that this is fixed in OBS Studio 27.0.0-rc2?
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.