Chris Oh’s Status Report for Feb 14

This week I focused on refining the software architecture and transitioning from high-level design into early implementation. I expanded the system design to incorporate both Beat and No-Beat modes, further specified the responsibilities of the conversion layer, and began prototyping the overall software framework. In parallel, I prepared materials for the upcoming design presentation.

Software Architecture Updates

  • Refined and updated the software architecture to explicitly support two operating modes: Beat Mode and No-Beat Mode.
  • Expanded the conversion layer design by clearly defining:
    • Raw Event IR structure
    • Quantization process for Beat Mode
    • Key mapping logic (MIDI → 88-key index)
    • JSON payload generation for hardware transmission

  •  Integrated a Streamlit-based UI into the Core Layer design to support:
    • Image upload
    • Mode selection
    • BPM input
    • Play/Pause controls
    • Status feedback

  • Ensured that the updated architecture maintains modular boundaries and allows independent testing of:
    • Image-to-MusicXML conversion
    • MusicXML parsing
    • Event processing
    • Hardwarecommunication

Design Presentation Preparation

  • Prepared slides and technical material for the design presentation.
  • Refined system diagrams to reflect:
    • Updated pipeline stages
    • Mode branching logic
    • Software-hardware interface definition

Week 2 Status Report Requirements: Part C

From an economic standpoint, LumiKey is intentionally designed to remain affordable and practical. The hardware uses commonly available, low-cost components such as an ESP32 microcontroller and addressable LED strips, which keeps overall system cost reasonable. On the software side, we rely on open-source tools like Python and music21, avoiding licensing fees and making long-term development more sustainable. Because the system is designed to attach to a standard piano or keyboard rather than replacing it, users do not need to purchase a specialized instrument. This approach helps keep the product accessible to students and families who may already own a keyboard but are looking for a more guided learning experience.

Schedule

I am currently on schedule. The architecture has been refined to include mode logic and UI integration, and the foundational software framework has been established. The project is transitioning from planning into active implementation.

Deliverables for Next Week

  • Implement core functionality of the conversion layer (MusicXML → Raw Event IR → chord grouping).
  • Begin implementing Beat Mode quantization logic.
  • Establish and test JSON transmission pipeline to the hardware layer.

Leave a Reply

Your email address will not be published. Required fields are marked *