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

/etc/fluidsynth.conf not loaded #1118

Closed
FredFoo opened this issue Jun 21, 2022 · 1 comment · Fixed by #1121
Closed

/etc/fluidsynth.conf not loaded #1118

FredFoo opened this issue Jun 21, 2022 · 1 comment · Fixed by #1121
Labels
Milestone

Comments

@FredFoo
Copy link

FredFoo commented Jun 21, 2022

FluidSynth version

FluidSynth executable version 2.2.7
Alpine Linux 3.16.0 on a Raspberry Pi 3

Describe the bug

If you provide $home/.fluidsynth and for instance set a default soundfont the soundfont is loaded. If you move the file to /etc/fluidsynth.conf (copied both filenames from the defaults in the source code in this repo) nothing happens. Have no idea where it fails in the code and cannot see an error message other than the default sf2 does not exist.

Expected behavior

Load and process both files just the same.

Steps to reproduce

  • create $home/.fluidsynth and add setting
  • start fluidsynth and check if setting has been applied
  • stop fluidsynth, move $home/.fluidsynth to /etc/fluidsynth.conf
  • start fluidsynth again and check for the same setting to be applied

Additional context

I assumed that in the file settings are given as if entering them on the cli, i.e. a line contains for example

set synth.default-soundfont /some/path/to/some/valid/file.sf2

In my case the purpose of the installation is only running fluidsynth. I run everything as root.

@derselbst
Copy link
Member

Thanks for the report. Fluidsynth didn't check whether the user config file actually existed. This has been fixed by the linked PR.

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

Successfully merging a pull request may close this issue.

2 participants