search

x42 / stepseq.lv2

Simple Step Sequencer
http://x42-plugins.com/x42/x42-stepseq-8x8
GNU General Public License v2.0
11 stars 7 forks source link

Feature Request: Configurable sequence length (upto max) #15

Open bjcosta opened 10 months ago

bjcosta commented 10 months ago

By the way I really appreciate all your plugins! Thanks for all the work you have put into the development of them.

Would it be possible to add support for a configurable sequence length (upto the hard coded max) that would allow support for sequences of different time signatures.?

I want to create drum beat sequences for different time signatures (say 3/4 or 5/4 or 7/8) and am using the MOD Dwarf. Right now there exist a few variants of your sequencer, that support say 8x8, 16x8 or 32x8 sequence grids however from my testing they only really support time signatures that are an integral multiple of the max sequence length as the sequence loop step is always fixed based on the step size of the sequencer.

If however there is a parameter that allows to configure how many of the steps are part of the sequence so instead of say for a 32x8 sequencer where it currently always loops at step 32, would you be willing to add support for a new parameter that allows it to loop at step N, where 1<= N <= 32 ?

The goal would be if the loop size is set to say 14 on a 32 step sequencer, then I could program in a 7/8 beat fairly easily as 14 is a multiple of 7.

Then we would be able to support custom length sequences (upto the hard coded maximum for each sequencer) allowing much easier support for different time signatures.

x42 commented 10 months ago

Please see https://github.com/x42/stepseq.lv2/issues/11#issuecomment-660354483

I suggest to rather use https://github.com/sjaehn/BSEQuencer

bjcosta commented 10 months ago

Thanks for the response. I will look more into BSEQuencer. It looks like it is also fixed from what I read on the front page but includes 24 step. It says: "Step sequencer with a selectable pattern matrix size (8x16, 16x16, 24x16, or 32x16)"

I am not sure why we would need non-fixed ports for the design I proposed above, I believe it just adds 1 new port?

I.e. Instead of a %32 for a 32 step sequencer to "reset" the sequence loop, it could be %N where N is value from the new loop steps port. There are still a fixed number of LV2 ports we are just adding a single new one for the loop steps and if there are values assigned to ports higher than this their values are just ignored.