ut-proj / undermidi Goto Github PK

This will use the new gen_server provided by the 'erlcmd-server' project.

Depends on:

• lfeutre/erlcmd-server#1

Perform the same basic operations as done in the scales module, where note patterns/templates are given a key, converted to MIDI pitches, etc.

Depends on:

• ut-proj/undertheory#2
• #29

Right now, when you play a series of notes with timings (timer:sleep) you block; it would be better to have this play in a spawned process ... that's going to take some work, though .. there's a good chance that #14 could solve this.

After looking at photos of Småland this morning, I became inspired and an explicit design for this long-standing wishlist item finally solidified in the old brain pan:

Infrastructure tasks:

• #20
• #21
• #22

Features:

• #23
• #24
• #25
• #26
• #27
• #28

Note that stopping playback on the beatracker and then resuming play will cause everything to be played over again, exactly as originally entered.

This design will be the long-sought union / convergence of live play (a la Extempore, SuperCollider, Overtone) and composition (choose your DAW or music notation software) ... essentially providing a very real REPL for musical composition and live-play/playback.

Tasks:

• Figure out how to get values of 30-300 BPM from MIDI CC to VCV Rack clocks
• Write an LFE function that maps desired BPM value to the appropriate combination of MIDI CC values (see table and screenshot below, in the comments)
• Add API support for setting the BPM
• Remove all code that dynamically calculates the BPM

Part of #42

Musical phrases will be stored in the state gen_server for beatracker.

Blocks:

• #26

Part of:

• #19

Related:

• ut-proj/midiserver#3

Part of:

• #19

I don't immediately see why, though. I think I have all dependencies.

➜  undermidi git:(release/0.2.x) make build
>> Building Go examples ...
make[1]: Entering directory '/home/afa/Erlang/plekto/undermidi/priv/go/src/github.com/ut-proj/midiserver'
>> Building bin/midiserver ...
# github.com/ut-proj/midiserver/internal/util
internal/util/signals.go:17:9: undefined: signal.NotifyContext
make[1]: *** [Makefile:43: bin/midiserver] Error 2
make[1]: Leaving directory '/home/afa/Erlang/plekto/undermidi/priv/go/src/github.com/ut-proj/midiserver'
make: *** [Makefile:70: build-go] Error 2

I.e,. transposing the MIDI conversion of the scales. This might simply entail adding another arity for um.scale:midi ...

I suspect this broke when the message formatting for batches changed.

Also, the example on the Go side is going to change, so we should update the LFE side to match:

Depends on:

• ut-proj/midiserver#19

Tasks:

• Review undertone's use of Extempore's portmidi driver
• Review all demo & music code produced to date that uses Extempore's MIDI directly
• Record those here as dev tasks to implement
• NoteOn
• NoteOff
• CC
• Convert between system MIDI data and midilib MIDI messages (may already be done? may need updating?)

Depends on:

• ut-proj/midiserver#2

Blocks:

• ut-proj/undertone#113

Tasks:

• Add function that exports term data for a song to tmp dir/file
• Add function that exports all term data (for all songs) to tmp dir/file

Users shouldn't need to have Go installed in order to use the midiserver

Tasks:

• ut-proj/midiserver#7
• Add Go bin directory in priv
• Add target to download correct binary
• Update LFE code to build correct binary name
• Update docs on how to build midiserver from source and how to run it from pre-compiled binaries
• Testing
  • macos amd64 bin
  • macos arm bin
  • linux amd64 bin
  • linux arm bin
  • macos go src
  • linux go src

