Some slider functions still need better labels (eg function generator wave type).

FLstudio

Really hard to reproduce.

Also sometimes solid hits don't remove themselves.

-Zach

You should be able to reload midi devices & output devices without restarting the program.

Sometimes things get unplugged...

Switch from float to typedef long mbeat_t.

This will probably introduce a few bugs.

and make sure they are working properly

• Be able to specify number of bins

Audio input from jack instead of pulseaudio. Then beat-off can be run without wires!

Turns out the python scripts we were using to debug was actually responsible for configuring the serial port correctly.

Setting the baudrate to 3mbps in C is hard...

Patterns can derive colors from a palette (ie a colormap: rainbow, "blues", "oranges", "matlab jet" etc)

• Global palette, or per-pattern?
• Sub-palettes, eg for a strobe which can vary from black/color/white.

./configure && make && sudo make install

automake/autoconf/libtool?

The current skin is designed for 1368x764 displays.

Now I have a shiny 1920x1080 monitor and it's tiny! Also it'd be cool to support tinier screens.

We at some point discussed having a layout-generating python script -- maybe we should look into that?

eom :(

Merge patterns & hits; patterns can take events in.

Audio pane needs a better way of controlling/viewing BPM.
Manual adjust bpm buttons, switch between manual/auto, etc.

• radial pulse/wave

• How are keyboard shortcuts configured?
• What kinds of behavior can be controlled from the keyboard?
• Chording? Modality?

drag vertices on the master pane

and make sure it works with lots of strips

Suggested fix: memcpy state in UI thread so that it stays consistent for the frame

"hitting" the strobe should stay on for a constant period of time, not wait for the "off" event.

instead of just mathematical parameters

The vamp beat detection plugin seems to work great but our PLL doesn't seem to be stable?

Both as a pattern and as a signal

Run patterns from a file without the UI.

Can be used to implement #25 without backend changes

Should have:

• Size (seconds in the past)
• Quantile (min, q1, median, q3, max)