Contributions, Issues, and Pull Requests.

[jub0t]

I'm actively accepting contributions, ideas, bug reports, feature requests, etc. Please read the text below on how to get started on contributing.

Rules

• No Third Party API/Cloud integration such as voice generators, image generators, video generators, etc.
• No code-changes or pull-request out of the blue (will be rejected).

Pull requests:

• For the most part: Don't create pull-requests, use Issues or Discussions (comment under this post) but if you do, follow the points below.
• Submit an idea, feature request, or similar in plain-text.
• NOTE: Do not work on anything listed on Roadmap section on the README.MD, instead try to come up with something original or suggest an improvement.

Bug reports:

• Try to include screenshots (really helpful).
• Provide steps to reproduce the bug/error.
• Provide some information about test-device for better understanding and debugging.
• Avoid technical clutter when creating an issue, a single understandable paragraph pinpointing the exact error is appreciated way more.
• Add code-blocks only when necessary, such as, when reporting logs or errors produced by the actual binary (the WolfCut app).

Things to keep in mind

• We are building this project for consumer grade Desktop devices, so any code or piece of software that is integrated into this app must run locally (no APIs) and must be performant and scalable enough to run on most devices (potatoes). Don't suggest things like "local image inference" or the likes unless you have a really compelling argument.

Pages:
Discussions: Comment under this Discussion thread for Ideas, Suggestions, Requests, etc.
Issues: for Issues, Bug reports, etc.

[michaltomczykowski]

A small contributing.md with project scope/architecture/structure/passing tests would be kinda useful

[nickfrostcode]

Idea: Website Revamp & Download Landing Page

The roadmap lists a website revamp and download landing page as high priority (🌟). I'd like to take this on.

Proposal

A clean, lightweight landing page covering WolfCut's core features (no watermarks, free voice filters, native performance), with dynamic download buttons that pull the latest Windows and macOS binaries directly from GitHub's public Releases API - just release metadata and asset URLs, no third-party service involved, so the links stay current without manual updates per release.

Stack

Next.js + Tailwind CSS for a fast, responsive build. Open to a different stack if you'd rather.

Structure

Should the site live in a website/ directory in this repo, or a separate repo (e.g. jub0t/wolfcut-website) to keep the core Rust app isolated?

Let me know if this works or if you want it adjusted before I start.

[ifyajah]

Why these heavy stack ?
Won't static site be better ? That is more light weight

Plain old html/css/js can get the job done

[TinyBrickBoy]

Idea: an Arch PKGBUILD in the repo under packaging/arch, next to the Nix flake.

On Arch and other rolling distros the AppImage from Releases opens as an empty
window. It carries the libwayland-client from its Ubuntu 22.04 builder, which is
older than the Mesa it ends up talking to, so EGL display creation fails with
EGL_BAD_PARAMETER and nothing renders. Building against the system WebKitGTK,
Wayland and Mesa avoids that class of problem entirely, and Arch users are the
group most likely to be filing the rough-edge reports you are asking for, so
making the app one command to install there pays back in bug reports.

It would be a -git package rather than a versioned one, because every green
build on main mints a new alpha tag and a pinned release goes stale within a
day. Nothing new at runtime: ffmpeg comes from the repos and whisper.cpp is an
optional dependency for transcription. It is a packaging file plus a short
README section, so it does not touch the app itself, and it is not on the
roadmap.

If you would rather it live on the AUR than in-tree, that works too and I would
maintain it there. Tell me which you prefer and I will send a PR.

[Bolaside]

oh man i'd be really grateful if you put it on AUR

[tpbrunner4-gif]

black screen for .jpg in preview and export. Am I doing something wrong?

[tpbrunner4-gif]

found out .png files work and display properly, .jpg do not.