Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Possibility to have effect per row
#1
Hi

It could be great to have in the setup menu or project menu an option to have the possibility to have effect per row, in order to not have to set then to reset the effect later.

eq if you put an effect like for example row probability, this effet will be available only for this row.


Thanks

Cedre

I tried to do this with putting a fx1 and then a special FX 00A (reset fx track) on fx2 on same row but it doesn't work.

An option coud be to have an fx or a special fx, like : Reset FX row
Reply
#2
Row 3 = probability on, row 4 = probability off, then you have probability for row 3.
It’s always like a knob that you set to a position and it stays until you change it again.
You really don’t want to fill plenty of fx rows with the same command.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#3
If I put Row Probabiity on row 3 at 50%
and I put Row Probabiity on row 4 at 100%

There is 50% chance that my row 4 is ignored, and so the probability of the row 3 will stay active for the next rows.
Reply
#4
(09-30-2020, 10:09 PM)Cedre Wrote: If I put Row Probabiity on row 3 at 50%
and I put Row Probabiity on row 4 at 100%

There is 50% chance that my row 4 is ignored, and so the probability of the row 3 will stay active for the next rows.

You are talking about a feature which is not in the current firmware. Indeed, row probability is a special one and if you enable it the chance is there that it doesn't get reset at the next step.

But all other probabilities can be programmed well like this. And then it is maybe the better option to use probability on one of the destinations instead of the row and you can turn them on and off from a safe FX.

And just for the practical use if you could do that:
175 patterns with each 64 rows, where in the menus do you want to set pattern 76 on row 6 to start the effect and row 7 to stop the effect...and that on many patterns on different rows? I know that is not an option.

One option i am actually thinking of while writing this is to exclude always the last FX (in a modular/cv track would be FX4 for example) from the row probability. In that case you could always turn it on or off from FX4 but leave all other parts within the probability on demand. Just an idea and i got to think about the impact.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#5
Oh sorry it is a misunderstanding, I just suggest a global parameter in the menu (EffectPerStep : true/false), not for each row.


Good idea to exclude FX4, so we can reset the row probability and it can be also creative too for other thing.
Reply
#6
(10-01-2020, 01:21 PM)XORadmin Wrote:
(09-30-2020, 10:09 PM)Cedre Wrote: If I put Row Probabiity on row 3 at 50%
and I put Row Probabiity on row 4 at 100%

There is 50% chance that my row 4 is ignored, and so the probability of the row 3 will stay active for the next rows.

You are talking about a feature which is not in the current firmware. Indeed, row probability is a special one and if you enable it the chance is there that it doesn't get reset at the next step.

But all other probabilities can be programmed well like this. And then it is maybe the better option to use probability on one of the destinations instead of the row and you can turn them on and off from a safe FX.

And just for the practical use if you could do that:
175 patterns with each 64 rows, where in the menus do you want to set pattern 76 on row 6 to start the effect and row 7 to stop the effect...and that on many patterns on different rows? I know that is not an option.

One option i am actually thinking of while writing this is to exclude always the last FX (in a modular/cv track would be FX4 for example) from the row probability. In that case you could always turn it on or off from FX4 but leave all other parts within the probability on demand. Just an idea and i got to think about the impact.

Seconding the FX4 idea mentioned here, or some other resolution. The current implementation of PROW has severe consequences if the row contains data for a rare event that contains several FX. For example, try PROW001, which can effectively mute the entire track indefinitely (including break points). 

PROW is certainly a special case... An alternative solution to the FX4 idea would be to introduce a new FX (or class of effects) for 'Instances'. For example, PRWI would invokes a single instance of the Row Probability effect that reverts to it's previous value on the following step (or the value resulting from FX called in the subsequent step).
Reply
#7
That is already in there since longer. All last FX are excluded from PROW. ;-)
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
#8
Nice, I'll try it out in FX4. Thanks!
Reply
#9
Just a quick note: Of the three places in the manual where PROW is documented, only one of them (in the CV16 section) mentions that the last FX column is excluded. If this is true for all cases then it might be worth copy/pasting that over into the other two during the next manual update.
Reply
#10
(12-23-2020, 07:24 PM)mvdirty Wrote: Just a quick note: Of the three places in the manual where PROW is documented, only one of them (in the CV16 section) mentions that the last FX column is excluded. If this is true for all cases then it might be worth copy/pasting that over into the other two during the next manual update.

Related to this comment, as a new user I'm often using ctrl+f to find keywords in the manual (note that I have already read it once from front to back). Although the manual is well organized and detailed, I often end up jumping into a section of text that is pertinent to one of the expanders, which can lead to confusion if the detail does not translate exactly to what a vanilla NerdSEQ user experiences. One has to scroll up, sometimes several pages, to see if the section is expander-specific.

I'm sure that there are conscious choices that have been made in organizing the manual that I haven't considered, but a constructive suggestion is 1) to completely remove expander details/descriptions into separate documents so that a vanilla NerdSEQ user is not overwhelmed by particulars of expanders that they do not own; or, 2) To place expander-specific details on some combination of a coloured background, different font, font colour etc... so that it's clear that bodies of text are specific to an expander.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)