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

Make FlexASIO configurable #6

Closed
dechamps opened this issue Oct 15, 2018 · 3 comments
Closed

Make FlexASIO configurable #6

dechamps opened this issue Oct 15, 2018 · 3 comments
Assignees

Comments

@dechamps
Copy link
Owner

In #3 multiple users are feeling of pain of having no control of how FlexASIO behaves. We should provide at least some basic way of configuring FlexASIO. Potential configuration knobs could include:

  • Debug output (see Make it easier to get FlexASIO debug logs #5)
  • Which PortAudio backend to use (WASAPI, DirectSound, etc.), as well as relevant PortAudio options
  • Which device to use (preferably addressed in a way that survives reshuffling of devices)
  • Minimum, maximum and preferred buffer sizes

Doing this in a GUI would take a lot of time that I don't have, so for now we might have to make do with something more basic, like a configuration file or registry entries.

@josephernest
Copy link

josephernest commented Oct 15, 2018

+1

Would be super useful.

My 2 cents:

GUI: not needed for now (this is long to code...)
Registry: not very convenient for user.
Simple and enough for 99,9% of the use cases:

C:\Program Files\FlexASIO\config.ini
####################################
api=WASAPI
deviceID=14
buffer=512
samplerate=44100

@omarcostahamido
Copy link

+1
and also define the number of channels? just in case...?

This was referenced Oct 28, 2018
@dechamps dechamps self-assigned this Oct 29, 2018
dechamps added a commit that referenced this issue Nov 1, 2018
With this commit, FlexASIO will attempt to load a configuration file
named "FlexASIO.toml" in the user's profile directory. If found,
it is parsed as TOML. Currently, only one option is supported:
"backend", which can be set to one of the PortAudio host API names
(e.g. "MME") to change the PortAudio host API that FlexASIO uses.

See #6.
@dechamps
Copy link
Owner Author

dechamps commented Nov 1, 2018

FlexASIO is now configurable through a configuration file. Therefore I am closing this issue.

Only two settings are configurable for now, for choosing the backend. I will keep separate issues open for requests for specific configuration options:

@dechamps dechamps closed this as completed Nov 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants