For 1 event:
The length of an event (=L) should determine the 'range' of the A & D parameter (H should be automatically inferred from the other parameters): H=L-(A+D)
We should only be able to modify the A & D parameters (also the L parameter by stretching or pitching)
In this case, if we have an event of L=100ms, we won't be able to set the A parameter to 2000ms because (A+D)+H=L
For several events (<=> Absolute and Relative in order to modify A & D parameters for several events):
(We are now beginning to get into serious trouble
)We should only be able to say if we want the parameter to be Absolute or Relative (not to specify the 'length')
The Absolute value should automatically be initialized with the length of the longest event on the track.
For example, let's say we have 2 events on the same track: E1=100ms; E2=500ms
We'll take as example the Attack parameter (should be the same for the D parameter):
If we 'lock A' in order to modify this parameter for E1 & E2 at the same time
Absolute would automatically be set to MaxLength(E1;E2)=500ms
If the 'A slider' is at the 1/5 of the events, we should have for the A value:
- for E1: Absolute/5=100ms
- for E2: Absolute/5=100ms
If the 'A slider' is at the middle of each event, we would have for the A value:
- for E1: Absolute/2=250ms --> but limited to 100ms because MaxLength(E1)=100ms
- for E2: Absolute/2=250ms
The main problem with this 'solution' is if we add a third event to the track which is longer than the 2 others (E3=1000ms) it will automatically change the Absolute value from 500ms to 1000ms, hence modifying the events already present on the track…
…What a headache man
!!! I think we'd better wait for the next version and talk afterwards