-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show currently played step in stepseq #2145
Comments
The trick with this (just like with oscillators) is "for which voice"? |
With scene level sequencers is at least easy, but as for per voice, guess I'd say "first played"? |
I thought other plugins used last played? |
Not sure, I think it's first played, if it's last played then the pointer would jump all the freaking time.... But it also might depend on the plugin... |
I'm pushing this out of 1.7.2 since the 'which voice' problem gives us the same problem it does here with all other scope type things. |
Pignent does most recent played fwiw. |
With this kind of stuff I'd definitely go with the last played voice, as that would be the most useful information, I think. It's also how most plugins do it, I think. |
I agree, I think last played voice is the way to go as well for step-sequencers at voice level. Last voice could also be used to animate other elements in the synth down the line (OSC or LFO displays for instance, if we end up doing that someday). Unless of course we are talking about Scene modulation elements, which in this case it would be first voice of course. |
Yup. We can plumb this through for here and mseg (#3289) - carefully - in 1.9 |
Sort of a pretty cool thing to have... Here's an example from a Kontakt arpeggiator script that has the same facility:
The text was updated successfully, but these errors were encountered: