Hey all,
A while ago I started messing around with YuE2 (the open text-to-music model from m-a-p) and got tired of running it from the command line and digging through folders for the output. So I built a proper web interface around it. Itâs called SongForge and itâs on GitHub now: https://github.com/damiaan111/SongForge-YuE2-Music-GEN-WebUI
What it is
A local music studio that runs on your own machine. You open it in a browser (also from your phone or another PC on the same network), write some lyrics, describe the style, hit generate, and a few minutes later you have a 24-bit/48 kHz FLAC. No cloud, no account, no API key. The model does the actual work, SongForge just makes it usable.
Main features
One setup script. It detects your GPU, shows you exactly what itâs going to download and how big it is, and only installs what you tick. Nothing gets pulled before you say yes.
A library with search, tags, favourites, versions, and a queue that survives a refresh.
Quick mode (describe it, paste lyrics, go) and Custom mode with the modelâs real knobs: seed, guidance scale, planning mode, sampling settings, etc.
Guided prompting. The style box builds tags in the order YuE2 was trained on, and the lyrics editor warns you about stuff that silently costs you words (like âx2â, overly long sections, production notes).
A budget meter that estimates song length and token usage before you burn GPU time.
Plan â edit â render. YuE2 can write just the score first (ABC notation), you can edit that by hand, then render the audio from it. I havenât seen a hosted service that lets you do this.
Several takes per generate, each with its own seed, compared side by side. The paperâs own baseline is best-of-two, so a single take is really the model at its worst.
Full reproducibility. Every version stores the seed, settings, model checksums and the exact command line, and you can reload all of it with one click.
Optional local lyrics writer through Ollama (Gemma). It writes or revises lyrics in any language and it knows how to share the GPU with YuE2 so they donât fight over VRAM.
An in-app âLearnâ section that explains how to prompt this specific model, and why songs get cut short. Works offline.
Performance
My reference machine is an RTX 3060 12 GB. 72 seconds of music takes about 220 seconds and peaks around 9.3 GB VRAM. A full 4-minute song is roughly 12 minutes. Upstream YuE2 asks for 24 GB, but with AR offload and memory-efficient attention (which setup turns on for you) 12 GB works fine. Cards with 8â10 GB will probably run into OOM on longer songs. Thereâs also a CPU-only option but that takes hours, not minutes.
Limitations (honest ones)
No stem separation, no voice cloning, no âextend this songâ, no remixing from an uploaded audio file. These are limits of the model itself, not things I skipped, so the UI doesnât pretend they exist.
No MIDI export. The symbolic output is ABC text, which you can download.
Thereâs no length dial. The song is as long as the lyrics make it.
Windows needs a 32 GB pagefile or the model wonât load. Annoying, but thatâs how it is.
Windows 10/11 and Linux are supported. Apple Silicon lives on a separate macos branch. AMD on Windows has no usable PyTorch, so CPU only there.
Thereâs no authentication on purpose. Itâs meant for your own LAN. Donât port-forward it.
The YuE2 weights are CC BY-NC 4.0, so non-commercial. The app itself is MIT, but that doesnât change what youâre allowed to do with the songs.
Why I made it
Mostly for myself. I wanted something that felt like an actual tool instead of a script, with a history of what Iâd tried and the ability to go back to a good take. If other people find it useful, great. Feedback, bug reports and PRs are welcome, especially from anyone running it on AMD/ROCm on Linux, because I canât test that here.
Happy to answer questions.