Step Sequencer value typeins #6516
Comments
|
I have no idea why we don’t do this, yeah. (I mean I do know why it is a bit clumsy but it’s not that bad). Let me tag it into a 1.1.n milestone |
baconpaul
added
Feature Request
|
Hi, I closed it because I thought it was in the wrong category.
I moved it to the issue:
#6518
Thanks friend!
Message ID: ***@***.***>
|
|
It would also be very nice if the individual steps could be edited with track envelopes. |
|
That would be overly complicated IMO. You can use the Deform slider to make plucks etc with the Step Sequencer modulator. Oh by the way, you can get very exact semitone values with the step sequencer if you hold Shift when dragging. This should be sufficient for tonal sequences? It's also explained in the manual 🙂 But let's keep this issue about keyboard inpot of values for Step Sequencer and not add any other unrelated discussion on top. Also, when opening issues, please be careful if what you're reporting is a bug report or a feature request. This is a feature request but it was opened as a bug report. Thanks! |
mkruselj
changed the title
|
I think the request was to have a reaper track envelope per step - which basically means each step is a param (or maps to one of a set of reserved generic params). Agree that doesn’t belong in this issue tho. |
|
@baconpaul |
|
I will vote against that. Also, you can already build your own step sequencer with values changing using LFO sliders, using the Formula modulator and writing some code 🙂 |
|
Yeah that would explode params i am thinking a bit about voice level macros ans being able to use a step as a mod target which could be interesting but is tricky the idea of adding 16122 params for the steps though seems pretty ugly especially since most would mostly do nothing |
|
Wait, isn't it 16 steps * 12 LFOs * 2 scenes = 384? And I guess triggers would be another 384 (integer valued so you can have off, FEG, AEG, FEG+AEG). Still, UGLY. |
|
Yes if you look at the plaintext of my message it us |
|
Ahahahaha that's some next level trickery. 😀 |
This opens a menu on the RMB gesture on the step sequencer and preserves the right drag with a timer; it links to documentation properly and formats the item. The only thing we need to do now is to pop upen the edit box and figure out what else we want on this menu. Neither of those are easy so checkpointing along the way. Menu pops from both mouse and accessible gestures. Addesses surge-synthesizer#6516 foo
This opens a menu on the RMB gesture on the step sequencer and preserves the right drag with a timer; it links to documentation properly and formats the item. The only thing we need to do now is to pop upen the edit box and figure out what else we want on this menu. Neither of those are easy so checkpointing along the way. Menu pops from both mouse and accessible gestures. Addesses #6516 foo
Hello,
I am learning to use Surge and I noticed that I wanted to enter the values in the step sequencer with the keyboard.
With the progress slider the values are approximate.
If I do the shortcut shift + f10 it doesn't make me edit a precise value in an editing field.
A clear and concise description of what the bug is.
The bug is that if I do the shortcut shift + f10 it goes to the LFO context menu where I can choose the type of LFO. But that contextual menu isn't exact.
The text was updated successfully, but these errors were encountered: