Doepfer Maq 16/3

Volgens mij moet je een tweede rij slachtofferen om er eentje met verschillende lengtes in te stellen maar ik heb hem nu niet bij me. Ik vond dit wel...

Remark (8): Step-Duration (Time)

The step-duration is not directly linked with a MIDI-event. It merely provides the duration for the step in question. If step-duration is assigned to a row it can refer to one row, two rows or all three rows. The indication is provided by the three decimal points of the display.

If, for example, "t.4. ." is entered for the bottom row (Row 3) it means that the settings entered on the dials of row 3 are valid for all three rows. "t 4. ." would indicate validity only for the two bottom rows. In order for the user to be able to control the step-duration on the bottom row, it must also refer to that row (i.e. the third decimal point on the display must be illuminated in our example). Otherwise the time-row will run in constant steps and will pass the step-duration values only to the other row(s) activated.

There are four possible scaling factors for the dials: Base time x 4, x 8, x 16, x 32. The base time results from the (internal or external) MIDI-clock. The step-duration can only be increased in whole multiples of the base time. The digits 4, 8, 16 and 32 refer to the maximum scaling factor (with respect to the clock) which can be reached if a control dial is turned all the way up.

If only small time differences between steps are desired "t4" should be selected, for larger differences one should select "t 8", "t16" or "t32". If a dial in the step-duration-row is turned all the way to the left, then the step in question will be omitted, i.e. this serves as SKIP-function.

The timing of each row is also influenced by an adjustable prescale factor (Menu 4: PRESCALE/TIME). If the step-duration function is assigned to a row the prescale factors entered in Menu 4 are in effect as well. Very complex timing arrangements can thus be programmed, although these will always within the framework of the MIDI-clock.

In principle the step-duration can be controlled with any one of the three rows of dials. However, for technical reasons we recommend that only the bottom row is used for this purpose, since the software has been optimized for this.

We would like to emphasize one more time at this point that not every arrangement possible is also sensible. One could of course assign step-duration or velocity to all three rows, but this would certainly make no sense ! Nonetheless, we deliberately decided not to outright exclude certain configurations, in order to avoid limiting the potential of the MAQ from the start. Since this allows for the possibility of nonsensical configurations, we urge all users to make sure that the configurations programmed do make sense. Otherwise there is a potential for uncontrolled reactions and side effects.

For example, if a velocity-row is combined with an monophonic aftertouch-row, then the velocity-value entered via the dials will overwrite the aftertouch-values!

Good luck!
 
Dat is geloof ik niet wat ik bedoel.

Degene waar ik nu mee zit te freaken met de maq... Zegt dat ik het anders moet formuleren omdat het we in stepseq land zitten..
Het gaat om de gate time per step..




Volgens mij moet je een tweede rij slachtofferen om er eentje met verschillende lengtes in te stellen maar ik heb hem nu niet bij me. Ik vond dit wel...

Remark (8): Step-Duration (Time)

The step-duration is not directly linked with a MIDI-event. It merely provides the duration for the step in question. If step-duration is assigned to a row it can refer to one row, two rows or all three rows. The indication is provided by the three decimal points of the display.

If, for example, "t.4. ." is entered for the bottom row (Row 3) it means that the settings entered on the dials of row 3 are valid for all three rows. "t 4. ." would indicate validity only for the two bottom rows. In order for the user to be able to control the step-duration on the bottom row, it must also refer to that row (i.e. the third decimal point on the display must be illuminated in our example). Otherwise the time-row will run in constant steps and will pass the step-duration values only to the other row(s) activated.

There are four possible scaling factors for the dials: Base time x 4, x 8, x 16, x 32. The base time results from the (internal or external) MIDI-clock. The step-duration can only be increased in whole multiples of the base time. The digits 4, 8, 16 and 32 refer to the maximum scaling factor (with respect to the clock) which can be reached if a control dial is turned all the way up.

If only small time differences between steps are desired "t4" should be selected, for larger differences one should select "t 8", "t16" or "t32". If a dial in the step-duration-row is turned all the way to the left, then the step in question will be omitted, i.e. this serves as SKIP-function.

The timing of each row is also influenced by an adjustable prescale factor (Menu 4: PRESCALE/TIME). If the step-duration function is assigned to a row the prescale factors entered in Menu 4 are in effect as well. Very complex timing arrangements can thus be programmed, although these will always within the framework of the MIDI-clock.

In principle the step-duration can be controlled with any one of the three rows of dials. However, for technical reasons we recommend that only the bottom row is used for this purpose, since the software has been optimized for this.

We would like to emphasize one more time at this point that not every arrangement possible is also sensible. One could of course assign step-duration or velocity to all three rows, but this would certainly make no sense ! Nonetheless, we deliberately decided not to outright exclude certain configurations, in order to avoid limiting the potential of the MAQ from the start. Since this allows for the possibility of nonsensical configurations, we urge all users to make sure that the configurations programmed do make sense. Otherwise there is a potential for uncontrolled reactions and side effects.

For example, if a velocity-row is combined with an monophonic aftertouch-row, then the velocity-value entered via the dials will overwrite the aftertouch-values!

Good luck!
 
Back
Top