Music Blocks/2025-03-16-meeting
Reports
Falgun
Music Blocks reflection tool
Presented a video of tests on a tool for reflection.
It presents questions as bullets.
Discussion: A program called Eliza is something good to check out.
Temperament
31 EDO -- it's working fine with 32, but not with 31 Stop button Octave -- confusing when there is only one pitch. Discussion -- Perhaps eliminate octave space? (Ask microtonalist?)
If it's greater than 45, then default to the grid.
Aman Naik
Trying to set up a time about social media; Devin requested Aman to propose some specific times.
Om Santosh
Slint testing
Slint for MB repo; running into an error
Nikhil
Git backend
Tried hashing to tie browsers to projects
Secret is stored in your local storage
Diwangshu
Reflective learning
Creates a summary, and analyzes
Tuner for Sample Widget
Discussion for how to improve. Suggestion to collaborate with Muhammad, who is also working on the tuner.
MIDI import
Analysis for note length and spacing to register, which can help us put different musical voices into different Start blocks (in a smarter way).
Muhammad
Sample
Shared results of tests for AI-generated samples
Organized the sounds -- needs reviewed; using a spectrogram could be a helpful tool to analyze the sound.
Justin
Play only
Please double-check that all the changes are made. Also, requesting for testing.
Ajeet has made a comment
MB-v4
MB-v4 program building: https://hackmd.io/_oLiSdcOSByx5Fhs4oOzsg?view
Ajeet
Cypress Tests
Presentation of tests
Harshit
1- Have a PR open about adding print block to phrase maker default stack, we need your input on this. 2- After discussion with Walter about the journal idea i am planning to drop it because rn its not making sense, please let me know what you think about that.
Anindya
Attended, but needed to leave early
"Tag me on the channel for any v4 related questions."
Shubham Singh
Pixel detect
Demonstration of work done
Discussion on Debugging
Semantic, syntactic. But there's a bigger-picture level of debugging where we need to help the user. Ask the student what there goal is, how to break it down, walk the student through the process of debugging.
- What works and what doesn't work?
- Have you tried x, y, or z?
- Walk a user through using print blocks and other debugging
Suggestion: Maybe we should take stock of what debugging tools we already have within Music Blocks (such as Print block) and use that to suggestion some mid-level debugging workflows for students.