AI-DJ

The company appears to be a two-person team building an experimental, real-time music mixing system that uses live sensor data from audience phones to drive a procedurally generated set — without playlists or traditional DJing. The core idea is to let crowd energy shape the music in real time.

The description states that AI-DJ is a system where:

• Audience phones connect via browser (no app install)
• Phones read motion (camera) and sound (mic) locally
• Sensor data is reduced to small JSON vectors and streamed over WebSocket
• A server aggregates this into a "room state" signal
• This drives a live mixing engine using Tone.js procedural audio
• No recordings are made; each phone discards raw media after processing
• The music is generated from fixed loops locked to one musical scale, ensuring no wrong notes

Inference The system appears to be an experimental proof-of-concept rather than a production-ready product.

The author claims:

• Most "AI DJ" projects are just smart playlists
• They wanted the room itself to be the input, not just a listener
• The crowd's movement steers the music live
• No playlist, no booth — the room is the DJ

Inference This positions AI-DJ as a novel approach to DJing that removes human agency in favor of collective audience behavior. It’s framed as an alternative to traditional or AI-assisted playlist systems.

The description does not state any specific customer or target market beyond the general idea of "crowd energy shaping music."

Not evidenced No indication of who would pay for this, what venues or events it targets, or whether there is a defined ICP.

There is no mention of pricing, monetization, or business model in the description.

Not evidenced No evidence of revenue streams, customer acquisition costs, or any commercial framework.

The team built:

• On-device signal extraction (motion via frame-differencing, sound via RMS/onset detection)
• Lightweight JSON vector streaming over WebSocket
• Aggregation logic on server side
• Procedural engine using Tone.js with fixed loops and musical scale constraints
• Quantized parameter changes to avoid glitchy transitions

Inference The system is technically feasible but limited in scope — built for demo purposes, not scalable or robust enough for commercial deployment.

The project was completed in one week by two people as a hackathon submission.

The description states that most existing "AI DJ" projects are just smart playlists, implying a gap in the market for more interactive or crowd-driven systems.

Inference The team sees themselves as solving a problem with current AI DJ tools by introducing real-time audience participation — though they do not name competitors or describe their competitive advantage beyond novelty.

• Novelty vs. Viability: The concept is experimental and may not translate into a sustainable product.
• Scalability Concerns: Built for demo, not scale; mobile browser limitations (camera throttling, HTTPS requirements) suggest technical constraints.
• Lack of Commercialization Evidence: No indication of monetization strategy or customer interest beyond the hackathon.
• Limited Scope: The system uses fixed loops and musical scales — may not evolve into a rich or varied experience over time.

1. What is your plan to validate demand for this type of music mixing experience?
2. Have you tested this with real crowds in real venues?
3. How do you intend to monetize the product, and what are your go-to-market strategies?
4. What are the technical limitations that prevent scaling beyond a small group of phones?
5. Are there any legal or privacy concerns around collecting sensor data from users' phones?