Hi! I'm not sure how to update the manual via Github but wanted to say I think I found a bad example in the description for XMAP on page 38.
In the description, it recommends using the command SKIP 1 < =0=0 to always skip the next line. But actually, since 0 is never less than 0 the result would be FALSE, so it would not skip the next line.
I recommend maybe changing it to SKIP 1 = =0=0, so the constant is always TRUE
Below is how it's written currently in the manual.
• XMAP → Execute a Mapping row from the → Mapping Screen. The selected
Mapping row will be executed once. This can be used to set a variable or to start an algorithm from the mappings. You can avoid that the row won’t be executed from the mappings itself by adding a SKIP 1 < =0=0 command in the mapping row before which takes care that the next row will never executed ( SKIP 1 ROW if the constant 0 (=0) is smaller (<) than constant 0 (=0)). Since 0 is never smaller than 0 the next row will always be skipped and thus never been executed from the mappings itself. It can be executed using XMAP though. This could also allow to create a sequence only by XMAP rows which are going to be executed by the sequencer. Please check the → Mapping Screen for more information. Be aware that the selected row will be completely executed, regardless if the source changed or not.
(09-21-2024, 05:19 PM)theb_roll Wrote: [ -> ]Hi! I'm not sure how to update the manual via Github but wanted to say I think I found a bad example in the description for XMAP on page 38.
In the description, it recommends using the command SKIP 1 < =0=0 to always skip the next line. But actually, since 0 is never less than 0 the result would be FALSE, so it would not skip the next line.
I recommend maybe changing it to SKIP 1 = =0=0, so the constant is always TRUE
Below is how it's written currently in the manual.
• XMAP → Execute a Mapping row from the → Mapping Screen. The selected
Mapping row will be executed once. This can be used to set a variable or to start an algorithm from the mappings. You can avoid that the row won’t be executed from the mappings itself by adding a SKIP 1 < =0=0 command in the mapping row before which takes care that the next row will never executed ( SKIP 1 ROW if the constant 0 (=0) is smaller (<) than constant 0 (=0)). Since 0 is never smaller than 0 the next row will always be skipped and thus never been executed from the mappings itself. It can be executed using XMAP though. This could also allow to create a sequence only by XMAP rows which are going to be executed by the sequencer. Please check the → Mapping Screen for more information. Be aware that the selected row will be completely executed, regardless if the source changed or not.
Will change that in the manual, thanks.
