As the brush dynamics editor only supports inputs from 0 to 1 and outputs from 0 to 1, it seems like it could be a good idea to support mapping inputs and outputs based on user preferences.

Inputs that could use mapping:

Velocity - I may consider 10 pix/sec slow (0) and 100 pix/sec fast (1) while someone else may consider 50 pix/sec slow and 500 pix/sec fast.

Pressure - While a tablet may support many levels of pressure, a user may not be accustomed to pressing a certain force to get a desired result, and may wish that pressure level 300 (instead of 511) be treated as the maximum pressure (1). Similarly a user may not be good at being very light on the tablet and may prefer a pressure level of 30 to be treated as the minimum pressure (0).

Tilt - A user may prefer a certain tilt range to map from. One user may prefer only slight tilts to get the full range (0-1) while another user may be fine with larger tilts.

Inputs that mapping does not make sense:

Direction (0-1 = 0-360 deg) Random

Input mapping should probably be configured in user preferences.

Similarly it may be useful for each target's outputs. For instance specifying the 0/1 size of a brush as a percentage of the brush size or opacity as a percentage of the current brush opacity.

Brian Allen Vanderburg II

On 09/15/2011 03:15 AM, Alexia Death wrote:

Inputs that mapping does not make sense:

Direction (0-1 = 0-360 deg) Random

Doesn't make sense how? Look at GPS. Random is made rather good use of in some presets and direction has its uses as well.

What I mean is it doesn't make sense for the direction to have any other mapping than from 0 to 360 degrees of the stroke to become 0 to 1 of the direction dynamics input.

All the input mapping idea is for is to map the physical input from the device or mouse to the dynamics input in a way that is natural for the user. It is not meant to do anything more exotic, all that can be done in the dynamics themselves. You've mentioned that something like this is already there for the tablet axis in the form of curves under settings. So a user can already use these to map how input from the device would become input for the dynamics, what pressure or tilt range is natural for them. (I don't own a tablet yet so I wasn't previously aware these are already there.)

Since these settings are already there, then my idea is reduced simply to having velocity dynamic configured as well so two different users with different ideas of what is slow and fast could still have their idea of slow mapped as 0 and their idea of fast mapped as 1 for the velocity dynamic, even if just using a mouse.