Author |
Message |
jamos
Joined: Jun 01, 2004 Posts: 514 Location: Eugene, Oregon, USA
Audio files: 4
G2 patch files: 41
|
|
Back to top
|
|
|
varice
Joined: Dec 29, 2004 Posts: 961 Location: Northeastern shore of Toledo Bend
Audio files: 29
G2 patch files: 54
|
Posted: Mon Jan 03, 2005 10:29 pm Post subject:
|
|
|
I changed the 3 ClkDiv module modes from "Gated Mode" to "Toggled Mode" and that seemed to fix the problem. Not sure why the way you have it patched does not work. _________________ varice |
|
Back to top
|
|
|
jamos
Joined: Jun 01, 2004 Posts: 514 Location: Eugene, Oregon, USA
Audio files: 4
G2 patch files: 41
|
Posted: Mon Jan 03, 2005 10:42 pm Post subject:
|
|
|
Thanks, that did indeed do the trick. |
|
Back to top
|
|
|
varice
Joined: Dec 29, 2004 Posts: 961 Location: Northeastern shore of Toledo Bend
Audio files: 29
G2 patch files: 54
|
Posted: Wed Jan 05, 2005 1:15 am Post subject:
|
|
|
jamos,
I traced the problem to an issue with the calculation order of the first and last sequencer modules. The last seq module needs to be calculated before the first. See page 122 of the G2 manual for more about the calculation order of modules. This serial sequence module scheme is actually a feedback loop which confuses the system into not being able to determine which module needs to be calculated first.
At first I thought that the problem with your patch had something to do with the fact that you had placed clock divider modules between the clock generator and seq modules, but I checked and found that the problem you descibe exists with a serial seq setup just like the example in the manual.
My testing shows that if the clock is stopped while the seq position is in the last module (with an exception explained below), when the clock is restarted, the first step of the first seq module will take 2 clock pulses before advancing to step 2 on the third clock pulse. Of course, the seq should advance to step 2 on the second clock pulse. Now the seq will be behind by one step. If you have an event trigger set on the first step (like your patch), the seq trigger output will send 2 triggers at step 1 before the seq advances to step 2 (that causes the double trigger of the drums in your patch at step 1).
The exception: If you happen to stop the clock at the very last step of the last seq module, the restart problem will not occur.
Solutions to the problem:
1. In the Editor, move the last seq module(s) either to the left of or above the first seq module to force the last seq module(s) to be calculated first. But this looks mighty damn ugly!
2. Add a Logic Delay module between the ClkGen clock pulse output and the seq modules clock inputs, set the delay to the shortest time (0.10ms). After a clock restart, this clock pulse delay allows the first seq module to read both the Reset and Loop inputs before the first clock pulse arrives. (See the online help about the seq modules common parameters for more info about these inputs).
I'm still not sure why changing the mode of the ClkDiv modules seemed to fix the problem in your patch. Maybe this mode takes an extra calculation cycle or two? _________________ varice |
|
Back to top
|
|
|
blue hell
Site Admin
Joined: Apr 03, 2004 Posts: 24079 Location: The Netherlands, Enschede
Audio files: 278
G2 patch files: 320
|
|
Back to top
|
|
|
|