Gyre

A downloader for videos (called coubs) from Coub.

What you can download

• Single coubs
• Stories
• Channels
• Tags
• Search results
• Communities (incl. Featured and Coub of the Day)
• Hot coubs
• Random coubs

Installation

There are several ways to install Gyre.

Flathub

Build with GNOME Builder

First clone this repository with GNOME Builder. Then hit the play button and it will automatically install and compile all dependencies for you. Afterwards you can export a Flatpak bundle to install Gyre on your machine.

Build with Meson

The following commands will clone this repository and install Gyre (system-wide by default). Please note that there's currently no automatic way to uninstall the program. You can run ninja uninstall within the build directory, but some files won't be removed, because they were generated by external commands (e.g. glib-compile-schemas). These files have to be deleted manually.

git clone https://github.com/HelpSeeker/Gyre.git
cd Gyre
meson . _build
cd _build
meson configure -Dprefix=<custom location>  # optional step
ninja install

The 4th step is optional and allows you to specify a custom install location. Depending on the location GLib might not be able to find the GSettings schema, which is required to run Gyre. If that is the case, you have to manually point it to the schema

GSETTINGS_SCHEMA_DIR=<custom location>/share/glib-2.0/schemas <custom location>/bin/gyre

Dependencies

• meson >= 0.50
• GTK >= 3.24
• libhandy >= 1.0.0
• Python >= 3.7
• aiohttp
• FFmpeg

Troubleshooting

(Flatpak only) Gyre prompts me for a new output location every time I load a profile, even though the directory exists.

Most likely you deleted the directory at one point and created a new one with the same name. With normal file system access this wouldn't be a problem, but the Flatpak version requests access via XDG Portal and in that case the new directory is different from the old one, even if they share the same name.

Choose the directory when prompted and export the profile again to update the output location to the new version.

(Flatpak only) Gyre is unable to open its error log.

Gyre tries to open the log with the default text editor. That doesn't work when running inside the Flatpak sandbox, so the error log will always be displayed by the internal viewer.

(Flatpak only) Dialogs exceed the boundaries of my phone display.

Gyre is mobile-ready thanks to libhandy, but there are issues with GTK 3, which require additional patches to make it work correctly on mobile. Mobile distros apply these patches, but they don't affect Flatpaks. I'm still looking for a solution to this problem (maybe an additional Flatpak with the patches applied?), but until then you are better off running Gyre locally.

Gyre on Windows

It is my goal to bring Gyre to Windows, but GTK and other GNOME technologies make it difficult to provide portable builds.

Support is very alpha, but you can still install Gyre by following these steps:

1. Install msys2
2. Run mingw64 in the command prompt, Powershell, etc.

Switch to the mingw64 terminal and continue...

3. pacman -S mingw-w64-x86_64-python mingw-w64-x86_64-gtk3 mingw-w64-x86_64-python-aiohttp mingw-w64-x86_64-python-gobject mingw-w64-x86_64-meson mingw-w64-x86_64-pkgconf mingw-w64-x86_64-cmake mingw-w64-x86_64-libhandy mingw-w64-x86_64-ffmpeg
4. Download or clone the repository
5. cd into the project folder
6. meson build .
7. cd build
8. ninja install
9. gyre

Once you have successfully installed Gyre, you can create a shortcut that points to the following command

msys2_shell.cmd -mingw64 -lc gyre

to open Gyre without having to start up a terminal. Depending on your setup you can also add -defterm (i.e. use the default terminal) to the command to speed up the launch.