[FIXED] Effects column not triggering consistently

[felixtatic]

I've been having an issue with the way the effects columns are working on my Nerdseq since i got it about a month ago. Luckily there are so many other features to sink your teeth into which have kept me occupied until now.

My issue is that Fx don't seem to be triggering consistently. Initially I felt like I was missing something and kept pushing forward trying to make it work but now i'm really not sure what's going on.

I made a test to demonsrate what's happening. (I hope it's clear in the video (colours could be chosen better i know)). Basically it seems that the effects are triggering in a inconsistent way. When i change the value of the bitcrush on row 00 it seems to work correctly for one cycle but then seems to skip the first trigger event on the next cycle and then stop working entirely.

I tried moving the break command to row 2 as suggested in a previous thread and that didn't help at all.

Am I being stupid here? What's going on? Thanks!!

[XORadmin]

Hey. I will make the same loop to see if I get the same effect. Just one thing, are you sure there is no probability turned on for this FX column?

[felixtatic]

Hey. I will make the same loop to see if I get the same effect. Just one thing, are you sure there is no probability turned on for this FX column?

Hey thanks for checking.

There's no probability at all, i haven't been able to get it to work in a sufficient way due to this issue so have avoided it so far. (Just to be sure I checked the "current values" from the "patch" button screen, all show 064 (is an audio track)).

[XORadmin]

Latest version?
Maybe you want to add the project file. It would make it faster for me to check.

[felixtatic]

Latest version?
Maybe you want to add the project file. It would make it faster for me to check.

Yea it's V1.24 RC10.

Here's the project file https://drive.google.com/file/d/18vnsLQO...sp=sharing

The example is on track 07, sequence number 38.

Thanks!

(wanted to add that i had the same issue on v1.23 too)

[XORadmin]

Ok thanks for the additional information and the project file.

I found the issue already and it is not that some things are skipped, but rather get activated on different times right after the FX (too long times). This affects only the Distortion, Bitcrush and Wavefold. It's a simple fix and I will for sure add it for the release version.

For now you probably just change the effect one step before and it will behave as you expect.

Thanks!

[felixtatic]

Ok thanks for the additional information and the project file.

I found the issue already and it is not that some things are skipped, but rather get activated on different times right after the FX (too long times). This affects only the Distortion, Bitcrush and Wavefold. It's a simple fix and I will for sure add it for the release version.

For now you probably just change the effect one step before and it will behave as you expect.

Thanks!

Okay thanks for clearing that up! I tried the method and it worked fine, so cheers!

I've noticed this issue with the row probability too. Here's the example project file again (track 7 sequence 38). link

Thanks!

[XORadmin]

Ok thanks for the additional information and the project file.

I found the issue already and it is not that some things are skipped, but rather get activated on different times right after the FX (too long times). This affects only the Distortion, Bitcrush and Wavefold. It's a simple fix and I will for sure add it for the release version.

For now you probably just change the effect one step before and it will behave as you expect.

Thanks!

Okay thanks for clearing that up! I tried the method and it worked fine, so cheers!

I've noticed this issue with the row probability too. Here's the example project file again (track 7 sequence 38). link

Thanks!

No this one works fine.
It means row probability and so the row is being executed or not. If it's not being executed then also your PROW command is being skipped.
Only the last FX is excluded from PROW,so you can be sure you get your probability back when you want to.

[ianski]

I've noticed an issue which may or may not be connected with this...

If you set a retrigger effect on the same track you are editing it will not function on that track, but it will function if you set it to effect another track.

For example, make a simple sequence on track 1 and insert some "Trigger 1" retrigger effects (I tried various values but try value 033 - Retrigger 4 x 15ms)
You will not hear any difference.

If you change the trigger to effect another track i.e. "Trigger 6" with the same values as above the retrigger works fine on that track and all others.

If I want to retrigger track 1 I have to do it from another track.

I only tested it with retrigger and MOD, and MOD worked fine but it's worth checking other effects that have the option to effect different tracks too to see if they have similar issues.

I am on the same latest firmware version.

You can recreate this easily by using a new blank pattern and following the above steps.

Thanks.

[XORadmin]

I've noticed an issue which may or may not be connected with this...

If you set a retrigger effect on the same track you are editing it will not function on that track, but it will function if you set it to effect another track.

For example, make a simple sequence on track 1 and insert some "Trigger 1" retrigger effects (I tried various values but try value 033 - Retrigger 4 x 15ms)
You will not hear any difference.

If you change the trigger to effect another track i.e. "Trigger 6" with the same values as above the retrigger works fine on that track and all others.

If I want to retrigger track 1 I have to do it from another track.

I only tested it with retrigger and MOD, and MOD worked fine but it's worth checking other effects that have the option to effect different tracks too to see if they have similar issues.

I am on the same latest firmware version.

You can recreate this easily by using a new blank pattern and following the above steps.

Thanks.

Reading your explanation I think it works well. I guess you have a trigger or in the trigger column and use also the FX for the same trigger.
The FX are executed as first and after that the trigger from the trigger column is executed and overrules this.

I am not aware of any issues there and the orders have been like this forever.