Skip to content
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

Open
mkruselj opened this issue Jun 18, 2020 · 9 comments
Open

Show currently played step in stepseq #2145

mkruselj opened this issue Jun 18, 2020 · 9 comments
Labels
Feature Request New feature request Modulation Modulation related issues UI Issues related to UI look&feel UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.

Comments

@mkruselj
Copy link
Collaborator

mkruselj commented Jun 18, 2020

Sort of a pretty cool thing to have... Here's an example from a Kontakt arpeggiator script that has the same facility:

seqpos

@mkruselj mkruselj added Modulation Modulation related issues UI Issues related to UI look&feel UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. labels Jun 18, 2020
@mkruselj mkruselj modified the milestones: 1.7.n, 1.7 beta 1 Jun 18, 2020
@baconpaul
Copy link
Collaborator

The trick with this (just like with oscillators) is "for which voice"?

@baconpaul baconpaul modified the milestones: 1.7 beta 1, 1.7.n Jun 18, 2020
@mkruselj
Copy link
Collaborator Author

With scene level sequencers is at least easy, but as for per voice, guess I'd say "first played"?

@VincyZed
Copy link
Collaborator

I thought other plugins used last played?

@mkruselj
Copy link
Collaborator Author

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...

@mkruselj mkruselj modified the milestones: 1.7.n, 1.7.1 Jul 17, 2020
@mkruselj mkruselj modified the milestones: 1.7.1, 1.7.2 Jul 30, 2020
@baconpaul
Copy link
Collaborator

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.

@baconpaul baconpaul modified the milestones: 1.7.2, 1.7.n Sep 4, 2020
@mkruselj mkruselj modified the milestones: 1.8.n, 1.9.0 Oct 8, 2020
@mkruselj mkruselj added the Feature Request New feature request label Nov 9, 2020
@baconpaul
Copy link
Collaborator

Pignent does most recent played fwiw.

@TheNerdyMusicGuy
Copy link

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.

@VincyZed
Copy link
Collaborator

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.
Just a thought :)

@baconpaul
Copy link
Collaborator

Yup. We can plumb this through for here and mseg (#3289) - carefully - in 1.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature request Modulation Modulation related issues UI Issues related to UI look&feel UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Development

No branches or pull requests

4 participants