We were away from this column for a few days, which turned out to be good timing, because the story only makes sense at five days long.

A music model called YuE2 went up on Hugging Face on 9 September. It writes complete songs from a style prompt and lyrics. By this morning it had about 6,700 downloads and 581 likes, which is modest. What happened in between is the part worth your attention.

The five days

On the 11th somebody posted it to r/LocalLLaMA with the line “surprised no one has posted it in this sub”. The same day, a pull request adding native support landed in ComfyUI. It was merged.

On the 12th somebody had it running in 8 to 9 GB of VRAM, via quantised weights in a separate audio inference project. A model that needed a serious card on Monday ran on a modest one by Tuesday.

Also on the 12th, someone fed it a Commodore 64 SID tune and used it to drive a vocal track, having built a converter that turns an eight bit chiptune into style, lyrics and melody conditioning. That is not a use case anybody designed for.

On the 14th came the one that actually matters. YuE2 works by generating semantic tokens which then become audio, and the encoder that converts existing recordings into those tokens was not part of the release. Without it you cannot bring your own music in. So somebody trained the missing encoder themselves and released it. Hours later, a LoRA trainer built on top of that encoder appeared, from a different person.

By today there is an instrumental LoRA trained on 2,700 tracks across more than a hundred genres, a hum to song adapter, a cover song workflow, and at least one toolkit author who has made it their default.

Six days. A release, a quantisation, a reverse engineered missing component, a training pipeline, and a set of adapters, almost none of it by the people who made the model.

Why we are pointing at this one

Because the usual argument for open weights is about cost or privacy, and this is the better argument.

A closed model that ships without a feature does not have that feature until the company decides otherwise. An open one that ships without a feature has it in a week, built by somebody who needed it, and then that piece becomes the foundation for the next three things. The encoder is the clearest case we have seen of it: one person filled a gap, and within a day the gap had a LoRA trainer sitting on it.

None of that requires the original team to be generous, responsive, or even still interested.

The part almost nobody is mentioning

YuE2 is released under CC BY-NC 4.0. The NC is non commercial.

We have checked that on the model page rather than taking anyone’s word for it, and we are not lawyers. But the plain reading is that music you generate with it is for personal and non commercial use, which means it is not a soundtrack for a monetised video, a client project, or anything with an ad on it.

In five days of enthusiastic posts, workflows, adapters and toolkits, we have not seen that mentioned once. Not because people are hiding it. Because the licence is boring and the demos are exciting, which is exactly how we got the MiniMax H3 licence wrong ourselves two weeks ago and had to correct it in public.

If you are making music for yourself, ignore this paragraph entirely and go and have fun. If you were about to solve your channel’s music budget, read the licence first. Our two minute routine is the version of this we now run before downloading anything.

Where we actually stand

We pay for our music. Our episode scores come from a commercial service, and we have not run YuE2, so we are not going to tell you how it sounds. Several people are claiming it matches or beats the current commercial offerings, and those are their ears, not ours.

What we can say is what would move us. A verdict on generated audio is not something we can measure our way to, which we learned the hard way when two settings that scored cleaner on our meters both made our presenter’s voice sound less like herself. Music is the same. It needs somebody to listen, and the only thing that counts is whether it sounds right to a person.

So it goes on the bench list rather than into production, and when we have run it you will get the honest version, including the part where the licence means we would still be paying for anything we publish.

A daily note from our news radar. The week gets the full treatment in the DIY AI Brief every Monday.