± HEALTH Bipolar disorder (BD) is a complex and heterogeneous psychiatric condition, characterized by fluctuating clin…+ SCIENCE Semiconductor materials are widely used in electronic, optoelectronic, and energy applications. While DFT-bas…+ HEALTH Lifestyle interventions for patients with prostate cancer have been shown to improve treatment adherence and…− HEALTH Large language model (LLM)-based conversational agents are increasingly used in health care, yet their capaci…+ HEALTH The application of artificial intelligence (AI) in simulating detailed patient-doctor interactions for object…+ HEALTH Diagnostic error, defined as missed, wrong, or delayed diagnoses or those not communicated to patients, is co…− ENTERTAINMENT The music streaming platform receives almost 90,000 AI-generated tracks each day, a jump from the 75,000 it l…− ENTERTAINMENT Sony has filed a second lawsuit against AI music generator Udio over 30,117 recordings, using rivals’ licensi…
TruaceTracing the truth around AIWednesday, July 22, 2026
Subscribe
TRV-2026-0504Certified recordJournalism

Sony sues Udio again over 30,000 songs, seeks $4.5bn

Sony has filed a second lawsuit against AI music generator Udio over 30,117 recordings, using rivals’ licensing deals to attack Udio’s fair-use defence.

Entertainment · P Space — documented harm · certified 2026-07-22 · v1 · article view · machine-readable

Current reading — problem

Sony's second lawsuit alleges AI music generator Udio infringed 30,117 recordings and seeks to defeat a fair-use defence by pointing to licensing deals struck by rival AI firms.

Evidence

  • JournalismTNW2026-07-21
Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0504, v1: “Sony sues Udio again over 30,000 songs, seeks $4.5bn.” Truvace, 2026-07-22. /record/TRV-2026-0504 (accessed at citation time). sha256 d3f88b88373e69fc…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1d3f88b88373e…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0504 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.