-
Notifications
You must be signed in to change notification settings - Fork 404
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
Dump current settings to a HTML file #6811
Comments
Oh this is a really nice idea and it’s not that hard. Let me add it to the mileston |
A couple of accessibility features 1. Add an "Accessibility" menu 2. Add a "set to recommended accessibility settings" item to it that sets the four settings which folks recommend. 3. Add a very early draft of patch->text for sharing a description of the patch for feedback on if it is is even useful to consider developing Addresses surge-synthesizer#6811
A couple of accessibility features 1. Add an "Accessibility" menu 2. Add a "set to recommended accessibility settings" item to it that sets the four settings which folks recommend. 3. Add a very early draft of patch->text for sharing a description of the patch for feedback on if it is is even useful to consider developing Addresses #6811
I was hopping for this to help patch analysis and teaching |
There’s a very initial draft in the nightly now |
Thanks very much, It's extremely helpful ! |
Hi,
Suggestions by me. An h1 at the top. H2’s that mirror the big sections in the UI, and so on. Grateful for this great start.
Thanks.
Jim H
On Jan 29, 2023, at 8:44 AM, Yan Maresz ***@***.***> wrote:
Thanks, I will test it asap !
—
Reply to this email directly, view it on GitHub <#6811 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRUZJJOZHRCQFLIFUDDDW3WUZX3DANCNFSM6AAAAAAUAVFIVY>.
You are receiving this because you authored the thread.
|
Great yes I didn't know if you wanted plain text or HTML so I went with just a massive pre block for the start :) I'll do some formatting today or tomorrow and update this issue. Thanks! |
What I really need to know is "is this basically what you thought you wanted" - if it is I will flesh out the details (like the modulation section has wrong units and so on) |
Hi Paul,
Yes, yes, yes. Thank you so very much. This is already very cool, especially for some new as I am. I really want to understand how synthesizers work and get control over this one and not just move controls and hope something good happens. I’ll be able to find patches I like and make them better according to my taste.
Wonderful tuff.
Jim
On Jan 29, 2023, at 9:03 AM, Paul ***@***.***> wrote:
What I really need to know is "is this basically what you thought you wanted" - if it is I will flesh out the details (like the modulation section has wrong units and so on)
—
Reply to this email directly, view it on GitHub <#6811 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRUZJI6OITZYBI44ITDSALWUZ2CVANCNFSM6AAAAAAUAVFIVY>.
You are receiving this because you authored the thread.
|
Great let me take this to a more complete state then and then I will update this issue and we can include it in our 1.2 release this spring |
@jhomme Upcoming nightly version of Surge will contain a better formatted HTML export of current patch. Do let us know if it's working out for you! |
Hi All,
Thank you so much for this. This is such a great learning tool.
Jim
On Feb 17, 2023, at 7:41 PM, EvilDragon ***@***.***> wrote:
@jhomme <https://github.com/jhomme> Upcoming nightly version of Surge will contain a better formatted HTML export of current patch. Do let us know if it's working out for you!
—
Reply to this email directly, view it on GitHub <#6811 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABRUZJPOJHSKO7CLES74MTLWYALDJANCNFSM6AAAAAAUAVFIVY>.
You are receiving this because you were mentioned.
|
Is your feature request related to a problem? Please describe!
It would be nice to have a quick way to review settings for patches without the need to tab and arrow through everything for keyboard users.
Describe the solution you'd like:
A button or menu choice to export the control names and settings for the current patch to an HTML file that reflects the interface groups of controls, but with headings and bulleted lists. For example, Seen 1 would be a heading 2, Osc 1 would be a heading 3, and so on. Perhaps it would even be possible for the feature to open the browser to this file.
Describe alternatives you've considered:
I considered either talking and recording the settings I have found or typing them into a file.
Additional context:
I know we could also simply save patches and give them to each other, but this feature would speed up looking through settings for people who only use keyboard who are blind, and even prevent accidental changing of parameters, although leaving the warning on about not over-writing the patch is also a good thing to keep active.
The text was updated successfully, but these errors were encountered: