Update README.md

We now do normal packages. Remove all info saying that only Flatpak works or some additional compiling is required.
This commit is contained in:
Rafał Dzięgiel
2021-02-05 19:27:27 +01:00
committed by GitHub
parent 0167f0ab4e
commit 8ca73fd56b

View File

@@ -28,8 +28,7 @@ This is still early WIP. Many features are not implemented yet and quite a few a
## Installation from Flatpak (recommended) ## Installation from Flatpak (recommended)
The `Flatpak` package includes all required dependencies and codecs. The `Flatpak` package includes all required dependencies and codecs.
Additionally it also has a few patches, thus some functionalities work better (or are only available) in `Flatpak` version (until my changes are accepted upstream). Additionally it also has a few patches, thus some functionalities work better (or are only available) in `Flatpak` version (until my changes are accepted upstream). List of patches used in this version can be found [here](https://github.com/Rafostar/clapper/issues/35).
It is provided as an easy "just install and use" solution.
```sh ```sh
flatpak install https://rafostar.github.io/flatpak/com.github.rafostar.Clapper.flatpakref flatpak install https://rafostar.github.io/flatpak/com.github.rafostar.Clapper.flatpakref
@@ -44,9 +43,6 @@ Pre-built packages are available in [my repo](https://software.opensuse.org//dow
#### Arch Linux #### Arch Linux
You can get Clapper from the AUR: [clapper-git](https://aur.archlinux.org/packages/clapper-git) You can get Clapper from the AUR: [clapper-git](https://aur.archlinux.org/packages/clapper-git)
**Important:** If you build `Clapper` from source code or install it using any other packaging system than `Flatpak`, you will still need some additional `GStreamer` elements and patches that are not upstreamed in `GStreamer` source code yet.
The requirements and how to build from git source code are described in the [wiki](https://github.com/Rafostar/clapper/wiki#installation-from-source-code).
## Q&A ## Q&A
**Q:** Does using `GJS` negatively impact video performance?<br> **Q:** Does using `GJS` negatively impact video performance?<br>
**A:** Absolutely not. `GJS` here is used to put together the GUI during startup. **A:** Absolutely not. `GJS` here is used to put together the GUI during startup.
@@ -55,7 +51,7 @@ Even the custom video widget that I prepared for this player (based on original
All these libs are acting "on their own" and no function calls from `GJS` related to video decoding and rendering are performed during playback. All these libs are acting "on their own" and no function calls from `GJS` related to video decoding and rendering are performed during playback.
**Q:** What settings should I set to maximize performance?<br> **Q:** What settings should I set to maximize performance?<br>
**A:** As of now, player works best on `Wayland` session. `Wayland` users might want to try enabling the experimental `vah264dec` plugin for improved performance (this plugin does not work on `Xorg` right now) for standard (8-bit) `H.264` videos. **A:** As of now, player works best on `Wayland` session. `Wayland` users can try enabling highly experimental `vah264dec` plugin for improved performance (this plugin does not work on `Xorg` right now) for standard (8-bit) `H.264` videos.
It can be enabled from inside player preferences dialog inside `Advanced -> GStreamer` tab using customizable `Plugin Ranking` feature. It can be enabled from inside player preferences dialog inside `Advanced -> GStreamer` tab using customizable `Plugin Ranking` feature.
Since the whole app is rendered using your GPU, users of VERY weak GPUs might try to disable the "render window shadows" option to have more GPU power available for non-fullscreen video rendering. Since the whole app is rendered using your GPU, users of VERY weak GPUs might try to disable the "render window shadows" option to have more GPU power available for non-fullscreen video rendering.