https://wiki.sugarlabs.org/index.php?action=history&feed=atom&title=Music_Blocks%2F2025-03-16-meeting 2026-05-04T13:53:52Z Revision history for this page on the wiki MediaWiki 1.43.0 https://wiki.sugarlabs.org/index.php?title=Music_Blocks/2025-03-16-meeting&diff=104619&oldid=prev 2025-03-16T12:41:27Z

<p>Today&#039;s meeting notes</p> <p><b>New page</b></p><div>== Reports ==<br /> <br /> === Falgun ===<br /> <br /> ==== Music Blocks reflection tool ====<br /> <br /> Presented a video of tests on a tool for reflection.<br /> <br /> It presents questions as bullets.<br /> <br /> Discussion: A program called Eliza is something good to check out.<br /> <br /> ==== Temperament ====<br /> <br /> 31 EDO -- it&#039;s working fine with 32, but not with 31<br /> Stop button<br /> Octave -- confusing when there is only one pitch.<br /> Discussion -- Perhaps eliminate octave space? (Ask microtonalist?)<br /> <br /> If it&#039;s greater than 45, then default to the grid.<br /> <br /> === Aman Naik ===<br /> <br /> Trying to set up a time about social media; Devin requested Aman to propose some specific times.<br /> <br /> === Om Santosh ===<br /> <br /> ==== Slint testing ====<br /> <br /> Slint for MB repo; running into an error<br /> <br /> === Nikhil ===<br /> <br /> ==== Git backend ====<br /> <br /> Tried hashing to tie browsers to projects<br /> <br /> Secret is stored in your local storage<br /> <br /> === Diwangshu ===<br /> <br /> ==== Reflective learning ====<br /> <br /> Creates a summary, and analyzes<br /> <br /> ==== Tuner for Sample Widget ====<br /> <br /> Discussion for how to improve. Suggestion to collaborate with Muhammad, who is also working on the tuner.<br /> <br /> ==== MIDI import ====<br /> <br /> Analysis for note length and spacing to register, which can help us put different musical voices into different Start blocks (in a smarter way).<br /> <br /> === Muhammad ===<br /> <br /> ==== Sample ====<br /> <br /> Shared results of tests for AI-generated samples<br /> <br /> Organized the sounds -- needs reviewed; using a spectrogram could be a helpful tool to analyze the sound.<br /> <br /> === Justin ===<br /> <br /> ==== Play only ====<br /> <br /> Please double-check that all the changes are made. Also, requesting for testing.<br /> <br /> Ajeet has made a comment<br /> <br /> ==== MB-v4 ====<br /> <br /> MB-v4 program building: https://hackmd.io/_oLiSdcOSByx5Fhs4oOzsg?view<br /> <br /> === Ajeet ===<br /> <br /> ==== Cypress Tests ====<br /> <br /> Presentation of tests<br /> <br /> === Harshit ===<br /> <br /> 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. <br /> <br /> === Anindya ===<br /> <br /> Attended, but needed to leave early<br /> <br /> &quot;Tag me on the channel for any v4 related questions.&quot;<br /> <br /> === Shubham Singh ===<br /> <br /> ==== Pixel detect ====<br /> <br /> Demonstration of work done<br /> <br /> == Discussion on Debugging ==<br /> <br /> Semantic, syntactic. But there&#039;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.<br /> <br /> * What works and what doesn&#039;t work?<br /> * Have you tried x, y, or z?<br /> * Walk a user through using print blocks and other debugging<br /> <br /> 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.</div>

Pikurasa