Reset on start?

[mosorensen]

I have a quick question about reset on start. 

The Reset Out on NerdSeq fires a trigger when the NerdSeq stops. But, for some of my modules, I also need a reset trigger on start (In addition to the Reset Out; different modules reset in different ways).  

A natural starting point is to just put a tigger in the first entry in a pattern (I have a Trigger Expander, if that makes a difference). But, then the trigger fires every time the pattern restarts, and I don't want that. I only want the trigger the very first time the pattern plays and then it should stay off afterwards. I imagine there is some clever combination of FXs and/or Tables that does this, and I am hoping that some of you smart people have already figured out how to do this.

[mgd]

A workaround could look like this:
Copy (i.e. clone) the first row of you song somewhere else (e.g. move everything 2 rows down copy into the first row or create the copy after the last row of your song). Make sure the copied row forms an island. Insert at the end of one of the pattern involved an FX STSP (Start Sequencer Pattern) 0XX with XX being the row number of the second row of your pattern (because the first row of pattern has already been performed once).

Note this only works when all pattern involved have the same length. If not special care and possibly more complex measures have to be considered.

If the above is not understandable drop me a note and I'll try to elaborate a bit more.

HTH,
Michael

[mosorensen]

I found an easier work around that works well enough for now.

In the first two rows of FX column 1, I put
TRIG 040
PRF1 001

This fires a trigger and then sets the probability that the trigger fires again to 1%, which is close enough (for some reason PFR1 000 does not set the probability to 0%).

[XORadmin]

I found an easier work around that works well enough for now.

In the first two rows of FX column 1, I put
TRIG 040
PRF1 001

This fires a trigger and then sets the probability that the trigger fires again to 1%, which is close enough (for some reason PFR1 000 does not set the probability to 0%).

The coming release does also allow probabilities of 0%.

Reset on start optionally is on my 2do list

[mosorensen]

I found an easier work around that works well enough for now.

In the first two rows of FX column 1, I put
TRIG 040
PRF1 001

This fires a trigger and then sets the probability that the trigger fires again to 1%, which is close enough (for some reason PFR1 000 does not set the probability to 0%).

The coming release does also allow probabilities of 0%.

Reset on start optionally is on my 2do list

That sounds terrific. I am pretty much checking every day for updates about the coming release.

[XORadmin]

I found an easier work around that works well enough for now.

In the first two rows of FX column 1, I put
TRIG 040
PRF1 001

This fires a trigger and then sets the probability that the trigger fires again to 1%, which is close enough (for some reason PFR1 000 does not set the probability to 0%).

The coming release does also allow probabilities of 0%.

Reset on start optionally is on my 2do list

That sounds terrific. I am pretty much checking every day for updates about the coming release.

You can already try it out since some time. Only some little things to do...

https://forum.xor.eu/showthread.php?tid=1348

[mgd]

I found an easier work around that works well enough for now.

In the first two rows of FX column 1, I put
TRIG 040
PRF1 001

This fires a trigger and then sets the probability that the trigger fires again to 1%, which is close enough (for some reason PFR1 000 does not set the probability to 0%).

That's a neat trick. The only disadvantage is that you can't use FX1 for anything else. Not a problem unless you use lots of FX ...

[zacheria44]

Hi everyone, was wondering if this feature has been added yet to V1.27 on if it is still in the works. If it has which page of the manual would I be able to find it on as I have not been able to in my own searching. Thank you!

[XORadmin]

Hi everyone, was wondering if this feature has been added yet to V1.27 on if it is still in the works. If it has which page of the manual would I be able to find it on as I have not been able to in my own searching. Thank you!

Not implemented yet