Reply to thread

Message: [QUOTE="Bombastus, post: 92400, member: 2178"] ElevenLabs currently lets users build Music Finetunes from up to 50 uploaded tracks and as much as 250 minutes of audio. Its API identifies the base music model, accepts audio files to train on, and exposes a training lifecycle with pending, in-progress, completed, failed, and blocked states. A fine-tune starts with a model that already knows how to generate music, then adapts it using another dataset. You are not rebuilding the whole system from zero, but you are still running a training process that changes how future generations behave. Calling the result a custom model can hide an important detail. The new behavior sits on top of an existing base, so [B][URL='https://goldmidi.com/community/threads/umg-has-not-disclosed-an-elevenlabs-training-license.77086/']undisclosed AI music training rights[/URL][/B] cannot be inferred merely because a company says it offers fine-tuning. [HEADING=2]A fine-tune starts from an existing model[/HEADING] Pretraining and fine-tuning happen at different stages. Pretraining gives a model its broad musical capability across whatever material was used to build the original system, while fine-tuning pushes that existing capability toward a narrower sound, genre, catalog, voice, or production identity. ElevenLabs makes the lineage unusually visible in its current Music Finetunes API. Every finetune records a model_id, and the response describes it as the base music model the finetune was trained on. Music v1, Music v2, and Music v2.5 can currently serve as those starting points. This creates two separate provenance layers. One concerns the data behind the base model. The other concerns the smaller adaptation dataset supplied later, and answering a question about one layer does not automatically answer the other. A company could fully document the tracks used for a custom fine-tune while saying little about the original base model. The reverse can happen too. Clear base-model licensing does not tell you who supplied a later customer's private training set or what rights covered those files. [HEADING=2]Fine-tuning does not have to rewrite every weight[/HEADING] The word training sometimes makes people picture every parameter inside a model being rewritten. Modern fine-tuning can be much lighter. Some methods update only a relatively small set of added parameters while leaving most or all of the original base weights untouched. Adapter-based [B][URL='https://arxiv.org/abs/2506.21298']parameter-efficient music adaptation[/URL][/B] has been tested on models including MusicGen and Mustango, where trainable adapter components steer the generator toward low-resource musical traditions without requiring a full retraining of billions of parameters. The technical shortcut changes the size of the update, not the basic category of the operation. A LoRA-style or adapter-style fine-tune can therefore be small enough to store separately from the underlying model. Load the base model, attach the learned adaptation, and generation shifts toward the material used during the tuning stage. None of this establishes how ElevenLabs implements its own Music Finetunes internally. Its public documentation does not specify whether the service updates full weights, trains adapters, or uses another adaptation method. What it does state clearly is that uploaded audio is used to train a finetune tied to a named base model. This matters when people use “training” as shorthand for only the huge first run that creates a foundation model. A later adaptation can involve far less compute and far less data while still learning persistent behavior from supplied examples. [HEADING=2]The adaptation dataset can create its own problems[/HEADING] ElevenLabs says its Music Finetunes are meant to learn stylistic patterns across instrumentation, arrangement, genre, production style, tempo, rhythmic feel, timbre, and vocals when vocals are included. The goal is consistency across future tracks rather than copying one uploaded song. Dataset design decides how cleanly that works. ElevenLabs warns against near-identical recordings and says repetitive collections can increase the risk of outputs resembling particular source tracks too closely. A smaller, coherent collection can be more useful than simply feeding the system more minutes. This gives fine-tuning a failure mode that prompting does not share in the same way. A weak prompt can produce a weak generation and disappear with the request. A badly constructed fine-tune can bake an unwanted bias, narrowness, or excessive resemblance into a reusable adaptation that affects generation after generation. Removing the custom adaptation also would not erase whatever the base model learned before the fine-tune existed. The two stages have different histories, which is why a serious training disclosure should identify both the starting model and the material used to adapt it. Fine-tuning is therefore narrower than training from scratch, but it is not merely a fancy prompt preset. Data enters an optimization process, persistent behavior changes, and the resulting system carries a new training history layered over the old one. [/QUOTE]

Name