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

a few issues #76

Open
joshgura opened this issue Jul 20, 2024 · 0 comments
Open

a few issues #76

joshgura opened this issue Jul 20, 2024 · 0 comments

Comments

@joshgura
Copy link

arch user, extracted .deb to try the standalone. here's some nitpicks.

the add preset dialog is a little ambiguous, not sure for example if you're adding directories or presets. turns out it's directories. somewhere it should say "add preset directory" because i was expecting to find presets in the first layer of that file browser. your way makes more sense, but there needs a little bit of tooltipping or captioning.

also, 'open' and 'save' are great features, but what are we opening and saving? i have a good idea now, looks like overall plugin state. maybe allow for an option whether to save a plugin-wide state/bank or a single preset? it's great that there's useful buttons, but when the functions aren't labeled in a descriptive way it's a little ... lonely feeling.

standalone needs an audio/midi dialog in order to route midi from any available input device, and quickly reroute geonkick to alternate audio output devices. (i noticed in qpwgraph that there are dozens of audio outputs, but routed to the wrong device and i didn't want to know why. i just rerouted the top two to change outputs...) every standalone audio software i have has such a dialog window. maybe geonkick does too, if so i apologize but i couldn't locate it on the first try.

will give a more in depth try soon.

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

1 participant