Sometimes – and honestly, this is new territory. The rules are still being written, and they differ from one platform and one client to the next. Here is where we think you stand, and what we suggest you do.
Vienna Performer renders what you composed. It is an AI-assisted tool, in the way that AI-assisted mixing and mastering are: it needs your exact input – notes, note lengths, velocities, dynamics – which is a very different thing from a prompt. It creates the performance you tell it to create. It invents nothing. The music is yours, and so is the copyright in it. We also keep neither your MIDI data nor your renders.
Streaming platforms
Every platform that has published a policy draws its line in roughly the same place: the distinction is between music that was generated and music that was made with AI-assisted tools, and what decides it is who made the creative decisions, not which tools touched the audio.
DDEX (Digital Data Exchange) is the metadata standard the release chain uses – labels, distributors, streaming services and collecting societies exchange it as XML. It describes how a recording was made:
- Five categories: AI vocals, AI instrumentation, AI composition, AI post-production, AI lyrics.
- Recording-level flag: Contains AI – All / Partly / None.
For a track with Vienna Performer in it, the answer is normally AI instrumentation, and Partly. There is usually no box for this in your own upload form, because your distributor submits these fields. So tell your distributor.
Why we recommend disclosing
Nothing requires you to, and nothing in a render gives you away – there is no watermark and no AI metadata in the file. We suggest disclosing anyway, for two reasons.
The first is that we would rather be straightforward about how this works than leave it to be characterized by someone else. The second is more practical: Partly is the flag that protects you. It marks the difference between a recording that used AI for the instruments and a recording that is AI-generated – and it is the fully AI-generated ones that platforms demote, exclude from playlists and in some cases do not pay.
Declaring says your instruments were rendered. It does not say your music was generated, it does not say the composition isn’t yours, and it does not put your release in the AI-generated category.
If a platform flags your track
Keep your project. The DAW session, the MIDI, the notation file and the renders are evidence that a human wrote the music and directed the performance. Detection tools listen to audio – they do not read metadata and they do not know what Vienna Performer is. If you ever have to make the case, your project files make it better than anything we could write here.
Film, television, games and library music
There is no standard here at all. In most cases clients care whether you own the copyright rather than how you made the recording – though production and library music is the exception, and some publishers now ask about AI use explicitly or rule it out in their submission terms. Read the contract in front of you.
If you are asked to describe your production method, this is wording you can use:
The music delivered is my own composition and arrangement. Orchestral parts were performed using Vienna Performer, a rendering service from Vienna Symphonic Library that performs notated or sequenced parts using models trained exclusively on recordings made by VSL with musicians of the Vienna Synchron Orchestra, licensed for that purpose. No third-party recordings, scraped audio or AI-composed material are involved. The instrument material in the delivered audio is warranted free of third-party rights by VSL; the composition and the master are mine.
Collecting societies
Nothing changes. The composition is human and registered as yours, and the rendered audio is a recording you produced, so the producer’s rights in it are yours too.
What VSL does, and does not, do
- No claim on your composition. We acquire no rights whatsoever in what you send us.
- No training on your material. Your input and your renders are never used to train, fine-tune or evaluate any model.
- Nothing kept. Your MIDI input and your renders are deleted after delivery.
- No marking in the file. Renders carry no watermark and no AI metadata.
- A guarantee you can pass on. The instrument material in your render is warranted free of third-party rights.
- One thing you may not say. A render may not be presented as the performance of a named or identifiable musician.
This guide is information, not legal advice, and the rules in this area are changing quickly. Where a platform or a client has its own requirements, those apply.