Right now, um:scales performs a lookup in the undertheory scales module. We should let users provide their own sequence of notes (in the form of, e.g., (1 3 |#4| 5 b7), etc.). To do things, we'll need to readjust some things and create some new functions:

• rename midi to pitches
• rename get to create
• add a guard to pitches
  • if scale is an atom, convert
  • if scale is a list, don't do a lookup
• update create to use new pitches

This need has arisen as a result of investigating implementation ideas for #16 -- chords are much more varied than scales and definitions are not consistent, so users will need to provide their own notes/forms even more there, than here with scales.

That being said, the majority of the logic will be shared between the two. So this change should take that info consideration:

• what functionality will be shared?
• move that out of um:scales and into um (or wherever else makes sense)
• adjust um:scales as necessary

These will be live-play musical phrases, sequences, etc.

Blocks:

• #25
• #26

Part of:

• #19

Blocks:

• #23

Part of:

• #19

Part of epic:

• #38

Tasks:

• Allow changes to time signature while running
• Change single start/stop data to a list of starts/stops
  • update the map for tracks to remove started_at and stopped_at
  • add new key transport that's an empty list by default
  • every call to start-track and stop-track will append to the transport field, e.g., #(stop ,now))
• #46
• Receive start/stop messages from midiserver
  • ut-proj/midiserver#29
  • update transport with timestamps when start/stop msgs received from midiserver
• Support callbacks based upon changes in timeclock data (e.g., sending MIDI messages, leaving room/time for message transmission -- should be delivered before the target beat, but after the beat prior to the target beat), e.g. at:
  • a given beat by absolute count
  • a given beat for a given measure
  • next beat
  • next nth beat of the next measure
  • next nth beat of the next nth measure

By index or name.

Part of:

• #19

Depends on:

• erlsci/midilib#4
• ut-proj/midiserver#21

Useful info from KORG MIDI implementation documentation:

Update README with example usage.

Depends on:

• #5

Features:

• add initial infra (project layout, README, CI/CD)
• Create OTP app w/supervision tree
• Create a MIDI Erlang Port server in Go:
  • work for this is being tracked here: ut-proj/midiserver#1
• Create an Erlang Port that can send and receive messages with the above MIDI server
• Update README

Depends on:

• ut-proj/midiserver#1

Blocks:

• #3

Resources:

• https://gitlab.com/gomidi/midi
• https://gitlab.com/gomidi/midi/-/blob/master/examples/liverecord/main.go

• Configurable MIDI device index
• Configurable MIDI channel

Depends on:

• ut-proj/midiserver#6

Options:

1. add a parallel function + macro
2. make batch parallel, and add a serial function + macro

Depends upon:

• erlsci/midilib#1
• ut-proj/midiserver#10

Tasks:

• Add the new midilib RC as a dep
• Update/add term_to_binary encoders for nested tuples/lists
• Expose MIDI-sending gen_server function
• Test once Go midiserver supports these messages

Depends on:

• #21

Part of:

• #19

• Arturia
• Luna
• Moog

In order to stop them at will, they'll need to be run by a controller / executor / supervision tree. Probably spawning dynamic children is all that's needed.

• Update the supervision tree to support spawning children dynamically
• Create a cyclic cc function for MIDI control
• Add wrapper for stopping the cycles by killing the child process

Depends on:

• ut-proj/undertheory#3

• play chord
• play note
• send CC
• ramp CC
• cycle CC (just one -- for infinite cycling, see #14)
• sustain pedal on/off
• soft pedal on/off

All messages in a give batch should get the same id. This will require a change to how messages are batched.

These should duplicate playback of the entire session, as entered.

Part of:

• #19

See:

• ut-proj/undertheory#15

The listing will display:

• index number
• name (if set)
• current state: playing, paused
• start beat (absolute)
• repeated? (boolean)
• end beat
• beat length

Depends on:

• #20
• #22
• #25

Part of:

• #19

Notes:

• phrases will be stored in the state gen_server for beatracker
• the timer gen_server for beatracker needs to be independent of musical phrases

Depends on:

• #22

Blocks:

• #26

Part of:

• #19

Features / Tasks

• Investigate interop to determine if any new MIDI CC messages need to be supported
• Experiment with existing MIDI CC support to see if any VCV Rack-specific convenience functions / macros are warranted
• Add the ability to send realtime messages to the Go midiserver (and thus to VCV Rack)
• ut-proj/midiserver#26
• #41
• #42

Resourrces

VCV is a free, open source modular synthesis framework (Eurorack emulator):

• https://vcvrack.com/
• https://vcvrack.com/manual/
• https://library.vcvrack.com/
• http://www.studiobrootle.com/best-vcv-rack-modules/

Specific support: MIDI control of the synth. See the MIDI plugins for more details:

• https://library.vcvrack.com/?query=&brand=VCV&tag=MIDI&license=free

Original issue created here:

• ut-proj/undertone#65

This gen_server will be in charge of:

• updating state according to an external clock source
• a remote-callable API for setting and getting data related to an external clock source

Tasks:

• Test eprc calls from LFE REPL (separate, non-undermidi node)
• ut-proj/midiserver#26
• Create new gen_server in undermidi/clock/ext.lfe for tracking clock ticks
  • Implement basic gen_server functions
  • add state for tracking clock counter and last-n times (timestamps for when ticks received
  • add functions for incrementing clock tick, total ticks
  • keep a queue of last N tickets and ensure that times for each tick are recorded
  • use times to calculate BPM (most recent, last-n, and for total queue size ... the last being useful for curve-fitting calculated BPM polynomial adjustment on different hardware)
• Create new gen_server in undermidi/clock/ext/beats.lfe for song-specific features built on the clock tick gen_server's data
  • Implement basic gen_server functions
  • add ETS-based state-tracking for song name, start timestamp, time signature, stop timestamp
  • add functions for returning song name, start timestamp, time signature, current BPM (aliased to other gen_server function)
  • add functions for starting and stopping a song
  • add function for calculating current measure
• Add new gen_servers to the supervisor

Follow-on work:

• #42
• #44

Resources:

• https://www.erlang.org/doc/man/erpc.html
• https://github.com/erlang/otp/blob/340aefb5cdd7aa73a3b9daa1781037334d8c7341/lib/kernel/src/rpc.erl
• https://github.com/erlang/otp/blob/340aefb5cdd7aa73a3b9daa1781037334d8c7341/lib/kernel/src/erpc.erl