Sequencer

[Synthematophon]

I have a new idea for the sequencer:
Instead of defining individual keys for each sequencer step, wouldn't it be possible to display the current sequencer memory in one place only? On the left and right there would then be buttons for > and < (or +1, -1) as well as >> and << (or +10, -10) for 10 steps forwards and backwards, and perhaps even <<< or <<< or (+100 and -100). This would allow you to control 999 sequencer steps without taking up additional space on the UI (other like single buttons).
To save the current sequencer, just press "SET" and e.g. >. The current setting is then saved on the current step plus 1.
I know that the program is mainly intended as a plug-in for a DAW. But as a standalone (as I use it) the scenario outlined would be brilliant.

Sorry to keep bothering you with changes!

[Archie3d]

Hmm... Why do you need that many steps? Could you describe what is that exactly you are doing, perhaps there a better solution to extending the sequencer to that many steps? For example, if you need a different sequencer configuration set for your repertoire, I would rather consider some sort of presets mechanism which would allow saving and recalling state of the entire sequencer with all its steps as a single preset (so that you will have a collection of named presets).

Also currently the sequencer is linked to MIDI program change, so to keep this link the number of addressable steps should be no more than 127.

[Synthematophon]

Hi, yes, what i need is a different sequencer configuration for my repertoire. Since i need as a minimum 10 sequencer steps for one single piece of music my actual configuration allowes only 50 of them. This on the other hand allowes me only to storage for approx. five pieces the configuration. Than the sequencer is "full". Do you have better solutions?   Thanks a lot and kind regards     Gesendet: Freitag, 19. Juli 2024 um 00:12 Uhr Von: "Arthur Benilov" ***@***.***> An: "Archie3d/aeolus_plugin" ***@***.***> Cc: "Synthematophon" ***@***.***>, "Author" ***@***.***> Betreff: Re: [Archie3d/aeolus_plugin] Sequencer (Issue #32)   Hmm... Why do you need that many steps? Could you describe what is that exactly you are doing, perhaps there a better solution to extending the sequencer to that many steps? For example, if you need a different sequencer configuration set for your repertoire, I would rather consider some sort of presets mechanism which would allow saving and recalling state of the entire sequencer with all its steps as a single preset (so that you will have a collection of named presets). Also currently the sequencer is linked to MIDI program change, so to keep this link the number of addressable steps should be no more than 127. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[lewisalexander2020]

The problem with Aeolus in it’s design is that the sequencer is similar to that of organteq. The sequencer is a “general Piston” like interface and not as organists would be used to using divisional and general pistons for recall use. If this could be re-engineered to include sub sequencers (used for divisionals), then the general sequencer can recall a general map which contains the divisionals. this is the problem a lot of organists are having issues with in certain organ software environments. lew

…

On 19 Jul 2024, at 06:19, Synthematophon ***@***.***> wrote: Hi, yes, what i need is a different sequencer configuration for my repertoire. Since i need as a minimum 10 sequencer steps for one single piece of music my actual configuration allowes only 50 of them. This on the other hand allowes me only to storage for approx. five pieces the configuration. Than the sequencer is "full". Do you have better solutions? Thanks a lot and kind regards Gesendet: Freitag, 19. Juli 2024 um 00:12 Uhr Von: "Arthur Benilov" ***@***.***> An: "Archie3d/aeolus_plugin" ***@***.***> Cc: "Synthematophon" ***@***.***>, "Author" ***@***.***> Betreff: Re: [Archie3d/aeolus_plugin] Sequencer (Issue #32) Hmm... Why do you need that many steps? Could you describe what is that exactly you are doing, perhaps there a better solution to extending the sequencer to that many steps? For example, if you need a different sequencer configuration set for your repertoire, I would rather consider some sort of presets mechanism which would allow saving and recalling state of the entire sequencer with all its steps as a single preset (so that you will have a collection of named presets). Also currently the sequencer is linked to MIDI program change, so to keep this link the number of addressable steps should be no more than 127. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#32 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATQDNKPIATZT3Q6BDGNYNCDZNCOX3AVCNFSM6AAAAABLCKYXSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZYGE4DAOBWGQ>. You are receiving this because you are subscribed to this thread.

[Archie3d]

I would not do a separate sequencer per division. What I could do though is keep that current sequencer as it is now (32 steps) but on top of this add a preset mechanism. Each preset will save the entire organ state (including all 32 sequencer steps). A preset will be saved and recalled by name (chosen by user). This way you will have your repertoire as a collection of named presets (each preset is one song for example), and you should be able to switch between them easily, which will also recall the entire state of the sequencer for each recalled preset (and probably activate the 1st step by default).

Is this something that could potentially solve your issues?

[Synthematophon]

Hi, this sounds great! Thanks so much!     Gesendet: Freitag, 19. Juli 2024 um 11:13 Uhr Von: "Arthur Benilov" ***@***.***> An: "Archie3d/aeolus_plugin" ***@***.***> Cc: "Synthematophon" ***@***.***>, "Author" ***@***.***> Betreff: Re: [Archie3d/aeolus_plugin] Sequencer (Issue #32)   I would not do a separate sequencer per division. What I could do though is keep that current sequencer as it is now (32 steps) but on top of this add a preset mechanism. Each preset will save the entire organ state (including all 32 sequencer steps). A preset will be saved and recalled by name (chosen by user). This way you will have your repertoire as a collection of named presets (each preset is one song for example), and you should be able to switch between them easily, which will also recall the entire state of the sequencer for each recalled preset (and probably activate the 1st step by default). Is this something that could potentially solve your issues? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>