Skip to content
Introduction
Appendix
SCMUDC Enrichment Implementation Summary

SCMUDC Enrichment Implementation Summary

Overview

This document summarizes the implementation of SCMUDC (Sound Control Management Usage Data Collection) event enrichment in the AfterTouch toolkit. The enhancement provides human-readable analysis of device telemetry data to improve usability and debugging capabilities.

Problem Solved

Previously, SCMUDC telemetry events were stored as raw JSON with Base64-encoded XML content, making them difficult to analyze. Users had to manually decode content to understand what device interactions were being recorded.

Solution Implemented

1. Backend Enrichment (pkg/service/proxy/)

New File: scmudc.go

  • SCMUDCRequest/SCMUDCEvent Structs: Parse incoming telemetry JSON
  • EnrichedSCMUDCEvent Struct: Human-readable analysis with decoded content
  • DecodedContent Struct: Parsed XML metadata (track names, artwork URLs, etc.)
  • enrichSCMUDCRequest(): Main enrichment function that:
    • Identifies event origin (app, hardware, or internal system)
    • Decodes Base64 XML content for device events
    • Creates human-readable summaries
  • Helper Functions: Button formatting, content summarization, origin descriptions

Enhanced File: recorder.go

  • Updated save() method: Extracts SCMUDC data during recording
  • New writeRequestWithEnrichment(): Adds enriched comments to .http files
  • New writeResponseWithEnrichment(): Includes SCMUDC analysis in response section
  • Updated Interaction struct: Added SCMUDCData field for API responses
  • New extractSCMUDCFromFile(): Parses enrichment data from existing .http files
  • Enhanced parseInteractionFile(): Populates SCMUDC data when listing interactions

2. Frontend Enhancement

Updated HTML (pkg/service/handlers/web/index.html)

  • New Column: Added “Event Details” to interactions table
  • Table Structure: Updated to accommodate SCMUDC enrichment display

Enhanced JavaScript (pkg/service/handlers/web/js/script.js)

  • Updated fetchInteractions(): Displays enriched SCMUDC data with icons
  • New Helper Functions:
    • getOriginIcon(): Maps origins to emojis (📱 App, 🎛️ Hardware, 🔄 Internal)
    • getActionIcon(): Maps actions to emojis (▶️ Play, ⏸️ Pause, etc.)
    • showSCMUDCDetails(): Detailed popover for complex events
    • displaySCMUDCPopover(): Modal dialog with full decoded content
  • Truncation Logic: Long content shows “(…)” with click-to-expand

Event Origin Clarification

Based on analysis of recorded data:

OriginSourceDescriptionExample Events
gabboSoundTouch AppMobile/desktop app UI interactionsPlay, Pause, Power via app
consoleDevice HardwarePhysical buttons on speakerPreset buttons, hardware power
deviceInternal SystemAutomatic device responsesContent playback, system actions

Enhanced .http File Format

Before (Raw) 

### POST /v1/scmudc/AABBCCDDEEFF
POST /v1/scmudc/AABBCCDDEEFF
Host: events.api.bosecm.com
...

{"envelope":...,"payload":{"events":[{"data":{"contentItem":"PD94bWw..."}}]}}

After (Enriched) 

### POST /v1/scmudc/AABBCCDDEEFF
// Origin: Internal System (device)
// Action: play-item
// Command: Billie Eilish - bad guy (instrumental version)
// Summary: Device: Spotify: Billie Eilish - bad guy (instrumental version)
//
// Decoded Content:
// - Source: SPOTIFY
// - Item: Billie Eilish - bad guy (instrumental version)
// - Account: gesellix
// - Artwork: https://i.scdn.co/image/ab67616d0000b273...
//
// Full XML Content:
// <?xml version="1.0" encoding="UTF-8"?>
// <ContentItem source="SPOTIFY" type="tracklisturl" ...>
//     <itemName>Billie Eilish - bad guy (instrumental version)</itemName>
//     <containerArt>https://i.scdn.co/image/ab67616d0000b273...</containerArt>
// </ContentItem>
POST /v1/scmudc/AABBCCDDEEFF
...

{% raw %}
> {%
    // Response: 200 OK
    // SCMUDC Event Analysis:
    // - Origin: Internal System (device)
    // - Action: play-item
    // - Summary: Device: Spotify: Billie Eilish - bad guy (instrumental version)
    // - Content: Billie Eilish - bad guy (instrumental version)
    // - Account: gesellix
%}
{% endraw %}

Web UI Enhancement

Interactions Table

  • New Column: “Event Details” shows enriched summaries
  • Visual Icons: Origin and action type indicators
  • Truncation: Long content abbreviated with “(…)” expansion
  • Backward Compatibility: Works with existing recordings

Event Details Display 

📱 ▶️ Play Button                    (Simple app action)
🔄 🎵 Billie Eilish - bad guy... (...)  (Complex device event with details)
🎛️ ⭐ Preset 5                        (Hardware preset button)

Detailed Popover

For complex events, clicking “(…)” shows:

  • Origin Description: “SoundTouch App” instead of “gabbo”
  • Full Content Information: Track names, artwork URLs, account details
  • Complete XML: Formatted and readable content item data

Implementation Benefits

For Users

  • Immediate Recognition: See what actions were performed without decoding
  • Better Debugging: Quick identification of app vs. hardware vs. system events
  • Rich Context: Track names, accounts, and content sources visible at a glance

For Developers

  • Structured Data: Consistent parsing and enrichment pipeline
  • Extensible: Easy to add new event types and origins
  • Backward Compatible: Existing recordings work without re-processing

For Analysis

  • Pattern Recognition: Quickly identify user behavior patterns
  • Service Integration: See which music services are being used
  • Device Usage: Understand app vs. hardware control preferences

File Structure 

pkg/service/proxy/
├── scmudc.go                 # New: SCMUDC enrichment logic
├── recorder.go               # Enhanced: Enrichment integration
│
pkg/service/handlers/web/
├── index.html                # Enhanced: New table column
├── js/script.js              # Enhanced: SCMUDC display logic
│
docs/
├── scmudc-events-analysis.md # New: Analysis documentation
├── SCMUDC-ENRICHMENT-IMPLEMENTATION.md  # This file

Technical Decisions

Base64 Decoding Strategy

  • When: During recording (not on-demand) for performance
  • Fallback: Parse from .http files if enrichment missing
  • Storage: Both enriched comments and structured data in API responses

Icon Selection

  • Emoji Usage: Universal, colorful, intuitive recognition
  • Semantic Mapping: Icons match function (📱 for app, 🎛️ for hardware)
  • Fallback: Generic icons (❓, 🔘) for unknown types

Backward Compatibility

  • Graceful Degradation: Missing enrichment data doesn’t break UI
  • File Parsing: Extract enrichment from existing .http files
  • API Enhancement: New fields optional in Interaction struct

Future Enhancement Opportunities

  1. Event Correlation: Link device events to user actions
  2. Statistics Dashboard: Origin-based usage analytics
  3. Content Recommendations: Track listening patterns
  4. Device Health: Monitor interaction frequency and patterns
  5. Export Features: CSV/JSON export of enriched event data

Testing Considerations

  • Edge Cases: Malformed Base64, missing XML elements
  • Performance: Large numbers of SCMUDC events
  • Browser Compatibility: Emoji display across different browsers
  • Data Validation: Ensure enrichment doesn’t introduce errors

This implementation significantly improves the usability of SCMUDC telemetry data while maintaining full backward compatibility and raw data access for advanced users.

Last updated on
Request Recording ConceptSCMUDC Events Analysis