Advanced OSC Integration with TouchOSC, QLab, and More

We need to translate the article content to French, keeping all formatting, code, URLs, etc. Must keep product names unchanged. Also keep markdown formatting. The article is in HTML with headings, paragraphs, lists, tables, code blocks. We need to translate all prose and explanatory text. Keep code examples, addresses, etc. Keep URLs unchanged. Keep product names unchanged. Use consistent terminology. Let's translate.

We need to keep the same structure:

etc. The article uses

headings,

,

,
, , , , ,

, , etc. Also tags with placeholder alt text. We must translate the alt text too? The alt text is "Screenshot placeholder: OSC data flow diagram" etc. We must translate that. Also the tags: we keep URLs unchanged, but the link text should be translated. For example: "https://music.apple.com/..." The link text is the URL; we keep that. But the surrounding text "…". The text inside the	is "https://..." etc. That is fine. Also the tags inside	etc. We keep them. Also we have blocks with code. We keep them unchanged. Also the we keep alt text translated. Also the headings etc. Also the remains. Also the final paragraph. We must keep the same line breaks. Also we must keep the tags. Also we must keep the etc. Also we must keep the etc. Also we must keep the with . Also we must keep the tags inside table cells. Also we must keep the tags inside . Also we must keep the etc. Also we must keep the block unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Also we must keep the block content unchanged. Ok. Now translation. We need to translate all prose. Let's go through each section. Title: "Advanced OSC Integration with TouchOSC, QLab, and More" -> "Intégration avancée OSC avec TouchOSC, QLab et plus" But the title is not in the article content; it's just in the prompt. The article content starts with Introduction . So we translate that. Introduction OSC (Open Sound Control) opens up endless possibilities for integrating song data with professional creative software. Beyond VJ applications like Resolume, Song Overlays Pro works with TouchOSC, QLab, Isadora, Max/MSP, and any OSC-compatible application. Translate: OSC (Open Sound Control) ouvre des possibilités infinies pour intégrer les données de musique avec des logiciels créatifs professionnels. Au-delà des applications VJ comme Resolume, Song Overlays Pro fonctionne avec TouchOSC, QLab, Isadora, Max/MSP et toute application compatible OSC. We keep product names unchanged. What you'll achieve: Build custom control surfaces in TouchOSC Trigger theater cues in QLab based on songs Create interactive installations with Isadora Process music data in Max/MSP Connect to any OSC-compatible software Translate: Ce que vous allez accomplir : etc. Also the -> alt translation: "Capture d'écran placeholder : diagramme de flux de données OSC" Prerequisites Before starting, make sure you have: macOS 13.0 (Ventura) or later Song Overlays Pro installed and running OSC-compatible software (TouchOSC, QLab, Isadora, Max/MSP, etc.) Basic understanding of OSC concepts (addresses, ports) Network connectivity between devices (if using multiple machines) Translate accordingly. Understanding Song Overlays Pro's OSC Output Before diving into specific applications, understand what data is available. OSC Addresses Song Overlays Pro sends to these addresses when a song is detected: Address Data Type Example /song/title String "Bohemian Rhapsody" /song/artist String "Queen" /song/album String "A Night at the Opera" /song/artwork String (URL) "https://..." /song/isrc String "GBUM71029604" /song/appleMusicUrl String (URL) "https://music.apple.com/..." /song/changed Boolean true We keep the table unchanged. Only translate the surrounding text. Message Format Messages are sent as OSC bundles All strings are UTF-8 encoded Sent immediately when a new song is detected /song/changed fires with every detection (useful for triggers) Translate. Step 1: Configure OSC in Song Overlays Pro Set up the OSC output for your target application. Open Song Overlays Pro Click OSC in the sidebar Toggle Enable OSC to on Configure connection settings: Host: Target device IP (or 127.0.0.1 for same machine) Port: Match your receiving application's port Click Test to verify connectivity Translate. Multiple Destinations Send to multiple applications simultaneously: Click Add Destination Enter additional host/port combinations Each destination receives identical data Useful for redundancy or multi-system setups Translate. Step 2: TouchOSC Integration Build a custom control surface that displays song information. Setting Up TouchOSC Open TouchOSC on your iPad/iPhone/Android Go to Connections → OSC Configure to receive from your Mac: Receive Port: Match Song Overlays Pro's output port Send Host/Port: Your Mac's IP and desired port (for bidirectional) Translate. Creating a Song Display Layout Open TouchOSC Editor (desktop app) Create a new layout Add Label controls for song data: Label for title: Set OSC address to /song/title Label for artist: Set OSC address to /song/artist Label for album: Set OSC address to /song/album Translate. Label Configuration For each label: Receive: Enable OSC Address: Corresponding /song/... address Value: Text (receives string) Font/Size: Style as desired Translate. Advanced TouchOSC Ideas Now Playing Panel: ┌─────────────────────────┐ │ 🎵 NOW PLAYING │ │ ───────────────────── │ │ Title: {/song/title} │ │ Artist: {/song/artist} │ │ Album: {/song/album} │ └─────────────────────────┘ DJ Controller Integration: Add song display to existing DJ layouts Combine with mixer controls Create set management views Translate. Step 3: QLab Integration Trigger cues in theater productions based on songs. Configuring QLab for OSC Open QLab (version 4 or 5) Go to Settings → Network Under OSC Input: Enable OSC input Set port to match Song Overlays Pro's output Note QLab's IP if on different machine Translate. Creating Song-Triggered Cues Method 1: OSC Trigger Cues Create a new OSC cue Set as trigger cue (responds to incoming OSC) Configure the trigger: Address: /song/changed Arguments: (any value triggers) Method 2: Script Cues For more control, use AppleScript: -- This script runs when song changes tell application id "com.figure53.QLab.5" set songTitle to (osc value "/song/title") -- Use songTitle to control cues end tell Translate the explanatory text, but keep code unchanged. Theater Use Cases Musical Transitions: Auto-advance cues when songs change Sync lighting with music changes Trigger scene markers Immersive Experiences: Display song info on projection Trigger effects based on specific songs Create dynamic setlists Example: Auto-Advance Playlist Create a group cue for each song Add OSC trigger that fires when /song/changed is received Use conditions to match /song/title to expected song Auto-fire the next cue group Translate. Step 4: Isadora Integration Create interactive visuals that respond to music metadata. Setting Up Isadora Open Isadora Go to Communications → OSC Setup More Tutorials Tutorial Display Song Data and Album Art in Resolume Learn how to send real-time song information and album artwork to Resolume Arena using OSC. Create reactive visuals that respond to what's playing. January 18, 2026 7 min read Tutorial Customize Your Overlay Theme and Appearance Make your song overlay match your brand. Complete guide to customizing themes, colors, fonts, and layout in Song Overlays Pro for a professional streaming setup. January 18, 2026 5 min read Tutorial Post Now Playing to Discord with Webhooks Automatically share what's playing to your Discord server. Set up Song Overlays Pro's Discord webhook integration to post real-time song updates to any channel. January 18, 2026 6 min read View All Tutorials