Open Issues Need Help
View All on GitHubAI Summary: This issue requests the translation of the `copilot-instructions.md` file into Japanese, ensuring it reflects the latest project status. Additionally, it asks to clarify the deploy structure to prevent 404 errors, likely by explicitly documenting how deployments are handled.
AI Summary: This issue proposes a change to the attached JSON format. Specifically, it suggests renaming the 'ProgramChange' field to include 'ProgramChange' in its name to enhance the self-descriptiveness of the tone color JSON. This aims to make the JSON structure more understandable regarding program change information.
AI Summary: This issue proposes adopting Biome as the TypeScript formatter and linter for the demo development of attached JSON. The goal is to improve code quality and consistency within the project's TypeScript components.
AI Summary: This issue proposes adding a new demo page to the attached JSON file. The purpose of this JSON file is to implement "minor noise countermeasures" for demos.
AI Summary: This issue proposes implementing a feature to control the on/off state of linear interpolation for timbre changes between adjacent (sequential) notes in attached JSON data. Additionally, a new demo page will be added to showcase this functionality.
AI Summary: This issue requests that all demo playback of attached JSON files be set to autoplay. Specifically, autoplay should be triggered immediately after SMF upload, after a dropdown selection is made, after MML input debounce, and after JSON editing debounce.
AI Summary: This issue proposes implementing a JSON visualization area for logs, specifically for each demo, with the goal of commonizing this functionality. The visualization should be a horizontally scrolling area, similar to a piano roll, with channels represented vertically. Events will be drawn horizontally using pixel coordinates.
AI Summary: This issue proposes a UI change for the "demo" feature. Specifically, it requests the placement of an MML input textarea near the SMF upload button, with the MML input taking precedence if both are provided. This aims to improve the user experience for generating demo sounds.
AI Summary: This issue proposes enhancing the demo functionality by allowing users to select instrument presets from a dropdown menu instead of having them hardcoded. This would improve user experience and flexibility in the demo's sound generation.
AI Summary: This issue proposes adding "portamento" and "soft LFO" functionality to the demo, using attached JSON data. The goal is to enhance the demo's capabilities by incorporating these specific musical expression features.
AI Summary: This issue requests a desk check of attached JSON demos to confirm they include examples of vibrato, portamento, and software LFOs for tone register modulation. The goal is to verify the presence of these specific musical effects within the provided demo files.
AI Summary: This issue proposes allowing users to specify instrument tones using an attached JSON file. This would enhance the flexibility of the smf-to-ym2151log converter by enabling custom sound configurations.
AI Summary: This issue proposes creating a new, separate demo page for delay vibrato, distinct from existing pages. The goal is to add this new functionality as a standalone demo.
AI Summary: This issue proposes adding a new minimal demo implementation to the `demo-library/` directory. This implementation will serve as a communication check to demonstrate how the `web-ym2151` repository can be used as a library, and this new demo should also be deployable.
AI Summary: This issue proposes exploring the feasibility of using the `mmlabc-to-smf-rust` repository as a library to implement MML input directly into a textarea, in addition to existing SMF input. The goal is to enhance the demo functionality by allowing users to input MML directly.