Remote Clapping Audio Synchronization Through Server-Merged Event Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems fail to allow multiple users located apart to share real-time clapping sounds during events like theatrical performances or musical performances, as pre-recorded clapping sounds are insufficient for enhancing the experience.

Innovation Solution

A communication method and system that enables users to transmit event data instructing sound generation to a server, which merges and relays these data to control the generation of synchronized clapping sounds across terminals, allowing users to share their real-time clapping sounds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If pre-recorded clapping sounds are used, then the system is simple to operate, but the realism and naturalness of the sound is insufficient

Engineering Contradiction:
Improveease of operationVSAvoidrealism of sound
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent uses audio copying technology to capture and reproduce actual clapping sounds from multiple users in real-time. Instead of using pre-recorded fixed sounds, the system copies the authentic clapping audio signals from each user's terminal and transmits them to other terminals, preserving the natural characteristics and variability of real clapping sounds while enabling remote sharing.

Inventive Principle:
Principle #26Copying

2Reliability

If real-time clapping sounds from multiple users are shared, then the realism and naturalness is improved, but data transmission delays increase

Engineering Contradiction:
Improverealism of soundVSAvoiddata transmission delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing communication channels and preparing audio processing pipelines in advance. Event data instructing sound generation is transmitted proactively, and the server prepares to merge and relay this data before actual clapping events occur, reducing latency during real-time transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The server acts as an intermediary that efficiently manages the transmission of event data between multiple terminals. Instead of direct peer-to-peer transmission which would create multiple delay paths, the server consolidates and relays event data, optimizing the transmission path and reducing overall data transmission delays while maintaining real-time performance.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If event data is merged and relayed through a server, then synchronized sound generation is achieved, but the system complexity increases

Engineering Contradiction:
Improvesynchronization of soundVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The server merges event data from multiple terminals into a unified data stream that instructs synchronized sound generation. By combining the event data indicating clapping sounds from first terminal, second terminal, and other terminals into a single coordinated output, the system achieves precise synchronization across all terminals without requiring complex peer-to-peer coordination protocols at each device.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The server provides multi-functional capabilities by handling event data collection, merging, timing synchronization, and relay to multiple terminals simultaneously. This universal approach consolidates what would otherwise require separate functions in each terminal, reducing overall system complexity while achieving reliable synchronized sound generation across the network.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Device complexity

If multiple terminals generate sounds independently, then the system is simpler, but duplicate sound production occurs

Engineering Contradiction:
Improvesystem complexityVSAvoidsound quality control
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system uses feedback mechanisms where the server receives event data from terminals, processes it centrally, and relays coordinated sound generation instructions back to the terminals. This feedback loop ensures that each terminal generates sound based on unified event data rather than independently, preventing duplicate sound production while maintaining relatively simple terminal devices.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12537982B2Communication method and system
Publication Date: 2026.01.27 YAMAHA CORP
  • US12537982B2 patent drawing
  • US12537982B2 patent drawing
  • US12537982B2 patent drawing

AI summary

A first terminal transmits first event data instructing generation of a first sound to a server. A second terminal transmits second event data instructing generation of a second sound to the server. The server transmits data including the first event data and the second event data to the first terminal. The first terminal controls generation of the first sound and the second sound, based on the data including the first event data and the second event data.