gh-obsproject/obs-browser

Watch

Fork 0

Linux Browser Source does not support h264. #293

New issue

Closed

opened 2021-05-07 11:58:54 -05:00 by enzanki-ars · 3 comments

enzanki-ars commented

2021-05-07 11:58:54 -05:00

(Migrated from github.com)

Operating System Info

Ubuntu 21.04

Other OS

No response

OBS Studio Version

27.0.0-rc3

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/kZiVzmgL-BT0OBgw

OBS Studio Crash Log URL

No response

Expected Behavior

Because the Linux build of Chromium is not build with support for h264, embeded browser source items using h264 do not play. On Ubuntu at least, they have the chromium-codecs-ffmpeg-extra due to the licensing problems. Is it possible to support this in at least a similar fashion on Linux?

Current Behavior

Playing a video inside a browser source with h264 should allow the video to play like it does on Windows and macOS.

Steps to Reproduce

Create a browser source with an h264 video embeded.
The embeded video should not play with an error regarding unsupported codec.

Anything else we should know?

No response

### Operating System Info Ubuntu 21.04 ### Other OS _No response_ ### OBS Studio Version 27.0.0-rc3 ### OBS Studio Version (Other) _No response_ ### OBS Studio Log URL https://obsproject.com/logs/kZiVzmgL-BT0OBgw ### OBS Studio Crash Log URL _No response_ ### Expected Behavior Because the Linux build of Chromium is not build with support for h264, embeded browser source items using h264 do not play. On Ubuntu at least, they have the `chromium-codecs-ffmpeg-extra` due to the licensing problems. Is it possible to support this in at least a similar fashion on Linux? ### Current Behavior Playing a video inside a browser source with h264 should allow the video to play like it does on Windows and macOS. ### Steps to Reproduce 1. Create a browser source with an h264 video embeded. 2. The embeded video should not play with an error regarding unsupported codec. ### Anything else we should know? _No response_

tt2468 commented

2021-05-08 02:47:00 -05:00

(Migrated from github.com)

Unfortunately that is simply because the Spotify builds do enable the build flags for proprietary codecs. You either will have to build CEF yourself, or you can DM me on Discord where I can give you an already built version.

WizardCM commented

2021-06-15 07:37:05 -05:00

(Migrated from github.com)

This is, unfortunately, expected behaviour on Linux unless you build CEF yourself with proprietary codecs enabled.

enzanki-ars commented

2021-06-19 14:01:21 -05:00

(Migrated from github.com)

In any case, is there a documented set of flags I can enable to build CEF with these extra codecs for a personal build. I'm more than willing to compile my own version and keep that up to date on my system, but am not seeing any docs on the CEF pages regarding this specifically. It seems like adding the following to GN_DEFINES should be enough, but not 100% sure: ffmpeg_branding=Chrome proprietary_codecs=1

Out of curiosity, given that it works on Windows, is there a reason why Windows is able to support it but not Linux? Seems weird given that there should be no difference in licensing between the two platform. In any case, is there a documented set of flags I can enable to build CEF with these extra codecs for a personal build. I'm more than willing to compile my own version and keep that up to date on my system, but am not seeing any docs on the CEF pages regarding this specifically. It _seems_ like adding the following to `GN_DEFINES` should be enough, but not 100% sure: `ffmpeg_branding=Chrome proprietary_codecs=1`

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#293

No description provided.

Rows
Columns