Extend JUMP FX function - Printable Version +- XOR Userforum (https://xor-electronics.com/forum) +-- Forum: Products (https://xor-electronics.com/forum/forumdisplay.php?fid=3) +--- Forum: NerdSEQ (https://xor-electronics.com/forum/forumdisplay.php?fid=6) +---- Forum: Feature requests (https://xor-electronics.com/forum/forumdisplay.php?fid=12) +---- Thread: Extend JUMP FX function (/showthread.php?tid=969) |
Extend JUMP FX function - mgd - 01-18-2021 Hi Forum, I'd like to see a JUMP command that is executed a set number of times. I could also see use for JUMP conditional on one of the CV inputs, i.e. CV above/equal/below a certain value/note. Kind regards, Michael RE: Extend JUMP FX function - XORadmin - 01-18-2021 If you have a good Idea about how to implement that into the current commands (within the digits of the FX), that would be nice. If I add something it has to fit into the current workflow without any extra special setting for functions. So a special CV function for one FX is not really something I would add. You could route a probability from the automators to a FX and the source could be a CV input. Then you could set a high/full probability or zero to get a 'execute' or mostly don't execute condition. RE: Extend JUMP FX function - mgd - 01-19-2021 Hi Thomas, I've thought a bit and the requirement to stay within the existing command framework kind of defies "proper" interface design, but here I go: As suggested by you PRF1/2/3/4 shall be used to provide an additional parameter. BRK 2xx jumps n times to row/position xx in the same pattern (forward and backwards). n is provided by PRFx. I don't know wether allowing for more than 100 rounds is required (read: I think 100 repetitions is enough). BRK 3xx/4xx/5xx/6xx conditionally jumps to row/position xx in the same pattern (forward and backwards). The condition is TRUE when CV In 1/2/3/4 is "high" (I don't think that comparing CV In 1/2/3/4 against a specific value provided by PRFx would be more useful - others may differ). I'm not convinced the above provides for a clean interface, but w/o adding new mnemonics that seems to be the best I could come up with. Kind regards, Michael |