OpenDeck platform

**paradajz** · 12-26-2014, 07:02 AM

Here are the planned features for version 2.0 of OpenDeck platform:

1) Program change support for buttons
3) Local LED control (configure LEDs to react on button presses instead of MIDI In)
4) SysEx protocol refinements
5) Some performance improvements

...and few more features probably. If anyone has some suggestions, I'd really like to hear them. I'm planning on making OpenDeck most powerful MIDI platform around!

**paradajz** · 01-22-2015, 06:16 PM

Just finished circuit for OpenDeck v2:

1) Support for 64 buttons / 32 encoders
2) Support for 48 regular LEDs / 16 RGB LEDs
3) 32 analogue inputs
4) DIN MIDI in/out
5) USB MIDI

**paradajz** · 05-12-2015, 04:35 AM

Originally Posted by nem0nic

For encoders, it would be useful to have settings for sensitivity, acceleration, and message type. Sensitivity would act as a multiplier or divider for the number of "ticks" in the natural resolution of the encoder (25 pulses per revolution for example). This could be used to not only help address "slow" pots, but also to slow down higher resolution pots (8 bit or higher). Acceleration would act similarly to sensitivity, except it would ramp resolution up based on how quickly the pot is being twisted. This would allow the encoder to have fine control over a parameter but allow for more radical value changes. Message type would allow the user to select what KIND of relative message is being sent from the encoder (binary offset, 2s comp, etc). Sometimes one is more suited to the task than another, and allowing the host software to set those values would be useful.

I guess you'll be happy to know I implemented bold parts, only acceleration is left. Also, I ordered few FSR sensors, so support for that is coming soon as well.

I also made significant performance improvements to software, as nearly everything is interrupt-driven right now, so software only does something when data is available, instead of constantly polling.

The big news is that since recently, Chrome beta supports WebMIDI!
http://blog.chromium.org/2015/04/chr...upgrading.html

What this means that I can abandon plans to build separate apps for Linux, Mac and Windows, and simply run configuration utility inside Chrome. How awesome is that?

**tekki** · 05-12-2015, 10:56 AM

Sounds awesome!

**paradajz** · 08-14-2015, 03:20 PM

Originally Posted by nem0nic

For buttons or knobs, it would be great to allow the control output message to also set a state in the controller. So a button might send 90 21 7F, but it might also send F0 00 53 43 01 00 42 00 13 01 F7 (to change the mode of button 19). Ideally it would be possible to send multiple commands of this type - allowing the user to reconfigure the controller on the fly. To take that idea even further, it would be AMAZING to allow incoming MIDI messages to trigger a similar stack of SYSEX strings. At that point, the host application could drive controller configuration based on any number of conditions (what view is selected, what effect is loaded, etc).

I am implementing this feature next.

New board coming soon as well.

Edit (2015-12-31): This feature will come in some later version of platform.

**paradajz** · 08-28-2015, 07:29 PM

First post is now updated with more relevant information, implemented features and list of upcoming stuff. Feedback needed!

**paradajz** · 09-02-2015, 10:23 AM

With this latest commit, I've added support for different encoding modes for encoders. For now, 7Fh/01h and 3Fh/41h modes are supported. Are there any other encoding modes? If anyone knows for some other configuration, please let me know so that I can add support for that as well.