thebne / midiate Goto Github PK

In input/midi.py I used an iterator to define ticks. Since I read MIDI only once every refresh call, it might lead to a deviation

architecture; apps, status bars and config APIs, as well as examples

Right now the code timestamps the message when received, but rtmidi backend gives a timestamp (https://github.com/SpotlightKid/python-rtmidi/blob/77f9bc887ddaaa5e5d45249aba8f974da4dfa7dd/src/_rtmidi.pyx#L924).

It might be a good idea to find a way to send the actual timestamp so that apps could use it

Search songs by playing chords

Use a watchdog (supervisor?) to make sure the input and settings processes are always running

• Make animation pretty
• Fix logic to stay with detection if notes change (from C E G to C G - still show CM)
• By default, convert all major chords (remove notation - CM to C)
• Animate chord by velocity and pitch
• Export chord detection as functionality (maybe move to reducers)

Allow configuring DB, listening IPs and ports and so forth when installing

Support building as a Dockerfile (or a docker-compose composition)

Let users play the piano in order to navigate through the app

• Prettify (better CSS)

Support routing and use URL to recover state (react-router-dom or similar)

backend sends sequence id, frontend checks if message is lost any acts accordingly (reset currentlyPlayed and lastEvent)

architecture, microservices status and basic info about adding new features

Allow developers to work with the same settings DB to store & retrieve data
(check out mongo with Eve)

actually tricky to implement without polling, see thestk/rtmidi#191

No need to have consts (in input/midi.py and in the recorder app)
Understand how to deduce those consts automatically

at least to all core functions

• Convert to SVG animations
• Show note name (optionally) near animation

support nginx or other backend to allow full parallelism of HTTP requests

Support pip install midiate

All functionality that isn't core - gadgets, apps, non-essential utilities - should be separated to external npms

send events like "MIDI disconnected", support querying MIDI list from frontend and changing input type

Optimize frontend, use PureComponents when possible and avoid re-running effects/callbacks unless necessary.

Goal is to run smoothly on mobile devices

support per-app settings and global settings as part of the API

• session settings - per-refresh state, with redux, supports getAppSettings(appName, setting) as selectos
• local settings - persistent settings with json or DB

There's a lot of code in the README.md but not a single screenshot of what the final result looks like, despite that presumably being the main selling point =D

I can highly recommend putting at least one (but possible more) screenshot of the final app high up in the README so that folks understand what the cool thing is they can make without having to set up a dev environment first =)

https://cs.nju.edu.cn/sufeng/data/musicmood.htm