Riffusion
Begin with the workflow and records, then use audio classification as supporting information—not platform attribution.
- Product context
- Generated musical clips and songs, depending on version.
- Useful evidence
- Project history, exports and creator disclosure
- Public detector output
- Category, component indicators, confidence and timeline
- Attribution supported
- No
Start with the production path
Historical descriptions of a product may not represent its current model or interface.
A rendered master flattens that history into one waveform. Classification can assess the waveform, but it cannot recover prompts, ownership, consent or the division between generated and performed work.
Evidence to request before drawing a conclusion
Date any technical claim and identify the exact model release; old artefact lists age quickly.
- The original export and its date
- Prompts, generation history or platform records where available
- DAW sessions, stems and edits made after export
- A direct account from the creator
What the report actually contributes
The current site sends the complete file to a specialist third-party service. It returns a primary category, separate vocal and instrumental percentages, confidence and sometimes window values. The application does not blend those fields into a platform score.
The detector does not test for a Riffusion-specific signature.
Use the answer in proportion to the stakes
For curiosity, a result may be enough context. For moderation, contracts, copyright, employment or education, obtain records and human review. An inconclusive result is not a concealed accusation, while a not-AI result is not a certificate of human authorship.