Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New releases via unportable (for now) #255

Open
Eloston opened this issue Oct 30, 2021 · 8 comments
Open

New releases via unportable (for now) #255

Eloston opened this issue Oct 30, 2021 · 8 comments
Assignees

Comments

@Eloston
Copy link
Member

Eloston commented Oct 30, 2021

What

unportable is a lightweight wrapper over ungoogled-chromium-portablelinux with a few key differences:

  • Enabled support for Wayland with Pipewire support in WebRTC (for screensharing)
  • Enabled VA-API support (as of Chromium 96.0.4664.93, it is supported on Wayland and X11)
  • Builds on Debian 11 (bullseye) with node-typescript and LLVM 13 backported from testing/sid.
    • node-typescript can be directly installed from testing/sid as of 2021-10-29
    • LLVM 13 can be rebuilt on Debian bullseye with no modifications, or you can use builds from apt.llvm.org
  • Built with ffmpeg_branding set to ChromeOS

Why

While @braewoods is sorting out issues (notably #247) with the new unified branch, I will be maintaining the unportable branch for myself until I am able to switch over to unified.

Where/When

Code is now available on the unportable branch. I will be updating this issue when new code is ready. I won't be making tags because it would get caught in the CI system and I haven't tested whether my code will go through the CI system successfully.

Instead, I will be making personal builds over at https://github.com/Eloston/ungoogled-chromium-binaries/releases, but they're built with Intel Skylake-compatible CPU instructions (-march=skylake) (UPDATE 2021-12-15: The latest Chromium 96 builds use corei7-avx, so it supports pre-Skylake architectures, maybe as early as Sandy Bridge). I do not intend to automate OBS builds, as I do not want to interfere with @braewoods's work.

Feedback

Please post questions/problems in new issues. This is just an announcement post.

@Eloston Eloston self-assigned this Oct 30, 2021
@ungoogled-software ungoogled-software locked and limited conversation to collaborators Oct 30, 2021
@Eloston Eloston pinned this issue Oct 30, 2021
@Eloston
Copy link
Member Author

Eloston commented Oct 30, 2021

95.0.4638.69-1.unportable1: 94a098d

@Eloston
Copy link
Member Author

Eloston commented Nov 19, 2021

96.0.4664.45-1.unportable1: bf38674

@Eloston
Copy link
Member Author

Eloston commented Dec 15, 2021

96.0.4664.93-1.unportable1: 8c4962d

Notable changes:

  1. VA-API is now supported on Wayland (X11 is still supported too)
  2. Changed ffmpeg_branding to ChromeOS to support more uncommon containers and formats.

@Eloston
Copy link
Member Author

Eloston commented Dec 17, 2021

96.0.4664.110-1.unportable1: 7a0e649

@Eloston
Copy link
Member Author

Eloston commented Jan 9, 2022

97.0.4692.71-1.unportable1: 9f7b06d

@Eloston
Copy link
Member Author

Eloston commented Jan 25, 2022

97.0.4692.99-1.unportable1: 3251690

@Eloston
Copy link
Member Author

Eloston commented Feb 14, 2022

98.0.4758.80-1.unportable1: a6eb01f

NOTE: Starting with this version, VA-API requires the command-line flag --disable-features=UseChromeOSDirectVideoDecoder (NOTE: If you already have --disable-features, for feature XYZ, then you need to append UseChromeOSDirectVideoDecoder with a comma, e.g. --disable-features=XYZ,UseChromeOSDirectVideoDecoder)

@Eloston
Copy link
Member Author

Eloston commented Feb 18, 2022

98.0.4758.102-1.unportable1: 6ebf5d4

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant