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

Player mode #6225

Open
mkruselj opened this issue Jun 1, 2022 · 5 comments
Open

Player mode #6225

mkruselj opened this issue Jun 1, 2022 · 5 comments
Labels
Feature Request New feature request UI Issues related to UI look&feel UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Milestone

Comments

@mkruselj
Copy link
Collaborator

mkruselj commented Jun 1, 2022

We could provide an easy and fast to use entrance into the world of Surge by means of having a switch between Player/Edit modes. The player mode would basically contain all header controls, and crucially a button to switch back to Edit mode (same button would switch to Play mode while in Edit mode, of course). Then we could provide Scene Voicing parameters (Play Mode, Polyphony, Scene Octave, Scene Pitch, Glide, Pitch Bend Range), all 8 macros, patch information in a frame rather than a popup, and a scope.

In addition, @baconpaul's suggestion was to pad out the available area with direct access parameters. These would be parameters that the sound designer chooses that are taken to the front panel of the Player mode verbatim, one to one, or optionally scaled between sound designer specified min-max range. Design of that workflow is TBD still (could do with a context menu option like "Set as direct access parameter..."), but here's a mockup that I did in Figma that shows how could this Player mode potentially look:

image

The cool thing about direct access parameters is that they can easily allow sound designers to quickly add most useful parameters (i.e. cutoff, resonance, attack, release etc.) without needing to assign macros. Plus, they would really take over the parameter physically (kind of like a remote hand), this wouldn't be an offset in the modulation path.

@mkruselj mkruselj added Feature Request New feature request Design Required We need to design a solution to this issue UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. labels Jun 1, 2022
@mkruselj mkruselj added this to the Surge XT 2.0 milestone Jun 1, 2022
@mkruselj mkruselj added the UI Issues related to UI look&feel label Jun 1, 2022
@VincyZed
Copy link
Collaborator

VincyZed commented Jun 2, 2022

+1, it's a cool idea and would be useful for many newcomers, as one of the things I hear the most from new users is that the interface is intimidating at first. Even though XT2 will partly improve on that regard, having this as an option would be a plus.

@MilesParker
Copy link

Very cool idea from peanut gallery. In general I think that these really are different personas; sound design and sound performance and as far as I've seen not very many synths address both cases well. Making them into separate modes makes a ton of sense. I do think that having the transition be natural -- ie not an entirely different expereince -- would be something to keep in mind.

@planist79
Copy link

good idea, a bit like the performance view in NI Guitar Rig.
I would appreciate the Waveform view in edit mode as well.

@mkruselj
Copy link
Collaborator Author

mkruselj commented Oct 15, 2022

Yes of course it would be there, but it would have to be exchangeable with another part of the GUI (tabbed with another section). We're full, layout-wise. Without spoiling too much:

image

@planist79
Copy link

hehe.. yeah, that's the obvious space for different tabs ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature request UI Issues related to UI look&feel UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Development

No branches or pull requests

4 participants