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

Digital Sequencer (XP) expander for settings #121

Open
firolightfog opened this issue Feb 1, 2022 · 1 comment
Open

Digital Sequencer (XP) expander for settings #121

firolightfog opened this issue Feb 1, 2022 · 1 comment

Comments

@firolightfog
Copy link

Dear Bret,

This is a (very) low priority proposal for some potentially commerical/paid expander modules. The features are already available in Digital Sequencer and Digital Sequencer XP (aka DS(XP)) anyway but there may be users thinking of financially support you or would prefer some comfort in changing the parameters.

Currently the RANGE/SNAP/S&H settings are buried into the context menu. Moving the expander modules close to DS(XP) would

  • show the current settings and
  • allow instant modification of them manually or by the polyphonic inputs on the right.

Having polyphonic outputs they can also work as stand alone modules providing fixed voltages. (Similarly to BogAudio PolyCon.)

image

The currently used RANGE values ( 0 to 10, -10 to 10, 0 to 5, -5 to 5, etc.) are presented differently. The top columns could set the upper limit (i.e 1, 3, 5, 10) and depending the BI/UNI settings the lower limit could be mirrored (-1, -3 ,-5, -10) or simply 0. The result would be the same set of options found in DS(XP).It's just easier to work with this GUI.

I'm not sure that this proposal will make it to your development list but I thought to leave here a note anyway. I also wanted you to know that I appreciate the effort you put into your modules and I went bananas after having the chance for testing the alpha of Digital Sequencer XP. It's absolutely massive!

Best regards, Andras

@clone45
Copy link
Owner

clone45 commented Feb 1, 2022

I think that the idea of releasing an expander as a paid add-on is an interesting idea! I'll keep this in mind, but I have so many fun modules to consider that this might be lower on the priority list. Thanks for taking the time to offer these concepts!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants