CategoryAllgemein

TesserAkt

Tesser_logo

TesserAkt

The TESSER environment is composed of a number of MaxForLive devices designed for real-time midi manipulation.

Credits

This environement is developed and mantained by Adrian Artacho.


To-Do

  • Rename the other repos called TesserAkt, including the Live sets, which do not have anything to do with the current meaning of TesserAkt now...

  • Complete documentation

  • <Tesser_function> like, making leise notes loud and the louder leise... values in/values out

About me

Welcome to my website. At the moment this is still a work in progress…

Social

Contact

Tesser_block

This Patch is part of the TESSER environment.

TTESS:Logo

Tesser_block

This device allows to block selectively different kinds of midi data.

TESS:block

Usage

The settings can be stored with the device/set. They can also be automated.

Credits

This device is a derivative patch largely taken from AbletonDrummer's object.


To-Do

  • document
  • Add feature to print in maxwindow specific kinds of cc input
  • Extended feature: block specific notes which are set using the gesture CC. This is practical, for example, if you are playing the keyboard and whant to block the area where the hands are from playing new notes, etc.

Tesser_AutoMidi

This Patch is part of the TESSER environment.

TTESS:Logo

Tesser_AutoMidi

This device is analogous to an autotune effect, only with midi. It takes midinotes and allows to substitute the entered midinote number and/or velocity with alternative CC values entered via CC86 and CC87.

TESS:automidi

View of the device. Click here) to edit.

Usage

Here is a full description of the functions associated to CC messages within the TESSER environment.

override pitch The entered pitch will be substituted by the last entered CC86 value.

override velocity The entered velocity will be substituted by the ;ast entered CC87 value.

auto AllNotesOff When this toggle is on, a note off (vel = 0) will cause a 0 123 message to be sent to all 16 midi channels.


To-Do

  • document
  • how does a gesture gets stored, and then recalled one by one in a loop? The device should accept (and store) a gesture string, possibly via CC90