[clef-development] question about osc-lanes

[Schumacher M. <mar...@mu...>]

Hey,

Just some announcements to get (perhaps) some feedback. We implemented a number of osc-lanes (for automation) on the "osc-lane"-branch. There are currently 3 different ones (implementing different logics for user interaction):

1) clef.osc-lane.absolute.wgt

That's the original and most "classic" or "generic" version, similar to automation tracks found in DAWs. 
 -> function-values (i.e. points) aren't changed unless "edited" explicitly by the user)

• the event-duration changes the domain (i.e. what is displayed in the function)
• x-min and x-max have no immediate effect but set the boundaries for normalization
• y-min and y-max change the domain (the displayed range) and set values for normalization.

-> probably slowest to work with but most flexible.

2) clef.osc-lane.absolute-2.wgt

This is a similar version to absolute.wgt albeit with a few shortcuts to facilitate user-interaction.
 -> function-values (i.e. points) are auto-normalized by dragging x-min/max and y-min/max

• the event-duration changes the domain (i.e. what is displayed in the function)
• x-min and x-max normalize immediately
• y-min and y-max normalize and setdomain

-> faster to work with but less flexible as for the y values it is impossible to extend (increase the y-distance) between the points (since the y-min and y-max normalization also sets the domain the display is always 'maxed out'). I.e. one cannot individually set the displayed range and the range of points.

3) clef.osc-lane.relative.wgt

This is a version taking a few shortcuts to facilitate user-interaction.
  -> function-values get edited destructively by changing event-duration

• the event-duration sets the domain (i.e. auto-rescales the function)
• x-min and x-max have no immediate effect but set the boundaries for normalization
• y-min and y-max change the domain (the displayed range) and set values for normalization.

This distinction/implemented functionality doesn't seem to make quite sense to me yet. The 2 latter ones seem to be kind of hybrids (in terms of 'logics'), ideally there should be only 2 complementary ones: clef.osc-lane.absolute.wgt and clef.osc-lane.relative.wgt). I think the issue is that one cannot auto-rescale while at the same time being able to extend the domain (i.e. what is displayed). The latter one demands an extra control for 'normalize-y'. Perhaps then the clef.osc-lane.relative.wgt makes sense. But then again, it could also make sense to have the distinction between one that sets the display and doesn't change immediately (absolute), and another one the changes the values immediately.

PS You can have a look/compare them in /Library/Events/osc-lane/osc-lane-test.maxpat

Marlon